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.
Product Version = NetBeans IDE Dev (Build 200409270901) Operating System = Windows 98 version 4.10 running on x86 Java; VM; Vendor = 1.4.2_03; Java HotSpot(TM) Client VM 1.4.2_03-b02; Sun Microsystems Inc. How to reproduce: - Create an empty userDir - Start NetBeans - Menu|Tools|Setup Wizard|Separate Windows Mode|Finish - Maximise the NetBeans IDE Toolbar window - Maximise the Projects Window - Maximise the Editor Window - [Ctrl+Shift+N] New Project - Select General Java Application - Project Name: JavaApplication1 - Project Location: C:\WINDOWS Finish - Maximise the Editor Window (Main.java was created ok) - code in void main(String[] args): noSuchMethod(); - Press [F9] to compile - Switch to and maximise the output window - Click on the link that highlights the error Expected result: The editor window should get focus and the cursor should be on the line where the error is. Actual result: The output window flickers and the editor window remains hidden.
It looks like some focus problem of windowing system or of a module that implements jump2error action. Feel free to reassign to correct module if I am wrong, thanks.
Not a P2, sorry, very rare and exotic scenario. Thanks for understanding.
Dear David, I accept your decision of setting the priority, because this is not my business. However why would this scenario be "very rare and exotic"? I disagree completely because: 1) This function, in the same scenario has worked in 3.6. 2) Clicking on a compiler error and having the source line dispayed is a very old traditional function. 3) Absolutely nothing here is "rare and exotic". 4) If you use these biased words and let them stand where they are then you could just as well close this issue because nobody would ever fix anything "very rare and exotic" because the words would suggest that fixing something "very rare and exotic" is against all business rules under which developers are supposed to operate. 5) This is a bug. As with any bug, this may have side effects, unknown consequences and root causes that are shared with other, higher priority bugs. brushing this aside as "rare and exotic" means ignoring the well-known anatomy of such bugs. 6) You are possibly correctly assuming that there are few SDI users. I can confidently say that the high number of bugs of this type in SDI mode would scare away from SDI any new SDI user. You are using circular logic here that may have the effect to effectively kill SDI mode.
fixed Checking in output2/src/org/netbeans/core/output2/ui/AbstractOutputPane.java; /cvs/core/output2/src/org/netbeans/core/output2/ui/AbstractOutputPane.java,v <-- AbstractOutputPane.java new revision: 1.28; previous revision: 1.27 done
The error is back in 4.1 early access 2.
4.1 EA 2 was branched of trunk on 2005-01-05. The fix by saubrecht was put into the main trunk on 2005-01-11. So the error is not back in EA2, but rather it is *still* in EA2. Please try with a recent development build or 4.1 Beta which will be released soon.
verified in NB4.1(200503281924)