Sliderpack triggers onControl callback when it shouldn't

[Lindon]

Confirmed - happening here on windows too. Seems to be a bug.

[Christoph Hart]

If you comment out that line:

HISE/hi_scripting/scripting/api/ScriptingApiContent.cpp at 4c64ee1944780c039c7566bf085f51ecaa45a931 · christophhart/HISE

The open source framework for sample based instruments - HISE/hi_scripting/scripting/api/ScriptingApiContent.cpp at 4c64ee1944780c039c7566bf085f51ecaa45a931 · christophhart/HISE

GitHub (github.com)

it will not fire the callback anymore unless you explicitly call changed() on the slider pack, but then we're back to square one I guess.

[d.healey]

@Christoph-Hart said in Sliderpack triggers onControl callback when it shouldn't:

it will not fire the callback anymore unless you explicitly call changed() on the slider pack, but then we're back to square one I guess.

Yes that won't solve it.

The other controls work like this.

If you move the control with the mouse it triggers its callback.
If you set the value of the control from another script processor it triggers the callback.
If you set the value from within the same script processor it does not trigger the callback but the control's value visually changes.

[d.healey]

@Christoph-Hart Think I might have found the fix

HISE/hi_scripting/scripting/api/ScriptingApiContent.cpp at 4c64ee1944780c039c7566bf085f51ecaa45a931 · christophhart/HISE

The open source framework for sample based instruments - HISE/hi_scripting/scripting/api/ScriptingApiContent.cpp at 4c64ee1944780c039c7566bf085f51ecaa45a931 · christophhart/HISE

GitHub (github.com)

Change sendNotification to dontSendNotification

Prevent sliderpack callback triggering when setting value via script. by davidhealey · Pull Request #258 · christophhart/HISE

GitHub (github.com)

[d.healey]

@d-healey Bugger, it no longer moves the sliders on the sliderpack.

[d.healey]

@d-healey Hmmm I think this is beyond my skill level...

[Christoph Hart]

Well, this is more complicated than I thought it was, the implementation should follow a discussion about what we're trying to achieve here. So if I understand it correctly, the control callback shall not be executed when you call setValueAtIndex() to be consistent with the other UI elements (so if you want it to be executed, call changed() afterwards), but if you change a slider on the user interface it should fire.

What happens if you exchange the entire data set for the slider pack? Should it fire a callback then or does it still rely on calling changed()?

[d.healey]

@Christoph-Hart I think it's always best to have more control so I say you should have to call changed.

[d.healey]

I've opened a github issue for this one.

[ulrik]

@d-healey confirmed on MacOS as well

[clevername27]

@d-healey said in Sliderpack triggers onControl callback when it shouldn't:

github issue

I seem to be running into the same situation - when I call .setAllValues, the callback triggers. I noticed that the GitHub issue is closed — are my expectations simply incorrect?

A related question – my sliderpack callback is being triggered, and when I query the value for the slider index, the value is -1. What does that mean?

Thanks.

[d.healey]

@clevername27 said in Sliderpack triggers onControl callback when it shouldn't:

when I call .setAllValues, the callback triggers.

Here's a workaround

for (i = 0; i < mySliderPack.getNumSliders(); i++)
    mySliderPack.setSliderAtIndex(i, value);

@clevername27 said in Sliderpack triggers onControl callback when it shouldn't:

when I query the value for the slider index, the value is -1. What does that mean?

I guess that must be something unique to the setAllValues function triggering the callback

[clevername27]

@d-healey Ah, right - that makes sense, because it's everything. Thanks, man!!!!

[d.healey]

@clevername27 Look what I just found

[clevername27]

@d-healey Brill!