https://bugs.kde.org/show_bug.cgi?id=477748
David REVOY <i...@davidrevoy.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |i...@davidrevoy.com
--- Comment #5 from David REVOY <i...@davidrevoy.com> ---
Hi,
As for the use case, consider a device like a Ms Surface Pro 3, or an old
Tablet PC. Sometimes these types of devices have a fairly high resolution
digitiser, but a slow way of processing all the events of the tablet (could be
the input connection in the device, or a slow CPU, not sure). In any case, the
result is a visible lag, which can be seen in the distance between the moving
cursor and the actual pen tip. This sometimes happens when all the events are
sent to the screen for rendering, and it feels like a "hardware event
bottleneck". Some paint programs can also be slow to render brush strokes.
In this case, event suppression (trimming or filtering/removing duplicates)
may be useful to improve performance.
Personally, I always keep them to a minimum with xsetwacom because I have good
hardware on my main workstation and I prefer to get the most coordinate/event
out of my digitizers:
xsetwacom --set "$tabletstylus" Suppress 0 # data pt.s filtered, default is 2,
0-100 (old 4)
xsetwacom --set "$tabletstylus" RawSample 1 # data pt.s trimmed, default is 4,
1-20 (old 1)
I only increased these values a little on my old laptop or my Surface Pro 3.
The gain is not dramatic as far as I can tell; and if you set a higher value
than the default of X11 (4 Rawsample and 2 Suppress), I remember that you
quickly damage the quality of the brush stroke (visible segment between
coordinates when drawing fast large spirals on the canvas).
--
You are receiving this mail because:
You are watching all bug changes.
