September 2011 - Wine-devel

Re: [PATCH 1/2] d3dx9: Do not allocate ctab memory, reuse the shader blob.
by Marvin 03 Sep '11

03 Sep '11

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 http://testbot.winehq.org/JobDetails.pl?Key=13934 Your paranoid android. === WVISTAADM (32 bit shader) === Failure running script in VM: The specified guest user must be logged in interactively to perform this operation

1 0

[patch] Fake display interface
by Jari Vetoniemi 02 Sep '11

02 Sep '11

Hello, I personally hate when applications decide to change my screen resolution without asking me, or some applications just won't run inside window. So I did fake display interface for the winex11.drv. It allows you to send any display resolution and frequency to the application, but it does not change resolution. It's small and simple patch, and won't probably ever be included into the mainline wine. However I'll post it here as it might be useful for some. To enable, create string key UseFakeDisp with value Y in H_C_U/Software/Wine/X11 Driver Default fake resolution is 800x600 60HZ, you can change default with registry keys FakeDispHeight, FakeDispWidth, FakeDispFreq You can also use env variable WINE_FAKEDISP=WIDTHxHEIGHT_FREQ (eg. WINE_FAKEDISP=1024x768_60) Might improve it later to use the same syntax for default resolution and allow multiple fake resolutions to be defined with ; separator. This is also useful for dual head setups where you may want to run game or application fullscreen on other monitor while still keeping the other alive. There is also interesting side effect: While some applications throw error or won't run on resolutions they don't support, some applications that don't support them still run with the resolution specified. Eg. I can run Ys games with 1440x900 resolution where they normally would not run, and they look great. Cheers.

2 1

Re: [PATCH] server: if a debugger is attached to a process, the DEBUG_ONLY_THIS_PROCESS should get set
by Alexandre Julliard 02 Sep '11

02 Sep '11

Bernhard Loos <bernhardloos(a)googlemail.com> writes: > @@ -825,6 +825,9 @@ int set_process_debug_flag( struct process *process, int flag ) > { > char data = (flag != 0); > > + process->create_flags = (process->create_flags & ~(DEBUG_PROCESS | DEBUG_ONLY_THIS_PROCESS)) > + | flag; > + I don't think this belongs in set_process_debug_flag, that's a different flag. Also I don't see what DEBUG_PROCESS is here for. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: 78256: Subject: [PATCH 1/5] wined3d: Print a FIXME for any flags passed to wined3d_surface_flip().
by buildbot＠kegel.com 02 Sep '11

02 Sep '11

The Buildbot has detected a failed build on builder runtests while building Wine. Full details are available at: http://buildbot.kegel.com/builders/runtests/builds/201 BUILD FAILED: failed shell_3 For more info about this message, see http://wiki.winehq.org/BuildBot

3 3

re: po: Fix some typography issues in the Czech translation.
by Dan Kegel 02 Sep '11

02 Sep '11

This patch found a bug in my scripts - it failed to grep the patch for sender and subject - but it looks like there might be something wrong with the patch itself, it doesn't apply here. Buildbot said: Full details are available at: http://buildbot.kegel.com/builders/runtests/builds/194 BUILD FAILED: failed git and here's what I get when I do it by hand: $ wget http://source.winehq.org/patches/data/78249 $ git apply 78249 typocz.patch:31: trailing whitespace. msgstr "Ověřte prosím, že název souboru byl zadán správně" typocz.patch:40: trailing whitespace. "Chcete ho vytvořit?" typocz.patch:49: trailing whitespace. "Chcete ho přepsat novým?" typocz.patch:54: trailing whitespace. msgstr "Nedovolený(é) znak(y) v cestě k souboru" typocz.patch:63: trailing whitespace. "Chcete ho přepsat novým?" error: patch failed: po/cs.po:210 error: po/cs.po: patch does not apply

3 4

Re: 78262: Subject: [2/6] dinput: Added enumerated devices to ConfigureDevices dialog (try 3)
by buildbot＠kegel.com 02 Sep '11

02 Sep '11

The Buildbot has detected a failed build on builder runtests while building Wine. Full details are available at: http://buildbot.kegel.com/builders/runtests/builds/208 BUILD FAILED: failed shell_3 For more info about this message, see http://wiki.winehq.org/BuildBot

3 2

Re: regedit: Remove the printing code
by Frédéric Delanoy 02 Sep '11

02 Sep '11

2011/9/1 André Hentschel <nerv(a)dawncrow.de>: > It does nothing (except confusing) > beside that i doubt someone wants to print registry hives That's not a reason IMHO. What should be done is fix the printing so it works like on windows (or put an error box: "not yet implemented", or similar)

1 0

Re: [PATCH 10/10] mshtml: Added more IHTMLElement_{put, get}_onclick tests
by Marvin 02 Sep '11

02 Sep '11

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 http://testbot.winehq.org/JobDetails.pl?Key=13915 Your paranoid android. === W2K3R2SESP2 (32 bit events) === Timeout === W2K8SE (32 bit events) === Timeout

1 0

Re: [PATCH 6/6] jscript/tests: Added decodeURI tests
by Marvin 02 Sep '11

02 Sep '11

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 http://testbot.winehq.org/JobDetails.pl?Key=13910 Your paranoid android. === WNT4WSSP6 (32 bit) === No test summary line found === W2KPROSP4 (32 bit) === No test summary line found === WXPPROSP3 (32 bit) === No test summary line found === W2K3R2SESP2 (32 bit) === No test summary line found === WVISTAADM (32 bit) === No test summary line found === W2K8SE (32 bit) === No test summary line found === W7PRO (32 bit) === No test summary line found === W7PROX64 (32 bit) === No test summary line found === W7PROX64 (64 bit) === No test summary line found

1 0

Re: [PATCH 4/6] jscript: Throw exception on error in JSGlobal_encodeURIComponent
by Marvin 02 Sep '11

02 Sep '11

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 http://testbot.winehq.org/JobDetails.pl?Key=13909 Your paranoid android. === WNT4WSSP6 (32 bit) === No test summary line found === W2KPROSP4 (32 bit) === No test summary line found === WXPPROSP3 (32 bit) === No test summary line found === W2K3R2SESP2 (32 bit) === No test summary line found === WVISTAADM (32 bit) === No test summary line found === W2K8SE (32 bit) === No test summary line found === W7PRO (32 bit) === No test summary line found === W7PROX64 (32 bit) === No test summary line found === W7PROX64 (64 bit) === No test summary line found

1 0