• Type: Bug
• Component: javafx
• Sub-Component: graphics
• Affected Version: 8

• Priority: P3
• Status: Closed
• Resolution: Fixed

• Submitted: 2013-05-08
• Updated: 2015-06-17
• Resolved: 2013-05-15

JDK 8
8Fixed

Great. Close it. 10-09-2013 The issue is fixed. 10-09-2013 [~francis-] The last one, I think, is ok - https://jdk8.java.net/download.html 10-09-2013 Sure, could you send me a link to the JDK you'd like me to test against? 10-09-2013 [~francis-] Could you verify, that issue is fixed for retina-display now? 09-09-2013 Before my fix, all windows on a retina display (even ones created on a retina monitor) were zoomed. After my fix, they are correct if they are created on a retina display, but due to a different bug, we don't update Screen properties properly if you drag a window across screens. The original description of this problem was not related to switching screens - it was related to *all* retina windows being mangled. the new problem described by Sergio is specifically about switching screens. Jira issue RT-27958 addresses the issues of keeping the screen attributes up to date... 11-06-2013 I have just tried with build 1.8.0-ea-b92 and the problem is still there. Do not get why it is marked as fixed here. These are the steps I use to reproduce the problem: - Run the application in an external monitor. - Drag the window to the retina display monitor. - The window keeps the same size, but all the components are reduced to a fragment of their size. In the rest of the window there are random images (in b90 the rest of the window was empty in my tests). 08-06-2013 The issue with multiple monitors is a different problem. At least one aspect of this is covered by RT-27963. Jim can comment on whether that issue is likely to resolve the problem you are seeing. 08-06-2013 This will be in JDK 8-b91 21-05-2013 Fixed in the 8.0 graphics scrum with the following changeset: changeset: 3603:04486a607212 date: Wed May 15 16:56:23 2013 -0700 summary: Fix RT-30272: Oversized and incomplete components shown on retina displays. Note that perspective cameras are still not quite correct on retina displays as is discussed in RT-30204. 15-05-2013 A work-around for the short term is to run the program with "-Dprism.forcepowerof2=true" since the "power of 2 textures" processing performs the proper adjustments, but we will fix this soon in the normal case as well... 15-05-2013 This appears to be due to the new camera transform code not being aware of the scaling done on retina displays... 15-05-2013 Attaching test case from git repo... 15-05-2013