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.
I've noticed that keyboard shortcuts to menu items around the UI seemed to work only sporadically in past releases, and lately have stopped working altogether. Take as examples deleting a file in explorer and deleting a component in the form editor: the Delete key is the shortcut for both. Under 3.3.1, my experience was that the Delete shortcut might work the first few times I used it, but would eventually stop working. Under the last couple of 3.4 development builds I've tried, the shortcut never works. The same is true of other shortcuts, such as Ctrl+X for Cut, Ctrl+C for copy, and Ctrl+V for paste. These keystrokes all work just fine for text input in the source editor and on property sheets, they just don't seem to work the menu shortcuts.
I deleted my user directory and re-installed NB 3.4dev20020503; problems has abated for the moment. I had previously imported my Forte 3.0 settings into NB 3.3.1, then my 3.3.1 settings into 3.4 dev20020426. It seems the symptoms got worse with each import.
Beg pardon, that first sentence should, of course read "...; problem has abated..."
Moving to core. Do you have any steps that 100% reproduce the behaviour? Also aren't you downgrading the jdk versions? Thanks.
CCing Trunk, maybe he will know more.
It's not an import-related problem. The shortcuts simply cease to function after I've been working in the IDE for a while. I'll try to pin down a more exact cause.
First and foremost, never, never, _never_ forget to add JDK and OS version whenever one file a bug. Without that information the bug report is INVALID
Guilty as charged. I'm running JDK 1.4 on Win2K Pro. I humbly beg forgiveness. I'm pretty sure this is related #23142, which I've determined to be the result of opening in the form editor a form whose constructor installs a custom FocusManager. Both sets of symptoms start simultaneously when I open the offending form, and haven't found a way to reproduce this issue in isolation from 23142. *** This issue has been marked as a duplicate of 23142 ***
Resolved for 3.4.x or earlier, no new info since then -> verified.
Resolved for 3.4.x or earlier, no new info since then -> closing.