I once programmed a class hierarchy targeting the same features (and much more). It consited of settings group objects and settings object ordered in a tree hierarchy. That hierarchy was much more complex (having templated settings, units, limits, flags, value checking, attributes for GUI form generation etc.). Each of the groups and settings shared a common interface base.
One feature that was very useful was the fact that we could display/edit the settings hierarchy using a QAbstractItemModel in a QTreeView. Do you intend to support the latter with your classes? -- Regards, Bernhard Lindner _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
