November 2014 - Wine-Devel - list.winehq.org

Re: [PATCH 3/6] d3d8/tests: Test messages on focus loss (v2).

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=10309 Your paranoid android. === w8 (32 bit device) === device.c:1181: Test failed: TestCooperativeLevel failed, hr 0x88760868. device.c:1226: Test failed: Reset failed, hr 0x88760868. device.c:1228: Test failed: TestCooperativeLevel failed, hr 0x88760869. device.c:1232: Test failed: Got unexpected value 0 for D3DRS_LIGHTING. device.c:1239: Test failed: D3DVIEWPORT->X = 10, expected 0. device.c:1240: Test failed: D3DVIEWPORT->Y = 20, expected 0. device.c:1241: Test failed: D3DVIEWPORT->Width = 400, expected 800. device.c:1242: Test failed: D3DVIEWPORT->Height = 300, expected 600. device.c:1243: Test failed: D3DVIEWPORT->MinZ = 2.00000003e-001, expected 0. device.c:1244: Test failed: D3DVIEWPORT->MaxZ = 3.00000012e-001, expected 1. device.c:1249: Test failed: Screen width is 640, expected 800. device.c:1250: Test failed: Screen height is 480, expected 600. device.c:1256: Test failed: Back buffer width is 640, expected 800. device.c:1258: Test failed: Back buffer height is 480, expected 600. device.c:1288: Test failed: Screen width is 640, expected 1024. device.c:1289: Test failed: Screen height is 480, expected 768. device.c:2364: Test failed: Expected message 0x46 for window 0, but didn't receive it. device.c:2369: Test failed: The focus window is active. device.c:2373: Test failed: Got unexpected hr 0. device.c:2379: Test failed: Got unexpected hr 0. device.c:2393: Test failed: Got unexpected hr 0. device.c:2523: Test failed: Expected foreground window 000B00CA, got 0002004C. device.c:2898: Test failed: Expected device window style 0x14cf0000, got 0x4cf0000. device.c:2902: Test failed: Expected device window extended style 0x108, got 0x100. device.c:2925: Test failed: Failed to reset device, hr 0x88760868. device.c:2929: Test failed: Expected device window style 0x14cf0000, got 0x4cf0000. device.c:2933: Test failed: Expected device window extended style 0x108, got 0x100. device.c:3301: Test failed: Failed to reset device. device.c:3308: Test failed: Expected {0, 0, 1024, 768}, got {0, 0, 512, 384}. device.c:3316: Test failed: Expected wndproc != 0x411620.

Nov. 17, 2014

Re: cryptext: add stubs for CryptExtAddPFX/CryptExtAddPFXW

by Nikolay Sivov

On 17.11.2014 22:21, Austin English wrote: > +HRESULT WINAPI CryptExtAddPFX(LPCSTR filename) > +{ > + FIXME("stub: %s\n", debugstr_a(filename)); > + return ERROR_CALL_NOT_IMPLEMENTED; > +} Return type and error code don't match here. If it should be HRESULT use E_NOTIMPL, otherwise return type should be DWORD or similar.

Nov. 17, 2014

Re: [PATCH 2/2] mshtml: Added IHTMLStyleSheet::cssText tests.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=10298 Your paranoid android. === w2000pro (32 bit dom) === dom: unhandled exception c0000005 at 780104AC

Nov. 17, 2014

Re: [PATCH 2/7] d3d9/tests: Test messages on focus loss.

