> But Fl_Widget doesn't have a value() method. Keeping an array of > Fl_Valuator* might work, but might get messy because it's value() > is non-virtual; you'd have to research whether or not the base class > value() does what you want in all cases. Unfortunately fltk > doesn't do polymorphism very well.
But now that we are no longer haunted by the ABI specter, we can do things like make values() virtual, right? I have a list of methods I'd like to see virtual, and I think there are others scattered around in STRs, but maybe make a list of methods that already overlap with base classes and should probably be virtual (unless they have a different signature, in which case one should probably be renamed, but that probably has to wait for a larger release), and then methods that could conceivably be overridden usefully. Then we can go through and change them all at once (except the renames). Or is there already such a list? _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
