On Tue, Oct 11, 2016 at 7:26 PM, Tapani Pälli
wrote:
> it seems commit a40640f5303c9d03845459ecc364a3466d25cb5b fixed this same
> issue (and some other failing tests) so this patch is no longer needed
>
>
Thanks! Sorry for the noise, then.
>
> On 10/11/2016 09:29 AM, Tomasz Figa wrote:
>
>> [Fi
it seems commit a40640f5303c9d03845459ecc364a3466d25cb5b fixed this same
issue (and some other failing tests) so this patch is no longer needed
On 10/11/2016 09:29 AM, Tomasz Figa wrote:
[Fixing CC list.]
Ping. Would appreciate someone taking a look at this. Thanks in advance!
On Fri, Aug 26
[Fixing CC list.]
Ping. Would appreciate someone taking a look at this. Thanks in advance!
On Fri, Aug 26, 2016 at 2:57 AM, Chad Versace
wrote:
> Bump.
>
> On Thu 11 Aug 2016, Chad Versace wrote:
> > If check_textarget() determined that textarget was incorrect, it emitted
> > GL_INVALID_OPERATI
Bump.
On Thu 11 Aug 2016, Chad Versace wrote:
> If check_textarget() determined that textarget was incorrect, it emitted
> GL_INVALID_OPERATION. This is the correct behavior when target and
> textarget are mismatched but textarget is a valid textarget enum.
>
> When textarget is not a valid text
If check_textarget() determined that textarget was incorrect, it emitted
GL_INVALID_OPERATION. This is the correct behavior when target and
textarget are mismatched but textarget is a valid textarget enum.
When textarget is not a valid textarget enum, the GL spec requires that
GL_INVALID_ENUM be
