On 09/15/2014 04:58 AM, Ran Benita wrote:
On Mon, Sep 15, 2014 at 08:21:34AM +0200, David Herrmann wrote:
Why don't we require a keymap in xkb_compose_state_new()? Should be
easy to do and we can then track modifiers reliably.
Ok, a keysym which is a modifier in one keymap should never be a
normal key in another.. unlike keycodes. But I don't see why we need
to rely on that when we can just take a keymap.
I prefer not adding a dependency on a keymap just for this one little
thing. That would preclude people who don't use xkbcommon keymaps from
using xkbcommon-compose (not likely, but maybe), and complicate the API
slightly. For not much gain..
Also it makes it clear that the compose information is *not* part of the
keymap.
_______________________________________________
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
