Am Samstag, 7. März 2015, 14:43:14 schrieb laurent Montel: > Le Saturday 07 March 2015 13:47:13 David Faure a écrit : > > > KdePlatformTheme::loadSetting > > > > This code runs before the application name is set, but the fallback to > > argv[0] should still work. [This makes me realize that we should call > > QCoreApplication::setApplicationName before creating the application > > instance, everywhere.]. > > > > > This function caches that instance of > > > > > > KSharedConfig, which is working ontop of an empty file and thus does > > > nothing. > > > > Right. But that's exactly what reparseConfiguration() should fix, the case > > where the file on disk was changed. > > Indeed, given that the migrator code is in kcoreaddons, it can't do it > > automatically. (On hindsight, maybe the config migrator should have been in > > KConfig...) > > > > I'm surprised that Laurent didn't hit this issue though? > > No I never see it, and nobody reported it before that. > So what is the fix that I need to do ?
The release is approaching really fast. We need a solution. What's wrong with the migration before QCoreApplication creation? As far as I can see, it's a plain copy from the old location to the new one. > Regards > > _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
