On Tuesday, 23 de August de 2011 15:14:05 Thiago Macieira wrote: > The interface I propose for this is one front-end class in Qt, ostensibly > named QSystemConfiguration, with one or more static functions of the > signature: > > static QVariant configuration(ConfigurationEntry entry); > > where ConfigurationEntry is an enum. This is inspired à la sysconf(3) and > pathconf(3) on Unix.
Add:
We also may need a class, which may or may not be the same one, that contains:
signal:
void configurationChanged(ConfigurationEntry entry, const QVariant &value);
Some systems do like to apply changes immediately to all applications, so it
should be supported.
In the specific case of the UI language changing, QApplication /
QGuiApplication should catch the signal and dispatch the LanguageChange events
to all widgets. Or should this be only in QtWidgets?
> Classes like Mobility's System Information can be provided as wrappers, in
> order to give C++ type safety. Unlike System Information, those methods
> should be static -- the physical dimensions of my display do not change if
> I instantiate another object.
To add the signals, they need to be QObjects. But I propose the getters
continue to be static.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Software Architect - Intel Open Source Technology Center
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
