Idea: SkipDirtyOnIdenticalValues WriteConfigFlag for KConfigBase / KConfig

[David Faure]

On Thursday 17 July 2008, Oswald Buddenhagen wrote:
> On Tue, Jul 15, 2008 at 12:28:54PM -0500, Matthew Woehlke wrote:
> > Oswald Buddenhagen wrote:
> >> also, the description is (or should be) "ensure that no local value
> >> exists if it matches the system default" - so changes in the system
> >> default can take effect.
> >
> > Terrible idea. Entries should not be deleted just because the saved  
> > value now matches the default; that would lead to unexpected behavior.  
> >
> hmm. i suppose.

On the contrary - if you change a toolbar to "big" and then to "normal" again,
it looks normal like any other toolbar. If you change the system default 6 months
later, it would be really unexpected that this toolbar doesn't behave like all others.

> for one, i got mixed up with the explicit option to restore (and
> keep) the system default - but that's what revertToDefault() is
> suposed to be for (it's broken - see todo). nobody uses that anyway. :-/

Well, KMainWindow and KToolBar definitely do use revertToDefault(),
so it would be nice if it could be unbroken......

-- 
David Faure, faure at kde.org, sponsored by Qt Software @ Nokia to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).