September 2008 - Wine-Devel

Re: Discussion of bug versions

by Lei Zhang

On Sun, Sep 28, 2008 at 6:35 PM, wineappdb <wineappdb(a)googlemail.com> wrote: > Why not offer version + (GIT) e.g "1.1.5 GIT" or e.g "1.1.5+" ? > And to pick it offer a combo box "Release" or "Git" then you pick your wine version. That'll double the number of Wine versions, and make searching much harder. Just think of 1.1.5 as [1.1.5 - 1.1.6).

Sept. 30, 2008

WineConf 2008 Keynote Video

by Jeremy Newman

http://www.winehq.org/site/wineconf/media -Newman

Sept. 30, 2008

Re: OpenGL child windows

by Chris Robinson

On Tuesday 30 September 2008 02:11:17 am Florian Köberle wrote: > A long time ago you wrote in > http://www.winehq.org/pipermail/wine-devel/2007-October/059550.html > that you got my example program running: > > "If I force offscreen rendering and add the flag, the demo works." > > Could you have a look at the following bug report and may explain how to > "force offscreen rendering"? > http://bugs.winehq.org/show_bug.cgi?id=15232 By forcing offscreen rendering, I believe I meant hacking Wine so that it always uses redirected/offscreen GL rendering even it it thinks it shouldn't need to. This is automatically done by Wine when drawing to a child windows, there's no way for an app to "force" it (short of creating a child window). IIRC, what needs to happen is Wine needs to use offscreen GL rendering when a window has WS_CLIPCHILDREN, but apps tend to set that flag even if they don't use child windows (needlessly causing redirected GL rendering). That's what I remember anyway, but I could be wrong.

Sept. 30, 2008

RE: IWineD3DResourceImpl_GetPriority/SetPriority

by Stefan Dösinger

Can you add a test for the default priority? From: wine-patches-bounces(a)winehq.org [mailto:wine-patches-bounces(a)winehq.org] On Behalf Of Kjell Rune Skaaraas Sent: Tuesday, September 30, 2008 11:18 AM To: wine-patches(a)winehq.org Subject: Re: IWineD3DResourceImpl_GetPriority/SetPriority Hello, Please don't use the previously attached patch since it makes changes to exception.c that should never have been part of the patch. Corrected patch is attached to this mail. Regards, Kjell Rune _____ Alt i ett. Få Yahoo! <http://no.mail.yahoo.com> Mail med adressekartotek, kalender og notisblokk.

Sept. 30, 2008

Re: make test .. monthcal new failure

by James Hawkins

On Tue, Sep 30, 2008 at 12:54 PM, James Hawkins <truiken(a)gmail.com> wrote: > On Tue, Sep 30, 2008 at 12:40 PM, Marcus Meissner <marcus(a)jet.franken.de> wrote: >> Hi, >> >> I get these new errors after todays git update: >> >> monthcal.c:677: Test failed: Expected 65542, got 65536 >> monthcal.c:677: Test failed: Expected 65542, got 65536 >> monthcal.c:677: Test failed: Expected 65542, got 65536 >> monthcal.c:677: Test failed: Expected 65542, got 65536 >> monthcal.c:677: Test failed: Expected 65542, got 65536 >> err:monthcal:MONTHCAL_WindowProc unknown msg 2006 wp=00000000 lp=00000000 >> err:monthcal:MONTHCAL_WindowProc unknown msg 2005 wp=00000001 lp=00000000 >> err:monthcal:MONTHCAL_WindowProc unknown msg 2006 wp=00000000 lp=00000000 >> err:monthcal:MONTHCAL_WindowProc unknown msg 2005 wp=00000000 lp=00000000 >> err:monthcal:MONTHCAL_WindowProc unknown msg 2006 wp=00000000 lp=00000000 >> err:monthcal:MONTHCAL_WindowProc unknown msg 2005 wp=00000001 lp=00000000 >> monthcal.c:956: Tests skipped: cannot perform today link test >> make: *** [monthcal.ok] Fehler 5 >> > > The fix is pretty simple, but I want to wait to see the test results > in Windows after this commit, just to make sure newer versions haven't > changed this behavior. > Actually, I just looked at the test results and this behavior is happening all the way up to win2k3, so I'll whip up a patch and send it in. -- James Hawkins

Sept. 30, 2008

Re: make test .. monthcal new failure

by James Hawkins

