Henri Verbeet a écrit :
On 16 February 2010 12:25, Christian Costa <[email protected]> wrote:
Did you test this? "state" is supposed to be always 0. Also,
debug_d3dstate() is much more readable than the state number.
Yes I tested it. Indeed, it's 0.
Ok. I will send a new patch using debug_d3dstate. Thanks.
That also means there's really no point in printing it.
Ok. What about doing the following :
- when state is 0, don't print any message because it's normal
- when state is not 0, print the state to have a meaningfull message
