September 2014 - Wine-Devel

Re: [PATCH 07/10] wined3d: Do not minimize invisible windows.

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=9065 Your paranoid android. === w2000pro (32 bit device) === device.c:2146: Test failed: Got unexpected wparam 0 for message 6. === wxppro (32 bit device) === device.c:2146: Test failed: Got unexpected wparam 0 for message 6. === wvistau64 (32 bit device) === device.c:2146: Test failed: Got unexpected wparam 0 for message 6. === w2008s64 (32 bit device) === device.c:2146: Test failed: Got unexpected wparam 0 for message 6. === w7u (32 bit device) === device.c:2146: Test failed: Got unexpected wparam 0 for message 6. === w8 (32 bit device) === device.c:2341: Test failed: Expected message 0x6 for window 0x1, but didn't receive it. device.c:2346: Test failed: The focus window is active. device.c:2379: Test failed: Expected message 0x6 for window 0x1, but didn't receive it.

Sept. 25, 2014

Re: [PATCH 06/10] d3d8/tests: Test messages on focus loss.

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=9064 Your paranoid android. === w2000pro (32 bit device) === device.c:2146: Test failed: Got unexpected wparam 0 for message 6. === wxppro (32 bit device) === device.c:2146: Test failed: Got unexpected wparam 0 for message 6. === wvistau64 (32 bit device) === device.c:2146: Test failed: Got unexpected wparam 0 for message 6. === w2008s64 (32 bit device) === device.c:2146: Test failed: Got unexpected wparam 0 for message 6. === w7u (32 bit device) === device.c:2146: Test failed: Got unexpected wparam 0 for message 6. === w8 (32 bit device) === device.c:2321: Test failed: Expected message 0x6 for window 0x1, but didn't receive it. device.c:2326: Test failed: The focus window is active. device.c:2332: Test failed: Got unexpect width 640. device.c:2333: Test failed: Got unexpect height 480. device.c:2472: Test failed: Expected foreground window 000B00CA, got 0002004C. device.c:3114: Test failed: Expected wndproc 0x413050, got 0x413050.

Sept. 25, 2014

Re: d3d10core: Add support for map_type flags D3D10_MAP_READ, D3D10_MAP_WRITE_NO_OVERWRITE and D3D10_MAP_DISCARD. (try 2)

by Henri Verbeet

On 24 September 2014 17:06, Johannes Brandstätter <jbrandst(a)2ds.eu> wrote: > + DWORD wine_map_flags = wined3d_map_flags_from_d3d10_map_type(map_type); > > TRACE("iface %p, map_type %u, map_flags %#x, data %p.\n", iface, map_type, map_flags, data); > > - if (map_type != D3D10_MAP_READ_WRITE) > - FIXME("Ignoring map_type %#x.\n", map_type); > if (map_flags) > FIXME("Ignoring map_flags %#x.\n", map_flags); > > - return wined3d_buffer_map(buffer->wined3d_buffer, 0, 0, (BYTE **)data, 0); > + return wined3d_buffer_map(buffer->wined3d_buffer, 0, 0, (BYTE **)data, wine_map_flags); You don't really need the wine_map_flags variable here. > +DWORD wined3d_map_flags_from_d3d10_map_type(D3D10_MAP map_type) > +{ > + switch (map_type) > + { > + case D3D10_MAP_READ_WRITE: > + return 0; > + > + case D3D10_MAP_READ: > + return WINED3D_MAP_READONLY; > + > + case D3D10_MAP_WRITE_DISCARD: > + return WINED3D_MAP_DISCARD; > + > + case D3D10_MAP_WRITE_NO_OVERWRITE: > + return WINED3D_MAP_NOOVERWRITE; > + > + default: > + FIXME("Unhandled map_type %#x.\n", map_type); > + } > + > + return 0; You can just return in the default case.

Sept. 25, 2014

Re: [PATCH 04/10] d3d9/tests: Test messages on focus loss.

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=9062 Your paranoid android. === w2000pro (32 bit device) === device.c:3107: Test failed: Got unexpected wparam 0 for message 6. === wxppro (32 bit device) === device.c:3107: Test failed: Got unexpected wparam 0 for message 6. === wvistau64 (32 bit device) === device.c:3107: Test failed: Got unexpected wparam 0 for message 6. === w2008s64 (32 bit device) === device.c:3107: Test failed: Got unexpected wparam 0 for message 6. === w7u (32 bit device) === device.c:3107: Test failed: Got unexpected wparam 0 for message 6. === wvistau64 (64 bit device) === device.c:3107: Test failed: Got unexpected wparam 0 for message 6. === w2008s64 (64 bit device) === device.c:3107: Test failed: Got unexpected wparam 0 for message 6.

Sept. 25, 2014

Re: [PATCH] vbscript: Implemented RGB (try 3)

by Qian Hong

