Hi,
> >> It looks like doing it right for relative is easy:
> >
> > But what is the point when this isn't used anyway?
>
> In what sense it is not used?
Old code is obviously broken for the relative case.
Seems to be used by hw/arm/spitz.c, which probably
emulates a absolute pointing device.
Il 03/02/2014 10:42, Gerd Hoffmann ha scritto:
Hi,
+switch (graphic_rotate) {
+case 90:
+if (evt->abs->axis == INPUT_AXIS_X) {
+evt->abs->axis = INPUT_AXIS_Y;
+}
+if (evt->abs->axis == INPUT_AXIS_Y) {
Need else here, same for "case 270".
Why?
Hi,
> > +switch (graphic_rotate) {
> > +case 90:
> > +if (evt->abs->axis == INPUT_AXIS_X) {
> > +evt->abs->axis = INPUT_AXIS_Y;
> > +}
> > +if (evt->abs->axis == INPUT_AXIS_Y) {
>
> Need else here, same for "case 270".
Why?
> > +evt->abs
Il 28/01/2014 10:57, Gerd Hoffmann ha scritto:
Transform absolute mouse events according to graphic_rotate.
Legacy input code does it for both absolute and relative events,
but the logic is broken for relative coordinates, so this is
most likely not used anyway.
Signed-off-by: Gerd Hoffmann
--
Transform absolute mouse events according to graphic_rotate.
Legacy input code does it for both absolute and relative events,
but the logic is broken for relative coordinates, so this is
most likely not used anyway.
Signed-off-by: Gerd Hoffmann
---
ui/input.c | 33 ++
Transform absolute mouse events according to graphic_rotate.
Legacy input code does it for both absolute and relative events,
but the logic is broken for relative coordinates, so this is
most likely not used anyway.
Signed-off-by: Gerd Hoffmann
---
ui/input.c | 33 ++
