Re: [PATCH 1/2] d3d8/tests: Don't check the foreground window if we're not in foreground.
On 8 October 2014 14:37, Stefan Dösinger stefan@codeweavers.com wrote:
These two patches fix test failures when the process is not in foreground that print changing error lines. This avoids generating warnings from the testbot whenever d3d8/tests/device.c is touched.
There are many more failures in d3d8:device when the test is not in foreground. Those failures write static lines and I'd prefer the testbot to be changed to run them in foreground instead.
Why does this affect d3d8, but not d3d9?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 2014-10-09 16:52, schrieb Henri Verbeet:
Why does this affect d3d8, but not d3d9?
Creating a fullscreen d3d9 device puts the process in foreground somehow, but creating a d3d8 device does not. I don't know which behavior is the bug and which is the feature. After creating a fullscreen device the focus window is the foreground window and SetForegroundWindow succeeds. A windowed device does not change the foreground window.
-
Henri Verbeet -
Stefan Dösinger