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.
Same issue as 41159 in NB3.6. NB4.0 IDE 2004 08 15 1800 JDK 1.5.0 beta2 NB 4.0 is not compliant to XP multiple monitor setup. (On the other hand, the argument goes, do we have to comply to Mr Gates & Co?) Nevertheless (since I'm more interested in having things work regardless) ... I have set my XP laptop screen as primary display and another monitor as extended display. I moved netbeans window to the extended display. I right clicked on the editor, the pop-up menu appeared at the extreme right of the primary display. I selected a range of text, right clicked on it hoping to copy it - but the menu appeared far away into the primary display, while my mouse cursor was at the extended display. This misbehaviour is not consistent ... I right-clicked on the output window, the pop-up menu appeared correctly on the extended display at the spot of mouse cursor. Now goes the kludgier misbehaviour - the top menu. Menu Where drop-down Item is displayed File Primary Edit Primary View Primary Build Primary Run Primary Refactor Extended (correctly) Versioning Sometimes here, sometimes there. Tools Extended (correctly) Window Extended (correctly) I wanted to list this feedback as a deficient feature. However, since the extended monitor is recogniseable but not consistently, I feel this is a defect. Obviously, two sets of algorithms are at work here, but there should consistently be only one. The first (erroneous) algorithm must have clipped its coordinates to the extremities of the primary display. The second (acceptable) algrorithm does not constrain itself to the primary display. I can't see how we could attribute this to unresolved bugs of JDK. If it is an issue with JDK, why is multi-monitor correctly recognised by some windows/menus?
See issue 25383 and issue 38375 - as a workaround, start NetBeans with the command-line argument -J-Dnetbeans.popup.no_hack=true *** This issue has been marked as a duplicate of 25383 ***
verified