On 22 June 2013 03:55, Bill Spitzak wrote:
> Daniel Stone wrote:
>> If you can think of a way to simplify this, please send concrete
>> patches to GTK+, Qt and co., and when they've changed, we can later
>> simplify xkbcommon. But unfortunately in the last however many years,
>> no-one's managed
Daniel Stone wrote:
What I suspect is the minimum resulting xkb description where this client
still works is going to be a LOT smaller, and will be much closer to the
proposed gamepad evdev mapping.
That doesn't fly for shortcuts, especially when you take into
consideration things like Ctrl+Sh
Hi,
On 22 June 2013 01:54, Bill Spitzak wrote:
> Daniel Stone wrote:
>> If the only input API you need is the input method API, then you don't
>> need other input APIs.
>>
>> wl_keyboard is pretty much for people who need to support non-textual
>> keyboard input, e.g. hotkeys/media keys and short
Daniel Stone wrote:
On 21 June 2013 23:02, Bill Spitzak wrote:
If clients use the input method for all the text input, exactly how much is
left of xkb keyboards? It looks like all this compiling is so that dead keys
and all the shift states work for producing different characters. That can
al
On 21 June 2013 23:02, Bill Spitzak wrote:
> If clients use the input method for all the text input, exactly how much is
> left of xkb keyboards? It looks like all this compiling is so that dead keys
> and all the shift states work for producing different characters. That can
> all be done by the
If clients use the input method for all the text input, exactly how much
is left of xkb keyboards? It looks like all this compiling is so that
dead keys and all the shift states work for producing different
characters. That can all be done by the input method and thus only the
input method has
From: Matt Roper
In preparation for upcoming changes, we want to make sure that apps
written with the toy toolkit continue to operate properly if no XKB
keymap is received. If there's no XKB keymap, then we shouldn't
try to figure out keyboard modifier states (since we probably don't
even have e
From: Matt Roper
In preparation for upcoming changes, we want to make sure that apps
written with the toy toolkit continue to operate properly if no XKB
keymap is received. If there's no XKB keymap, then we shouldn't
try to figure out keyboard modifier states (since we probably don't
even have e
