April 2008 - Wine-devel - list.winehq.org

Wine 1.0 release plan update
by Dan Kegel 25 Apr '08

25 Apr '08

Alexandre's taking a vacation in May, and the schedule is bending slightly to fit. We're also not promising a particular release date, though the previously predicted date is still as likely as it was before. http://wiki.winehq.org/WineReleasePlan now says: --- snip --- * 0.9.61 - 2 May 2008 - start of code freeze for 1.0 * 1.0.0-rc1 - 9 May 2008 (early because of Alexandre's vacation) * No release 16 May (Alexandre on vacation) * 1.0.0-rc2 - 23 May (early because of Alexandre's vacation) The exact date of the 1.0.0 release can't be predicted; we'll keep on doing release candidates until we're comfortable with it. We expect it will be in June. --- snip ---

1 0

Re: ddraw: Fix tests that fail with the reference rasterizer
by Stefan Dösinger 25 Apr '08

25 Apr '08

Am Freitag, 25. April 2008 05:38:40 schrieb James Hawkins: > Hi, > > Changelog: > * Fix tests that fail with the reference rasterizer. > if (SUCCEEDED(IDirectDrawSurface7_AddAttachedSurface(surface1, surface4))) > refrast = TRUE; Do you take care of detaching the surface again? Did you try checking the DirectDraw description or GUID? Maybe there's a better way to detet the refrast, if you want the teest to succeeed in a VM

2 1

Re: d3d8: Fix a few test failures in win2k3
by Stefan Dösinger 25 Apr '08

25 Apr '08

Am Freitag, 25. April 2008 03:36:04 schrieb James Hawkins: > Hi, > > Changelog: > * Fix a few test failures in win2k3. > > dlls/d3d8/tests/device.c | 9 ++++++--- > 1 files changed, 6 insertions(+), 3 deletions(-) Looks ok to me Somewhen we may want to move all this multiple times copypasted device init code into a shared function :-/

1 0

Safedisc for 1.0+ ?
by TheBlunderbuss 25 Apr '08

25 Apr '08

3 3

ddraw: ComputeSphereVisibility
by David Adam 25 Apr '08

25 Apr '08

Hello, I am trying to debug the demo of The Sting. Now, the main is that the screen is almost black. It is surely related to the following FIXME: fixme:d3d7:IDirect3DDeviceImpl_7_ComputeSphereVisibility Unfortunately, I did not find any informations about this function. Does anyone know what this function does, ( and better knows a possible implementation)? Thanks, David Adam

2 1

Re: [PATCH] user32: edit controls should ignore WM_KEYDOWN on control + enter.
by Vitaliy Margolen 25 Apr '08

25 Apr '08

Lei Zhang wrote: > On Thu, Apr 24, 2008 at 10:22 PM, Lei Zhang <thestig(a)google.com> wrote: >> Hi, >> >> This should be the last bit in getting control + enter working in >> multiline edit controls. I attempted to write a test for this using >> SendInput() or SetKeyState() + SendMessage(), but I couldn't get seem >> to simulate holding down the control key. >> > Should work. You can also look at keybd_event() how it does it. It's pretty much a wrapper around SendInput(). All you'll need is keybd_event(VK_CONTROL, 0, 0, 0); to press it. And keybd_event(VK_CONTROL, 0, KEYEVENTF_KEYUP, 0); to release it. Vitaliy.

2 1

Re: [2/2] [try2] user32:mdi.c Fix creating MDI child window according with test. [resend]
by Alexandre Julliard 25 Apr '08

25 Apr '08

Anatoly Lyutin <vostok(a)etersoft.ru> writes: > Uses SWP_NOZORDER according with Dmitry's comment. > > Changelog: > Fix creating MDI child window according with test. It doesn't work: msg.c:3065: Test failed: Create visible MDI child window: the msg sequence is not complete: expected 0000 - actual 0046 msg.c:3120: Test failed: ShowWindow(SW_MAXIMIZE):invisible MDI child: the msg 0x0047 was expected, but got msg 0x0046 instead msg.c:3120: Test failed: ShowWindow(SW_MAXIMIZE):invisible MDI child: the msg 0x0005 was expected, but got msg 0x0083 instead msg.c:3120: Test failed: ShowWindow(SW_MAXIMIZE):invisible MDI child: the msg 0x0046 was expected, but got msg 0x0047 instead msg.c:3120: Test failed: ShowWindow(SW_MAXIMIZE):invisible MDI child: the msg 0x0083 was expected, but got msg 0x0047 instead msg.c:3120: Test failed: ShowWindow(SW_MAXIMIZE):invisible MDI child: the msg 0x0047 was expected, but got msg 0x0005 instead msg.c:3120: Test failed: ShowWindow(SW_MAXIMIZE):invisible MDI child: the msg sequence is not complete: expected 0000 - actual 0046 msg.c:3345: Test failed: ShowWindow(SW_MAXIMIZE):invisible maximized MDI child: the msg 0x0047 was expected, but got msg 0x0046 instead msg.c:3345: Test failed: ShowWindow(SW_MAXIMIZE):invisible maximized MDI child: the msg sequence is not complete: expected 0000 - actual 0083 msg.c:3484: Test failed: Create MDI child window with invisible parent: the msg sequence is not complete: expected 0000 - actual 0046 -- Alexandre Julliard julliard(a)winehq.org

