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.

Bug 23142 - Tab, up-arrow, down-arrow keys not working in editor
Summary: Tab, up-arrow, down-arrow keys not working in editor
Status: VERIFIED FIXED
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: issues@editor
URL:
Keywords:
: 23143 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-05-04 06:44 UTC by kanderson
Modified: 2007-11-05 13:42 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kanderson 2002-05-04 06:44:18 UTC
Since 3.4 dev20020426, the tab, up-arrow, and down-arrow keys aren't working for me in the 
source editor.  Tab no longer inputs a tab but rather shifts focus around the components of the 
editor window.  Up-arrow and down-arrow mostly to do nothing in the text window, but they 
will sometimes send focus away from it, and they do operate the scroll bars and tab-pane tabs 
when focus has been shifted to those components.
Comment 1 kanderson 2002-05-05 00:33:12 UTC
I deleted my user directory and re-installed NB 3.4dev20020503; problems has abated for the moment.  I 
have another issue (#23143) of a keyboard problem apparently correlated with importing settings between 
NB versions.  Could these two be related, or duplicates?
Comment 2 kanderson 2002-05-05 00:49:23 UTC
Oops!  Make that first sentence "...; problem has abated...".  Apologies, my bad.
Comment 3 kanderson 2002-05-05 03:24:33 UTC
Didn't stay abated for long.  The problem returned after working with the IDE for awhile. And it's 
not just the source editor, the property sheet string editor is also affected.
Comment 4 kanderson 2002-05-11 05:50:15 UTC
*** Issue 23143 has been marked as a duplicate of this issue. ***
Comment 5 kanderson 2002-05-11 06:05:21 UTC
Found it.  I had a form based on a class which installs a custom FocusManager during construction.  When 
I opened that form in the form editor, the keys broke---my FocusManager just happens to co-opt the Tab, 
up-arrow, and down-arrow keys.  If I don't install the FocusManager at design-time, there is no problem.
Comment 6 kanderson 2003-07-11 03:37:56 UTC
Abandoned my custom KeyboardFocusManager long ago; haven't had a problem since.