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

Re: [Public WebGL] stencilFuncSeparate and stencilMaskSeparate



We just removed (enums) IMPLEMENTATION_COLOR_READ_FORMAT and TYPE, but
per my other email I realize that only one of the three entry points
is currently useless, so never mind.

-Ken

On Wed, Nov 3, 2010 at 4:44 PM, Vladimir Vukicevic <vladimir@mozilla.com> wrote:
> Hmm, I'd rather keep them in, in case extensions end up layering back some of the removed functionality.  We've generally left API entry points alone (e.g. hint()), no?
>
>    - Vlad
>
> ----- Original Message -----
>> The WebGL-specific limitations imposed on stencilFuncSeparate and
>> stencilMaskSeparate in
>> https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/doc/spec/WebGL-spec.html#6.5
>> imply that these entry points are now useless. If it isn't possible to
>> change the front or back reference or mask value to something
>> different than the other, then these entry points can't be used to
>> change those values for either face. Doing so must generate
>> INVALID_OPERATION. stencilFunc and stencilMask must be used instead.
>>
>> Rather than adding useless logic to WebGL implementations (see
>> https://bugs.webkit.org/show_bug.cgi?id=48669), should we just remove
>> these entry points for the time being?
>>
>> -Ken
>> -----------------------------------------------------------
>> 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: