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: http://www.opendesignstudio.org/inkscape/Inkscape_spin_button_error.mp4

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 listInkscape-devel@...1901...://lists.sourceforge.net/lists/listinfo/inkscape-devel

The bug affected me also. I use Fedora 20 with GNOME.

On 10 March 2016 at 16:54, C R <cajhne@...400...> wrote:

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: http://www.opendesignstudio.org/inkscape/Inkscape_spin_button_error.mp4

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 listInkscape-devel@...1901...://lists.sourceforge.net/lists/listinfo/inkscape-devel

---

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

Am 10.03.2016 um 18:18 schrieb Martin Owens:

...

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.

The patches don't seem to fix anything in the core, just the parts in the extensions. Although they might be a good guide to a fix (I'm not sure).

Are these patches waiting on review Eduard?

Martin,

Sorry, I think you misunderstood: The focus of those bugs is different and I only noticed an issue with the spin button while working on them. The patch attached to those bugs is not really meant to fix the spin button issue* but to address the other issues mentioned in those bugs. I didn't commit the patch yet to give people a chance to test it first (If you want you can review it, Nicolas already mentioned that it works on XP, tough, so it's not necessary).

The issue I noticed might be related to the issue discussed here but not even that is verified yet... It just seemed familiar, so I though I'd mention it.

Regards, Eduard

* I delayed the CPU-intensive part with a timeout to give the main thread some time to process the mouse click which makes the spin button issue less likely but a real fix is still required.

Just found the bug for this issue by chance: https://bugs.launchpad.net/inkscape/+bug/1164150

Am 10.03.2016 um 19:21 schrieb C R:

Maybe it's worth looking over the shoulder of one of the other major FOSS projects to see how they handled it. I'm not getting the same behaviour in any of them. GIMP seems particularly robust, and will take all sorts of spin button abuse. It will even gracefully handle flicking the mousewheel while click-holding the opposite spin button. :)

-C

On Thu, Mar 10, 2016 at 5:38 PM, Eduard Braun <Eduard.Braun2@...173... mailto:Eduard.Braun2@...173...> wrote:

Am 10.03.2016 um 18:18 schrieb Martin Owens:

        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.

    The patches don't seem to fix anything in the core, just the
    parts in
    the extensions. Although they might be a good guide to a fix
    (I'm not
    sure).

    Are these patches waiting on review Eduard?

    Martin,


Sorry, I think you misunderstood: The focus of those bugs is
different and I only noticed an issue with the spin button while
working on them. The patch attached to those bugs is not really
meant to fix the spin button issue* but to address the other
issues mentioned in those bugs. I didn't commit the patch yet to
give people a chance to test it first (If you want you can review
it, Nicolas already mentioned that it works on XP, tough, so it's
not necessary).

The issue I noticed might be related to the issue discussed here
but not even that is verified yet... It just seemed familiar, so I
though I'd mention it.

Regards,
Eduard


* I delayed the CPU-intensive part with a timeout to give the main
thread some time to process the mouse click which makes the spin
button issue less likely but a real fix is still required.

---

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

On Thu, 2016-03-10 at 20:28 +0000, C R wrote:

Looks like current user work arounds include selecting a different tool, or punching the keyboard over and over until it stops. :D

`punch the computer` is an indication that it is a critical bug imo.

It's probably the signal issue explained earlier in the thread, we would expect to see it more with renderings which take more time. So adding blur and a lot of objects with lots of nodes should slow it down.

Does this appear to be true?

Martin,