On Tue, Sep 30, 2008 at 12:40 PM, Marcus Meissner <marcus(a)jet.franken.de> wrote: > Hi, > > I get these new errors after todays git update: > > monthcal.c:677: Test failed: Expected 65542, got 65536 > monthcal.c:677: Test failed: Expected 65542, got 65536 > monthcal.c:677: Test failed: Expected 65542, got 65536 > monthcal.c:677: Test failed: Expected 65542, got 65536 > monthcal.c:677: Test failed: Expected 65542, got 65536 > err:monthcal:MONTHCAL_WindowProc unknown msg 2006 wp=00000000 lp=00000000 > err:monthcal:MONTHCAL_WindowProc unknown msg 2005 wp=00000001 lp=00000000 > err:monthcal:MONTHCAL_WindowProc unknown msg 2006 wp=00000000 lp=00000000 > err:monthcal:MONTHCAL_WindowProc unknown msg 2005 wp=00000000 lp=00000000 > err:monthcal:MONTHCAL_WindowProc unknown msg 2006 wp=00000000 lp=00000000 > err:monthcal:MONTHCAL_WindowProc unknown msg 2005 wp=00000001 lp=00000000 > monthcal.c:956: Tests skipped: cannot perform today link test > make: *** [monthcal.ok] Fehler 5 > The fix is pretty simple, but I want to wait to see the test results in Windows after this commit, just to make sure newer versions haven't changed this behavior. -- James Hawkins

Sept. 30, 2008

make test .. monthcal new failure

by Marcus Meissner

Hi, I get these new errors after todays git update: monthcal.c:677: Test failed: Expected 65542, got 65536 monthcal.c:677: Test failed: Expected 65542, got 65536 monthcal.c:677: Test failed: Expected 65542, got 65536 monthcal.c:677: Test failed: Expected 65542, got 65536 monthcal.c:677: Test failed: Expected 65542, got 65536 err:monthcal:MONTHCAL_WindowProc unknown msg 2006 wp=00000000 lp=00000000 err:monthcal:MONTHCAL_WindowProc unknown msg 2005 wp=00000001 lp=00000000 err:monthcal:MONTHCAL_WindowProc unknown msg 2006 wp=00000000 lp=00000000 err:monthcal:MONTHCAL_WindowProc unknown msg 2005 wp=00000000 lp=00000000 err:monthcal:MONTHCAL_WindowProc unknown msg 2006 wp=00000000 lp=00000000 err:monthcal:MONTHCAL_WindowProc unknown msg 2005 wp=00000001 lp=00000000 monthcal.c:956: Tests skipped: cannot perform today link test make: *** [monthcal.ok] Fehler 5 Ciao, Marcus

Sept. 30, 2008

Re: d3d8: Fix incorrect ordering of brackets in IDirect3DVertexShader8Impl_GetDevice.

by Rob Shearman

2008/9/30 Henri Verbeet <hverbeet(a)gmail.com>: > 2008/9/30 Rob Shearman <robertshearman(a)gmail.com>: >> The comparison should be (D3D_OK == hr && myDevice), not (D3D_OK == >> (hr && myDevice)). >> > d3d8 and d3d9 are pretty bad at stuff like this, unfortunately. > Strictly speaking we should also compare to WINED3D_OK instead of > D3D_OK here, but they have the same values. Ok, I will fix that in my patches and resend. -- Rob Shearman

Sept. 30, 2008

Re: d3d8: Fix incorrect ordering of brackets in IDirect3DVertexShader8Impl_GetDevice.

by Henri Verbeet

2008/9/30 Rob Shearman <robertshearman(a)gmail.com>: > The comparison should be (D3D_OK == hr && myDevice), not (D3D_OK == > (hr && myDevice)). > d3d8 and d3d9 are pretty bad at stuff like this, unfortunately. Strictly speaking we should also compare to WINED3D_OK instead of D3D_OK here, but they have the same values.

Sept. 30, 2008

Re: Bad patch, what's the procedure?

by Michael Stefaniuc

Hi, Kjell Rune Skaaraas wrote: > Hello,I've submitted a patch to wine-patches for > IWineD3DResourceImpl_GetPriority/SetPriority that's incorrect (it > makes changes to exception.c which shouldn't be there, they were just > part of me trying to debug something). Is there anything like a cancel > procedure I should do, or should I just fix up the patch and submit it > again? Oh yeah and this will teach me to read the diff more thoroughly > next time...Regards,Kjell Rune it really depends. If you have the revised patch ready you can reply to your patch (to wine-patches) with the new patch and say something like "please use this patch instead as the other one was broken". If you still need to work on fixing the patch reply to wine-devel saying something like "please do not apply this patch; it's broken and I'm working on a revised patch". bye michael

Sept. 30, 2008