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

Keyboard transfer is not exact #5255

Closed
attikov opened this issue Aug 5, 2023 · 10 comments
Closed

Keyboard transfer is not exact #5255

attikov opened this issue Aug 5, 2023 · 10 comments
Labels
bug Something isn't working

Comments

@attikov
Copy link

attikov commented Aug 5, 2023

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

.

@attikov attikov added the bug Something isn't working label Aug 5, 2023
@rustdesk
Copy link
Owner

rustdesk commented Aug 5, 2023

@fufesou

@fufesou
Copy link
Collaborator

fufesou commented Aug 5, 2023

@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.

V3NFRYOAGFNP4NHC6$R5PTA

@attikov
Copy link
Author

attikov commented Aug 5, 2023

Good question, didn't even know that such thing exists, it was in legacy mode, map mode works like a charm.
I'll try to remember that this setting exist. Is there a documentation on that? What is doing what?

@fufesou
Copy link
Collaborator

fufesou commented Aug 5, 2023

https://github.com/fufesou/rustdesk/wiki/Keyboard-mode----Translate-Mode

4IQ2JD2X$4(R3$D0HT)~P

@rustdesk rustdesk closed this as completed Aug 6, 2023
@rustdesk
Copy link
Owner

rustdesk commented Aug 6, 2023

No idea why some users are still in legacy mode after upgrading to 1.2. @fufesou have a check.

@mikekgr
Copy link

mikekgr commented Aug 6, 2023

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 !

@dignow
Copy link
Contributor

dignow commented Aug 6, 2023

@mikekgr If you do the following steps, the keyboard mode will be set to the "Legacy mode".

  1. Upgrade local version to 1.2.2,while keeps the remote version to 1.1.9.
  2. Establish a connection to the remote side.

Then the configuration file will set the keyboard method to the "Legacy mode".

  1. After upgrading the remote side to 1.2.2, the keyboard mode is still 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
to the configuration file.

But I'm not sure it's worth dealing with this special case.

@rustdesk
Copy link
Owner

rustdesk commented Aug 6, 2023

But I'm not sure it's worth dealing with this special case.

No need to spend time on this.

@rgurfriend
Copy link

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

@miladhatami1393
Copy link

No need

@rustdesk rustdesk unpinned this issue May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

7 participants