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.
After Invoking and confirmation of OD, all shortcuts for cut and copy actions stop working. Steps to reproduce: ------------------- 1) Start IDE with fresh userdir 2) Open a j2se project 3) Open a java file 4) Invoke Tools|Options 5) Press OK --> Inside Editor, no shortcuts for above mentioned actions do work. This bug makes OD unusable for most users. [200511201900, JDK 1.6.0 beta, solaris 10/sparc]
Copy&Cut actions are disabled -> I am not disabling them. Should be some mystery in editor.
Looks like it has been interduced somewhere between 200511151900 and 200511161900.
Some more info. This issue is probably two bugs in one. 1) Editors in dialogs (e.g. breakpoint customization) do not handle the copy/paste/delete at all. No matter if pening the options dialog or not. After talk to Jarda it seems that there are two possible solutions for that. a) core will fix the actions to work in modal dialogs (those opened using DialogDisplayer) b) Hanz will set shortcuts for both actions global and editor 2) After opening OD and closing it using OK button. The shortcuts stop working for the opened editor. Newly opened files work fine. Seems like something what happens after clicing OK screws up the shortcuts in currently opened editors.
*** Issue 68976 has been marked as a duplicate of this issue. ***
I was able to reproduce for cut action. I have debugged it and it seems that the editor's cut action is disabled. The code that beeps is TopComponent:851. I'll check the editor's code responsible for updating of the enabled status.
I've finally found the problem - there are two physical instances of the BaseKit.CutAction. One of them gets its enabled status set properly but the other one is physically used by the o.o.actions.CutAction and the OD dialog probably triggers this somehow. See CloneableEditor:199 to see the delegation of the actions between editor and CE top component. Although there is a specialized construction that should avoid this problem (see BaseKit.cutActionDef) - it's only instance-level so if two kit instances get created it's out of luck. I'll make it on static level, that should help.
Fixed in trunk: Checking in libsrc/org/netbeans/editor/BaseKit.java; /cvs/editor/libsrc/org/netbeans/editor/BaseKit.java,v <-- BaseKit.java new revision: 1.145; previous revision: 1.144 I have attempted to ensure that this will not cause a memory leak and I've entered issue 69151 but it does not seem to be related to this integration.
Verified in 200511241900.