Albrecht Schlosser wrote:
> Sure, that's fine if we want to support an option from now on in the
> future. But we do also say that Fl_Multiline_Input is deprecated,
> and we shouldn't add options over options to control something
> that is deprecated.
Oh, I didn't know FMI is deprecated.
I'm apparently behind the times ;)
If we deprecate FMI in favor of FTE, then it would likely need
a similar flag so that 'submit form' type applications using it
can retain predictable tab focus behavior when used in place of FMI.
> Yes, this would be the optimal way to implement it, but I wouldn't
> want to have yet another option for a deprecated widget.
I could see where with FMI deprecated, and FTE taking its place,
a global option could control FTE to the same effect.
I'm seeing my own situation; an app with many single and
multiline input fields, and wanting the entire submit form
(all widgets) to behave in a certain way (tab key nav).
I can certainly set a per-widget option via the app,
but if it were a global, users could control it which
might be useful, not sure.
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
