If I open the editor on the wrong virtual desktop, I either need to close it, switch to the right desktop, and relaunch it, or use task manager to drag the existing instance to the correct virtual desktop. If I just switch to another virtual desktop while the editor is open on another virtual desktop, WIN + Shift + O doesn't launch the editor on the new desktop, possibly because the workspace editor is single instance. If I use PTRun to launch the editor while it's open on another virtual desktop, I get the same behavior.
I was expecting the editor keyboard shortcut to launch the editor on the current virtual desktop, whether that's launching another instance or moving the existing instance.
It would be even easier to launch workspaces on specific virtual desktops if the workspaces themselves could be configured to launch on a specific virtual desktop, then I wouldn't need to worry as much about what virtual desktop contains the workspace editor.
If I open the editor on the wrong virtual desktop, I either need to close it, switch to the right desktop, and relaunch it, or use task manager to drag the existing instance to the correct virtual desktop. If I just switch to another virtual desktop while the editor is open on another virtual desktop, WIN + Shift + O doesn't launch the editor on the new desktop, possibly because the workspace editor is single instance. If I use PTRun to launch the editor while it's open on another virtual desktop, I get the same behavior.
I was expecting the editor keyboard shortcut to launch the editor on the current virtual desktop, whether that's launching another instance or moving the existing instance.
It would be even easier to launch workspaces on specific virtual desktops if the workspaces themselves could be configured to launch on a specific virtual desktop, then I wouldn't need to worry as much about what virtual desktop contains the workspace editor.