On 16.12.2010 00:07, Greg Ercolano wrote: > OK, then some of the examples need tweaking.
Good point. I don't think that anybody thought of the examples. > test/navigation raison d'etre is to show predictable > up/dn/lt/rt arrow key nav, so it probably either needs > a toggle button added to allow toggling Fl::option(OPTION_ARROW_FOCUS) > to still be useful. +1 for the toggle button IIRC arrow key navigation is also documented somewhere - we must check and fix this, too (adding info about the option). > Some other examples will need to affect this option too. > For instance, examples/table-spreadsheet uses a single Fl_Input > to edit cells, and how it responds affects arrow navigation > of the spreadsheet. That program will probably need the > option set to 1 at the top of main() to fix it. It's your baby ;-) But what if there are also other Fl_Input widgets that should use the default (no focus change) ? This looks really like a reason to change the navigation feature in a per-widget way, or maybe to subclass the Fl_Input that is used for the table and add an appropriate handle() method [1]. I'm thinking of the program's function as a general example; otherwise we could also switch the arrow navigation on for the whole program. [1] I don't know whether this would be easy or at all possible w/o some bad hacks or copying lots of code from Fl_Input... Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
