> > Having created this "button" widget, it might be more > portable to use it > in subsequent refs, rather than calling startBtn explicitly? > Perhaps that is what you intended? > > Yes, that was a hangover from an attempt to debug the label > issue i talked about, i just forgot to change it back to > button->member() > > But if the callback implementation in this case is only ever > going to be used by StartBtn is there any point me doing the > cast? and should i just declare the function as receivng a > button widget instead?
If the callback only ever references that one widget, then you probably don't have to do the little dance to get a class specific callback anyway - it could just as well be fully static. 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
