--nextPart3214809.YW2BrTYfB0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 01 December 2004 12:05, Stefan Nikolaus wrote: > > geschrieben: > >> What about defining default values for the parameters passed to the > >> configuration object. Some of the member functions already define > >> default group names. > >> For each member function that takes a variable group name, we define a > >> parameter and a corresponding group in the .kcfg file. > > For kdelibs/kdeui this idea will end up with six parameters. Rethinking > this, it could be confusing. So splitting the configuration object seems > to be the only way to handle this issue. Or has anyone another idea? > > Another question: > In kdeui/kdockwidget.cpp, e.g. at line 2527, there are also entry names > that are variable. How do I handle these? kconfig_compiler does not > support the generation of entry names with parameters passed to the > configuration object. Two possibilities: 1) kconfig_compiler learns how to do that 2) The entry itself takes a parameter. BTW I don't think the current configuration code generated by kconfig_compi= ler=20 is optimal for the kind of usage done by kdockwidget.cpp and kmainwindow.cp= p. The KConfigSkeleton object basically provides for a storage object for the= =20 settings, while KMainWindow and KDockWidget would rather need some sort of= =20 mapping object that facilitates mapping the properties of various objects=20 (toolbars, windows, etc) to the configuration file. E.g. if you have 10 windows that you have to store the properties of, it=20 shouldn't be needed to create 10 configuration objects that store these=20 poroperties, it should be enough to have 1 mapping object that can map the= =20 properties to the configuration file. Cheers, Waldo =2D-=20 bastian@kde.org | Free Novell Linux Desktop 9 Evaluation Download bastian@suse.com | http://www.novell.com/products/desktop/eval.html --nextPart3214809.YW2BrTYfB0 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQBBra31N4pvrENfboIRAte8AKCbFJzn9WVqbx0O1M9qzPzcFw63nQCgpojG etiFUJB4MVvWTxKzUmDkXFY= =+ohr -----END PGP SIGNATURE----- --nextPart3214809.YW2BrTYfB0--