Window Focus Issue - Dialogs Get Pushed Behind

https://pluginguru.net/unify/manual/doku.php?id=settings

• The default setting for “always on top” works well with many DAWs, but for some (e.g. Cubase), you may prefer to turn this off, especially if you find that certain pop-up message windows are “stuck” behind Unify's windows.

I've also encountered this with just a Unify inside Unify situation in Cubase. The child Unify refused to go behind anything - even a totally different app window unrelated to Cubase. I have to admit I hate to give up the "always on top" in Cubase though - I find things become almost unworkable for me without it.

@nico

I'm open to suggestions for better ways to handle this. At the moment I can't think of any.

@getdunne @robert-p @praisetracks

I've just tested a workaround, that seems to do the trick for me when a Cubase dialog box gets hidden behind a plugin child window:

In one of my external midi controllers, I've configured a button to trigger Command > Windows > Close All Plugin Windows (see attached image).

This works even in the case of an open dialog box buried behind other windows and therefore not getting keyboard input.

The saving grace is that Cubase will receive and execute commands triggered via midi even while it doesn't receive keyboard or mouse input.

So when a Cubase dialog box is buried behind one or more plugin child windows and Cubase is effectively frozen to keyboard and mouse input, triggering the command "Close all Plugin Windows" via midi closes all the plugin windows and thus uncovers the dialog box.

Tested on Cubase 11 on Windows 10 (1909 fully patched).

p.s. This method of also comes in handy in many situations of plugins having control of key commands, but you want to send a command to Cubase while keeping the plugin window in the foreground.

Posted by: @nico

@getdunne @robert-p @praisetracks

I've just tested a workaround, that seems to do the trick for me when a Cubase dialog box gets hidden behind a plugin child window:

In one of my external midi controllers, I've configured a button to trigger Command > Windows > Close All Plugin Windows (see attached image).

This works even in the case of an open dialog box buried behind other windows and therefore not getting keyboard input.

The saving grace is that Cubase will receive and execute commands triggered via midi even while it doesn't receive keyboard or mouse input.

So when a Cubase dialog box is buried behind one or more plugin child windows and Cubase is effectively frozen to keyboard and mouse input, triggering the command "Close all Plugin Windows" via midi closes all the plugin windows and thus uncovers the dialog box.

Tested on Cubase 11 on Windows 10 (1909 fully patched).

p.s. This method of also comes in handy in many situations of plugins having control of key commands, but you want to send a command to Cubase while keeping the plugin window in the foreground.

 

 Cubase-CloseAllWindows.jpg

Thanks @nico,

I am wanting to do more in Cubase but still have a hard time getting away from Cakewalk since using it for so many years. I will have to take a look to see if there is a similar command or key binding that might accomplish this.

Stay tuned. 🤓