wincompose
wincompose copied to clipboard
Please revert "Remove the “Disable” and “Restart” features."
As the title Mentions: Please revert "Remove the “Disable” and “Restart” features." 66408b27c40b7b1b3e88edaf694b9247d0f5b632 Regarding the Commit Message:
Disabling WinCompose does not make much sense; the compose feature may be disabled by selecting no compose key in the options. The user may also choose not to start WinCompose at startup.
With working with remote Desktops there are situations where i want to quickly disable one WinCompose instance with 2 clicks such that they do not conflict … And no, I do not want to mess with the compose keys (yes i have multiple) in the options …
Restarting WinCompose only makes sense when the interface language was changed, and there is already a button for this in the Options window. Having a “Restart” entry in the notification icon menu will mislead the user into thinking that whatever problem they are having can be solved by restarting WinCompose.
There are situations where having 2 WinCompse Instances using Remote Desktop (one local one remote) can confuse the keyboard indicator lights and key states … (With Caps Lock as the Compose Key) Sometimes "Restarting" WinCompose while toggling Caps Lock can fix this issue … Sometimes I even need to completely close all WinCompose instances, toggle Capslock on & off in both OS's and then restart them. But as a first attempt the "Restart" option was useful. Hm … true … I should have tried the disable as well in those sistuations … maybe only disable would be enough …
And I assume figuring out why those conflicts happen is not worth the effort … Note: I have not used the new version for long yet, so i can't tell if the indicator lights issue still happens …
So … any new info regarding this? I see 7 upvotes but no comments … I'll wait with updating for now … I would love to not have to maintain and build a forked version …
Ich would also like to see this restored. I'm using Caps Lock as Compose Key and with me, it happens from time to time for unknown reasons that Wincompose doesn't catch the keystroke correctly and the system goes into Caps Lock. Pressing it again then IS caught and I then get only capslocked compose sequences.
The way out of this used to be easy: Disable Wincompose, Press Capslock once, Enable Wincompose, done.
Now it isn't anymore so I plea for restoring it.
Cheers Philipp
If "restart" has been removed recently, I'm not upgrading from 0.9.4. Please put it back. I use it when WinCompose stops expanding compose sequences. If I knew how I got into that state, I would raise a bug for it; but I don't.
Given there there are two use cases needing "restart" (fixup remote desktop confusion; recover from bug), I think it should be restored.
I would love to check out the fixes from 0.9.7 to 0.9.11 but I'm still waiting for this to be reverted and still using 0.9.6 …
So please! Please revert it! What's the hold up? Why are you against this perfectly fine feature? At least make it possible to enable it optionally …
+1 on this. Sometimes CAPS LOCK (my "compose" key) gets "stuck" and the only way to stop writing all caps is exit WinCompose, press CAPS LOCK, start WinCompose again. I used to use "disable, press caps lock, enable" as a workaround. PLEASE put the "Disable" feature back! It was very useful!
BTW good to know that the change was in the changelog. I'm going back to the last version before this "improvement".
+1
I've figured out a workaround! I've been dealing with having to exit and restart WinCompose a few times a day for the past couple of years, but then I learned that you can use Microsoft's PowerToys to remap keyboard keys. Simply remap Caps Lock to a virtual key (“VK”), and it will no longer trigger Caps Lock, but continue to function as your Compose key:
This way, if WinCompose misses handling an input, it just does nothing. No more wonky behavior. 😌
As a side note, this may be a way to fix the issue in WinCompose – to rebind whatever key you choose as your Compose key to a virtual key in the same way that PowerToys does it, so that you don't ever accidentally trigger the key's original function.