Roast/Cup Profile: value keep changing to max or min if double clicked

[bigl00z3]

Expected Behavior

in Roast/Cup Profile.. When double clicking on a value for the spider chart, the value should move by 2 steps

Actual Behavior

When double clicking, the values keeps changing until reaching either the lowest (0) or the highest (10) value (takes around 14 seconds to move from 0 to 10).

Steps to Reproduce the Problem

1. Open Roast file
2. Open menu Roast/Cup Profile..
3. Double click on the arrow to increase a value.

Specifications

• Artisan Version: tested in Artisan 1.6.99 and Artisan 2.0.0
• Artisan Build (number in brackets shown in the about box): tested in (d8854fe) and (a0a1fac)
• Platform (Mac/Windows/Linux + OS version): OS X
• Connected devices or roasting machine: Currently none. I'm just editing a roast after cupping it.

Please attach your current Artisan settings file (as exported via menu Help >> Save Setings as *.aset) file.
Please attach any relevant Artisan *.alog profiles.

Artisan files.zip

Note that you need either add a .txt extension or zip the files before uploading. Otherwise you will receive a "Not a supported file type" error on uploading.

[MAKOMO]

Hm. Dave and myself cannot duplicate this on our RPis (nor on Windows and Mac OS X). This might be caused either by the outdated Qt 5.7 GUI lib bundled with Artisan for Raspian Stretch or we just do not understand clearly the issue.

[bigl00z3]

It’s actually on the Mac that I have the issue (where I edit the cup profile, generally the next day when I’m tasting it) not on the Raspberry I did a quick video of it: https://bigloose.com/n/index.php/s/KswfACsKppK4k75 Nicolas

…

On 5 Jul 2019, at 09:32, Marko Luther ***@***.***> wrote: Hm. Dave and myself cannot duplicate this on our RPis (nor on Windows and Mac OS X). This might be caused either by the outdated Qt 5.7 GUI lib bundled with Artisan for Raspian Stretch or we just do not understand clearly the issue. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#360?email_source=notifications&email_token=ACDZVCWSD5HQLYWM3UXJSXLP532I3A5CNFSM4HWJA7HKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZIY5VA#issuecomment-508661460>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACDZVCQDXS7TODJZWCD7LWLP532I3ANCNFSM4HWJA7HA>.

[MAKOMO]

Wow! Now I can duplicate the issue at least on one of my machines. It does not happen always, but it happens. I have also an idea why. Very strange chain of events... I'll try to fix this with a work around.

[MAKOMO]

Commit 53c1500 somehow improves on the situation caused by slow redraw of the canvas but does not fully resolve it. A tripple click still leads to this behaviour.

Related:
https://stackoverflow.com/questions/41568990/how-do-i-prevent-double-valuechanged-events-when-i-press-the-arrows-in-a-qspinbo