-
Enhancement
-
Resolution: Unresolved
-
P4
-
None
-
5.0
-
generic
-
generic
A colleague (see comments for contact info) has pointed out that for Java
applications that interface to OpenGL, the current set of notifications about
surface changes that the JAWT provides as return codes from
JAWT_DrawingSurface::Lock is not sufficient. In particular, notifications about
the display configuration changing need to be provided so that (for example) the
OpenGL context can be destroyed and recreated if necessary. It isn't clear
whether the JAWT_LOCK_SURFACE_CHANGED return code describes this case.
Additionally, it is unclear whether the current JAWT_LOCK_SURFACE_CHANGED would
be sufficient to handle the case of a window being dragged from one screen to
another; however, it appears this isn't handled by the current AWT so this would
be a lower priority.
As should be apparent these ideas are still a little vague but it is clear that
at least some more documentation on these issues is needed.
applications that interface to OpenGL, the current set of notifications about
surface changes that the JAWT provides as return codes from
JAWT_DrawingSurface::Lock is not sufficient. In particular, notifications about
the display configuration changing need to be provided so that (for example) the
OpenGL context can be destroyed and recreated if necessary. It isn't clear
whether the JAWT_LOCK_SURFACE_CHANGED return code describes this case.
Additionally, it is unclear whether the current JAWT_LOCK_SURFACE_CHANGED would
be sufficient to handle the case of a window being dragged from one screen to
another; however, it appears this isn't handled by the current AWT so this would
be a lower priority.
As should be apparent these ideas are still a little vague but it is clear that
at least some more documentation on these issues is needed.