Hi again! Since my callbacks are outside of my classes (I have seen a video where the author encapsulated them in the class, but I couldn't compile that way, but let's forget about this), which forces my to declare variables globally (or in a namespace) and generally clutter up the .cpp source, I though to myself, wouldn't it be nice if callbacks were registered as classes with a dictated method name for the callback, so that this way one could encapsulate variable/pointer declarations inside class prototypes and clean up the .cpp source ? Then suddenly handle() came across my mind !
My question is: is it safe to do all event handling inside a MySubclass::handle() and and forget callbacks altogether ? In any case, there is (AFAIK) a much more limited selection of events that some widgets can be notified about with callbacks, in contrast to those available to the virtual handle() method. Is the point of callbacks to provide a "simpler" procedural way for event handling ? _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
