Hi Sven,
to give some background -
the MIN/MAX were included because we needed to support pointing devices
like the Wii-remote; these work with absolute, though variable, ranges,
since, in case of the Wii remote, the distance to the LED-bar determines
the width of the two LEDs in the field-of-view, and therefore the amount
of area which is usable. In principle, this can be solved by the driver
too, but you might run into scaling issues there. Note that currently
only the mouse cursor of the "default" window manager will respond to
min/max and scale the input accordingly.
So, to answer your initial question, it is not a bug that linux-input
does not set these fields, but a "feature" :) but I welcome your patch
that extends this "feature".
To Azilat: you have a point about wrong min-max reported, but I would
consider that a driver issue.
Greets
Niels
Sven Neumann wrote:
Hi,
the DFBInputEvent struct has min and max fields that can optionally be
set. The documentation for DFBInputEventFlags indicates that they are
useful for handling absolute motion events. And indeed that's where I
would like to use them. Unfortunately it appears that the linux-input
driver does not set these fields. Can that be considered a bug and would
you accept a patch that fixes this? Or am I misunderstanding the purpose
of these fields?
On a related note, I found DFBInputDeviceAxisInfo in the directfb.h
header file. This looks useful, but unfortunately I did not find any
method to query the input device for this information. Did I miss
something obvious?
Sven
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
--
.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/ |
"------------------------------------------"
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev