ben at meyerhome.net
Sun Jun 29 07:36:32 BST 2003
-----BEGIN PGP SIGNED MESSAGE-----
On Saturday 28 June 2003 4:20 pm, Waldo Bastian wrote:
> On Saturday 28 June 2003 19:09, Benjamin Meyer wrote:
> > I don't think that when you delete a setting (that can only be set in the
> > local config) it should delete the global config and when deleteEntry()
> > is called it does just that, deletes the entry. I think the current way
> > of deleting the global config is incorrect.
> I believe you misunderstand the current semantics then. The "global" flag
> in the KConfigBase API is used to distinquish between kmyapprc and
> kdeglobals, it's not used to distinguish between $KDEHOME and $KDEDIR,
> KConfig only modifies files in $KDEHOME by definition.
No, I do understand what that global flag is for. I am talking about the
bDefault flag. "global config" != "kdeglobals" If you though that they were
the same then my e-mails probably didn't make much sense and re-reading them
might clarify my view.
Just a small point: Either kdelibs/kdecore/KCONFIG_DESIGN or
kdelibs/kdecore/DESIGN.kconfig should be renamed to something less confusing
or they should be merged.
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?
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.
If the problem is with the "cascading configuration files" then the [$d]
should be removed.
If the problem is with classes like KToolbar etc then either they should all
get new constructors with all of their defaults and/or they should be given
the ability to read the default settings from the xmlgui files. (which have
presidence over global configs right?)
- -Benjamin Meyer
Public Key: http://www.csh.rit.edu/~benjamin/public_key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
-----END PGP SIGNATURE-----
More information about the kde-core-devel