Interface: Skipping changed() callback during onInit
-
@d-healey Can you explain how I can deactivate the warning?
-
-
@d-healey Thank you for your response - why can't it be called during init? I'm using it to initialize buttons to specific values (and execute the associated callback from when that happens.). (I'm not calling it from init, but I'm calling functions that do, so maybe that's the same thing,)
-
@clevername27 said in Interface: Skipping changed() callback during onInit:
why can't it be called during init
Dem's da rulez
-
@d-healey Ah, I see. (Wouldn't a message to that effect be better?) So, would that apply to directly calling the callback during init, too?
-
@clevername27 yeah, if you search you'll find my post about it and Christoph's explanation
-
@d-healey Thank you - do you mean this thread?
-
-
@d-healey Thanks for taking the time to dig that up - I hit up Chris about calling the callbacks explicitly. Cheers.
-
@clevername27 Yeah just call the inline function that you're passing to the setCallback() method.
The only thing that changed() would do on top of it is it would set the control as "last touched" if it's set as a plugin parameter. I'm unsure whether that also puts it "in focus" in HISE.
-
@aaronventure Thank you - did not know that!
-