I don't think it's about reloading settings at runtime, but if we where to support that it wouldn't be easy in system settings, simply connecting changed() signal to the apply() slot would do the trick.
Then there is the question if one wants to support this behavior, and based in which use case. 2013/5/27 David Baum <david.b...@naraesk.eu>: > Hello. > > Am Dienstag, 21. Mai 2013, 07:17:23 schrieb Thiago Macieira: >> On terça-feira, 21 de maio de 2013 16.44.20, Damian Ivanov wrote: >> > Hi all, >> > >> > When people change a setting in KDE they 1st hit the apply button. >> > In GNOME people change the setting and the setting is change instantly >> > there is no apply button. >> > >> > Is it possible to have the same behavior in KDE? >> >> No, there's no option to change to that model. Not only that, we miss the >> infrastructure to achieve it. All of our applications are written with a >> model of never reloading their settings at runtime, so even if you made >> dialogs apply immediately, it would still not be the GNOME behaviour. > > Well, one part of systemsettings already has the GNOME behaviour: Phonon > Multimedia → Phonon → Hardware > > Changing the selected profile results in instant changes. Even if you close > the > dialog without pressing apply the settings changes. > > Kind regards, > David > >>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe << -- Daniel Nicoletti KDE Developer - http://dantti.wordpress.com >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
