Hello guys !
We talked about that a few times, for example there : BubbleMessageComponent not deleted (using last tip)
There are a few things that are wrong with the BubbleMessageComponent class. First, in the JuceDemo example project, with the Widgets / Button demo, if we try to close the app while a BubbleMessageComponent is still visible, an assertion is unleashed.
Then, I have very often issues in some personal plug-in projects using that class, when the PluginEditor is closed with a BubbleMessageComponent still visible, or fading out at the same moment. I have either the BubbleMessageComponent which stays visible even if the plug-in has been removed, or a crash. I have not found a good solution yet, that’s why I’m posting this message…
Would it be possible to have an example of good practices to use this class, or maybe some corrections if needed ? See the destructor of the class maybe… And of course, it would be great to solve the issues in the JuceDemo project.
Thanks in advance !