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 185170 - [a11y] SQL command execution (Ctrl+Shift+E) doesn't work
Summary: [a11y] SQL command execution (Ctrl+Shift+E) doesn't work
Status: RESOLVED INCOMPLETE
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 normal (vote)
Assignee: Jiri Rechtacek
URL:
Keywords: A11Y
Depends on:
Blocks:
 
Reported: 2010-04-28 10:45 UTC by Michael Nazarov
Modified: 2010-04-29 10:05 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 Michael Nazarov 2010-04-28 10:45:15 UTC
Unable to execute entered SQL command using shortcut. Toolbar button works fine.
Comment 1 Jiri Rechtacek 2010-04-28 13:03:31 UTC
  Product Version         = NetBeans IDE Dev (Build 201004280200) (#51757331153f)
  Operating System        = Linux version 2.6.31-20-generic running on amd64
  Java; VM; Vendor        = 1.6.0_18; Java HotSpot(TM) 64-Bit Server VM 16.0-b13; Sun Microsystems Inc.
  Runtime                 = Java(TM) SE Runtime Environment 1.6.0_18-b06
  Java Home               = /usr/local/share/java/jdk1.6.0_18/jre

Weird, it works for me on IDE build above. Besides C-S-E you can use common shortcut C-F6 which executes SQL file since NB6.7

Could you add more details about IDE which did work? Thanks
Comment 2 Michael Nazarov 2010-04-28 13:08:32 UTC
It was Beta 6.9 on Linux.
Ctrl+F6 doesn't work for me as well.

NetBeans IDE 6.9 Beta (Build 201004200117)
1.6.0_10-beta
Linux version 2.6.27-14-generic

Well, it might be old java issue. Let me check.
Comment 3 Jiri Rechtacek 2010-04-28 13:14:20 UTC
A correction, I meant Shift-F6 not Crtl-F6. My wrong.
Comment 4 Michael Nazarov 2010-04-28 13:48:03 UTC
Yes, Shift+F6 works. As for Ctrl+Shift+E -- it clears content of editor text area so it might be due to key combination conflict. I'll try to check and reassign to other area (?) if so.