<div dir="ltr">Any suggestion on where to go from here? Does this need more discussion elsewhere or should a simple return WINED3DERR_INVALIDCALL do it?<br><br>I'm having trouble understanding where I should be checking for this error and returning an the invalid call.<br>
<br><div class="gmail_quote">On Mon, Jul 21, 2008 at 9:28 PM, Stefan Dösinger <<a href="mailto:stefan@codeweavers.com">stefan@codeweavers.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">> Ah, so it's essentially a recursive Reset call. My guess would be that<br>
> we don't want to allow that, but it requires some tests on native<br>
> win32 to verify. You could try returning WINED3DERR_INVALIDCALL when<br>
> Reset gets called from inside another Reset call, to see how the<br>
> application reacts to that.<br>
</div>This also raises another question regarding the window handling in wined3d:<br>
Are we allowed / supposed to modify the window size and position of the<br>
destination window the app supplies like this? A lot of apps seem to need<br>
that, otherwise the rendering is placed incorrectly or not visible because<br>
the window is hidden. However, it could be that Windows somehow renders<br>
correctly without changing the Window's properties.<br>
<br>
So the SetWindowPos() call in Reset() might be the wrong thing here. It is<br>
not entirely unexpected that the app calls Reset when it receives a Window<br>
position / size change. If the Window size changes, the app is supposed to<br>
reset the D3D device, otherwise the rendering output is stretched in<br>
Present(which can look kinda ugly)<br>
<br>
<br>
</blockquote></div><br></div>