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.
[ BUILD # : 200509261930 ] [ JDK VERSION : 1.4.2_xx ] Choose Edit->Start Macro Recording. In the editor, hit the down arrow to move to the next line. Choose Edit->Stop Macro Recording. The 'Recorded Macro' dialog displays. Give the name 'Down Line'. Click the 'Add' button to add a key binding. Hit Ctrl-N. This is assigned to 'New File', but NB let me assign it anyway. The first time I did this, hitting Ctrl-N displayed the 'New File' dialog. I played around with it more (e.g. assigned Ctrl-Shift-Q to the shortcut), then it worked as expected. I added the macro again (caret-down) with the shortcut 'Ctrl-N' and NB finally gave me a warning 'Ctrl-N' is already assigned to 'New File'. I tried it yet again using 'Ctrl-N' and it didn't give me the warning and overrode 'New File'.
*** Issue 64693 has been marked as a duplicate of this issue. ***
This issue is still valid and very nasty, it is easy to override shortcuts without any warning, ie. Ctrl-S. Old TM -- changing to TBD. -------- NB 5.5beta b200605020200, JDK 1.6.0 b81 Solaris 10/Sparc
I guess the first time you don't get the warning the first time as Ctrl+N is a global shortcut (not editor specific). Once you assign the Ctrl+N shortcut in the first step then you start to get a warning. We need to examine the system shortcuts as well. Reassigning to Vita. IIRC MacroSavePanel is where the shortcut gets assigned. Unfortunately it's in editor/lib where the IDE specific things should not be used but IMHO the Stop macro recording action could be overriden in NbEditorKit in editor/src and MacroSavePanel could be subtyped to NbMacroSavePanel under editor/src or any other suitable solution could be found.
It looks like the problem is when assigning a keyboard shortcut to a macro right after it's been recorded. I can see two problems: 1. The 'Recorded macro' dialog does not check the global shortcuts. 2. It doesn't assign the shortcut properly, because the shortcut is not shown in the Tools|Options dialog. The Tools|Options shortcut editor on the other hand seems to work fine - assigns shortcuts correctly and checks the global shortcuts.
Fixed with #107385. The save macro dialog now uses the same mechanism as Tools-Options -> Keymap. Therefore it checks all assigned shortcuts and gives a warning when you try to reassign a shortcut, which is already assigned. If you confirm that the shortcut is reassigned (#1). It also refreshes the keymap model in Tools-Options, so the newly assigned shortcuts should be visible (#2).
*** Issue 65199 has been marked as a duplicate of this issue. ***