Button.setValue(1) oninit not reflected in UI

[Dan Korneff]

@CyberGen What about calling the change after a delay?

Content.callAfterDelay(500, function(){
     Knob1.setValue(1);
     Knob1.changed();
}, this);

[CyberGen]

@Dan-Korneff & @ulrik So, enabling "Save in Preset" works, but I didn’t want to rely on that for this, primarily because patches can be edited and that could mess with the initial setup that I'm looking for.

I wasn’t aware of the callAfterDelay() function. That did the trick—thank you for the tip!

I have to say, though, it’s still a convoluted way to achieve this, especially considering how many buttons I’d need to set it up for. I’m still wondering why simply setting the default value doesn’t work with script buttons. It seems to work fine with other components.

[CyberGen]

@ulrik So I just realized, what you are saying here is that I should turn off the save in preset mode. That makes the setValue work. But not the default value.

[d.healey]

@CyberGen The default value of buttons seems to not be useful. If a control is set to saveInPreset then anything you set in on init will be overwritten immediately after by the stored value.

[VirtualVirgin]

@d-healey I can confirm that the default value for buttons is not working here either.

[d.healey]

@VirtualVirgin said in Button.setValue(1) oninit not reflected in UI:

is not working

What do you expect it to do?

[VirtualVirgin]

@d-healey If I set the default value to "1" and recompile I would expect the button to be on.
Is that not what it is meant to do?

[d.healey]

@VirtualVirgin said in Button.setValue(1) oninit not reflected in UI:

Is that not what it is meant to do?

It doesn't do that for any other control. With slider the default value is the value it will reset to when you double click it.

[VirtualVirgin]

@d-healey Right, I see. What is it meant for then?

[d.healey]

@d-healey said in Button.setValue(1) oninit not reflected in UI:

The default value of buttons seems to not be useful.