Enterprise Client Community

if a not enabled field has the focus, pressing tab doesn't make the focus to switch to next component.

in our case, a button which has the focus gets not enabled and afterwards hitting tab won't leave the field.

we have another phenomenon in some fixgrids which have the focus, if you press tab again focus seems to disapear somewhere to space. Hitting tab long enough leads to the desired result.

i looked into the demo application and found an list which shows the described behaviour.
Its the "Tree with Checkbox" fixgrid. You can set the focus on the grid and hit tab. i think after round about twelve times the focus control is on the first control of list.

i thought it would be a workaround to set the fixgrid attribute focusable to false, but focus ends up in list again.

this is an urgent problem, because the application should mainly be operated by keyboard.

First problem is solved - also disabled components now are reacting on tab/shift-tab. Background: the normal focus traversal mechanism is inactive for disabled components in Swing, so we had to push a bit...

Björn

Also second problem is solved.

Why so many tabs without visible reaction? The grid cells that are not populated with data are rendered into an invisible area, E.g. if grid has 10 rows but only 5 rows of data are available. The focus manager already checked this, but did not check if invisible controls contained sub-components. This is e.g. the case in the example you mentioned: the tree node is a container containingh the check box.

Corrected with updat that will be published (most likely) today.

Björn

great this works!

but another point is, that the attribute focusable=false in gridcols seems not to work.
Focus travels through headerline of the fixgrid before it comes into the first entryfield.