On 1 April 2013 02:40, Sam Edwards <cfswo...@gmail.com> wrote: > I opted not to write ddraw tests. The existing ddraw window style tests > suggest that DirectDraw doesn't even set WS_VISIBLE when initializing a > (non-visible) window, which is very odd, so any new tests would have been > todo_wine anyway. Nonetheless, my changes to wined3d are minimal and > shouldn't affect ddraw's behavior. > I think it's ok for the tests to be todo_wine, but we do want ddraw coverage for this in the tests.
> + ZeroMemory( &d3dpp, sizeof(d3dpp) ); > + d3dpp.SwapEffect = D3DSWAPEFFECT_DISCARD; > + d3dpp.Windowed = TRUE; > + d3dpp.BackBufferWidth = screen_width / 2; > + d3dpp.BackBufferHeight = screen_height / 2; > + hr = IDirect3DDevice9_Reset(device, &d3dpp); > + ok(hr == D3D_OK, "IDirect3DDevice9_Reset failed with %08x\n", hr); I think you'll want to use reset_device() here. (Although I also just notice 766e732fb changed that to use screen_width x screen_height instead of 640x480, which is perhaps a bit of an unfortunate choice. It's fine to change reset_device() to use screen_width / 2 x screen_height / 2, if needed.)
