Re: Direct3D thread safety review

[H. Verbeet]

On 18/05/07, Stefan Dösinger <stefandoesinger(a)gmx.at> wrote:
> * When a method needs locking, the lock is aquired after printing the trace,
> but before checking error conditions(like windows).
> * If a method doesn't need locking(e.g. unimplemented, or just a getter for
> static info(GetCaps), or QI / AddRef / Release), then the lock is not held
>
> Since ddraw, d3d8 and d3d9 need their own locking anyway, my plan is to
> implement locking in them and assume synchronised calls in wined3d - ie no
> wined3d locking. No 2 threads may call wined3d at the same time, and
> ddraw/d3d8/d3d9 have to take care of that. That keeps the code simpler.

Makes sense to me.