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 Thanks Al, I'll check your updated diff file which indeed seems to correct the indentation problem. Now for the pertinence of this STR, I believe that FL_WHEN_CHANGED should handle all important changes when the keyboard is used as when the mouse is used, otherwise we have a serious nonorthogonality problem here. If the mouse changes the button state when released on a button then the keyboard should change it as well. IMHO, the documentation confirms this problem and should be updated as well when this coherency problem is fixed. It may make our life more complicated but this is what we should do IMHO. Also, I believe that a normal button has two transient states 1 then 0, and that it is really interesting to know in what state we are, when we use it as a two states button (thanks to the when() condition set to FL_WHEN_CHANGED (ideally without the FL_WHEN_RELEASE OR'ed IMHO)) It an easy to determine in the callback if we are pushed or released. For the clarity of the discussion, Imagine for example a midi keyboard application where we would like to simply associate a midi note event (note on or off) according to a key shortcut pressed or released. In such application, I believe it would be highly desirable to have the midi callback called twice whatever it was originated by the mouse push and release or by a keyboard key pressed and release. A natural way I would think of first would be to USE FL_WHEN_CHANGED for that and that it would work transparently for both mouse and keyboard. Not sure I'm clear (!) , Fabien 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
