State management in D3D

[Stefan Dösinger]

Am Montag 11 September 2006 18:41 schrieb H. Verbeet:
> On 11/09/06, Stefan Dösinger <stefandoesinger at gmx.at> wrote:
> > * Keep a list of dirty states for each gl context in use: We don't need
> > something as fancy as trees for that, a little array can do the job, like
> > this(example for render states, but can be used for all other stuff too):
>
> You would at least need to use a proper list. Consider an application
> that sets the same state multiple times. Note that what you're
> proposing is pretty similar (in basis) to the way we currently handle
> shader constants loading.
That's what I'd use the state.changed field for. Set it to TRUE when the state 
is first modified and to FALSE when it it applied to gl. Do not add the state 
to the list of changes whn state.changed == TRUE
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-devel/attachments/20060911/655a153c/attachment.pgp