@d-healey said in All Control Callbacks Get Triggered On Init?:
Another solution is to put a button at the end of your component tree and put your code in its callback, this will be called after all the other components. Or instead of adding a dummy button, use the actual last component in your tree if suitable.
That's a good one. Kontakt has on persistence_changed which executes after on init, meaning that on init has to pass first, which does not happen if the track is muted in the DAW or the VEPro instance isn't connected. So my instruments there always load up with the "loading" image which says exactly that, and all the UI controls get their visibility set only in persistence_changed.
But if in HISE the controls get executed after the init callback passes, then simply adding a dummy control at the end is not a big deal. Much like the PersistentData thing, or the colorPalette, or my dummy DAW automation controls. or my dummy switcheroo volume sliders. Hey, we need a dummy component list!