Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RDP not getting focus on Alt-Tab #1535

Open
rubaboo opened this issue Aug 6, 2019 · 13 comments
Open

RDP not getting focus on Alt-Tab #1535

rubaboo opened this issue Aug 6, 2019 · 13 comments
Labels
1.77.2 Version 1.77.2 Bug Something isn't working as expected

Comments

@rubaboo
Copy link

rubaboo commented Aug 6, 2019

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

  • Version used: 1.77.0.41307
  • Operating System and version (e.g. Windows 10 1709 x64): Windows 7 SP1
@anotherdave
Copy link

anotherdave commented Sep 9, 2019

Confirmed with mRemoteNG 1.77.1.27654, Windows 10 1709 x64.

@rubaboo
Copy link
Author

rubaboo commented Oct 2, 2019

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
Copy link

bluikko commented Nov 26, 2019

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

Should be the highest priority work IMHO.

@GeriZ
Copy link

GeriZ commented Mar 21, 2020

Please fix this problem ASAP!

Thank you

@majkinetor
Copy link

Should be priority

@TakiGuan
Copy link

Have the same issue.

@siwee
Copy link

siwee commented Sep 16, 2020

Should be priority

@yrebrac
Copy link

yrebrac commented Jan 27, 2021

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

@majkinetor
Copy link

FYI, PRemoteM doesn't have that problem.

@bluikko
Copy link

bluikko commented Jan 27, 2021

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
Copy link

majkinetor commented Jan 27, 2021

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
Copy link

tolot27 commented Jul 1, 2022

Still present in 2022.06.13-v1.77.3-nb

@davidpierson
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.77.2 Version 1.77.2 Bug Something isn't working as expected
Projects
None yet
Development

No branches or pull requests