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
Keyboard transfer is not exact #5255
Comments
@attikov Hi, thanks for your feedback. Did you use "Map mode" or "Translate mode beta" I've tried Win -> Win. The "Map mode" just sends the key codes to the remote side. The host knows whether the key is the left ctrl or the right ctrl, and the other keys. |
Good question, didn't even know that such thing exists, it was in legacy mode, map mode works like a charm. |
No idea why some users are still in legacy mode after upgrading to 1.2. @fufesou have a check. |
What I have seen in my upgrade from 1.1.9 to 1.2.2 (in some Windows 10 PCs) is that the default keyboard remaining in legacy mode until I exclusively change it ! |
@mikekgr If you do the following steps, the keyboard mode will be set to the "Legacy mode".
Then the configuration file will set the keyboard method to the "Legacy mode".
The way to deal with the problem is that if the version of the remote side is less than 1.2.0, the do not save the keyboard mode But I'm not sure it's worth dealing with this special case. |
No need to spend time on this. |
pls add separate keyboard in rustdesk for android phone to android phone remote control . typing is not good . or tell me a solution for phone to phone typing smoothly |
No need |
Bug Description
The host does not know it the pressed key was the left ctrl or the right ctrl, (most likey other keys too) losing functionality in some apps.
How to Reproduce
.
Expected Behavior
.
Operating system(s) on local side and remote side
W10 -> W10
RustDesk Version(s) on local side and remote side
1.2.0+
Screenshots
.
Additional Context
.
The text was updated successfully, but these errors were encountered: