[bug] .changed() not working
-
@d-healey it works if you call it from another function (like a button)
-
@iamlamprey Yeah I tested that too
-
@d-healey confirmed in develop branch
b41b58f12ecca927c1fe8f12610dd993fa00db28 -
Could this possibly be affecting my automation issue?
isMetaParameter + automation help
I could use a hand with parameter automation on exported plug-ins. I've created a simple example that contains 3 panels and a knob. Clicking the panels chang...
Forum (forum.hise.audio)
-
@Dan-Korneff I don't think so because that works in HISE, but the problem here doesn't.
-
@d-healey The problem is that calling
changed()
in the onInit callback doesn't fire the callback. I took a look at the code and it explicitely cancels the execution:HISE/hi_scripting/scripting/api/ScriptingApiContent.cpp at d3f364f5c2832770a8bade634607e0f70b55f9df 路 christophhart/HISE
The open source framework for sample based instruments - HISE/hi_scripting/scripting/api/ScriptingApiContent.cpp at d3f364f5c2832770a8bade634607e0f70b55f9df 路 christophhart/HISE
GitHub (github.com)
I don't remember exactly why I did this (passive aggressive note to past me: a comment would have been helpful...), but I'm sure there are a few edge case problems that arise from this (eg. it will fire a bit later anyways because of the user preset load).
I've added a warning message that tells you that this function will not do anything, so now you're at least not left in the dark with that problem.
-
@Christoph-Hart Thank you for your response. What if I call the callback explicitly?
-
@clevername27 said in [bug] .changed() not working:
@Christoph-Hart Thank you for your response. What if I call the callback explicitly?
I just use a one-off timer...
-
@clevername27 if you mean calling the function directly then it will work (like any other function as long as its defined before the call), it鈥榮 just the connection value change -> callback that is disabled during onInit.
-
@Christoph-Hart Thank you,