Follow-up Comment #6, bug #20822 (project mypaint):
Some input for this problem: Apparently there were changes in xinput handling
on Gtk 3.8, so this is going to hit everyone else soon. Many people have 3.6
still and thus the problem won't manifest itself.
>From #gtk channel on gimpnet:
15:37 < alex> tigert: In Gtk 3.8 consecutive motion events are tossed away and
you only get the last one for the frame you're drawing.
15:38 < alex> tigert: If you want the whole history for the frame there is
some
per-device history
15:38 < alex> gdk_device_get_history() i think
15:38 < tigert> alex: I wonder why this is not a problem for everyone then?
15:39 < alex> Yeah, its a bit extreme for you
15:39 < alex> i mean, if its repainting at 60hz you should get better than
that
15:40 < tigert> this is fedora 19
15:40 <@Company> 3.8
15:40 < tigert> ah right
15:40 <@Company> F19 already qualifies :)
15:40 <@Company> i think ubuntu has 3.6 or so
15:41 <@Company> and 3.8 started with the more aggressive compression
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?20822>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Mypaint-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/mypaint-bugs
