-
-
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
Key sequence doesn't switch languages in the local machine #4362
Comments
@fufesou may need handle ctrl shift specially as tv. no rush to work on it, because we did not get complaint from others, let collect more feedbacks from others. we do not have to follow tv/anydesk behaviors some times. |
tracked by #4367 |
please put priority on this, because every a need for non-English language person |
Mac (UK keyboard) to Windows (UK keyboard) does not map correctly either. \ on local keyboard maps to # to remote machine. I have to locally press ~ to get remote \ |
|
@RichardBurt65 Hi, thanks for your feedback.
Did use the "Map mode"? Which input source did you use on macOS?
You can try
|
Bug Description
Both local and remote machine have EN-RU keyboard; Ctrl-Shift is used to switch between languages. When remote window (Rustdesk) is active, Ctrl-Shift switches language bar EN->RU-EN in the remote but not in the local machine. In result, you always typing in latin (EN).
How to Reproduce
Connect to remote machine, try pressing language switching key sequence and notice that language bar (in the taskbar) is switching in the remote but not in the local machine.
Open notepad on the remote and try to type in cyrillic -- it won't work unless you switch (with mouse, for example) local language bar to cyrillic.
Expected Behavior
Key sequence is switching language in both local and remote machines. That's how it works in Teamviewer and Anydesk
Operating system(s) on local side and remote side
Windows 10 -> Windows 7
RustDesk Version(s) on local side and remote side
1.2.0 both local and remote
Screenshots
Additional Context
No response
The text was updated successfully, but these errors were encountered: