[r35, or dev apr 09] Start NB with fresh user dir.
Click on 'examples' in Explorer. Ctrl-F. Type
"colorprev" in search field, hit Enter. Select
ColorPreview and ColorPreviewBeanInfo in search
results list. Press Sh-F10 -> Open to open these
files in the editor, then Alt-C to close search
results window. Now try to use Alt-Left or
Alt-Right to switch tabs - does not work, just
beeps. Property sheet is empty, all node actions
off, etc. Yet the cursor is blinking in the editor
window. It seems that the editor window correctly
has KB focus - and there is a blue bar around it -
yet there was no notification to other components
that the editor window is now the selected TC or
mode or whatever.
See screenshot. I have just selected a block of
text with shift + arrow keys, and pressed Alt-W.
Note that the Window menu does not have "Source
Editor" selected, nor is Next View/Prev View
enabled, nor various node actions in the toolbar.
Note that if in my Linux window manager (Sawfish,
sloppy focus) you press Alt-TAB twice to focus
some other app and back, then NetBeans realizes
that the editor is focused and everything begins
working again. Or if you press Ctrl-2 Ctrl-3, or
click on another part of the NetBeans MDI window
and back to the editor, etc., the situation is
I have observed a similar bug in the Explorer,
where e.g. the Filesystems tab appears to have
focus yet Alt-Left and Alt-Right are not working.
However I do not know how to reproduce that.
User impact: temporary confusion that keyboard
shortcuts are not apparently working, actions are
Created attachment 9936 [details]
It is strange because winsys performs TopComponent activation when it
receives FOCUS_GAINED event for given TopComponent (or any of its
subcomponent) and when focus is in editor TopComponent should be
activated too. Need to investigate.
Because Window System v1 will not be supported from now by our team, all old
winsys issues (now "core/window system v1" issues) are going to be closed as
Changes in API which emerged both from UI spec
and problems with adjusting to the older API are described in the document
It shows also recommends how the client code should be adjusted to the new
If you think this issue apply also to the new winsys then change the
subcomponent (to "core/window system") and REOPEN it.
issue doesn't apply to new window system - verified