-
Bug
-
Resolution: Fixed
-
P2
-
1.4.0
-
beta
-
generic, x86
-
windows_98, windows_nt
-
Verified
To reproduce this bug:
Run the Dithering demo on 256 color on win98, then switch the color to any other higher color depth, for example 16, 24, 32 bit color depth. You will see the images on the canvases be messed up totally. This does not happen on winNT.
Run the test on 16 bit or higher color depth, then switch it to 256 color, you will see the color on the dithering canvas shows as different shapes, which is unacceptable. But by resizing the dithering frame, the dithering images will repaint and work fine. This does happen on winNT.
This bug did not happen on kestrel, so it is a regression.
------------------------
I've just updated the Synopsis of this bug to better reflect the actual
problem. The original bug described a problem when switching from 8-bit
mode to any other display mode. However, the problem is not tied to
8-bit mode, but instead to every mode. The real problem is that we do not
currently account for display switches in our code, so the rendering result
after a display mode switch is unpredictable (but generally incorrect).
There are several contributing factors behind this problem which have
all been filed as bugs and listed in the See Also area of this bug report.
chet.haase@Eng 2000-09-11
Run the Dithering demo on 256 color on win98, then switch the color to any other higher color depth, for example 16, 24, 32 bit color depth. You will see the images on the canvases be messed up totally. This does not happen on winNT.
Run the test on 16 bit or higher color depth, then switch it to 256 color, you will see the color on the dithering canvas shows as different shapes, which is unacceptable. But by resizing the dithering frame, the dithering images will repaint and work fine. This does happen on winNT.
This bug did not happen on kestrel, so it is a regression.
------------------------
I've just updated the Synopsis of this bug to better reflect the actual
problem. The original bug described a problem when switching from 8-bit
mode to any other display mode. However, the problem is not tied to
8-bit mode, but instead to every mode. The real problem is that we do not
currently account for display switches in our code, so the rendering result
after a display mode switch is unpredictable (but generally incorrect).
There are several contributing factors behind this problem which have
all been filed as bugs and listed in the See Also area of this bug report.
chet.haase@Eng 2000-09-11
- duplicates
-
JDK-4348489 Win32: DitherTest leaves garbage on the screen when colors switched from 16 to 8
-
- Closed
-
- relates to
-
JDK-4366691 deadlock condition on win32 during display mode switch
-
- Resolved
-
-
JDK-4366698 possible deadlock on Peer object on win32 during display mode switch
-
- Resolved
-
-
JDK-4366799 colormap sometimes wrong in 8-bit display mode (win32 only)
-
- Resolved
-
-
JDK-4351377 crash in screen rendering on MT apps on win32 after display mode switch
-
- Closed
-