DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2040 Version: 1.3-feature To be honest, my rationale was two-fold for this STR. (1) Minimising the amount of work a caller would need to do to intercept when the FL_Choice's value changed and (2) minimising the modifications to Fl_Choice itself. By making picked() virtual, the caller just needs to override one method. In Fl_Choice, picked() is called in all right places dealing with how a choice is selected be it via a FL_SHORTCUT, or FL_PUSH or even a FL_KEYBOARD event. At the time I was looking into this, it appeared that in order to get the same effect, would be to override the handle method of Fl_Choice and to (re)implement all the various ways an item can be selected. Now, that was my rationale for this STR. However, this all moot if STR #2041 (http://www.fltk.org/str.php?L2041) is adopted. With STR #2041, the same effect can be done with SmartChoiceTest by the usual means of overriding the handle() method. Then it would be a simple matter of capturing the FL_TOOLTIP event. Link: http://www.fltk.org/str.php?L2040 Version: 1.3-feature _______________________________________________ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
