[PATCH 2/4] d3d9/tests: Avoid mode changes in d3d9ex' test_lost_device.

Wed Oct 15 03:20:45 CDT 2014

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 2014-10-15 08:31, schrieb Henri Verbeet:
> If you really wanted to avoid mode changes in test_lost_device()
> you'd have to change reset_device() as well, but the test actually
> tests for return codes after a mode change. It doesn't work on the
> testbot because IIRC it starts at 1024x768.
Right, the S_PRESENT_MODE_CHANGED should have alerted me. Do you have
any idea why a successful reset brings the device into this state?

Does reset_device call IDirect3DDevice9_Reset (instead of ResetEx)
intentionally? The IDirect3DDevice9_ part suggests that it is
unintentional, but in the context of the patch that added it
(2f307a14) it makes some sense.