In order to simplify GUI design maintenance, I am using the following inheritance scheme for my plugin’s editor:
AudioProcessorEditor -> MyEditorComponent -> MyEditor
MyEditorComponent is maintained with the Jucer and happens to change rather frequently, while MyEditor contains quite a lot of code that I didn’t want to squeeze in between the …[/] special comments of the Jucer-generated component. I found this way of putting the GUI in between AudioProcessorEditor and the actual code implementation very easy to maintain.
I might bemissing something, but I wonder whether the destructor of AudioProcessorEditor should better be virtual (same goes for the derived Juve generated component, btw), so both MyEditorComponent and MyEditor will be decomposed correctly on destruction. Even if one does not further derive from the Jucer-generated component, there remains the same situation.