Christopher Cope writes:
> Can someone provide some follow up on this? There is a problem with
> the current code. The way I fixed it allows the end user to set the
> mode with xinput. That seems preferable to having to apply a patch to
> wine if the mouse in use doesn't work.
I'd suggest to fil
Can someone provide some follow up on this? There is a problem with the current
code. The way I fixed it allows the end user to set the mode with xinput. That
seems preferable to having to apply a patch to wine if the mouse in use doesn't
work.
Christopher Cope wrote:
>The way I set it was to
The way I set it was to enable with the original labels or absolute label with
relative mode. My mouse has absolute labels, but with relative mode set. My
mouse won't work correctly without this patch. Relative and absolute mode can
be set relatively easily.
Alexandre Julliard wrote:
>Christo
Christopher Cope writes:
> @@ -286,8 +286,10 @@ static void enable_xinput2(void)
> class->number, class->min, class->max, class->resolution,
> class->mode,
> XGetAtomName( data->display, class->label ));
> if (class->label == x11drv_atom( Rel_
"Cope, Christopher Edward" wrote:
> @@ -1638,16 +1636,14 @@ static void X11DRV_RawMotion( XGenericEventCookie
> *xev )
> if (XIMaskIsSet( event->valuators.mask, class->number ))
> {
> double val = *values++;
> -if (class->label == x11drv
