#68 Raw keycodes support

[Darren Salt]

My raw keycodes support, ported from 0.7.0. One of its
features is that it supports the compose key in X ;-)

This works a little differently to Philip's patch,
which will need to be reverted before this can be applied.

[Darren Salt]

[Philip Kendall]

Logged In: YES
user_id=29214

Is there anything fundamentally wrong with my patch for
doing this, or is it just a matter of porting your code for
Xlib/framebuffer/etc to "my" scheme?

If the latter, can you update your patch to work with the
new scheme please? :-)

[Fredrick Meunier]

Logged In: YES
user_id=11017

The thing I don't like about your scheme Phil, is that we still end up
translating back to INPUT_KEY_* symbols, which have poor coverage of
international characters (and symbols). Rather than increase the number of
INPUT_KEY_ symbols I'd prefer if we used INPUT_KEY_* for symbols
available on the Spectrum keyboard, and used the SDL-style UNICODE
value (on keypress-only) for widget UI dialog entry.

Darren: SDL doesn't have cross-platform ability to get symbol equivalent
for raw symbols, so I think I'd have to include a full keysym-to-fuse-
keysym map for all supported platforms. Have I missed something?

[Gergely Szasz]

Logged In: YES
user_id=57243

Yes :-) native is not so *native* :-) ...

I think, the best solution is to get an interpreted (host)
keyboard event from the UI (so we do not bother about
keyboard layouts etc...)
The UNICODE is good for glyphs, but not so good for other
keys, e.g.: Left, Right, F12, keypad plus etc... so, we need
an UNICODE value plus an INPUT_KEY_* like thing for this ...