On 16.12.2010, at 17:18, Greg Ercolano wrote: > Domingo Alvarez Duarte wrote: >> I've updated my code to latest svn and noticed that the new key navigation >> with the TAB key first select all on the first press and need a second >> press to move to another widget. >> >> Why we need two key presses ? > > Indeed.. not sure offhand what's causing that. > > FWIW I haven't checked anything in yet for Fl_Input, so I don't > think it's me.
Nope. > Domingo, is this a regression, or is this behavior that's been > in there all along and there's an STR patch that solves it? > If it's a regression, which svn version did it work in? > If it's an STR, which #? It's always been there in FLTK 1.1. This is one more of these "peculiar" FLTK behaviors. > I agree the behavior is bad, as it's inconsistent with the behavior > of Shift-Tab, and would be happy to try to solve it while my nose > is in Fl_Input. It's easy to solve, but I don't have it handy now. It's something to do with checking if position() and mark() are different (i.e. if there is a selection), and then going to either end of the selection instead of to the next input field. Note 1: Entering an Fl_Input with TAB selects the complete text, hence the need to press TAB twice. Note 2: In current FLTK 1.3 versions, the behavior is consistent, i.e. it is the same for TAB and SHIFT/TAB. There has been a Shift/Tab inconsistency in previous Linux (X11) versions, but this was another story and is fixed in FLTK 1.3 (but not in 1.1). HTH Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
