We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When the mouse is connected, opening floating keyboard in the Android client causes the pointer to be misplaced.
RD version: Android RD 1.2.3 Nightly System version: Android 13 Miui 14.0.12
What have I tried
How to reproduce bugs
When you click the down arrow, the program resumes full-screen mode.
ANDROID13 to Windows10
1.2.3nightly to 1.2.3
phenomenon
No response
The text was updated successfully, but these errors were encountered:
click keyboard button(I enabled floating keyboard,keyboard sougou input)
What does this mean? What is flaoting keyboard? no misplace if no floating keyboard?
Sorry, something went wrong.
keyboard my default keyboard have this function(can see in screenshot), maybe RD cannot recognize the keyboard have already closed.
tracked by #3893
Apologies, we have no resource to reproduce your issue.
click keyboard button(I enabled floating keyboard,keyboard sougou input) What does this mean? What is flaoting keyboard? no misplace if no floating keyboard?
Additionaly using a mouse to click keyboard button will simultaneously act a click on remote device. This is not what I expected.
No branches or pull requests
Bug Description
When the mouse is connected, opening floating keyboard in the Android client causes the pointer to be misplaced.
RD version: Android RD 1.2.3 Nightly
System version: Android 13 Miui 14.0.12
What have I tried
How to Reproduce
How to reproduce bugs
Expected Behavior
When you click the down arrow, the program resumes full-screen mode.
Operating system(s) on local side and remote side
ANDROID13 to Windows10
RustDesk Version(s) on local side and remote side
1.2.3nightly to 1.2.3
Screenshots
phenomenon
Additional Context
No response
The text was updated successfully, but these errors were encountered: