> Evan Laforge wrote: > > 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. > > FLTK 1.3 is probably the time/place to do this. > If you have a list, make an STR for FLTK 1.3 so we have it on record.
In my view, everything in Fl_Widget except x(), y(), w(), h(), the callback() variants, when() and possibly do_callback() should be virtual. (I can see advantages of do_callback() being virtual too, but could be persuaded otherwise). I think this is already STR'd somewhere, but perhaps not. Best, Stan _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
