-
Enhancement
-
Resolution: Unresolved
-
P4
-
None
-
5.0
-
generic
-
generic
From discussions with ###@###.### and from looking at e.g. bug 4409931
it seems that the native code for Java2D and the AWT can handle screen depth
changes and multimonitor support (like a window moving from one monitor to
another) fairly well internally. However, applications which perform rendering
at the native level via the JAWT also require notification of these kinds of
events. It isn't clear whether the current bitmasks returned by
JAWT_DrawingSurface::Lock() are complete enough to describe all of these events
or whether these bitmasks are returned in all cases (for example, if the
application fetches a new JAWT_DrawingSurface object each frame instead of
fetching it once and repeatedly calling Lock/Unlock on it). Investigation is
needed to see whether the current APIs and implementation are sufficient.
it seems that the native code for Java2D and the AWT can handle screen depth
changes and multimonitor support (like a window moving from one monitor to
another) fairly well internally. However, applications which perform rendering
at the native level via the JAWT also require notification of these kinds of
events. It isn't clear whether the current bitmasks returned by
JAWT_DrawingSurface::Lock() are complete enough to describe all of these events
or whether these bitmasks are returned in all cases (for example, if the
application fetches a new JAWT_DrawingSurface object each frame instead of
fetching it once and repeatedly calling Lock/Unlock on it). Investigation is
needed to see whether the current APIs and implementation are sufficient.
- relates to
-
JDK-4409931 Switch color on the primary monitor from high to 256 cause multiscreen app crash
-
- Closed
-