CriticalSection crashes with VS 2022

[kunz]

@eyalamir

We probably need to discuss the design that leads you to such problems.

This is true. When you set up it the right way, you can eliminate the singleton lifetime problems.

There is one problem I wasn’t able to fix:

LookAndFeel_V4 difficulties applying Typeface to just one component

I am having trouble following the LookAndFeel Tutorial. According to the “Cusomizing Color” Section, I coded this: in My Component.h: private: juce::LookAndFeel_V4 m_LookAndFeelIcons; and in it’s constructor: m_LookAndFeelIcons.setDefaultSansSerifTypeface(MyBinaryAssets::MyTypeFace); someBTN.setLookAndFeel(&m_LookAndFeelIcons); But the Button does not change it’s font…? When I do something like: someBTN.getLookAndFeel().setDefaultSansSerifTypeface(MyBinaryAssets::MyTypeFac…

It looks like it is not possible to set a different LookAndFeel with other typefaces to a specific component. Some weird singleton magic happens in the background.

@eyalamir

As a plugin developer you want to save user resources at any junction you can, and the memory for shared resources is a easy win that would greatly benefit your users in projects with many plugins, don’t prevent them from having it.

I agree

A short resume:
Singletons are useful in the plug-in world when you share resources and solve technical problems. But they are a bad design choice otherwise.