> It doesn't have to. Knob pixmap initialization etc. could be moved > into a setter function for the knob type property. As long as the knob > type is not set, the background is not drawn.
While I understand what you mean, I don't think it's good. A good example is probably the lcd widget: There is no good reason that the number of digits should ever be changed (and no function to do that). So it should be declared const (it is not, a bug imo). However, const members must be set on construction, so this will conflict with setter functions. For comparison: Advantages of setter function: * You can change some things on runtime (but it's pretty unlikely you'll ever do that) Advantages of value template parameters, i.e. LcdSpinBox<1>, LcdSpinBox<2>...: * You can use const values which have (small) runtime advantages and make the code safer/cleaner. Are you really sure it is better to use properties than value template parameters? ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _______________________________________________ LMMS-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmms-devel
