> > Why is Fl_Pixmap's draw() method public rather than protected, again?
> He actually edited his code meanwhile, it was only two lines of C++ code > there... Anyway, I agree that draw() should be protected. Actually, I was being facetious there, sorry I was not more clear (maybe I'll toss in some emoticons next time on aid of clarity!) I don't think we actually can make Fl_Pixmap's draw() method protected easily, since it needs to be called by other widgets, that may not share common ancestry (recall that Fl_Pixmap et al derive from Fl_Image, and not from Fl_Widget...) However, in the specific case of the failed example, if it had been protected, that would (I assume) have made it more obvious to the user that their code was doing something erroneous... SELEX Galileo Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
