As per the latest changes with clearing of the LookAndFeel (on switch to newer one or destruction of the PluginEditor), I am setting it to nullptr at the root of the components tree (currently that is the PluginEditor).
The issue I am having is within the calls to
lookAndFeelChanged () method (triggered by the
setLookAndFeel (nullptr) call) of child components that would be searching for a custom colour (defined in the now gone custom LookAndFeel).
Any guidelines on how to deal with this issue?
Basically, if I have custom colours (that aren’t defined in the default LookAndFeel), I would hit this assert in
findColour () every time I reset the LookAndFeel. And I may need to reset it multiple times, during the lifetime of a PluginEditor, because that’s how I switch to different visual “themes”.