Another Singleton Pattern for QML -or- Multi-threading Pitfalls With Singletons
Details
Aren't singleton objects just the greatest? You can access them from any part of your code, you can use them in QML... Why wouldn't use them in absolutely everything?
We'll talk about some nightmare issues related to singleton objects when working with multi-threaded code and a pattern that reduces the risk when using C++ singleton objects in QML.
Among topics:
- The Singleton Design Pattern
- GUI vs Non-GUI threads
- Cross-thread function calls
- Catching fatal exceptions
- Unit tests