-
Notifications
You must be signed in to change notification settings - Fork 84
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
Combinations not working #312
Comments
Thanks for the report. You can help with debugging by opening the debug window (systray icon → help) and taking a screenshot after entering a failing combination. I suppose you are using a French AZERTY keyboard? |
Italian QWERTY; I'll send the screenshot as soon as I have the issue again. |
…nese IME. This addresses issue #312.
Thanks! I was able to reproduce and fix the problem. The fix will be in the next release. |
Hi! I think the issue is fixed in WinCompose 0.9.5, but I’d be happy to hear from you if that’s actually the case. |
Thanks; I'll try to install and test it as soon as possible, I'll keep you updated. |
Hi, I did some test with both the new and old IME, and it does seem to work; thanks. |
I'm using WinCompose 0.9.4 in Windows 10.0.18362.535, and since when I updated to this version sometimes it doesn't accept some combination; examples of not accepted combinations are:
<Multi_key> <è> <è> : "È"
<Multi_key> <equal> <Right> <Right> : "⇒"
<Multi_key> <equal> <Right> <Up> : "⇗"
<Multi_key> <question> <question> : "[backtick]"
last one should give a backtick; instead of those, I get:
è
[moves right]
[moves up and right]
?
I'm not sure how to replicate this: it's not from system start, or at least not always, it seems it happens after a while the PC is on; if I restart WinCompose, it works fine again.
Edit: It just happened again, nothing changed since I restarted it; it seems after a while it has issue, and restarting it solves them for a bit. I literally used WinCompose to do a backtick, wrote four character, tried again to do a backtick, and I got
?
instead.The text was updated successfully, but these errors were encountered: