[kde-edu]: kbruch UI

[Anne-Marie Mahfouf]

On 31 October 2004 11:16, Sebastian Stein wrote:
> Jason Harris <kstars at 30doradus.org> [041031 17:12]:
> > Hello,
> >
> > On Sunday 31 October 2004 08:28 am, Anne-Marie Mahfouf wrote:
> > > the ENTER key is intuitive in a field t validate the value you enter
> > > it also appears to me intuitive that after Enter it jumps at the
> > > other field
> >
> > I agree, and it's pretty easy to do.  Just make a slotAdvanceFocus()
> > Slot, and attach it to the returnPressed() Signal of each line edit.
> > The slot will look something like this:
> >
> > void KBruch::slotAdvanceFocus(void) {
> >  if ( sender()->name() == QString( "editBox1" ) ) editBox2->setFocus();
> >  if ( sender()->name() == QString( "editBox2" ) ) editBox3->setFocus();
> >  if ( sender()->name() == QString( "editBox3" ) ) processEntry();
> > }
>
> Yes, but doesn't this hurt the usability? TAB is used to change focus and
> not ENTER.
tab is used to change focus, yes but in the case of input from the user I 
think Enter is correct. Personnally I find this behaviour on lots of web 
forms for example (I just used one to pay my daughter's school and the focus 
went to the other field after enter). I am not sure kids use the tab key 
anyway, my kids use the mouse preferentially.
What you can do though is ask the usability team for a usability study on 
KBruch as was done on KHangMan. Then you'll have precise indications about 
what is OK.

annma