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 109041 - Backspace key will not work.
Summary: Backspace key will not work.
Status: RESOLVED FIXED
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 6.x
Hardware: PC All
: P2 blocker (vote)
Assignee: Vitezslav Stejskal
URL:
Keywords: RANDOM
Depends on: 109038
Blocks:
  Show dependency tree
 
Reported: 2007-07-06 18:10 UTC by darrinps
Modified: 2007-11-05 13:44 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description darrinps 2007-07-06 18:10:42 UTC 
Added a new driver and created a connection.

Right clicked and selected Execute Command.

Went to the SQL Command area and typed SELET by mistake.  Tried to backspace to delete the T and nothing happened. 
Tried to do this several times but the backspace key does not work in that editor.

Created a new Java class and verified that the backspace does work there.
Comment 1 darrinps 2007-07-06 18:30:13 UTC 
After playing around with the format options, it started to work.
Comment 2 Andrei Badea 2007-07-09 14:45:19 UTC 
I recall seeing similar behavior once, but I don't think it is caused by the SQL editor itself. I have never seen this
before and there were no changes in the SQL editor in 6.0.

Reassigning to editor for evaluation.
Comment 3 Andrei Badea 2007-07-10 14:37:08 UTC 
Just experienced it in the Java editor. The movement (arrows, PgDn/Up, Home, etc.) keys don't work. Backspace doesn't
either. Delete does, but shows a wait cursor, as if it was an asynchronous action.
Comment 4 Petr Hrebejk 2007-07-10 15:51:34 UTC 
Probably a dupe of recently fixed bug.
Comment 5 Vitezslav Stejskal 2007-07-10 17:37:12 UTC 
Should be fixed now. The code for loading keybindings was cleaned up when fixing issue #109038. Please try again in a
dev build and reopen if it happens again.