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.5.0_05 ] I cannot reproduce the case every time but here are the steps 1. Open some file in the editor 2. Press ctrl and F and G buttons together quickly Two dialogs appear: find and go to line find has the input focus. 3.Press escape You cannot input with the keyboard Of course I never press f and g buttons together intentionally but sometimes you make mistakes.
Editor actions ? ... probably general problem of actions ... feel free to reassigne.
I'm able to reproduce the appearance of the two dialogs on my Linux FC3 but I'm still able to type from the keyboard then. Could you please describe your environment more in detail? Thanks. Romane could you please try to reproduce on Solaris? Thanks.
I suspect org.netbeans.editor.extKeyEventBlocker
My environment is solaris express 9/05 (build 21) on amd 64, JDS 3.0. netbeans and java version is indicated in the report
I am not able to invoke both Find and Go to line dialogs at once. My suspicion is that this is a known JDK bug on Linux and Solaris with blocked input. It occurs on more dialogs, but Find dialog is best known for this issue. Try to reproduce the issue just on the Find dialog. The workaround is to click on any button in the dialog but do not release the mouse button and move the mouse away from the button instead. Than you can type input again. I will try to find the JDK bug number.
It is probably this JDK bug: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6183877 It is fixed in Mustang. Please try to reproduce it with Mustang dev build. See also issue 50423 and issue 58166.
It seems like a dulicate of the issue #50423 But to be sure before I will make a duplicate, two questions: 1. Is input blocked in the find dialog or in go to class dialog? (if yes, please make a duplicate of issue #50423) OR 2. Is input blocked in editor? (if yes, try to reproduce the problem again with netbeans running with a debug flag -J-Dnetbeans.debug.editor.blocker=true and attach an output of console as attachement - you should see messages like: "attaching listener...", "removing listener from..." and potential "consuming keyPressed event...")
*** Issue 61390 has been marked as a duplicate of this issue. ***
Vano, I believe this issue could happen just after you have reproduced problem mentioned in issue #66217 Looking in the code of FindDialogSupport I see, there is stopping of KeyEventBlocker on focusGained or windowDeactivated. It seems it is not called in your case.
I don't want to use mustang, it's unstable. Is there a way to port the fix back to any jdk 5 update?
Why mustang? Try to reproduce this issue again with the debug flag -J-Dnetbeans.debug.editor.blocker=true on jdk 1.5.0_05 and attach an output. I think this can be reproduced by this scenario: 1. try to reproduce the issue #66217 2. If focus will not be in find dialog, close the dialog. 3. Keyboard should be locked...
Ok I followed your steps. Attaching output
Created attachment 26836 [details] output
Thanks for debugging. Yes, stopBlocking method is not called. (As a workaround try to open find dialog again and bring focus to find what text area...) Changing to P2
posibly fixed in [maintrunk] /cvs/editor/libsrc/org/netbeans/editor/ext/FindDialogSupport.java,v <-- FindDialogSupport.java new revision: 1.71; previous revision: 1.70 /cvs/editor/libsrc/org/netbeans/editor/ext/GotoDialogSupport.java,v <-- GotoDialogSupport.java new revision: 1.22; previous revision: 1.21 Because I was not able to reproduce it, could you please test and verify it? Thanks
So this will be in build 200511151900? If yes I'll be able to test it tomorow.
yes, it will be in tomorrow's build. Thanks in advance.
Tested on 200511171900