Loading...
Searching...
No Matches
score::Settings Class Referencefinal
Application-wide user settings registering and handling. More...
Detailed Description
Application-wide user settings registering and handling.
Settings do not fit in the other MVP parts of the software due to the command application difference.
When "ok" is pressed in the settings panel, the plug-ins are required to commit their changes to their respective models. Else they discard them.
A plug-in wishing to add user settings must :
- Implement score::SettingsDelegateModel, score::SettingsDelegatePresenter, score::SettingsDelegateView
- Register them with SCORE_DECLARE_SETTINGS_FACTORY.
Public Member Functions | |
| void | setupView () |
| void | teardownView () |
| void | teardownModels () noexcept |
| Settings (const Settings &)=delete | |
| Settings (Settings &&)=delete | |
| Settings & | operator= (const Settings &)=delete |
| Settings & | operator= (Settings &&)=delete |
| void | setupSettingsPlugin (QSettings &s, const score::ApplicationContext &ctx, SettingsDelegateFactory &plugin) |
| SettingsView< SettingsDelegateModel > & | view () const |
| auto & | settings () const |
Member Function Documentation
◆ teardownModels()
|
noexcept |
Destroy the registered settings models. The models are QObjects: they must go before the QApplication does. Owners that also own the QApplication (the Minimal*Application test scaffolding) call this explicitly before deleting the app; the destructor calls it too (idempotent) for the normal case where the app outlives us.
The documentation for this class was generated from the following files:
- lib/core/settings/Settings.hpp
- lib/core/settings/Settings.cpp