I've got Fl_Input almost ready with the de-emacsification,
and 'standardization' of the key bindings across all platforms.
One thing that we should probably address while we're at this:
The Tab key.
Tab and Shift-Tab are almost exclusively used for field navigation.
The only exception being text editors.
All our Fl_Input derived widgets use Tab for field nav..
*except* Fl_Multiline_Input, which has an exception to treat
Tab like a text editor.
The behavior seems obsolete with the advent of Fl_Text_Editor.
(Arguably an app expecting Tab from users should use Fl_Text_Editor)
Also, one can still access the Tab character via ^I.
For vote:
Modify Fl_Multiline_Input to use Tab for field nav, to be
consistent with all the other derived versions of this class.
(the ^I workaround for users would be documented)
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
