-
-
Notifications
You must be signed in to change notification settings - Fork 7.2k
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
Alt + NumPad codes are not sent to the remote OS (Windows) #6697
Comments
Hi @fufesou thanks for the quick reaction!
On the other hand on the local Windows 10 (not the remote one) the behavior is not affected by the "NumLock" state. No matter if it is |
Sorry, I don't quite understand what you mean. Is the above result what you want? Still have any issues? The "Translate mode" just send letters to the controlled side. |
Is the above result what you want? Still have any issues? Yes, the issue does still exist. The expectation is that the Alt Codes are working independently from the "NumLock" state. At least this is how it works on the local Win10. On the local Win10 if I press and hold Alt, press Num4, press Num1 then On the remote Win10 however it is different. The behavior is exactly as expected if "NumLock" is
|
Thanks. I've read the code. The two modes has the same effect in Alt Codes case. We've added some workaround(extra keystrokes on the controlled side) for the led state. The Alt Codes are not available then. But it is somewhat difficult to satisfy all cases. We'll find a better way to simulate these cases in the future. |
Sure thing. This is not the easiest thing to align for all the cases. The case of this issue seems quite a niche one. |
Bug Description
Alt Codes seems not to be working https://en.wikipedia.org/wiki/Alt_code
How to Reproduce
Expected Behavior
)
symbol will appear in the remote systemOperating system(s) on local side and remote side
Windows 10 -> Windows 10
RustDesk Version(s) on local side and remote side
1.2.3 -> 1.2.3
Screenshots
Not applicable
Additional Context
No response
The text was updated successfully, but these errors were encountered: