[PATCH] user32/test: Start the AdjustWindowRectExForDpi() from a known state.

[Francois Gouget]

rect and rect2 have been modified by the previous test by the time we
get to AdjustWindowRectExForDpi(). This makes interpreting the traces
harder in case of a failure. So reset them to the same starting state
as for the AdjustWindowRectEx() test.

Signed-off-by: Francois Gouget 
---

This does not fix the Windows 10 1709+ failures :-(

dlls/user32/tests/win.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/dlls/user32/tests/win.c b/dlls/user32/tests/win.c
index 78dc55f00a8..b9309a8cba6 100644
--- a/dlls/user32/tests/win.c
+++ b/dlls/user32/tests/win.c
@@ -5407,6 +5407,8 @@ static void test_AWR_flags(void)
                 style, exstyle, wine_dbgstr_rect( &rect ), wine_dbgstr_rect( &rect2 ));
             if (pAdjustWindowRectExForDpi)
             {
+                SetRect( &rect, 100, 100, 200, 200 );
+                rect2 = rect;
                 pAdjustWindowRectExForDpi( &rect, style, FALSE, exstyle, 192 );
                 wine_AdjustWindowRectExForDpi( &rect2, style, FALSE, exstyle, 192 );
                 ok( EqualRect( &rect, &rect2 ), "%08x %08x rects do not match: win %s wine %s\n",