-
-
Notifications
You must be signed in to change notification settings - Fork 40.9k
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
Plans to solve the RDP issue? #18931
Comments
The plan is to accept PRs from people who have the issue and can provide a solution. |
Probably related to https://docs.qmk.fm/#/mod_tap?id=caveats / https://docs.qmk.fm/#/one_shot_keys relevant section:
I never had any issues with RDP sessions probably because I don't use mod-tap or one shot keys. |
Simple key-to-key remap seems to work reliably for me in full-screen RDP, but not macros (missing modifier strokes). Now I know that user mode key remap does not work reliably with RDP due to reasons discussed here. Wonder whether this applies to QMK macros. That is, while key-to-key remap works at firmware level, but macros work at user mode and hence the issue? |
@LukasKubicek Is this only for shifted/modded keycodes? If so, does adding a Line 386 in 89fdafc
|
A minor tweak to fixed issues with auto shift and with sym layer not always registering the correct key for me. I use RDC to connect to locally running Linux VM. The commit is here: |
This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs. |
This issue has been automatically closed because it has not had activity in the last 30 days. If this issue is still valid, re-open the issue and let us know. |
Hello good people. I have to work in RDP sessions almost every day. Mostly Windows 10 to remote Windows 10.
When in RDP, my keyboard (Moonlander configured with Oryx) occasionally produces wrong characters, it seems to be nondeterministic, but it is enough to make it unusable for work. On the local machine everything works correctly.
It seems that it is known issue for many years:
#1037
But there are only some non ideal workarounds.
Is there some plan to fix this RDP issue? Did someone maybe try to contact developers of RDP and consult with them? Or is all hope lost? In today's world of remote work I imagine this must be a troubling issue for many people with QMK kyeboards.
The text was updated successfully, but these errors were encountered: