From: spitzak
This allows X applications to be run on wayland without having to
delete conf files needed to run the legacy X server on the same machine.
This is the only method I have found that will allow the built-in
default conf file to be used while an /etc/X11/xorg.conf.d directory
exists.
On Sat, Apr 20, 2013 at 4:53 PM, Ran Benita wrote:
> (This is easy to miss without some [xkbcommon] in the subject!)
>
> On Tue, Apr 09, 2013 at 09:57:29PM -0400, matthias.cla...@gmail.com wrote:
>> From: Matthias Clasen
>>
>> Users of libxkbcommon need these values to iterate over all
>> keycode
On Sun, Apr 21, 2013 at 8:14 AM, Martin Minarik
wrote:
> I disagree with inventing a new protocol. The joypad
> devices are generally already supported in the linux
> kernel[1].
They are, but from a developer point of view it's not pretty; it's
been a while since the last time I messed with
Hi all,
I'll be travelling next week and don't expect to have a lot of time to
review and apply patches. Ander and Rob Bradford will keep an eye on
the list and I'll be back April 29th.
Kristian
___
wayland-devel mailing list
wayland-devel@lists.freede
As a hobby game dev, what follows is a description of my dream input system.
Apart from the existing input protocol...
I would expect Wayland to support a protocol that can enumerate input
devices and discover capabilities regardless of type. What follows that
wayland has a sensible set of i/o pr
Hello Todd
> That's a complete controller state in 32 bytes. The
analog values
> in actual hardware are usually actually returned as
unsigned byte
> values, but from a protocol point of view converting
each stick axis
> to the range [-1.0f .. 1.0f] and the triggers to [0.0f
.. 1.0f] is
> saner.
