> For non-intrusive, casual event handling, it's usually best > to ALWAYS pass the event to the base widget, either before > or after your own code, and make an effort to preserve the > return value from the base widget, unless you need to > override it. > > I'd suggest this for all derived handle() methods, > even GL windows.
I'd go further, and say *particularly* for Fl_Gl_ derived windows. I don't remember the details, but do recall that at some time in the past I had a problem with a derived gl window that was caused by my *not* calling the base class in the derived handle method... SELEX Sensors and Airborne Systems Limited 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
