KConfig Bug?

[Waldo Bastian]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 26 June 2003 16:49, Benjamin Meyer wrote:
> > That depends. If a global entry is defined (in $KDEDIR/share/kdeglobals)
> > then it should add a [$d]-entry to $KDEHOME/share/kdeglobals to
> > invalidate that entry. If there is NO global entry defined in
> > $KDEDIR/share/kdeglobals then it is sufficient to just remove the entry
> > from
> > $KDEHOME/share/kdeglobals, if there was any.
>
> Yah I was able to figure that part out.  So there are two options.  Delete
> from the local config (remove the line) and delete from the global config
> (add a [$d])  If bGlobal is true is should do the first one, but it is
> doing the second.

It should be doing the second.

The whole idea of this is that an entry can be either in the global file 
(kdeglobals) or in the app-specific file (kmyapprc). 

When you write to the app-specific file (which one usually does), you can 
write the entry with:
	writeEntry(key, value, true /* persistent */, false /* global */, false /* 
locale */)
and delete it with:
	deleteEntry(key, value, false /* locale */, false /*global*/);

When you write them to kdeglobals (only used by KDE-wide settings typically), 
you can write the entry with: 
	writeEntry(key, value, true /* persistent */, true /* global */, false /* 
locale */)
and you can later delete it with:
	deleteEntry(key, value, false /* locale */, true /*global*/);

Which makes me really wonder why you want to use deleteEntry at all actually. 
What are you trying to do?

Cheers,
Waldo
- -- 
bastian at kde.org -=|[ SuSE, The Linux Desktop Experts ]|=- bastian at suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE++xZWN4pvrENfboIRAidZAJ9VqndFgS7s1+SCQa+KV8rfvtOSvQCfe4dW
wd4fIskHLzrfQWgFUS2ud+E=
=ehwe
-----END PGP SIGNATURE-----