When you are connected to a remote client and type 'Command + Q' to quit the app they are in - it quit's the app :) but, it also quits the ScreenConnect App as well.
Can we change the "'File Menu → Quit command + Q" for the Screen Connect App - so that when you are controlling a remote client (who is also on Mac, though not important), there's no Command + Q option (or, change it to command + shift + Q option).
Kent.
Just started using the trial version but definitely the Command+Q & Command+H quitting & hiding the app itself is a HUGE negative. I agree with TheMacJedi comment above, muscle memory plays a huge part when you've been a long time Mac user, I'm also going on 20+ years on a mac. Not having this feature out of the gate has us at a no right now for purchasing :(
I end up using a bunch of different computers to connect with the Mac ConnectWise Client. While I've got my keyboard mapped on my main laptop, still having the default not be Command-Q would be fantastic as it eliminates this Quit issue on other machines I use. This feature would be a huge help...muscle memory is stronger than you'd believe, especially as other shortcuts do seem to work well.
Issue still remains, and my quick work around for now is to use the Screen Connect app. In there you can send keyboard commands, just select the "WIN" then Q to, and it will quit whatever app is running and not your phone.
Not a quick or easy work around, but since the "Windows" key maps cleanly to the client machine "Command" key it seems to be the easiest way right now.
Totally on board that once in a session, command keys should route to that session and not the host machine.
I've also seen now how the Mac Keyboard system preference workaround (where I manually set a preference to use Option-Command-Q as the Quit option for the ScreenConnect Client app...this breaks whenever the client is updated.
So as I moved to version 6.5 and now version 6.6, the Mac sees this as a new app and no longer uses the shortcut anymore until I reset the preference.
I've noticed other apps, for example the Parallels Client I use for RDP as well as their app server connections, has Command-Q set as the default for Quit in the menu but when you are in an open session with another host controlling another machine, Command-Q doesn't quit the app...the command is instead passed on to the remote computer correctly. So this functions as you would expect when using a remote session, regardless of what the menu says.