I’m hitting your assertion in LeakCounter,
[code]/** If you hit this, then you’ve leaked one or more objects of the type specified by
the ‘OwnerClass’ template parameter - the name should have been printed by the line above.
If you're leaking, it's probably because you're using old-fashioned, non-RAII techniques for your object management. Tut, tut. Always, always use ScopedPointers, OwnedArrays, ReferenceCountedObjects, etc, and avoid the 'delete' operator at all costs! */[/code]
1)Should I understand your words like this:
I should put my object directly in my JUCE classes, but not theirs pointers(which I need to new and deleteAllChildren()).
2)my project is half JUCE(for UI and plugin framework) and half pure C++(my audio engine), so I should also avoid using pointer new and delete in my pure C++ part ? In other words, it’s always a good habit to directly use the object instead of pointers?