[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] Proposed clarification in spec section 6.3 Framebuffer Object Attachments



Add two more: copyTexImage2D and copyTexSubImage2D.

Mo

On Fri, Oct 29, 2010 at 11:34 AM, Benoit Jacob <bjacob@mozilla.com> wrote:
> Hi,
>
> In section 6.3 we say that in case of conflicting attachments, "Calls which modify the framebuffer such as clear and drawArrays must generate an INVALID_FRAMEBUFFER_OPERATION error, and leave the contents of the framebuffer untouched."
>
> I suggest to replace "which modify" by "which access" and to list explicitly all four (I believe) such functions:
>  clear()
>  drawArrays()
>  drawElements()
>  readPixels()
>
> Indeed, in OpenGL, glReadPixels is generating INVALID_FRAMEBUFFER_OPERATION on incomplete framebuffers, so I guess that this should be no different.
>
> Cheers,
> Benoit
> -----------------------------------------------------------
> You are currently subscribed to public_webgl@khronos.org.
> To unsubscribe, send an email to majordomo@khronos.org with
> the following command in the body of your email:
>
>

-----------------------------------------------------------
You are currently subscribed to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email: