On 1/15/07, Brian Paul <[EMAIL PROTECTED]> wrote:
>
> Should probably do the same thing for ctx->FragmentProgram._Current too.
> Can you make that change, Jerome, and test?
>
> -Brian
>
I commited somethings similar, i haven't really a test case for
fragment program to trigger such bug for fragmen
Should probably do the same thing for ctx->FragmentProgram._Current too.
Can you make that change, Jerome, and test?
-Brian
Keith Whitwell wrote:
> Jerome - this looks good.
>
> Keith
>
> Jerome Glisse wrote:
>> Hi Keith,
>>
>> I have reported few days ago a bug, at least what i thought to be
Jerome - this looks good.
Keith
Jerome Glisse wrote:
> Hi Keith,
>
> I have reported few days ago a bug, at least what i thought to be
> a bug in handling of _Current when you bind a new vertex program
> (all this in shader/program.c ~line 1948). I think that whenever
> _Current == Current then
Hi Keith,
I have reported few days ago a bug, at least what i thought to be
a bug in handling of _Current when you bind a new vertex program
(all this in shader/program.c ~line 1948). I think that whenever
_Current == Current then you should also bind new program on
_Current and not only on Curre
