search

mRemoteNG / mRemoteNG

mRemoteNG is the next generation of mRemote, open source, tabbed, multi-protocol, remote connections manager.
https://mRemoteNG.org/
GNU General Public License v2.0
8.95k stars 1.42k forks source link

RDP not getting focus on Alt-Tab #1535

Open rubaboo opened 5 years ago

rubaboo commented 5 years ago

Expected Behavior

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.

Current Behavior

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.

Possible Solution

Steps to Reproduce (for bugs)

  1. Start mRemoteNG, start an RDP session, open Notepad inside RDP session, type a few characters.
  2. On your Windows machine, switch to any other app.
  3. Alt-Tab back to mRemoteNG.
  4. Try typing something - the keyboard input does nothing.

Context

Your Environment

anotherdave commented 5 years ago

Confirmed with mRemoteNG 1.77.1.27654, Windows 10 1709 x64.

rubaboo commented 5 years ago

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.

bluikko commented 5 years ago

These focus issues are the most infuriating aspect of trying to work with mRemoteNG.

Should be the highest priority work IMHO.

GeriZ commented 4 years ago

Please fix this problem ASAP!

Thank you

majkinetor commented 4 years ago

Should be priority

TakiGuan commented 4 years ago

Have the same issue.

siwee commented 4 years ago

Should be priority

yrebrac commented 3 years ago

+1 should be priority. this a real workflow interrupter.

majkinetor commented 3 years ago

FYI, PRemoteM doesn't have that problem.

bluikko commented 3 years ago

FYI, PRemoteM doesn't have that problem.

PRemoteM is not really a replacement for mRemoteNG, unfortunately - at least at this time. Way too basic.

majkinetor commented 3 years ago

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)

tolot27 commented 2 years ago

Still present in 2022.06.13-v1.77.3-nb

davidpierson commented 1 week ago

Not able to reproduce this bug in my older version, 1.76.20.24615 In case that helps to narrow down the issue.