DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2368 Version: 1.3-current To part 1 (arrow keys can leave Fl_Input): Yes, I think that we agreed about changing the default to 1. However, as I suggested, I'd also like to make it changeable dynamically for backwards compatibility (otherwise some end users might complain). I propose two static methods: - int Fl_Input::normal_move(); ///< gets the arrow key behavior setting - Fl_Input::normal_move(int); ///< sets the arrow key behavior Default would be 1 (normal), the old behavior would be 0. Suggestions for better names appreciated. To part 2 (double TAB): The description above is not entirely correct. Entering an Fl_Input widget with TAB (or SHIFT/TAB) selects the complete contents (if any). Pressing TAB while in the Fl_Input widget un-selects the current selection, if something is selected (first TAB key). If there is no selection, then the TAB key moves to the next widget (second TAB key, if content was selected in step 1). IMO there's no difference in behavior of TAB vs. SHIFT/TAB except the moving direction (SHIFT/TAB => backwards). The code in question is in src/Fl_Input.cxx, line #511 ff. since the early days of FLTK 1.1 (svn -r 1517). I propose to disable it by using a #ifdef/#endif construct in case anyone asks for it, but I assume that no one would miss this. If nobody objects, I'll take this STR and implement both changes at the next weekend. Link: http://www.fltk.org/str.php?L2368 Version: 1.3-current _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
