Bug: Wincompose blocks chained dead keys in keyboard layouts that use them

[jmcwilliams403]

When using a layout such as Bépo, Cherokee Phonetic, or some other custom layout that makes use of chained dead key sequences, WinCompose will block any dead key sequence beyond anything reachable within the two keystrokes of normal non-chained dead keys, even when I'm not currently in a compose sequence. This basically means I have to choose whether I want to use only WinCompose or only my custom keyboard layout to access a specific Unicode character with multiple diacritics on it.

By the way, layouts with chained dead keys are indeed possible on Windows and have always been possible. They just have to be compiled differently than normal, but the end-result is a native Windows layout DLL. Both of the example layouts I mentioned are present in Windows 11 or are in official insider builds.