Albrecht Schlosser wrote:
>> test/navigation raison d'etre is to show predictable
>> up/dn/lt/rt arrow key nav, so it probably [..] 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).
Done; r8043
>> Some other examples will need to affect this option too.
>> For instance, examples/table-spreadsheet uses a single Fl_Input..
>
> It's your baby ;-)
Right, though I guess there might be other babies..
trying to think what they might be.
> 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,
Yes, I agree per-widget control is also needed.
A simple flag in Fl_Input would solve it for FMI,
and a similarly named flag would I think be needed for Fl_Text_Editor,
esp. if FMI is being deprecated.
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
