February 2015 - Wine-Devel - list.winehq.org

Re: [3/6] dxgi: Add missing dxgi 1.2 structs and interfaces [try 2]
by Stefan Dösinger Feb. 13, 2015

Feb. 13, 2015

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Martell, Looks pretty good, you missed two things: Am 2015-02-12 um 20:34 schrieb Martell Malone: > +interface IDXGIOutputDuplication : IDXGIObject { { placement. > + [in, out] UINT *_countmode, [in, out] UINT *mode_count; After that go ahead and resubmit patches 1-3. Again I recommend to have a look at git send-email. It's quite simple: What it essentially comes down to is adding this to wine_src/.git/config: [sendemail] from = Martell Malone <martellmalone(a)gmail.com> to = wine-patches <wine-patches(a)winehq.org> smtpserver = smtp.googlemail.com chainreplyto = false thread = false smtpencryption = tls smtpuser = martellmalone(a)gmail.com suppresscc = self The password was in my case automagically managed by the KDE keychain. Then you just do "git send-email origin". I recommend a sanity check with --dry-run first. Feels almost like pushing :-) . -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJU3bobAAoJEN0/YqbEcdMwCO4P/RlJWBhdZlgs2P8uYZosElTi ofQ2gQNX3Qo53vqwVgtNsmoFyAUHcqUX5euoACeDwjoGpOIe0cJ98ON2sJHADRqa nUPNjPrh/Xo/5WYhQs04hWGRbaFQTCgS+gjuld2ePqIgnAtl880G8GCptD0elcX2 blwa5nPOcxjzaqWX/BB159oioyfWy/IFC5B55Tb7WshSxpkSwgvWkIQsaO2ttF4B 3reG4z1xvgNJZfNH2MzND+d3EJrIq2iydr9dAS4ph1biEbSnlisFR1PwlVFXI7XT CGCmJD7eSM5hU3nRFWB8stEUSumwm8IPQXpcN8PSdzjcWwXuJ1lk6t4t2IlPIuET knXI4D+4XgduVKjBGDxp75fRDL6RmwaRckTnuCLUiCVDcr+bIPHuC1FKFpGxB4Vu q8FZ4wuo4vTegZ9niwi5FPZxc86zLvh3R1qv8mugLJPGbdl+6HYz6aZVtQRXewAe nDZg5nE/DxVrzFF/Ehg9gGHtmwkQeNpxbGK+vsv+qU1sqaod7+FQeTDkfCcs/Ola /7OIdJctBmjpPUGVamVTPUlrRwVNVSboZjDgwN32uBJ/opRFR331HreGL3Aj5UZ1 1EgCcv3tKC8YgiXF7YCrft8EtZFYu/PyZZm0KSjucpGbyviPf03pfNfaj5zPrlMv k1sPLynBjlhOiOO1HRI8 =3BtO -----END PGP SIGNATURE-----

2 6

Re: comctl32: SysDateTimePick32 control add Alt+down hot key like windows
by Marvin Feb. 13, 2015

Feb. 13, 2015

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=11515 Your paranoid android. === w2000pro (32 bit datetime) === datetime.c:795: Test failed: Expected MonthCal to be valid The test timed out === wxppro (32 bit datetime) === datetime.c:795: Test failed: Expected MonthCal to be valid === wvistau64 (32 bit datetime) === datetime.c:795: Test failed: Expected MonthCal to be valid The test timed out === w2008s64 (32 bit datetime) === datetime.c:795: Test failed: Expected MonthCal to be valid === w7u (32 bit datetime) === datetime.c:795: Test failed: Expected MonthCal to be valid The test timed out === w8 (32 bit datetime) === datetime.c:795: Test failed: Expected MonthCal to be valid The test timed out === wvistau64 (64 bit datetime) === datetime.c:795: Test failed: Expected MonthCal to be valid === w2008s64 (64 bit datetime) === datetime.c:795: Test failed: Expected MonthCal to be valid

1 0

3DC format test failures
by Stefan Dösinger Feb. 12, 2015

Feb. 12, 2015

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Matteo, I'm getting test failures in test_3dc_formats on various machines. Do you have any idea how to change the test without reducing its usefulness? It seems that we're seeing all possible swizzles on Windows. Geforce 9600, Windows 7: visual.c:16804: Test failed: Expected color 0x003f3f3f or 0x007f0000, got 0x007f7f7f, case 0. visual.c:16804: Test failed: Expected color 0x003f3f3f or 0x007f0000, got 0x007f7f7f, case 1. Radeon X1600, Windows 7: visual.c:16804: Test failed: Expected color 0x003f3f3f or 0x007f0000, got 0x007fffff, case 0. visual.c:16804: Test failed: Expected color 0x003f3f3f or 0x007f0000, got 0x007fffff, case 1. This one smells like an implementation problem: Wine or r300g. Looks like the draw fails. visual.c:16804: Test failed: Expected color 0x003f3f3f or 0x007f0000, got 0x00ff00ff, case 0. visual.c:16804: Test failed: Expected color 0x003f3f3f or 0x007f0000, got 0x00ff00ff, case 1. Cheers, Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJU3JdCAAoJEN0/YqbEcdMwK1EP/RqbMOXv8wkirSvrudJuzOdk /R68iLVBN3wJSuTnGz+gJz4RR3N3hdN3YeI3M+eTHoyqk/4JhKDKSE8M/W94ILEh BYH1m98D/EpphSwkiREcRma4eAFkC3K4U0zvxjOLkLq0BLaK6vAD6BuK97jORqmh i8oZS4vIpayq5DSvi+niNz5Wk/JLo8fu/6049kmY0r7asSYOcl8LEAgynUKRiKDT 6wyEsnC2Y5lKJ4zRMHGmxi/68R3CsxgAODIIW/JKC6/XskEydAM5TZ+h4lOLj0zU fzAkJRwBpwP4nS3XEI2bbMyA5ZLCLfa7Qo+otuUwU6vL6+6v6uwBRWNJtW+rQydk 2ceSfEj+FaoUqlqI8iySRmVkivYDKyp4wZL8/2WlAqstvC40cbYKRsa9YtMZFZF8 WpJip57t2pjAHdHCnAaA5qD7ulrjleAnMq7Yw3WqusA7NWPGWB8W02oKWuzfXYK3 C2byraxi5HQaHfxi5c60+WdJyzKGUhDn9PBdDRHmWJF77msk9x4ktl/DvtBF9XNZ X549ff8otGpJvczCDJZObvLU4qvQmPw6raHda+8qtGj4HcqVu3rq+WNv7+7zvmxk myLKNhYNhxSYzwwLHOTO3XGac2VJ/Gl4BEiBCn1chIAuZRGd2iWB4DMD0ptq4ovw 0CiBK8gTt/f5TsLTTzTl =ZgiK -----END PGP SIGNATURE-----

2 2

Problem in compiling wine on 64 bit system
by Ali Aminian Feb. 12, 2015

Feb. 12, 2015

Hello Changhui Liu thanks for your reply I finally managed to compile 32 bit wine on 64 bit Ubuntu 14.04 by installing a 32 bit Ubuntu under schroot. wine has a very good documentation on it but it would be better if the documentation said how to install 32 bit Ubuntu under schroot using "Ubuntu image", because downloading base Ubuntu system takes a little time if you don't have access to high speed internet. I also still have problem compiling wine the "shared WoW64 setup" way but i guess compiling the two version separately is sufficient.

1 0

Re: [PATCH] winepulse: add audio driver
by Andrew Eikum Feb. 12, 2015

Feb. 12, 2015

On Wed, Feb 11, 2015 at 10:15:28AM +0100, Maarten Lankhorst wrote: > This is a squash of all the winepulse related patches in repo.or.cz/w/wine/multimedia.git > Thanks Maarten. This has received a lot of testing by myself and by a large number of end-users, as many distros ship this by default. It will also materially improve the experience for users with high latency audio devices, especially USB devices, which the alsa-pulse plugin can't properly support (see [1] for a recent discussion). Pending any code review feedback, I'd like to see this merged. [1] http://lists.freedesktop.org/archives/pulseaudio-discuss/2014-October/02204… Andrew

1 0

wine 1.8 schedule
by Bessières, Marc Feb. 12, 2015

Feb. 12, 2015

Hello, According to [1] the criteria for Wine 1.8 is the CSMT patch set. At FOSDEM 2015 Stefan Doesinger said at one moment something like CSMT is not ready yet(I don't remember exactly how he formulated it as he wasn't talking specifically about CSMT). Wine 1.6 was released in July 2013 [2] so more than 18 months ago. And 1.6 took 15 months to be released. A lot of good work has been put into 1.7 branch > git rev-list wine-1.6..wine-1.7.35 | wc -l 7708 Currently still a lot of people are using the 1.6 branch. So on the forum Roseanne often has to ask people to upgrade from the stable branch to the development one. On bugzilla, the triagers very often have to close bugs reported on 1.6 and already close in 1.7 (latest example a few hours ago [3]) I do not deny that the work to release is negligible (for example I see that in bugzilla there are 71 bugs tags as regressions [4] for 1.7). Maybe not having the CSMT patch set would also not be the best PR possible. But the number of commits and bugs solved is clearly good PR and good for the users. I'm not asking for an immediate release for sure, but to start a discussion on: - maybe a change of criteria for wine-1.8 - a rough schedule for wine-1.8 in order to give most of Wine users the best of what is being produced by you guys. Cheers, Marc [1] http://wiki.winehq.org/WineReleaseCriteria [2] https://www.winehq.org/news/2013071801 [3] https://bugs.winehq.org/show_bug.cgi?id=38023 [4] https://bugs.winehq.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&b…

6 6

Re: cryptui: add CryptUIWizDigitalSign stub
by Dmitry Timoshkov Feb. 12, 2015

Feb. 12, 2015

Austin English <austinenglish(a)gmail.com> wrote: > +33 stdcall CryptUIWizDigitalSign(long ptr wstr ptr ptr) Appropriate .spec type for HWND is not ptr. -- Dmitry.

3 4

Re: [PATCH 6/6] wined3d: Set z = 0.0 via the projection matrix instead of depth clamping.
by Matteo Bruni Feb. 12, 2015

Feb. 12, 2015

2015-02-11 21:53 GMT+01:00 Stefan Dösinger <stefan(a)codeweavers.com>: > This works on cards that don't implement ARB_depth_clamp like r500 > cards. > > Note that texturing is influenced by position.w, not position.z. > --- > dlls/wined3d/directx.c | 7 ------- > dlls/wined3d/state.c | 33 ++++++++++----------------------- > dlls/wined3d/wined3d_gl.h | 2 -- > 3 files changed, 10 insertions(+), 32 deletions(-) It's probably hard to measure and not going to really matter in practice but toggling the depth clamping (where supported) might be slightly faster than updating the projection matrix. I'm not NACKing the patch though.

2 2

Re: crytpui: add CryptUIWizDigitalSign stub (try 2)
by Dmitry Timoshkov Feb. 12, 2015

Feb. 12, 2015

Austin English <austinenglish(a)gmail.com> wrote: > +33 stdcall CryptUIWizDigitalSign(long ptr wstr ptr ptr) ... > +BOOL WINAPI CryptUIWizDigitalSign(DWORD flags, HWND parent, LPCWSTR title, PCCRYPTUI_WIZ_DIGITAL_SIGN_INFO info, > + PCCRYPTUI_WIZ_DIGITAL_SIGN_CONTEXT *context) What's the difference with previous version? -- Dmitry.

1 0

Re: [PATCH 5/6] d3d8/tests: Test rhw depth clip with z enabled but no depth buffer set.
by Marvin Feb. 11, 2015

Feb. 11, 2015

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=11495 Your paranoid android. === w8 (32 bit visual) === visual.c:4139: Test failed: Expected color 0x0000ff00 at 80, 60, got 0x00ff0000. visual.c:4139: Test failed: Expected color 0x0000ff00 at 560, 60, got 0x00ff0000. visual.c:4139: Test failed: Expected color 0x0000ff00 at 80, 180, got 0x00ff0000. visual.c:4139: Test failed: Expected color 0x0000ff00 at 560, 180, got 0x00ff0000. visual.c:4139: Test failed: Expected color 0x0000ff00 at 80, 300, got 0x00ff0000. visual.c:4139: Test failed: Expected color 0x0000ff00 at 560, 300, got 0x00ff0000. visual.c:4139: Test failed: Expected color 0x0000ff00 at 80, 420, got 0x00ff0000. visual.c:4139: Test failed: Expected color 0x0000ff00 at 560, 420, got 0x00ff0000.

1 0