fufesou

## Current code Current master branch, Korean input is ok for me. Could you please give me some details about how to reproduce this issue? Thx iOS version? https://github.com/user-attachments/assets/617b4d78-0a8d-4c77-8352-c3f4ccf48660 ##...

There may be some problems with my input settings. I'll test more. https://github.com/user-attachments/assets/771742a6-c0ec-4303-8f5c-1561a0533542 > breaks some composition input It's my mistake. I found that after I switched to Korean input...

I still cannot input `하`. I've tried a new device(iPhone SE and iPhone 15 Plus), clearing the cache, restarting the simulator and macOS.  > I have tested it before...

> Also, please confirm whether you can input Korean normally after removed this logic. No. I have tested the system message app and safari, the letters cannot be composed once...

> You can test with testflight. Ok

@ClisMakise @mahdiyar11007 How about right click (long press) ? I've printed the mouse message on the controlled side. Only one `down` and one `up` events are received on click operation....

@DarkLordGMS @ThomasCr Sorry for inconvenience. Please try the latest nightly build. We've put a fix. https://github.com/rustdesk/rustdesk/releases/tag/nightly > there's a bunch of 1's on the keyboard These 1 are in a...

> Would it be possible to have a toggle added in the settings to be able to enable or disable that? Sorry, no. I'll put a fix today.

@DarkLordGMS Thanks for your test and feedback. > The 1's are still visible when I open the keyboard I can reproduce it with SwiftKey, both `1.3.1` and the latest nightly...

Thanks! Is 1.3.1 work fine for you? Did you use the Sumsung input method in your video? > Is it possible to revert to v1.3.1 without losing my saved connections...