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 208033 - shortcuts for 'step into' and 'step over' are routed differently
Summary: shortcuts for 'step into' and 'step over' are routed differently
Status: STARTED
Alias: None
Product: platform
Classification: Unclassified
Component: Actions (show other bugs)
Version: 7.1
Hardware: PC Linux
: P4 normal (vote)
Assignee: Jan Peska
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-02 23:38 UTC by tbrunhoff
Modified: 2014-02-04 05:53 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
ide layout (387.78 KB, image/png)
2012-02-02 23:38 UTC, tbrunhoff
Details
File menu popup after hitting F10 (184.76 KB, image/png)
2012-02-02 23:41 UTC, tbrunhoff
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tbrunhoff 2012-02-02 23:38:50 UTC
Created attachment 115463 [details]
ide layout

Setup:
- I have a dual screen where the main ide is on the left and there is an external window with various panes on the right (see first attachment), including the "internal" gdb output window.
- map F11 to "step into"
- map F10 to "step over"
- set a breakpoint
- start debugger
- when breakpoint is hit, press F11 (everything works as expected)
- now hit F10... the file menu pops up! (see second attachment)
- now click on the edit window, and then hit F10... step over now works correctly.

Product Version: NetBeans IDE Dev (Build 201201180601)
Java: 1.6.0_23; Java HotSpot(TM) Client VM 19.0-b09
System: Linux version 2.6.35.14-106.fc14.x86_64 running on i386; UTF-8; en_US (nb)
User directory: /home/toddb/.netbeans/dev
Cache directory: /home/toddb/.netbeans/dev/var/cache
Comment 1 tbrunhoff 2012-02-02 23:41:08 UTC
Created attachment 115464 [details]
File menu popup after hitting F10
Comment 2 soldatov 2012-02-04 12:30:03 UTC
TAB, F10, SHIFT-F10 and CTRL-TAB most important a11y keys in NetBeans.
Comment 3 tbrunhoff 2012-02-04 22:09:49 UTC
Well, I can imagine the chaos if I tried to set the tab key as a shortcut key (I certainly hope the options page would prevent me from doing so). F10, on the other hand, was easy enough to remap (and I didn't pay attention to its default value), so this probably means that some part of the ide has F10 hardwired to the File menu.

So that begs the question: if F10 is so important to NB, why is it an internal shortcut for bringing up the File menu? Alt-F works just fine and dandy :-)
Comment 4 soldatov 2012-02-05 09:16:01 UTC
Alt-F is a mnemonic in English locale. F10 activates first menu item.
NetBeans 7.1 speaks on 5 languages.
1) English
Alt-F calls File menu item. F10 calls File menu item.
2) Russian
Mnemonics doesn't work. F10 calls File menu item.
3) Portuguese
Alt-F doesn't work (File==Arquivo and Alt-F==Alt-A). F10 calls File menu item.
4) Chinese
Alt-F calls File menu item. F10 calls File menu item.
5) Japanese
Alt-F calls File menu item. F10 calls File menu item.
Comment 5 Egor Ushakov 2012-02-08 15:29:10 UTC
I do not know for sure, but when I reproduce it focus appears in quick search field, could it be that NB shortcuts are not propagated into that component?
Comment 6 Egor Ushakov 2012-02-08 15:29:31 UTC
please evaluate
Comment 7 Jaroslav Tulach 2012-05-18 09:38:09 UTC
F10 is hard coded and handled by Swing's JMenuBar. The bug is sort of related to bug 206908.
Comment 8 tbrunhoff 2012-05-18 18:53:14 UTC
I don't understand the downgrade to P4. That does not seem to match with the guidelines for P values.

FYI: In my case, and likely others, I map the debug hotkeys to the ones used in MS Visual Studio so that I can have a consistent environment (which is the point of being able to change hotkey association). So I have:
 - F10 - step over
 - F11 - step into
 - shift-F11 - step out
 - F5 - continue
 - shift-F5 stop debugging
 - F9 - toggle debug
Comment 9 Jaroslav Tulach 2012-05-21 11:16:54 UTC
(In reply to comment #8)
> I don't understand the downgrade to P4. That does not seem to match with the
> guidelines for P values.

Really? I can see "Minor usability problem" => P4.