alex added a comment.
> I would argue for just removing the `grp.writeEntry("dbfile", m_dbFile)`
line. This keeps the current behavior for the second group, and still solves
the problem for the first group when there is no config yet. Only users of the
second group with an existing config have to do a one-time change to their
config, e.g. resetting/removing the "dbfile" config value.
But what about renaming the dbfile entry, maybe to `alternate_dbfile` ? Then
the second group of users has to adapt to the changes and
the first group can be sure that the default profile gets looked up correctly
(in case the config already exists).
REPOSITORY
R120 Plasma Workspace
REVISION DETAIL
https://phabricator.kde.org/D28619
To: alex, #plasma, bruns, broulik
Cc: plasma-devel, Orage, LeGast00n, The-Feren-OS-Dev, cblack, jraleigh, zachus,
fbampaloukas, GB_2, ragreen, ZrenBot, ngraham, himcesjf, lesliezhai,
ali-mohamed, jensreuterberg, abetts, sebas, apol, ahiemstra, mart
