December 2013 - Wine-Devel - list.winehq.org

Re: winex11: Implement X11DRV_FLUSH_GDI_DISPLAY ExtEscape command

by Alexandre Julliard

Sebastian Lackner <sebastian(a)fds-team.de> writes: > Calling MsgWaitForMultipleObjects could help as a workaround for this > patch, but would be a relatively large overhead: wineserver calls, > listening for input events, ... - even though in windowless mode the > plugin doesn't have any window, but just an hDC to draw on. The > functions are called for every video frame, thats why I want to keep the > overhead as small as possible. You'll still need to check for events one way or another. > Do you think it would be better to expose those functions > (X11DRV_SET_DRAWABLE, X11DRV_FLUSH_GDI_DISPLAY) somehow else? No, not really. -- Alexandre Julliard julliard(a)winehq.org

Dec. 31, 2013

Re: winex11: Implement X11DRV_FLUSH_GDI_DISPLAY ExtEscape command

by Sebastian Lackner

Well, I cannot get rid completely of private escapes since the function X11DRV_SET_DRAWABLE also is not available public, and I also don't know any alternative to this command (is there any?). I know that the structs for these private functions might change at any time, but thats a risk where we also have not really any alternative choice (except adding wrapper functions, but also not really a good solution). Calling MsgWaitForMultipleObjects could help as a workaround for this patch, but would be a relatively large overhead: wineserver calls, listening for input events, ... - even though in windowless mode the plugin doesn't have any window, but just an hDC to draw on. The functions are called for every video frame, thats why I want to keep the overhead as small as possible. Do you think it would be better to expose those functions (X11DRV_SET_DRAWABLE, X11DRV_FLUSH_GDI_DISPLAY) somehow else? I can live with the risk that the interface might change in the future ;-) Sebastian Am 31.12.2013 12:33, schrieb Alexandre Julliard: > Sebastian Lackner <sebastian(a)fds-team.de> writes: > >> This patch implements an additional ExtEscape command >> X11DRV_FLUSH_GDI_DISPLAY, which can be used by external applications in >> order to flush all drawing operations to the Xserver. >> >> This patch is necessary for a new feature of Pipelight: In NPAPI >> windowlessmode the browser provides an X11 drawable, and expects the >> plugin (= the wine application) to draw on it. The current >> implementation uses CreateDCA() to create a new hDC and then >> X11DRV_SET_DRAWABLE to draw on an arbitrary X11 drawable. The additional >> command implemented in this patch is required to ensure that the drawing >> is finished before the PAINT event returns. Normally an XSync would be >> even better, but a lot of testing shows that XFlush is also sufficient >> (and faster), thats why we decided to use this approach. > > You should call MsgWaitForMultipleObjects or some similar function > instead of adding private escapes. >

Dec. 31, 2013

Re: [2/2] ntdll: Dynamically grow buffer in read_changes_apc

by Alexandre Julliard

André Hentschel <nerv(a)dawncrow.de> writes: > --- > dlls/ntdll/directory.c | 35 +++++++++++++++++++++++++++-------- > 1 file changed, 27 insertions(+), 8 deletions(-) You can't allocate memory inside an APC callback. -- Alexandre Julliard julliard(a)winehq.org

Dec. 31, 2013

Re: winex11: Implement X11DRV_FLUSH_GDI_DISPLAY ExtEscape command

by Alexandre Julliard

Sebastian Lackner <sebastian(a)fds-team.de> writes: > This patch implements an additional ExtEscape command > X11DRV_FLUSH_GDI_DISPLAY, which can be used by external applications in > order to flush all drawing operations to the Xserver. > > This patch is necessary for a new feature of Pipelight: In NPAPI > windowlessmode the browser provides an X11 drawable, and expects the > plugin (= the wine application) to draw on it. The current > implementation uses CreateDCA() to create a new hDC and then > X11DRV_SET_DRAWABLE to draw on an arbitrary X11 drawable. The additional > command implemented in this patch is required to ensure that the drawing > is finished before the PAINT event returns. Normally an XSync would be > even better, but a lot of testing shows that XFlush is also sufficient > (and faster), thats why we decided to use this approach. You should call MsgWaitForMultipleObjects or some similar function instead of adding private escapes. -- Alexandre Julliard julliard(a)winehq.org

