Make TAB go from one text field to the next

[GoogleCodeExporter]

Note that we don't handle selecting text etc., so we either clear the
target field on entry (generally not a good idea) or not (so you need to
backspace the value to modify it)

I've looked a little for implementation:

Let TAB character leak out of Readline()
Calling code (window handler) is very often:

clicked_button=Window_clicked_button();
switch(clicked_button)
{ 
}

The smallest modification would be:

if (Key==SDLK_TAB)
  clicked_button=Find_next_field(clicked_button);
else
  clicked_button=Window_clicked_button();
switch(clicked_button)
{ 
}

Original issue reported on code.google.com by yrizoud on 11 Aug 2009 at 9:16

[GoogleCodeExporter]

Personally, I'd like for it to clear the target text field. It can never be 
perfect without text selection, but when I'm 
setting the canvas size, say, I want to go [insert new value], [tab], [insert 
new value]. This is my (and I think pretty 
much everyone's) little mental workflow for things like this, based on 
universal GUI conventions, and having to 
backspace the old value is tedious.

Original comment by cameron...@comcast.net on 12 Aug 2009 at 2:26

[GoogleCodeExporter]

A small bit of info that is present in Hatch's posts about this on Pixeljoint, 
but I
forgot to repeat here: 
Everywhere in Grafx2, right-clicking a field (instead of left-clicking) enters 
it in
edit mode while clearing the old value. (I know it's not "standard", and yet 
once you
remember it, you use it all the time.)

Related: Issue 204 Text fields selection

Original comment by yrizoud on 12 Aug 2009 at 4:28

[GoogleCodeExporter]

Hi,

what is when grafx2 saves the first click on the field (left or right) and then 
on 
TAB he repeats this on the next field? So if u start with a right click every 
field 
entered with TAB will be entered and cleared and if u start with left it will 
be 
only entered.

... greetings HoraK-FDF

Original comment by HoraK-...@web.de on 1 Sep 2009 at 8:16

[GoogleCodeExporter]

That's smart.
I only regret this still reserves both mouse buttons, I had some hope we could 
free
one for a "slider" to easily alter numeric values without the keyboard.

Original comment by yrizoud on 1 Sep 2009 at 9:56

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Original comment by pulkoma...@gmail.com on 15 Sep 2009 at 7:13

• Added labels: Milestone-2.3

[GoogleCodeExporter]

Original comment by pulkoma...@gmail.com on 15 Jan 2010 at 7:34

• Added labels: Milestone-NotPlanned