Yeah, I know that this generally isn't good for performance, but this isn't a high-performance plugin. :) For the usual audio plugins that Teragon develops, it's not a problem that the actual control values end up getting applied during the first process() call, but with ExtraNotes the behavior is actually quite weird. Basically, the buttons don't do anything (seemingly), but then when you start to playback and get process() calls, they all jump into action when the dispatcher is ready to execute them.
Actually, in the future, I would say that any plugin that has "tabs" probably needs to handle this. Perhaps there should be a tab control for this in TeragonGuiComponents.
Yeah, I know that this generally isn't good for performance, but this isn't a high-performance plugin. :) For the usual audio plugins that Teragon develops, it's not a problem that the actual control values end up getting applied during the first process() call, but with ExtraNotes the behavior is actually quite weird. Basically, the buttons don't do anything (seemingly), but then when you start to playback and get process() calls, they all jump into action when the dispatcher is ready to execute them.
Actually, in the future, I would say that any plugin that has "tabs" probably needs to handle this. Perhaps there should be a tab control for this in TeragonGuiComponents.