I'm running Ubuntu 15.10 with Gnome Shell, but I can reproduce the bug in Unity as well.

Since the main thread is blocked, the callback that is triggered when releasing the mouse button is delayed. When it finally executes the spin button "thinks" that the mouse button was pressed for much longer than it actually was and therefore changes the value even further (because spin buttons are supposed to do this if you hold the button).

Sounds probable. I'd love a fix in trunk. I've been avoiding clicking the buttons but sometimes I forget.
It's a bit awkward when showing people how to use inkscape. :)
I kinda have to hide the problem &/or recite a disclaimer. 

If someone could save me the trouble, that would be absolutely wicked. :)

-C
 


Am 10.03.2016 um 16:27 schrieb C R:
Has anyone else noticed there's something pretty seriously wrong with the spin buttons in Inkscape? 

If you click more than a few times on either the up or down arrow the value goes nuts, and keeps going nuts until you switch to a different tool.

Here's a short video capture of the issue:

Any ideas?

This bug doesn't seem to affect any other programs (I tried Scribus, and GIMP, and both do not feature this bug).

I'm running Inkscape 0.91+devel r (Mar  8 2016).

This bug is also present in 0.91 stable.

-C


------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140


_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel