QoL compile messages in the console...
-
Is there a way to get rid of thise:
"Skipping changed() callback during onInit for ..." messages each time I compile...?
HISE Development for hire.
www.channelrobot.com -
@Lindon
I think only in the source code. But you could put Console.clear() at the end of onInit. This will at least clear it... -
@Lindon yeah, stop calling .changed() in on init
If you need the execution, call the function directly.
-
@aaronventure said in QoL compile messages in the console...:
@Lindon yeah, stop calling .changed() in on init
If you need the execution, call the function directly.
Yes but what if you're calling .changed() in a CB?
If the component is set to 'saveInPreset', the CB will be executed and .changed() will be called... -
@Matt_SF is that also where it triggers? I'll take my jokes elsewhere.
-
@aaronventure No worries :) But yes, and it lead me to wonder if we should avoid calling this function when possible. Of course it depends on what you want to do in your project (on Init or not), but it's convenient to use...
I remember this was discussed on the forum some time ago but I couldn't fint it. -
@Matt_SF I remember asking for a Engine.isInitialized() method that would return true after init is done and all saved components have been called, but no response from @Christoph-Hart
This would easily allow for gating in these scenarios, and others. Changed() has use beyond just calling the function, it sets focus to the component and sets the last touched envelope for the DAW,
-
This would easily allow for gating in these scenarios, and others. Changed() has use beyond just calling the function, it sets focus to the component and sets the last touched envelope for the DAW,
Ah thanks, I didn't know that
-
@aaronventure said in QoL compile messages in the console...:
@Lindon yeah, stop calling .changed() in on init
If you need the execution, call the function directly.
Ha ha..., but as you may have gathered - Im not calling changed() in init, its in the CB for widgets... so if Im using the console.print() as some sort of debugging aid - I get a truck load of these messages that completely obscure what Im trying to read - making Console.print() nearly useless for debugging...
-
@Lindon yeah I think in this case Engine.isInitialized or similar would solve multiple issues including this one.
-
@aaronventure said in QoL compile messages in the console...:
@Matt_SF I remember asking for a Engine.isInitialized() method that would return true after init is done and all saved components have been called, but no response from @Christoph-Hart
This would easily allow for gating in these scenarios, and others. Changed() has use beyond just calling the function, it sets focus to the component and sets the last touched envelope for the DAW,
yeah - -but this doesnt work...If Im trying to debug something in the widget on init, then I have no way of gating so it appears and the messages dont, same for Olie's solution to Console.clear() - now I cant debug init phase events...
Nope - I would like it to go back to the old way where this message wasnt shown - Im more than happy to have some pre-processor compile time definition for this SHOW_INIT_SKIP_MESSAGES = 0
@Christoph-Hart ???
