Don't require KApplication for using KGlobalSettings
Review Request #111348 - Created July 1, 2013 and discarded
|Aleix Pol Gonzalez|
Initialize it when QCoreApplication is initialized, no matter what. KApplication keeps the call to KGlobalSettings::activate(), it just won't do anything the second time that it's called. Behavior shouldn't change, if AFAIK. Now KGlobalSettings will be initialized automatically, as long as the application links against kde4support
Veto. This ignores the history behind activate(). Commit log has the reason: " - Don't let kde plugins change the font of a non-kde application " If a Qt-designer plugin links to the lib that contains this code, it will suddenly apply the kglobalsettings to the whole process, which is exactly why we introduced activate() : so that it's only applied explicitely in *apps* that want it. IMHO KGlobalSettings should end up in kde4support with KApplication, so either apps use both or none, so the activate() in kapp does the job like in kde4.