Follow-up Comment #9, bug #19948 (project mypaint):
Actually, I looked at the test-input devices dialogue: Something quite
interesting is going on.
It doesn't flicker between wacom-driver and core pointer as expected.
Instead, what happens is that it shows 'core pointer' and when I press down
with the stylus, it lags(no messages shown) and then suddenly the hapering
stroke appears along with some data on the screen. It was still set to the
core-pointer. Testing it again, I did get it to show the wacom driver in the
screen, but the result was the same. (When I lift my stylus away from the
screen after setting the stroke, it will revert to the core pointer when the
stroke is processed.)
I checked it the 'working copy' I had, and there the device was the
wacom-driver. To make sure everything was the same, I set it to the core
pointer. I had some trouble getting it to the core pointer, (mypaint didn't
want to recognise my button clicks) and when I got it to work, I noticed that
I had similarly trouble getting the wacom driver to be recognised again. When
it finally did respond to the clicks, it also drew all the lines I had been
making with the wacom pen in hopes of getting it to be recognised, in a
hapered style like the lines I get in the newer version.
I don't know if these events are related or that it's two seperate bugs with
the device-changing.
If required, I can attempt to make a screen-capture video of the motions and
the test-device output.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?19948>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Mypaint-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/mypaint-bugs