Dec. 31, 2013

Re: Status of WineD3D on Windows

by Stefan Dösinger

Am 30.12.2013 um 12:15 schrieb Peter Lehmkuhle <plehmkuhle(a)googlemail.com>: > On http://wiki.winehq.org/WineD3DOnWindows it is written that "DirectDraw [..] can't be used at this point due to a conflict with opengl32.dll.“ It seems that the wiki is down at the moment, so I can’t check what’s on this page. I am not aware of any "official“ Windows wined3d builds. The code compiles fine, and I am using this fact for testing every now and then. I even have a hacky Visual Studio setup to compile the code with msvc without any need for a bash installation. What are you trying to do with wined3d on Windows? Re ddraw, we did not take any steps to resolve the ddraw.dll-opengl32.dll dependency cycle as it has never been a priority. Patches are welcome :-) .

Dec. 31, 2013

Re: [PATCH 1/4] ole32: Fix parameter validation for CreateClassMoniker()

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://newtestbot.winehq.org/JobDetails.pl?Key=3908 Your paranoid android. === wvista (32 bit moniker) === moniker: unhandled exception c0000005 at 00424509 === w2008s64 (32 bit moniker) === moniker: unhandled exception c0000005 at 00424509 === w7pro64 (32 bit moniker) === moniker: unhandled exception c0000005 at 00424509 === w2008s64 (64 bit moniker) === moniker: unhandled exception c0000005 at 000000000041F2CA === w7pro64 (64 bit moniker) === moniker: unhandled exception c0000005 at 000000000041F2CA

Dec. 31, 2013

Re: kernel32/tests: Add test for FindFirstFileA

by Zhenbo Li

2013/12/30 Zhenbo Li <litimetal(a)gmail.com>: > As MSDN[1] mentioned, "This parameter should not ... end in a trailing > backslash (\)." So I think I should add this test case. > > [1]: > http://msdn.microsoft.com/en-us/library/windows/desktop/aa364418%28v=vs.85%… > --- > dlls/kernel32/tests/file.c | 15 +++++++++++++++ > 1 file changed, 15 insertions(+) > Sorry, I made a mistake while reading the previous code. Please reject this patch, and I'll send another patch later. Sorry for this inconvenience.

Dec. 31, 2013

Re: winhttp/tests: Constify a character string

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://newtestbot.winehq.org/JobDetails.pl?Key=3905 Your paranoid android. === w7pro64 (32 bit winhttp) === winhttp.c:859: Test failed: failed to send request 12175

Dec. 31, 2013

