Tabbing from field to field

[forskare]

Once there is focus on a field, tabbing is workable. However, the subject of tabbing from field to field, skipping fields, setting a tabbing order, etc, is not discussed anywhere that I can find. I know it's possible to write code to help with some tabbing issues in dialogs but on a grid, not so. My customer is used to the keyboard and tabbing with their old A4 app. Sure, there will be some changes and not everything can be done with the keyboard.

Furthermore, I used to be able to use the down arrow key and move into the search progressive lookup, keep pressing the down arrow and when the record is reached, press the Enter key and the record appears in the grid. Now, the won arrow key does not work for that and the mouse must be used. In a short list the down arrow and enter key is faster but in a long list, scrolling with the mouse wheel and clicking is faster.

Anyone know where can I find info on tabbing in a grid or setting a tab order, etc.?

[GGandhi]

Re: Tabbing from field to field

I am not sure there is any way to duplicate what people used to have in the desktop, the behavior may be replicated in the web using lots of code and your time to reinterpret the key strokes. however to answer some of your questions:
>usually the tab key moves to next down instead of the enter key ( I think as a protection in web, not sure where I heard that)
>so obviously shift tab puts you back one field up.
>in a short list down arrow will select the next available info, the up arrow puts back one choice up and as usual you can tab out when satisfied.
>if you want to skip a field you have two options (a) set them as label, looks funny in an editable grid, (b) use enable property 1=2 to make it non editable. it will look greyed out probably more acceptable. these two will make the field permanently non editable, you may be able to do conditional non editable state by applying some logical calculation based on some other field.
hope this helps.

[forskare]

Re: Tabbing from field to field

I've been trying various ways to help solve the issue. One idea I have is to group as many key stroke fields together as possible and the same with the mouse strokes. I'm still bewildered as to why field titles are given focus. Makes no sense to me. I am aware of your first 2 points and will try the third option. That definitely will be of help.

Thank you

[westridge]

Re: Tabbing from field to field

I assume this refers to a UX component?
If so, could the solution lay within the onBlur() event?

Question:
Are you able to set the "initial focus" and tab to the next field from there?
Yes, I can begin typing in the the field. However, I find that I must first click my intended initial focus field before I can use the tab key to move to the next field.
is there a magic handshake to just use the tab key to move forward?

[forskare]

Re: Tabbing from field to field

Sorry, I should have made that clearer. I am using grids. However, what you're suggesting should work just as well on the grids. Time to experiment.

Thank you, I appreciate your suggestion.

Edit:

Once a field has focus, I can tab forwards and backwards (Shift-Tab) as long as I don't leave the grid or the detail section/ You should be able to do the same in the UX. I have a few search fields set to Progressive Find. when I begin typing the search part works fine. At one point I was able to tab from the search box to the display list and use the arrow key from there. Now, that does not work. I can, however, select a record with the mouse and press the enter key (instead of clicking the View Record button, and the record comes into view. I've somewhat handy using one hand for the keyboard and the other for the mouse. However, a major improvement is urgently needed. A web app without adequate tabbing is a detriment. It's not a 'killer' but it sure does not help to sell an app.