JDK-4702062 : Bad color/sizing of graphics objects after other fullscreen app run (win32 only)
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 1.4.0
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_nt
  • CPU: x86
  • Submitted: 2002-06-13
  • Updated: 2002-06-18
  • Resolved: 2002-06-18
Related Reports
Duplicate :  
Description
Run Notepad (demos/jfc/Notepad.jar)
Run DisplayModeTest (test/java/awt/Fullscreen/DisplayModeTest)
Select a different display mode than the current one (particularly the
screen depth) and activate it
Exit DisplayModeTest
Note how the text in Notepad is the wrong size (too wide or skinny, depending
on your original and SetDisplayMode display depths)


Comments
EVALUATION We're not doing all the right things on a display mode switch. In particular, we are not switching the GraphicsConfiguration object in an important situation. In WVolatileImage.displayChanged(), we only change out the graphicsConfig object if the surfaceDataHw object is not null. But in the case described, our app never rendered between the first switch (to the DisplayModeTest setting) and the second (when DisplayModeTest ends), so we never replaced the surfaceDataHw object. The end result is that we replace graphicsConfig the first time through but not the second, so when we get back control after DMT exits, we are stuck with the GraphicsConfiguration object in the intermediate DMT setting. The fix is easy; simply take the graphicsConfig changing code out of the (surfaceDataHw != null) condition so that we swap out the gc on every display mode switch. Then we will always be current to the new mode. ###@###.### 2002-06-13 Closing as a duplicate of 4636548; both problems come from the same base cause (improper resetting of surfaceData state during display change events) and should be fixed together. ###@###.### 2002-06-18
18-06-2002

WORK AROUND Resize window - this causes our offscreen images to get recreated and fixes and problems relating to out-of-date color model information. ###@###.### 2002-06-14
14-06-2002