by Stefan Dösinger

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 2014-11-17 13:41, schrieb Alexandre Julliard: > Stefan Dösinger <stefandoesinger(a)gmail.com> writes: >> Which window manager do you use? > > fvwm. I can reproduce the problem. The reason seems to be that the WM_ACTIVTE(WA_INACTIVE) message is never sent because the window doesn't have focus due to the focus follows mouse behavior. I can reproduce the problem with KDE when I enable focus follows mouse, and fvwm works when I disable it there. I'll remove the WM_ACTIVATE message from the expected messages, that should fix the test. I'm still puzzled though why the remaining part of the tests work, and why test_lost_device works with focus follows mouse WMs. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJUagi1AAoJEN0/YqbEcdMwj6oP/ienrX/ZF/R+ARQRyGbZsLsg dQyvCvWKrqeuJ5N/b1rLAhVRCqplKh3SXt0uPFD+U2cikCk+x2A04seu59sPBuPj oMzvVNAXKyCT4Vvx1YGRfHfezkGahMs6+uJHQWrncNg3XoTuT6OdKiWJcDBetWn7 C/vvrno+gzskJou7ekBzRPdZbHYNhEODRc7lOWiBHMldsU0sWYO4oiaiwATi5Ks6 lBT+oMinPvNvQ/hCL9s2RkvNYlNg7QK9YvVNhyn5PbFxlNooC5LE/swxZwhBdEUd eOzVyxWrb3aR0szG5WUD5TsLAmblPfCAcz8cLmsQ5mkBBYxhLiRWzZcEmuwjjcEE ogDby7hB1v5NVtuAalouuhtdKGqMOa0fjZjNU541SSllT7zTAXlWKgym331kiblS wBtWwPT8+NQ1B4QwhR72eolyyhhHrtli9gdry6wHDLv6k0giqZHma+BmRg3nUeca nwjVpOKCl+r7lXbwqrnYK/C2z606zsY9VIGh5e2tFTUOxotv/CHmbstFqaRNVh+1 kmnkroWmYmmeVASIO/bPT4Y6qZIs9cYSh631eJxVo88Tucp+QXnLHSHjqy3KGm2T wAMEWRaT11AmsYTMNtbF62GtUZB36ayv1E5hKRvIrSnA2FOkR0fiF4T7CHtpydRR dxqXtLpXrxWm8bXFhuXI =6zKp -----END PGP SIGNATURE-----

Nov. 17, 2014

Re: [PATCH 5/5] d3d10core/tests: Port alpha_test() to d3d10core.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=10295 Your paranoid android. === w8 (32 bit visual) === visual.c:2635: Test failed: unexpected colortable on offscreen surface

Nov. 17, 2014

Re: [PATCH 2/7] d3d9/tests: Test messages on focus loss.

by Alexandre Julliard

Stefan Dösinger <stefandoesinger(a)gmail.com> writes: > Am 2014-11-17 10:16, schrieb Alexandre Julliard: >> ../../../tools/runtest -q -P wine -T ../../.. -M d3d9.dll -p d3d9_test.exe.so d3d9ex && touch d3d9ex.ok >> d3d9ex.c:1656: Tests skipped: This GPU supports SM3, skipping unsupported shader test. >> d3d9ex.c:1942: Test failed: Expected message 0x6 for window 0x1, but didn't receive it, i=0. >> d3d9ex.c:1964: Test failed: Got unexpected hr 0x8760878, i=0. >> d3d9ex.c:1942: Test failed: Expected message 0x6 for window 0x1, but didn't receive it, i=1. >> d3d9ex.c:1964: Test failed: Got unexpected hr 0x8760878, i=1. >> make: *** [d3d9ex.ok] Error 4 > Which window manager do you use? fvwm. -- Alexandre Julliard julliard(a)winehq.org

Nov. 17, 2014

Re: [PATCH 2/7] d3d9/tests: Test messages on focus loss.

