KConfig Bug?

[Waldo Bastian]

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

On Sunday 29 June 2003 08:36, Benjamin Meyer wrote:
> DESIGN.kconfig even talks about:
>
> bool isEntryDefault(key); // Is entry equal to the default?
> void resetEntry(key); // Restore to default
> void deleteEntry(key); // Remove entry <- only on implimented so far.
>
> in its <planned changes>.  So shale we, remove the [$d], impliment the
> above functions or should I file a bug report against Konsole for not have
> its defualt value in the binary, but rather in its global config?

I don't understand your obsession with [$d]. I'm trying to understand what you 
want but you are all over the map. You can get a "resetEntry(key)" in a blink 
if that's what you need.

> There seems to be two conflicting designs here.  KConfig wants to have a
> pure "cascading configuration files" system while classes like KToolbar
> need the default values specified in a configureation file.

There is no conflict. I have already given you an example for kcmkonsole how 
it can access default values using the code currently in CVS HEAD (attached 
again). This is all that is needed to change the "Use Defaults" behavior as 
found in configuration dialogs so that it takes into account defaults 
provided by either system administrators or default configuration files 
installed by applications. With our current design of configuation dialogs 
you don't even need "resetEntry()" functionality, because you always want to 
load the default settings in the GUI first, let the user apply, and then 
write back to the configuration.

I agree completely with your assesment that the current behavior of "Use 
defaults" is problematic because it reverts to the application default 
settings instead of the defaults provided by settings in $KDEDIR (if present) 
for exactly the reasons that you outlined.

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+/rINN4pvrENfboIRAmZIAJ9Cpr7i78dG1jXmxMs62VS59Hp98gCdHUSg
4BPr4mrLLaUmX+dRyYdBMPc=
=VTBw
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: default_config.patch
Type: text/x-diff
Size: 2093 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20030629/dde608dd/attachment.patch>