Re: [4/4] ws2_32: Cope with invalid hints in getaddrinfo/GetAddrInfoW

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://newtestbot.winehq.org/JobDetails.pl?Key=3900 Your paranoid android. === wxppro (32 bit sock) === sock.c:554: Test failed: oob_server (c0): unexpectedly at the OOB mark: 0 === wvista (32 bit sock) === sock.c:5410: Test failed: test 0: expected one result when hints are used for localhost sock.c:5410: Test failed: test 1: expected one result when hints are used for localhost sock.c:5410: Test failed: test 2: expected one result when hints are used for localhost sock.c:5410: Test failed: test 3: expected one result when hints are used for localhost sock.c:5410: Test failed: test 8: expected one result when hints are used for localhost sock.c:5410: Test failed: test 9: expected one result when hints are used for localhost sock.c:5410: Test failed: test 10: expected one result when hints are used for localhost sock.c:5410: Test failed: test 11: expected one result when hints are used for localhost sock.c:5410: Test failed: test 20: expected one result when hints are used for localhost sock.c:5410: Test failed: test 21: expected one result when hints are used for localhost sock.c:5518: Test failed: test 0: expected one result when hints are used for localhost sock.c:5518: Test failed: test 1: expected one result when hints are used for localhost sock.c:5518: Test failed: test 2: expected one result when hints are used for localhost sock.c:5518: Test failed: test 3: expected one result when hints are used for localhost sock.c:5518: Test failed: test 8: expected one result when hints are used for localhost sock.c:5518: Test failed: test 9: expected one result when hints are used for localhost sock.c:5518: Test failed: test 10: expected one result when hints are used for localhost sock.c:5518: Test failed: test 11: expected one result when hints are used for localhost sock.c:5518: Test failed: test 20: expected one result when hints are used for localhost sock.c:5518: Test failed: test 21: expected one result when hints are used for localhost === w2008s64 (32 bit sock) === sock.c:554: Test failed: oob_server (750): unexpectedly at the OOB mark: 0 sock.c:5410: Test failed: test 0: expected one result when hints are used for localhost sock.c:5410: Test failed: test 1: expected one result when hints are used for localhost sock.c:5410: Test failed: test 2: expected one result when hints are used for localhost sock.c:5410: Test failed: test 3: expected one result when hints are used for localhost sock.c:5410: Test failed: test 8: expected one result when hints are used for localhost sock.c:5410: Test failed: test 9: expected one result when hints are used for localhost sock.c:5410: Test failed: test 10: expected one result when hints are used for localhost sock.c:5410: Test failed: test 11: expected one result when hints are used for localhost sock.c:5410: Test failed: test 20: expected one result when hints are used for localhost sock.c:5410: Test failed: test 21: expected one result when hints are used for localhost sock.c:5518: Test failed: test 0: expected one result when hints are used for localhost sock.c:5518: Test failed: test 1: expected one result when hints are used for localhost sock.c:5518: Test failed: test 2: expected one result when hints are used for localhost sock.c:5518: Test failed: test 3: expected one result when hints are used for localhost sock.c:5518: Test failed: test 8: expected one result when hints are used for localhost sock.c:5518: Test failed: test 9: expected one result when hints are used for localhost sock.c:5518: Test failed: test 10: expected one result when hints are used for localhost sock.c:5518: Test failed: test 11: expected one result when hints are used for localhost sock.c:5518: Test failed: test 20: expected one result when hints are used for localhost sock.c:5518: Test failed: test 21: expected one result when hints are used for localhost sock: unhandled exception c0000005 at 00000000 === w7pro64 (32 bit sock) === sock.c:5410: Test failed: test 0: expected one result when hints are used for localhost sock.c:5410: Test failed: test 1: expected one result when hints are used for localhost sock.c:5410: Test failed: test 2: expected one result when hints are used for localhost sock.c:5410: Test failed: test 3: expected one result when hints are used for localhost sock.c:5410: Test failed: test 8: expected one result when hints are used for localhost sock.c:5410: Test failed: test 9: expected one result when hints are used for localhost sock.c:5410: Test failed: test 10: expected one result when hints are used for localhost sock.c:5410: Test failed: test 11: expected one result when hints are used for localhost sock.c:5410: Test failed: test 20: expected one result when hints are used for localhost sock.c:5410: Test failed: test 21: expected one result when hints are used for localhost sock.c:5518: Test failed: test 0: expected one result when hints are used for localhost sock.c:5518: Test failed: test 1: expected one result when hints are used for localhost sock.c:5518: Test failed: test 2: expected one result when hints are used for localhost sock.c:5518: Test failed: test 3: expected one result when hints are used for localhost sock.c:5518: Test failed: test 8: expected one result when hints are used for localhost sock.c:5518: Test failed: test 9: expected one result when hints are used for localhost sock.c:5518: Test failed: test 10: expected one result when hints are used for localhost sock.c:5518: Test failed: test 11: expected one result when hints are used for localhost sock.c:5518: Test failed: test 20: expected one result when hints are used for localhost sock.c:5518: Test failed: test 21: expected one result when hints are used for localhost === w2008s64 (64 bit sock) === sock.c:554: Test failed: oob_server (654): unexpectedly at the OOB mark: 0 sock.c:5410: Test failed: test 0: expected one result when hints are used for localhost sock.c:5410: Test failed: test 1: expected one result when hints are used for localhost sock.c:5410: Test failed: test 2: expected one result when hints are used for localhost sock.c:5410: Test failed: test 3: expected one result when hints are used for localhost sock.c:5410: Test failed: test 8: expected one result when hints are used for localhost sock.c:5410: Test failed: test 9: expected one result when hints are used for localhost sock.c:5410: Test failed: test 10: expected one result when hints are used for localhost sock.c:5410: Test failed: test 11: expected one result when hints are used for localhost sock.c:5410: Test failed: test 20: expected one result when hints are used for localhost sock.c:5410: Test failed: test 21: expected one result when hints are used for localhost sock.c:5518: Test failed: test 0: expected one result when hints are used for localhost sock.c:5518: Test failed: test 1: expected one result when hints are used for localhost sock.c:5518: Test failed: test 2: expected one result when hints are used for localhost sock.c:5518: Test failed: test 3: expected one result when hints are used for localhost sock.c:5518: Test failed: test 8: expected one result when hints are used for localhost sock.c:5518: Test failed: test 9: expected one result when hints are used for localhost sock.c:5518: Test failed: test 10: expected one result when hints are used for localhost sock.c:5518: Test failed: test 11: expected one result when hints are used for localhost sock.c:5518: Test failed: test 20: expected one result when hints are used for localhost sock.c:5518: Test failed: test 21: expected one result when hints are used for localhost sock: unhandled exception c0000005 at 000007FEFE4C9CD9 === w7pro64 (64 bit sock) === sock.c:554: Test failed: oob_server (980): unexpectedly at the OOB mark: 0 sock.c:5410: Test failed: test 0: expected one result when hints are used for localhost sock.c:5410: Test failed: test 1: expected one result when hints are used for localhost sock.c:5410: Test failed: test 2: expected one result when hints are used for localhost sock.c:5410: Test failed: test 3: expected one result when hints are used for localhost sock.c:5410: Test failed: test 8: expected one result when hints are used for localhost sock.c:5410: Test failed: test 9: expected one result when hints are used for localhost sock.c:5410: Test failed: test 10: expected one result when hints are used for localhost sock.c:5410: Test failed: test 11: expected one result when hints are used for localhost sock.c:5410: Test failed: test 20: expected one result when hints are used for localhost sock.c:5410: Test failed: test 21: expected one result when hints are used for localhost sock.c:5518: Test failed: test 0: expected one result when hints are used for localhost sock.c:5518: Test failed: test 1: expected one result when hints are used for localhost sock.c:5518: Test failed: test 2: expected one result when hints are used for localhost sock.c:5518: Test failed: test 3: expected one result when hints are used for localhost sock.c:5518: Test failed: test 8: expected one result when hints are used for localhost sock.c:5518: Test failed: test 9: expected one result when hints are used for localhost sock.c:5518: Test failed: test 10: expected one result when hints are used for localhost sock.c:5518: Test failed: test 11: expected one result when hints are used for localhost sock.c:5518: Test failed: test 20: expected one result when hints are used for localhost sock.c:5518: Test failed: test 21: expected one result when hints are used for localhost

Dec. 31, 2013

Re: [3/4] ws2_32: Add extended IPX protocol support (try 2, resend)

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://newtestbot.winehq.org/JobDetails.pl?Key=3899 Your paranoid android. === wxppro (32 bit sock) === sock.c:522: Test failed: oob_server (c0): unexpectedly at the OOB mark: 0 sock: unhandled exception c0000005 at 00000000 === w2008s64 (32 bit sock) === sock.c:522: Test failed: oob_server (750): unexpectedly at the OOB mark: 0 sock: unhandled exception c0000005 at 00000000 === w2008s64 (64 bit sock) === sock.c:522: Test failed: oob_server (654): unexpectedly at the OOB mark: 0

Dec. 31, 2013