Juce app states

Hey all. Until now, I have been using Juce to make simple control surfaces for underlying algorithms. I would now like to make something more like a full app that has different app states. I have been looking at an SDL tutorial related to this involving an app state manager singleton.


Is this a good general approach for a Juce app, or is there a recommended way of doing things that I am missing?

I’d say this is more a matter of personal style than anything else. JUCE doesn’t care how you use it (as long as you operate its classes correctly).

Thanks dude. I just wanted to check. I often spend hours working on a fangled way to do something only to find out later that juce has some feature that:

a) already does what I was attempting
b) does it in a much better way than I had attempted