From da506959705a6fc2731a8b994dd7be97c693f09a Mon Sep 17 00:00:00 2001 From: jules Date: Mon, 18 Dec 2017 09:56:44 +0000 Subject: [PATCH] Fixed a typo in a comment --- modules/juce_gui_basics/lookandfeel/juce_LookAndFeel.cpp | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/modules/juce_gui_basics/lookandfeel/juce_LookAndFeel.cpp b/modules/juce_gui_basics/lookandfeel/juce_LookAndFeel.cpp index a364b2b7be..2e55c87c1c 100644 --- a/modules/juce_gui_basics/lookandfeel/juce_LookAndFeel.cpp +++ b/modules/juce_gui_basics/lookandfeel/juce_LookAndFeel.cpp @@ -59,9 +59,9 @@ LookAndFeel::~LookAndFeel() - 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. + Component::setLookandFeel (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,