> > Also - can we demonstrate that there is no performance impact from > > virtualising this method? Presumably that will [often | > usually] mean an > > extra level of indirection on each callback event...? > > Well, IMHO callbacks are rarely called (mostly by user interaction, > i.e. clicking a button - as opposed to handle(), i.e. moving the > mouse), and thus I don't think that *this* would be a problem.
Ah, that's a fair point - I was visualizing the handle() method as you say, but of course do_callback() is mainly going to be triggered from (infrequent) user generated events, so a little extra overhead may not be an issue. > But in other cases, maybe timer events could also be used to call > callbacks, rr dragging a scrollbar with when(FL_WHEN_CHANGED). > Hmm, ... I don't know how to estimate use cases. :-( No, nor me. I suppose if we wanted to go this way, we could make some empirical observations of before/after tests and see if there's any perceptible effect... 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-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