Hi Shuai, > Call ok(RGB(0, &h00001f&, &h0000f1&) = &hf11f00&, " I think Call ok(RGB(0, &h1f&, &hf1&) = &hf11f00&, "... is better and clearer.

Sept. 25, 2014

Re: Question about implementing a test for BCryptGetFipsAlgorithmMode

by Juan Lang

On Tue, Sep 23, 2014 at 2:47 PM, Kai Blaschke <kai.blaschke(a)kb-dev.net> wrote: > Kai, out of curiosity, is there an app that depends on being able to >> enable FIPS mode? >> --Juan >> > > The only real-life implementation I know about using the flag and actually > implementing FIPS is the MS .NET framework. Any application making use of > functionality in the System.Security.Cryptography namespace will be limited > to algorithms allowed in FIPS if the setting is enabled. You can try this > by enabling FIPS on Windows and playing Terraria, for example. In this > case, the application depends on FIPS mode being disabled. I see. In that case, I think you could just leave it disabled all the time, no? I don't see any sense in pretending to enable FIPS mode, personally. --Juan

Sept. 24, 2014

Re: [PATCH 4/5] d3d9/tests: Extend focus loss tests.

by Stefan Dösinger

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 2014-09-24 13:21, schrieb Henri Verbeet: > I suspect that adding tests for CreateAdditionalSwapChain() at > least would only be a modest amount of work, but without tests, > I'd expect that we should only minimize the fullscreen swapchain. > Or, put a different way, only the window that we received the > message for. The window we receive the message for is the focus window, and windows doesn't touch it at all (unless of course device window == focus window). -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJUIveCAAoJEN0/YqbEcdMwcxsP/0TFjZ9b0HWrMiLLm0Y6OTsk UML3T9heaoc2TlBWcHwOTfe9+D5Z7fqligSACJvkWuR6s+Rq33kYwGtVbM5FdQIy 2bT9c40LhZs8eAUECBKZP71+ACSgpnBR6TQBkC71nmmYX5pS44EDMxno8NKggRmn C9pJ0i0miEa++cOeGVGsRJxm7/Wg5A8x0k78t6NTWm84a8Mx67HILK+kpLUIujdT /f2StxINaE+MxApfZvSclE0nNc6Yb+IBdYLQvNGkXU7bL3JH0cvmAF4qNlqab+Ew 8qMcIRouf8fTpLnrNIVL+Hq/kxbOeRk1V6PlC0Lt1nhsNwO/jPsYfSbBEHkfxMEr BzQ6IdctSLI9W1V4YCCZAUC80TgsHy1Zcpb+r9h+2stNr6DRSvMxIgLY4vL6TLBr UkcZ7Xz84tVaO3s2rWJs9z2Ioe1ZdtxLvJJjn3IEHufcRvKsOQXGhEwhXvVsBoA8 Ix/Q+Q9839D+s2gqmUpHHkO/wq1LcMmQsBJkN/Y3PSQhmo+JlEC0qyp+LpWr6/XT mBrGfXMbFU8Opzm8//TeFeHXTaPcdd/0YaTWnsb4MccBoDvMAe1aVciXEDZiFrYs +nOTdWx4k0j95yvHFoCQ2RqSR2DQKKv5F9NkhBzi7pMktbHBNGdcupwE620r/VmZ AdxUvrAPrCObCmpe4DKA =vbb2 -----END PGP SIGNATURE-----

Sept. 24, 2014

Re: Wine Gecko 2.34-beta1 release

by Qian Hong

Hi Jacek, On Wed, Sep 24, 2014 at 9:42 PM, Jacek Caban <jacek(a)codeweavers.com> wrote: > We need a long term solution, which means > working on auto generated C/C++ bindings based on the new, WebIDL files. > I may write a separated mail about that if there is an interest. Thanks for the hard work on wine gecko! For the WebIDL topic, I believe it is interesting and appreciated :) BTW, as we discussed in MN, could we host a read-only public mailing list or similar things to monitor wine-gecko daily build failures? Looking forward to the new wine gecko release. -- Regards, Qian Hong - http://www.winehq.org

Sept. 24, 2014

Wine Gecko 2.34-beta1 release

by Jacek Caban

Hi all, After about a year since the last release, I'm happy to announce that we have a new Wine Gecko packages ready for testing. I'm not attaching a patch this time, because it's quite big and will change over next few weeks (I will be submitting some of those changes, so the patch would be invalid soon). I set up a Wine fork at [1] instead. It contains snapshot of my development tree on top of Wine, so be prepared for forced updates. Let me know if you'd prefer it to be in a different form. This update catches up on development made for 10 Firefox releases that happened meantime. There were many problems that needed to be solved for this to happen. There were tree wide changes breaking our build config as well as API changes, that needed to be fixed. We still have long term problem with API that we use for embedding Gecko (mostly DOM APIs) that is slowly removed from Gecko. We need a long term solution, which means working on auto generated C/C++ bindings based on the new, WebIDL files. I may write a separated mail about that if there is an interest. I decided to make this beta from Gecko tip at the point where it's branched. I usually waited until Gecko enters beta, but I want to catch up on development as much as possible this time. How the final release will look like depends on how testing goes. It will not be sooner than after a bit of Firefox beta. As usually, everything that uses MSHTML is an interesting testing target. Let me know if there are any problems. Thanks, Jacek [1] http://repo.or.cz/w/wine/wine-gecko.git

Sept. 24, 2014

Re: dpvoice: Add DirectPlay Voice Test (try 2)

by Alexandre Julliard

Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> writes: > Hi, > Fix errors on systems which don't have Direct Voice configured. > > Changelog: > dpvoice: Add DirectPlay Voice Test It doesn't work here: ../../../tools/runtest -q -P wine -T ../../.. -M dpvoice.dll -p dpvoice_test.exe.so voice && touch voice.ok voice.c:106: Test succeeded inside todo block: AddComponent(addr) with 0x00000000 voice.c:109: Test succeeded inside todo block: AddComponent(port)) with 0x00000000 voice.c:187: Test succeeded inside todo block: AddComponent(addr) with 0x00000000 voice.c:190: Test succeeded inside todo block: AddComponent(port)) with 0x00000000 make: *** [voice.ok] Error 4 -- Alexandre Julliard julliard(a)winehq.org

Sept. 24, 2014