On 23 October 2013 12:12, Andrew Chadwick <[email protected]> wrote: > People have reported success with the -wip branch, so I've pushed it > to master for wider testing. I'm going with option 2 for filling in > the missing pressure and tilt info; let me know if linear > interpolation isn't smooth enough.
Thanks for working on this problem. One thing though, if we do not prod/harass/help the GTK+ guys - I don't think the bug will go away and we will need to keep our workarounds. > On 21 October 2013 18:28, Andrew Chadwick <[email protected]> wrote: >> Branch: https://gitorious.org/mypaint/achadwick-mypaint/commits/eventhack-wip >> - this is the workaround for the GDK bug that artificially limits >> input events to no more than the frame rate. It's coming along quite >> nicely, I think, thanks to some really useful testing from various >> keen people (thanks!) >> >> One problem remains: pressure (and tilt) fidelity is lacking. See the >> attachment: that's a circular brush, but the staircase effect is very >> evident. We have two options for dealing with this: >> >> 1. Duplicate GDK's processing of raw Xi2 axis/valuator info in the >> guts of the filter; or >> >> 2. Linearly interpolate using the translated pressure and tilt info >> available to us during processing of the events GDK lets registered >> event handlers see. >> >> I'm in favour of option 2 myself, since it's less work, and less state >> to maintain in what is a fragile, platform-specific, and hopefully >> temporary hack. Would it be sufficient? >> >> -- >> Andrew Chadwick > > > > -- > Andrew Chadwick > > _______________________________________________ > Mypaint-discuss mailing list > [email protected] > https://mail.gna.org/listinfo/mypaint-discuss -- Jon Nordby - www.jonnor.com _______________________________________________ Mypaint-discuss mailing list [email protected] https://mail.gna.org/listinfo/mypaint-discuss
