MacArthur, Ian (SELEX GALILEO, UK) wrote: > I'm guessing what the shown syntax means, but is that over-riding the > do_callback() method with the actual callback functionality? > > Surely that is *not* how do_callback() is meant to be used?
Yep, that was my impression, too. (See my other post) But probably this was only a "wrong" example. > 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. 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. :-( Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