by Stefan Dösinger

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 2014-11-17 10:16, schrieb Alexandre Julliard: > ../../../tools/runtest -q -P wine -T ../../.. -M d3d9.dll -p d3d9_test.exe.so d3d9ex && touch d3d9ex.ok > d3d9ex.c:1656: Tests skipped: This GPU supports SM3, skipping unsupported shader test. > d3d9ex.c:1942: Test failed: Expected message 0x6 for window 0x1, but didn't receive it, i=0. > d3d9ex.c:1964: Test failed: Got unexpected hr 0x8760878, i=0. > d3d9ex.c:1942: Test failed: Expected message 0x6 for window 0x1, but didn't receive it, i=1. > d3d9ex.c:1964: Test failed: Got unexpected hr 0x8760878, i=1. > make: *** [d3d9ex.ok] Error 4 Which window manager do you use? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJUaeydAAoJEN0/YqbEcdMws5sP/359g6vG9JdlySLbZgeaMQOS kJZPlp+txceKJAHBfjhSmd3pDgIE6nfXUnnuMdLMrxQHicp/zsFNX1iiVQw9cZLl TVLvWHu4637TUMXCYADjTSszY7ki9NTdhS9xUDB3hAtLOMdqIs5Se6//ttWWG0hQ BK2FEFU2ECn9k0vq+4swASeqPmi1YELgVu2JT7JnqI7rpQzN7Vhu48+tNr+Rx1rI zXq7TYWv7wOPz/z0Q+25W79e2ljY07nVV/oNzjL8YZLdo+kZv0R/CBt/qys21hDE fKR5QxamtNgUnXNt8bXLk8Gr8XDk9Ho9IF2c6Lw/te+sSJK6EuVoaoRhFmmZ6wpd k7fx+70vX2f3/9UynDNkyT61abm701xZ5mNJ4MclXoV2mg8u4WVRtGb1GtdDSQHB uYmgVPJwe0SOI7tUQpw1+7cyo0rxintD4yGvHowehSDaHn3KwrNcMmZUxf3eTXdo +dbrHwIw0CkEyWB6CKYNHev55H0sk6ksCQUJ8P64BR4/M4cuW9qvCXCN9qD4kHnz o/hLZL7+h9NexC4f2nFJwmQkIkFQnoMeb4tFEaxFDboGlXvllCTsu94dG8tXkSUx HfSD4+qtmwZNwIgxCfjGDsmkNzOHVnMOOrj7nHrsuZSttlAvl9bpIccM+0DB64iJ AHL67WRJ27y2ku/wEtrx =65GT -----END PGP SIGNATURE-----

Nov. 17, 2014

Re: [PATCH 2/7] d3d9/tests: Test messages on focus loss.

by Alexandre Julliard

Stefan Dösinger <stefan(a)codeweavers.com> writes: > Resolution changing behavior will be tested in a separate patch. > --- > dlls/d3d9/tests/d3d9ex.c | 277 ++++++++++++++++++++++++++++---------------- > dlls/d3d9/tests/device.c | 293 +++++++++++++++++++++++++++++++---------------- > 2 files changed, 375 insertions(+), 195 deletions(-) It doesn't work here: ../../../tools/runtest -q -P wine -T ../../.. -M d3d9.dll -p d3d9_test.exe.so d3d9ex && touch d3d9ex.ok d3d9ex.c:1656: Tests skipped: This GPU supports SM3, skipping unsupported shader test. d3d9ex.c:1942: Test failed: Expected message 0x6 for window 0x1, but didn't receive it, i=0. d3d9ex.c:1964: Test failed: Got unexpected hr 0x8760878, i=0. d3d9ex.c:1942: Test failed: Expected message 0x6 for window 0x1, but didn't receive it, i=1. d3d9ex.c:1964: Test failed: Got unexpected hr 0x8760878, i=1. make: *** [d3d9ex.ok] Error 4 -- Alexandre Julliard julliard(a)winehq.org

Nov. 17, 2014

Re: Update on MSNet

by Josh DuBois

On 11/14/14, 4:11 PM, Susan Cragin wrote: > You can now ask that or any other question. I just asked about the licenses, Page 6. > > http://blogs.msdn.com/b/dotnet/archive/2014/11/12/net-core-is-open-source.a… I think a post there answers the question about WPF and Winforms already: http://blogs.msdn.com/b/dotnet/archive/2014/11/12/net-core-is-open-source.a… <quote> Immo Landwerth [MSFT] 12 Nov 2014 5:08 PM @Myau: Does this mean yes or no to open-sourced WPF? We currently don't plan on open sourcing the client stacks, which includes Windows Forms as well as WPF. </quote>

Nov. 14, 2014

Re: Update on MSNet

by Susan Cragin

You can now ask that or any other question. I just asked about the licenses, Page 6. http://blogs.msdn.com/b/dotnet/archive/2014/11/12/net-core-is-open-source.a…

Nov. 14, 2014