Update of bug #19896 (project mypaint):
Operating System: Ubuntu => Ubuntu 12.04
_______________________________________________________
Follow-up Comment #7:
There seems to be a consensus on the GIMP bug for it
(https://bugzilla.gnome.org/show_bug.cgi?id=661872) that this is something to
gdk_device_get_history(). MyPaint does not use this function anywhere. It's
possible that there's two bugs here.
Whatever it is, this is fundamentally not a MyPaint bug. A workaround might be
nice, but we have to support silly things like using the edge of the screen as
a ruler (with the mouse, admittedly).
Please can you tell me *what verson of MyPaint* you are using? If git, please
give the first 8 or so characters of the commit hash.
Please *also confirm* that it acts like http://youtu.be/9rDf6_FwKEY
Whichever version you're using, I'd like to make a filter for this if it can
be done sensibly. By sensibly I mean, I need to know whether the (x=0) or
(y=0) or (x=y=0) motion events are happening in isolation, and/or if there's
anything else on the event we can use to distinguish glitch from non-glitch.
So... as yet another request, sorry...! Please can you *temporarily insert the
following block of debugging code* into the start of motion_notify_cb() in
gui/tileddrawwidget.py and run MyPaint from the terminal? I want to see a
trace of the events we receive which highlights one or several of these
glitches: it's best done as an attachment or as a pastebin. Please don't go
near the screen edges when you scribble - draw _only_ in the centre of your
screen :)
### DEBUGGING CODE FOR MAGNESUS:
/usr/share/mypaint/gui/tileddrawwidget.py
# Look for "def motion_notify_cb" and paste this immediately after
that line.
# Be careful with indents. Mypaint uses space only
if event.state & gdk.BUTTON1_MASK:
print "DEBUG: ex=%r ey=%r p=%r xt=%r yt=%r ax=%r ay=%r" % (
event.x_root, event.y_root,
event.get_axis(gdk.AXIS_PRESSURE),
event.get_axis(gdk.AXIS_XTILT),
event.get_axis(gdk.AXIS_YTILT),
event.get_axis(gdk.AXIS_X), event.get_axis(gdk.AXIS_Y),
)
### DEBUGGING CODE ENDS
If you use a packaged MyPaint, this is installed in
/usr/share/mypaint/gui/tileddrawwidget.py and you will need to edit it with
the following command
$ sudo gedit /usr/share/mypaint/gui/tileddrawwidget.py
If you can paste the "DEBUG:" lines of the generated nonsense (I'm expecting
ey=0.0 or ex=0.0 when it happens), that would be most useful. If necessary,
capture the output to a logfile:
$ mypaint | tee $HOME/Desktop/mypaint_bug19896_`date +%Y%m%d%H%M%S`.log
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?19896>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Mypaint-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/mypaint-bugs
