Hello Ping,

thank you for your answers.

> > Especially when moving the mouse near to the border or when lifting one
> > side of the mouse a little bit the cursor is freezing. Then moving or 
> > clicking the mouse has no effect until I fully lift the mouse from the 
> > tablet and put it back on it.
>
> Please try
> "xsetwacom set $dev CursorProx 256 $n, where dev is you device identifier
> and n is an non-negative integer.  Try n from 0, and somewhere bigger and
> smaller than 8 to see which one works better for you.  8 is the current
> value for n.

I tried and got:

    X Error: 8 BadMatch (invalid parameter attributes)
    Error (22): WacomConfigSetRawParam: failed
    Set: Failed to set cursor value for 'CursorProx'

After twiddling a little bit with the values I found the accepted range for 
both parameters distance and hysteresis is 0 to 63.

I have no more freezing with the following command:

    ./xsetwacom set cursor CursorProx 63 63

But I have to lift the mouse quite far from the tablet to relocate it without 
cursor movement. So I understand the need for the CursorProx feature. If only 
the proximity detection after putting the mouse back on the tablet would be 
more reliable.

> Refer to 
> http://linuxwacom.sourceforge.net/index.php/howto/xsetwacom for details on
> how to use xsetwacom. I will take a look into the code to figure out a
> better way to support this function soon.

Is the distance to the tablet a value directly reported from the hardware or 
is it calculated from other values? I mean, is it really necessary to force 
the cursor out of proximity? Maybe only not reporting movement events if the 
cursor has a specific distance would work better.

> Suppress applies to all devices.  It reduces number of points/events sent
> to XInput. Thus, maybe able to reduce jitter to some extent. But, it
> reduces the accuracy of your data. Threshold only applies tp prssure.
> Please refer to http://linuxwacom.sourceforge.net/index.php/howto/inputdev
> for detail.

Sorry, I confused these two settings.

But I have to confirm Oliver's observation: When moving the cursor slowly it's 
a bit jerky. Is relative mode implemented in hardware or is it calculated 
from the reported absolute coordinates in software. Maybe a smooth relative 
movement can be calculated as the delta to the absolute coordinate of the 
point where the mouse came in proximity of the tablet.

If I ever have some more time I would like to help. :-)

With best regards,
Stefan

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Reply via email to