I used to get my application properties doing:
PropertySet* const globalSettings = ApplicationProperties::getInstance()->getUserSettings();
It looks like the ApplicationProperties class is not declared as a singleton anymore (I use the last git version).
What is the correct way now to get my application properties from anywhere in my code?
It would be great to access it with something like JUCEApplication::getProperties()->getUserSettings()…
Just a precision:
I could obviously declare an ApplicationProperties instance in my inherited JUCEApplication class, and make a static method to access it.
The problem is that I used to store ApplicationProperties in my audio plugin projects, which don’t have such Application class…
Hey now! Don’t go bad mouthing singletons, or I’m gonna tell on you[/quote]
I never had a strong feeling about Singleton’s either way. But I work with a fellow who, really, acts out part of “Highlander”, shouting ‘There can only be ONE!!!’ whenever he declares one. After 9 years in the office next door, I might be developing an emotional aversion…