When the TAB is pressed in Explorer, Favorites and
other such components then it is not possible to
find the focus and navigation from keyboard is not
possible until switching e.g. Form Explorer to
Favorites and back.
I think it should be fixed directly in explorer like components,
Swing's focus cycle traversals should be properly defined and then
Tab will be switching among components in focus cycle traversal (or do
The tab key is not consumed by the explorer. It correctly lets the
framework pass the focus along.
The next thing in the chain is (according to the focus lost event) the
TabbedAdapter.setFocusable(false) seems to cure the problem. (at leat
Dafe, any idea if this could be harmful? I'm always kind of defensive
when dealing with focus.
it's not ok.
it seems the that focus cycle gets out of the TabbedAdapter component
onto the whole window and that assigns it to the first component in
it.. usually it's the topleft explorer.
fix by copy&modify of LayoutFocusTraversalPolicy. Create a focus cycle
within a TabbedContainer, never allowing the focus to leave the active
The fix seems to work with the most common components in the IDE
desktop, but there could be special cases that could fail. Therefore I
would prefer not to integrate into beta1, but give it more testing
new revision: 1.12; previous revision: 1.11
I have tested the use tab in most of IDE components and it seems to be
fine. Verified in dev build #200502241900; jdk1.5.0_02-b07
Created attachment 26832 [details]
i'm fixing issue 61092 and found out that the problem is in TabbedContainer.
when it's used in a standalone dialog window (e.g. properties dialog) it somehow
consumes the focus and it's not possible to navigate the properties dialog with
a tab key without a mouse-click first.
after some experiments i discovered that both issues (54264 and 61092) are fixed
just by removing 'setFocusable( true )' from the TabbedContainer (compare to
revision 1.11). then the focus works as expected both in the properties dialog
and main window modes as well.
milos, what do you think?
how come the tabbedcontainer is used in dialogs?
i have no problem with it, but please test extensively, I remember this bug to
be somewhat esoteric in nature..
the property sheet uses tab control and the property sheet can be embedded in a
tested on winxp, jdk 1.4-1.6
Checking in TabbedContainer.java;
new revision: 1.16; previous revision: 1.15