Small clarifications to EGL_ANDROID_presentation_time

Change-Id: I4365a981776ab0a5719c268258b87ff1418f9aeb
This commit is contained in:
Jesse Hall 2013-06-26 07:50:32 -07:00
parent 0077db94d5
commit 5ac6c0a3dd
1 changed files with 18 additions and 3 deletions

View File

@ -10,6 +10,7 @@ Contributors
Jamie Gennis
Andy McFadden
Jesse Hall
Contact
@ -21,7 +22,7 @@ Status
Version
Version 2, April 1, 2013
Version 3, June 26, 2013
Number
@ -92,7 +93,9 @@ Changes to Chapter 3 of the EGL 1.2 Specification (EGL Functions and Errors)
If the surface presentation time is successfully set, EGL_TRUE is
returned. Otherwise EGL_FALSE is returned and an appropriate error is
set.
set. If <dpy> is not the name of a valid, initialized EGLDisplay, an
EGL_BAD_DISPLAY error is generated. If <surface> is not a valid EGLSurface
then an EGL_BAD_SURFACE error is generated.
Issues
@ -110,9 +113,21 @@ Issues
System.nanoTime() method, or from the native clock_gettime function by
passing CLOCK_MONOTONIC as the clock identifier.
3. Should the presentation time be state which is used by eglSwapBuffers,
or should it be a new parameter to an extended variant of eglSwapBuffers?
RESOLVED: The presentation time should be new state which is used by
the existing eglSwapBuffers call. Adding new state composes better with
other (hypothetical) extensions that also modify the behavior of
eglSwapBuffers.
Revision History
#1 (Jamie Gennis, April 1, 2013)
#3 (Jesse Hall, June 26, 2013)
- Enumerated errors generated by eglPresentationTimeANDROID.
- Added Issue #3 with resolution.
#2 (Jamie Gennis, April 1, 2013)
- Clarified how uses that either do or do not need an absolute time should
be handled.
- Specified the eglPresentationTimeANDROID return value.