dfaure added a comment.
I have a hard time accepting that the documentation was wrong -- and if it was, then this commit has to fix it, and port as much of the app code that does exactly this, as possible. I don't really know what mReference is. What about a test that uses KConfig directly (no skeletons), to test e.g. what kwindowconfig.cpp? Sorry to be a non-believer, I just sense a very strong risk of regression here, and if not, then a lot of porting effort. Unless there's a good reason for this stuff to be that way, that we still have to find out. I lack time and concentration right now to dig further, but I wanted to not delay my reply longer. REPOSITORY R237 KConfig REVISION DETAIL https://phabricator.kde.org/D28221 To: bport, ervin, dfaure, davidedmundson Cc: kde-frameworks-devel, LeGast00n, cblack, GB_2, michaelh, ngraham, bruns
