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.
Summary: | Maximized window size wrong after screen resolution change | ||
---|---|---|---|
Product: | platform | Reporter: | ebakke |
Component: | JDK Problems | Assignee: | Antonin Nebuzelsky <anebuzelsky> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 7.2.1 | ||
Hardware: | PC | ||
OS: | Mac OS X | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
ebakke
2013-02-15 17:16:43 UTC
A new JDK bug filed. It will appear at http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=8019269 Closing wontfix on NetBeans side. ebakke, can you please test with jdk 8 and with jdk 7u40, and report back if the problem is also reproducible? https://jdk8.java.net/download.html https://jdk7.java.net/download.html Thanks. I'm on Mac OS X and my work laptop is also my personal machine. When at work, I'm hooked up to an external 1920x1200 Dell monitor, while at home I'm connected to a 2560x1440 Cinema Display. I run NB "full-screen". When I disconnect at work and reconnect at home, NB doesn't take up the whole screen on the external monitor. When I click on the "full-size" button, it expands in the horizontal direction to 2560, but doesn't do anything in the vertical direction. In order for me to get NB to resize completely, I have to restart the IDE :-( Wops, I forgot to respond to the previous comment. Will try on the newest JDK once I have a secondary monitor around again. I was able to reproduce the bug again today, then upgraded to 7u40 (Java: 1.7.0_40-ea; Java HotSpot(TM) 64-Bit Server VM 24.0-b55), and the bug seems to have disappeared. I will keep using 7u40 for a while and see if the bug resurfaces (especially in a multimonitor setting, which I don't currently have access to). Thanks for your help! -- Eirik (In reply to comment #5) > upgraded to 7u40 and the bug seems to have disappeared. > I will keep using 7u40 for a while and see if the bug resurfaces. Thanks |