KConfig Bug?
Benjamin Meyer
ben at meyerhome.net
Thu Jun 26 17:25:04 BST 2003
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> I am trying to restore the config to the original state (as far as the user
> is concerned).
I guess the real problem stems from the fact that I am unable to determine
where the default value comes from when [$d] is involved. They could come
from within the application readEntry("foo", defaultValue) or from the global
config.
In a kind of ironic twist I noticed that if an application has a global config
and the same key/value (the default value) is written, kconfig wont save it
localy.
- -Benjamin Meyer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE++x5g1rZ3LTw38vIRAjtBAJ9aQtKO1emYK8rXBJuzVoEuHdr0egCeJNwC
tdYC0Mjf5RwbeU2W+ED5Wz8=
=gseK
-----END PGP SIGNATURE-----
More information about the kde-core-devel
mailing list