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.
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.
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 :(