mirror/JUCE
1
0
Fork 0
mirror of https://github.com/juce-framework/JUCE.git synced 2026-01-10 23:44:24 +00:00
Code Activity

Added more comments to a LookAndFeel assertion that seems to be confusing people

Browse source
This commit is contained in:
jules 2017-12-15 09:15:15 +00:00
parent 3b130b10fe
commit 25d3a7f89d
1 changed files with 12 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

16
modules/juce_gui_basics/lookandfeel/juce_LookAndFeel.cpp
View file

@ -50,10 +50,18 @@ LookAndFeel::LookAndFeel()
LookAndFeel::~LookAndFeel()
{
/* This assertion is triggered if you try to delete a LookAndFeel object while it's
- still being used as the default LookAndFeel; or
- is set as a Component's current lookandfeel; or
- pointed to by a WeakReference somewhere else in the code
/* This assertion is triggered if you try to delete a LookAndFeel object while something
is still using it!
Reasons may be:
- it's still being used as the default LookAndFeel; or
- it's set as a Component's current lookandfeel; or
- there's a WeakReference to it somewhere else in your code
Generally the fix for this will be to make sure you call
Component::setDefaultLookandFeel (nullptr) on any components that were still using
it before you delete it. Or call LookAndFeel::setDefaultLookAndFeel (nullptr) if you
had set it up to be the default one.
Deleting a LookAndFeel is unlikely to cause a crash since most things will use a
safe WeakReference to it, but it could cause some unexpected graphical behaviour,