- This topic has 4 replies, 2 voices, and was last updated 3 years, 5 months ago by
.
-
Posts
-
Setup: NX client (6.12.3) in Windows 10 connects to NX server on macOS (same version). On the Windows PC I have two monitors and one of them is ‘dedicated’ to the NX client running on full screen.
The issue is as follows: When I copy some text on any Windows app and then switch the focus to the NX client window and try to paste it using the LWin + V shortcut (since the Windows key is mapped by NX to the Comand key on macOS), often the result is that:
1) nothing gets pasted and the Windows 10 clipboard popup is shown instead, and
2) the Windows key seems to remain stuck in a pressed state, so that if I press any other key like E or P on any context the corresponding shortcut like Win + E or Win + P is triggered. The only way to fix this is to switch focus to some Windows app again and and hit the LWin key once or more until the start menu pops up.
After some trial and error I figured that this issue only occurs if I press LWin + V immediately after bringing the NX client app into focus. If I wait just 1 second then the text is pasted correctly and the Win key does not get stuck.
Also, and probably obviously, the issue only occurs if the option to grab the keyboard input is enabled in NX settings, but disabling it is not a valid workaround unfortunately (cause that breaks other things).
Hopefully the description is clear enough, otherwise let me know, maybe I can also make a short video or something.
Hello, this seems like a known problem:
Some key combinations are not captured on Windows when the grabbing of the keyboard is enabled
Hmm that link says that some key combinations are never captured and that is not really the case here, since Win + C or Win + V work fine while over the NX client window. I can copy and paste stuff on the mac. The problem only arises when switching focus between any other Windows app and the NX client and then rapidly issuing a key combination that includes the Win key. If a small delay is introduced before issuing the key combo then it works. Is that clearer now?
OK, I was able to replicate on my own. It looks a different problem, so a new TR is appropriate: The Win key gets stuck when used in shortcuts
This topic was marked as solved, you can't post.