Keystrokes not detected when trying to assign compose key(s)

[vhalkola]

When trying to assign compose key(s) in the options section, no keystrokes are detected. I'm running Windows 10 version 2004 and have a Sun Microsystems Type 6 USB keyboard with Finnish/Swedish layout and would like to assign the Compose key (producing the same keycode as Menu on Windows keyboards) to function as compose. However, when the "Please press a key to use as your compose key" box shows, pressing any key except enter or space bar (which both press the "Cancel" button) has no effect whatsoever.

Moreover, checking the "Alternate compose key is always Compose" does not assign compose function to the Compose key, but as physical compose keys on keyboard are relatively rare, I guess this is not the intended behaviour. Other keypress detection applications I have tested have no issues detecting keystrokes apart from Sleep, Volume Up, Volume Down, Mute, Help, Stop, Again, Props, Undo, Front, Copy, Open, Paste, Find and Cut.

[samhocevar]

Thanks for reporting this. I hope this can be easily fixed: can you please open the debug window (Notification icon → Help → Debug Window) and post a screenshot of what it prints when you press that compose key?

The “Alternate compose key is always Compose” option is not related to your issue; its is for people who have several keys configured as a compose key, e.g. Alt and Caps Lock, and determines whether the sequence AltCaps Lock should be interpreted as ComposeCompose or as ComposeCaps Lock.

[vhalkola]

It appears that the keystroke gets detected, but for some reason nothing happens regardless. Screenshot attached. /Ville

…

________________________________________ Från: Sam Hocevar <notifications@github.com> Skickat: den 20 november 2020 11:02:29 Till: samhocevar/wincompose Kopia: vhalkola; Author Ämne: Re: [samhocevar/wincompose] Keystrokes not detected when trying to assign compose key(s) (#367) Thanks for reporting this. I hope this can be easily fixed: can you please open the debug window (Notification icon → Help → Debug Window) and post a screenshot of what it prints when you press that compose key? The “Alternate compose key is always Compose” option is not related to your issue; its is for people who have several keys configured as a compose key, e.g. Alt and Caps Lock, and determines whether the sequence AltCaps Lock should be interpreted as ComposeCompose or as ComposeCaps Lock. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#367 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADVKR5JNTEFNRZGUYC2B4Q3SQYWCLANCNFSM4T4OWIZQ>.

[samhocevar]

I’m afraid no screenshot was attached. Maybe it is an issue with the mail → github gateway and you’ll have to post it using the web interface instead. Sorry for the inconvenience.

[dcnjbwiebe]

Same issue on Windows 10, version 20H2 with Lenovo keyboard. I am attaching a screenshot of the debug window when attempting to assign the right Alt key as the compose key. Top two (highlighted) lines were the result. Other lines in the debug window were from the process of taking the screenshot.

[vhalkola]

It appears the attachments get stripped off if you answer directly by email. Here's the screenshot, looks pretty much the same as the one from dcnjbwiebe:

[samhocevar]

I have tried to understand what may be caused this, and I realised key captures would not work when WinCompose is disabled, i.e. when the icon has a red mark across it:

Could you tell me whether this is the case for you, or if I should try to find another possible cause for the problem?

[samhocevar]

Hi! Could you all who are affected by this bug please test WinCompose 0.9.5 to see if it improves the situation? Thanks in advance.

[dcnjbwiebe]

Uninstalled 0.9.4 and installed 0.9.5 and everything is working. Thanks!

…

-- Jonathan Wiebe Cogitor, judicor: ergo sum. <>< ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Friday, November 27, 2020 9:57 AM, Sam Hocevar ***@***.***> wrote: Hi! Could you all who are affected by this bug please test [WinCompose 0.9.5](https://github.com/samhocevar/wincompose/releases/tag/v0.9.5) to see if it improves the situation? Thanks in advance. — You are receiving this because you commented. Reply to this email directly, [view it on GitHub](#367 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AR4BGGTFJYVCOKLEBRLMKUDSR7SCHANCNFSM4T4OWIZQ).

[vhalkola]

Testing 0.9.6. The keystroke gets detected now, but no Compose behaviour is assigned to the chosen key (Compose on Sun Type 6 keyboard, detected as Menu by Windows [edit: applies to any other key as well]). Moreover, although I choose not to retain original key behaviour, the key still behaves like a Menu key where applicable, e.g. trying to write "ø" (Compose - o - /) in the URL field in Firefox just brings up the associated menu and results in "o/" in PowerShell.

Another interesting feature is that upon startup two instances of WinCompose are launched.

[vhalkola]

0.9.5 seems to lack the aforementioned bugs, though. It's unable to detect Mute, Volume Up, Volume Down, Help, Stop, Again, Props, Undo, Front, Copy, Open, Paste, Find and Cut, but I assume this results from relying on the Windows keyboard driver that outright ignores keycodes from these keys.

[samhocevar]

Hi, and sorry for not providing an update here. I think the problem in 0.9.6 was mostly caused by the two instances running concurrently, which was fixed in WinCompose 0.9.8. If you still use the software and the problem has not disappeared please let me know!