The Khronos Group - a non-profit industry consortium to develop, publish and promote open standard, royalty-free media authoring and acceleration standards for desktop and handheld devices, combined with conformance qualification programs for platform and device interoperability.

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Ambiguous description of vgWritePixels/vgReadPixels

Together with the code sample ("The code ... is equivalent to the code ...", p. 129), where 'data' is not allocated before use, this sentence may be somewhat misleading to the conclusion that it allows direct access to the pixel data. Especially because vgGetPixels is described in active voice: "The vgGetPixels function retrieves pixel data ...". Shouldn't it therefore be "The vgReadPixels function copies pixel data from the drawing surface..."?

vgWritePixels is similar.

Of course it is clear what the function does if one reads the whole description. Sorry for nitpicking but a spec should be as unambiguous as possible, shouldn't it?