s...@sjssoftware.com wrote: > [..] >> (2) all sorts of Fl_Group's child modification methods (add, remove, >> insert, clear, etc.) should be virtual... >> >> Albrecht > > As a user, I've often wished that (nearly) the entire Fl_Widget > interface was virtual. That's because when I feel that I have > to design some sort of custom widget the result usually ends up being > derived from Fl_Group. That in turn means that in order to > manipulate my widget in even the simplest of ways (change its > color, for instance), the caller must know its type, which is > quite inconvenient.
I can understand your problem, but not exactly the example. It is obvious that virtual methods would help, but in your _example_ Fl_Widget::color() would be okay, wouldn't it? Unless you overloaded the color() method in your derived widget. Is this what you meant, or am I missing something? > Just food for thought, I hope. Any input welcome. Albrecht _______________________________________________ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
