DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR New]

Link: http://www.fltk.org/str.php?L2142
Version: 1.3-feature


I suggest that we should change all core widget's draw() methods from
protected to public.

IMHO, there's no reason to protect the draw methods, because draw() is
virtual anyway. A simple way to circumvent the "protection" is a cast to
Fl_Widget and then to call the virtual draw method. Fl_Group, e.g. uses a
Fl_Widget pointer to call the draw methods of its children.

I noticed that some widgets have a public draw() method (e.g. Fl_Input),
but most of the draw() methods are protected. Obviously, the reason why
Fl_Input's draw() method is public is, because it is used in
Fl_Value_Input.cxx.

Is there any reason (not to change the draw methods to public) that I
don't see here? If not, then I'm willing to do the dirty work ... ;-)

P.S. To avoid potential ABI conflicts, we should do this ASAP.


Link: http://www.fltk.org/str.php?L2142
Version: 1.3-feature

_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to