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.
JDK 1.4.1 Q-build 200302110810 SDI mode Open a source file and use Alt+G on a member e.g. method call that links to a different source file that is not already open in the editor. In most cases there is no focus i.e. when you start typing then nothing happens. Ctrl+3 fixes this. I have turned the editor toolbar off but that doesn't help. In adition to this, there is often no positioning in the new file: The window displays the top of the new file. If instead of pressing Ctrl+3, I switch back to the first file by clicking on its tab and press Alt+G again on the same method call then it works. This has been broken all the time for months. I first thought that this was covered and fixed by issue 27731 or issue 28416 but unfortunately it is a separate thing. IMHO this deserves a high priority because Alt+G is an essential navigation tool.
I cannot reproduce it on win2k. The lost of the focus happens only to a source file that is not already open in the editor. It seems that it is a duplicate of the issue #31087, where "Newly created file does not have focus / cursor" *** This issue has been marked as a duplicate of 31087 ***
I have some doubts although I might well be wrong that this is a duplicate of issue 31087. My doubts are only based on past experience (not evidence) where the issue I am seeing was diagnosed incorrectly before.
The description in #31087 says: "Same thing [focus lost] seems to happen after opening a file from the Explorer by selecting it and pressing Enter. If it is already open in a hidden tab, that tab is fronted and the cursor appears just fine; only when newly opening the pane does the problem occur." If you are using Alt+G and the declaration is in the file which is not open in the editor, then this file is open and it is the same situation as in the description above. If you think I am wrong, please reopen this bug.
Reopening. It seems that although it is similar problem like the issue #31087, it will be better to track it separately. The issue meets the criteria of P3, changing priority. Setting the target milestone to 4.0
Good news. It appears that the issue disappeared completely in build 3.5 dev q-build 200303131400. I have not had a single instance of the problem for a few days now while with the previous q-build, the problem was always there. I am changing this issue to fixed because I am not aware of others who share it with me. Thanks to the person who fixed it :)
:-) Perhaps it was the fix of the issue #31750
Thanks for the link Martin. It looks like issue #31750 has fixed even more than this. Look at issue 27333 if you wish. This appears to be partially fixed also. I'll make a comment there.
:-))) Finally I remember. I knew that I had already solved the similar problem like in the issue #31750, but I couldn't find the issue number, thus I created new one. I would say the issue #27333 is the same as issue #31750. But I will wait to your comments that you are going to add there ;-)
verified