Better handling of non-keyboard keys in sequences

[Nixill]

As a user of a standard en-us keyboard, seeing non-keyboard keys in the glyph sequences gets annoying cause it does me absolutely no good. But I don't want them taken out, because users of keyboards that aren't en-us would have an easier time with them.

Instead I propose the following options for how WinCompose should treat sequences that use keys that aren't part of the user's current keyboard layout.

All of the examples below would produce the character ↛, which has the default sequence of ♦ / → (and no pure ascii sequence).

1. Allow nested composing (if ♦♦emoji sequences are turned off, or with Ctrl♦ to initiate inner sequence). For example, ♦ / ♦ - >. Clicking the non-keyboard key in the sequence would then show the sequences to make it.
2. Allow, and show, alt codes. For example, ♦ / alt(26).
3. Display only the unicode sequence. For example, ♦ u 2 1 9 B.
4. Hide the sequence entirely.

[Nixill]

Also, if this becomes a user-configurable option, then there should also be a "do nothing" option.

[samhocevar]

Hello, I’d like to apologise for not answering sooner. All your suggestions made sense but none was entirely satisfying. I agree that taking out the sequences should be avoided, though.

Now that I have given it some more thought, what I plan to do is add a warning mark on sequences and keys that cannot be typed with the current keyboard configuration. A tooltip will give more information about the problem.