2 1

Re: John Klehm : winex11: Add support for IsXExtensionPointer tablet devices.
by Michael Stefaniuc 25 Apr '08

25 Apr '08

This patch break compilation on my RHEL5 box with xorg-x11-proto-devel-7.1-9.fc6 which misses the IsXExtensionPointer define. bye michael Alexandre Julliard wrote: > Module: wine > Branch: master > Commit: 2c26ea609d6b2b8a25be20984c0014ceb202466a > URL: http://source.winehq.org/git/wine.git/?a=commit;h=2c26ea609d6b2b8a25be20984… > > Author: John Klehm <xixsimplicityxix(a)gmail.com> > Date: Tue Apr 22 20:11:28 2008 -0500 > > winex11: Add support for IsXExtensionPointer tablet devices. > > --- > > dlls/winex11.drv/wintab.c | 5 +++-- > 1 files changed, 3 insertions(+), 2 deletions(-) > > diff --git a/dlls/winex11.drv/wintab.c b/dlls/winex11.drv/wintab.c > index 37596ba..b086e44 100644 > --- a/dlls/winex11.drv/wintab.c > +++ b/dlls/winex11.drv/wintab.c > @@ -530,14 +530,15 @@ void X11DRV_LoadTabletInfo(HWND hwnddefault) > devices[loop].use == IsXKeyboard ? "IsXKeyboard" : > devices[loop].use == IsXPointer ? "IsXPointer" : > devices[loop].use == IsXExtensionDevice ? "IsXExtensionDevice" : > + devices[loop].use == IsXExtensionPointer ? "IsXExtensionPointer" : > "Unknown" > ); > > - if (devices[loop].use == IsXExtensionDevice) > + if ((devices[loop].use == IsXExtensionDevice) || (devices[loop].use == IsXExtensionPointer)) > { > LPWTI_CURSORS_INFO cursor; > > - TRACE("Is Extension Device\n"); > + TRACE("Is XExtension%s\n", (devices[loop].use == IsXExtensionDevice)? "Device":"Pointer"); > cursor_target++; > target = &devices[loop]; > cursor = &gSysCursor[cursor_target]; > > > -- Michael Stefaniuc Tel.: +49-711-96437-199 Consulting Communications Engineer Fax.: +49-711-96437-111 -------------------------------------------------------------------- Reg. Adresse: Red Hat GmbH, Otto-Hahn-Strasse 20, 85609 Dornach bei Muenchen Handelsregister: Amtsgericht Muenchen HRB 153243 Geschäftsführer: Brendan Lane, Charlie Peters, Michael Cunningham, Werner Knoblich

1 0

Re: ntoskrnl.exe: Change calling conventions [try 2]
by Alexandre Julliard 25 Apr '08

25 Apr '08

Alexander Morozov <amorozov(a)etersoft.ru> writes: > Changelog: > ntoskrnl.exe: Change calling conventions for InterlockedExchange, > InterlockedCompareExchange, InterlockedDecrement and InterlockedIncrement > > --- a/dlls/ntoskrnl.exe/ntoskrnl.exe.spec > +++ b/dlls/ntoskrnl.exe/ntoskrnl.exe.spec > @@ -28,11 +28,11 @@ > @ stub Exfi386InterlockedExchangeUlong > @ stub Exfi386InterlockedIncrementLong > @ stub HalExamineMBR > -@ stdcall InterlockedCompareExchange(ptr long long) kernel32.InterlockedCompareExchange > -@ stdcall InterlockedDecrement(ptr) kernel32.InterlockedDecrement > -@ stdcall InterlockedExchange(ptr long) kernel32.InterlockedExchange > +@ stdcall -norelay InterlockedCompareExchange(ptr long long) NTOSKRNL_InterlockedCompareExchange > +@ stdcall -norelay InterlockedDecrement(ptr) NTOSKRNL_InterlockedDecrement > +@ stdcall -norelay InterlockedExchange(ptr long) NTOSKRNL_InterlockedExchange > @ stdcall InterlockedExchangeAdd(ptr long ) kernel32.InterlockedExchangeAdd > -@ stdcall InterlockedIncrement(ptr) kernel32.InterlockedIncrement > +@ stdcall -norelay InterlockedIncrement(ptr) NTOSKRNL_InterlockedIncrement Why didn't you fix InterlockedExchangeAdd too? -- Alexandre Julliard julliard(a)winehq.org

2 1

Re: [Resend 2/5] imm32: Add the header for private imm32 function.
by Alexandre Julliard 25 Apr '08

25 Apr '08

ByeongSik Jeon <bsjeon(a)hanmail.net> writes: > Unknown function in the SDK/DDK's header. > --- > include/wine/imm_private.h | 35 +++++++++++++++++++++++++++++++++++ You don't want to add a new header for that, especially not a global one. The function is exported on Windows too, so it's OK to declare it in the DDK header. -- Alexandre Julliard julliard(a)winehq.org

1 0