DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2026 Version: 1.3-current And more: IMHO the first part (FL_SHORTCUT) is wrong or at least questionable. I don't think that it is useful to change a FL_NORMAL_BUTTON's value() and set the changed() flag. Does a normal button have a value()? By definition, it has, but is it used at all. IMHO, for a normal button the value() should be ignored, it is only used to click it (or type its shortcut) to trigger its callback. For the second part: I don't think that it is a good idea to handle FL_KEYUP events for a button. If the callback has been triggered already by the FL_SHORTCUT event (i.e. key press/down), then all is done already. If I read the proposed patch correctly, the callback would be triggered twice (once for FL_SHORTCUT, and once for FL_KEYUP, when the shortcut key is pressed/released resp.). Would this be useful? I'm really confused now... Link: http://www.fltk.org/str.php?L2026 Version: 1.3-current _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
