This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
[dev build #200408262030; jdk1.5.0-rc-b63] There was formerly shortcut Ctrl+~ to switch among ide windows. Now the Ctrl+Tab is set as shortcut but this combination is used for traversing among components that are not traversable through Tab key only (they use tab for other functionality of component). Due to this conflict user is not able to traverse through Ctrl+Tab traversable components because the windows switcher appears instead.
Dafe, I think this is yours. I can imagine maybe ctrl-tab is a problem for things like the Properties editor (not the normal editor, but the ugly one), or anything like that. IMO, this can probably be closed as WONTFIX - the only time you need ctrl-tab, not tab, is when there are multiple focus cycle roots within, say, an editor tab, and I can't think of a single case where that is not a bug in whatever editor is there. If it's popping up when you press ctrl-tab in a dialog, that's a bug, but it's not a transmodal action, and AFAIK it doesn't do that. Jaromir, we specifically don't want people to be able to move focus between random components via ctrl-tab - for every window there is a proper keyboard shortcut on the window menu, and that's the way to do it. Using ctrl-tab in NetBeans *should* move between winsys modes. If a TopComponent requires ctrl-tab to manage its focus traversal, it's a bug in that TopComponent, not a bug in the winsys. Is there some specific case where something isn't working because of the way we use ctrl-tab?
BTW, for handling tab in JTables and such, we have code (see org.openide.explorer.propertysheet.BaseTable) to allow you to tab into, through and out of a JTable without needing ctrl-tab to do it. It's not pretty, but it's not hard. So I think this sort of thing is solvable without requiring ctrl-tab. Correct me if I'm wrong.
This is the testcase where I have problems to jump from the component to other: 1.create the properties file 2.open it (not "edit" but "open" action from explorer popup) 3.I try to jump to "New Property" button (it is not possible by keyboard) - Ctrl+Tab is used for the windows switching.
Yes I expected such bug will appear and I agree that now keyboard navigation in properties editor is bad (but was bas as well before!, I tried). Unfortunately, only way on our side to fix this is to revert shortcut for "Switch to Recent Window", which would be worse than current state. Ctrl+Tab is well accepted as window swithing mechanism, on the contrary to Ctrl+~, which was hard to discover and even not functioning for german, italian keyboards. Ability to use Ctrl+Tab is relatively big usability advantage. Note that we are providing far better navigation support than Swing's default, that's why we can override Swing's default shotcut. The way to go is to fix keyboard traversal in properties editor window, not change general shortcut. I tried to play with properties editor window, and it's not usable from keyboard no matter if Ctrl+Tab is mapped to our window switching or not (no way to move focus between table cells etc., multiple pressing Tab will end up in "nowhere" focus, even Ctrl+Tab will end in "nowhere" focus, no way to give focus back to the properties table). I'm closing as wontfix and I would recommend to enter bug against properties editor to fix their keyboard focus cycles, with note that Ctrl+Tab is reserved for winsys.
Verified - issue #48178 filed against properties module.