I expect the focus to be in the active app inside RDP session, so that after switching to mRemoteNG with Alt-Tab I can use keyboard without having to mouse click inside RDP first.
When switching to mRemoteNG using Alt-Tab, the input focus is not in RDP session, nor in any other of the fields or controls of mRemoteNG interface. Hitting Tab multiple times does nothing.
Confirmed with mRemoteNG 1.77.1.27654, Windows 10 1709 x64.
Actually, it's not only Alt-Tab. If I click inside the RDP session frame (that is partially visible behind another app), the mRemoteNG window comes up to the front, but the focus is not inside RDP. I have to click the second time. Very counter-intuitive and getting really aggravating. If you could prioritize this, it would be great.
These focus issues are the most infuriating aspect of trying to work with mRemoteNG.
Should be the highest priority work IMHO.
Please fix this problem ASAP!
Thank you
Should be priority
Have the same issue.
Should be priority
+1 should be priority. this a real workflow interrupter.
FYI, PRemoteM doesn't have that problem.
FYI, PRemoteM doesn't have that problem.
PRemoteM is not really a replacement for mRemoteNG, unfortunately - at least at this time. Way too basic.
Way too basic.
What is exactly that you are missing apart from some protocols ? Feature wise, I think it doesn't miss anything. (better to answer on its own repo so not to spam this issues with irrelevant stuff)
Most helpful comment
These focus issues are the most infuriating aspect of trying to work with mRemoteNG.
Should be the highest priority work IMHO.