August 2010 - Wine-devel - list.winehq.org

Re: [PATCH 04/10] ddraw/tests: New visual back buffer flipping tests. (try 2)
by testbot＠testbot.winehq.org 03 Aug '10

03 Aug '10

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=4179 Your paranoid android. === W2KPROSP4 (32 bit visual) === visual.c:3027: Test failed: got R FF G 00 B 00, expected R FF G FF B FF

2 1

Re: [PATCH 09/10] ddraw: Add checking of SURFACEDESC type into CreateSurface methods. (try 2)
by testbot＠testbot.winehq.org 03 Aug '10

03 Aug '10

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=4188 Your paranoid android. === W98SE (32 bit dsurface) === No test summary line found

1 0

Re: [PATCH 08/10] ddraw: Allow attaching backbuffers and primaries. (try 2)
by testbot＠testbot.winehq.org 03 Aug '10

03 Aug '10

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=4187 Your paranoid android. === W2KPROSP4 (32 bit visual) === visual.c:3027: Test failed: got R FF G 00 B 00, expected R FF G FF B FF === W98SE (32 bit dsurface) === No test summary line found

1 0

Re: [PATCH 07/10] ddraw: Allow creating back buffer for DirectX 1 interfaces. (try 2)
by testbot＠testbot.winehq.org 03 Aug '10

03 Aug '10

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=4186 Your paranoid android. === W2KPROSP4 (32 bit visual) === visual.c:3027: Test failed: got R FF G 00 B 00, expected R FF G FF B FF === W98SE (32 bit dsurface) === No test summary line found

1 0

Re: [PATCH 2/5] ws2_32/tests: test ConnectEx
by Mike Kaplinskiy 03 Aug '10

03 Aug '10

On Mon, Aug 2, 2010 at 11:50 PM, Mike Kaplinskiy <mike.kaplinskiy(a)gmail.com> wrote: > --- > dlls/ws2_32/tests/sock.c | 227 ++++++++++++++++++++++++++++++++++++++++++++++ > 1 files changed, 227 insertions(+), 0 deletions(-) > Shoot, any chance you can just take #1 and take 2-5 from the first batch? That's an outdated not working version of the patches. Otherwise I'll resend tomorrow. Sorry, Mike.

1 0

Re: [PATCH 03/10] ddraw/tests: Add test for NULL/bad size of surface caps in CreateSurface. (try 2)
by testbot＠testbot.winehq.org 03 Aug '10

03 Aug '10

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=4178 Your paranoid android. === W98SE (32 bit dsurface) === No test summary line found

1 0

Re: [PATCH 02/10] ddraw/tests: New attachment/flipping tests for back buffers. (try 2)
by testbot＠testbot.winehq.org 03 Aug '10

03 Aug '10

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=4175 Your paranoid android. === W98SE (32 bit dsurface) === No test summary line found

1 0

Re: [PATCH 01/10] ddraw/tests: New CreateSurface for DDSCAPS_BACKBUFFER tests. (try 2)
by testbot＠testbot.winehq.org 03 Aug '10

03 Aug '10

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=4174 Your paranoid android. === W98SE (32 bit dsurface) === No test summary line found

1 0

Re: shdocvw: Update French translation
by Frédéric Delanoy 03 Aug '10

03 Aug '10

Please discard; has been mangled by misconfigured git 2010/8/2 Frédéric Delanoy <frederic.delanoy(a)gmail.com>: > --- > dlls/shdocvw/Fr.rc | 5 +++++ > 1 files changed, 5 insertions(+), 0 deletions(-) > > diff --git a/dlls/shdocvw/Fr.rc b/dlls/shdocvw/Fr.rc > index 94b4a7e..b7326bb 100644 > --- a/dlls/shdocvw/Fr.rc > +++ b/dlls/shdocvw/Fr.rc > @@ -55,6 +55,11 @@ IDR_BROWSE_MAIN_MENU MENU > MENUITEM SEPARATOR > MENUITEM "&Propriétés...", ID_BROWSE_PROPERTIES > } > + POPUP "&Favoris" > + { > + MENUITEM "&Ajouter aux favoris..." ID_BROWSE_ADDFAV > + MENUITEM SEPARATOR > + } > POPUP "&Aide" > { > MENUITEM "À &propos d'Internet Explorer...", ID_BROWSE_ABOUT > -- > 1.7.2 > >

1 0

Re: The WineAPI wiki.
by James Mckenzie 02 Aug '10

02 Aug '10

Max TenEyck Woodbury <max(a)mtew.isa-geek.net> wrote: >Sent: Aug 2, 2010 4:25 AM >To: wine-devel(a)winehq.org >Subject: Re: The WineAPI wiki. > >On 08/02/2010 07:00 AM, Dmitry Timoshkov wrote: >> Max TenEyck Woodbury<max(a)mtew.isa-geek.net> wrote: >> >>> I have started the WineAPI wiki at >>> >>> https://sourceforge.net/apps/mediawiki/wineapi/index.php?title=Main_Page >> >> You have chosen not very good name. There is no such a thing as Wine API, >> Wine implements Win32 API, and doesn't specify/add anything custom to it. >> The name "WineAPI" implies that Wine defines its own API which is not true, >> and is confusing. >> This should be named, the Windows32/Window64 API as implemented by Wine Documentation site. That is what it is. We have found shortcomings in the MSDN documentation (I'm dealing with this right now in one function call for Richedit.) This should be a collaborative site where Wine developers, Windows on Wine developers and others can place information on what Wine has implemented today, what needs to be implemented (with case code and discoveries) and what Wine cannot implement. >This has been discussed elsewhere on this mailing list. > Agreed. >There is a lot of information specific to Wine, particularly its >internal structure, that is not shared with Microsoft's product. >Further, there is a little confusing and incorrect information in the >Microsoft documentation. Bluntly, the Microsoft documentation is what >they want it to be. We need to document what it really is. > >We have tried to embed API documentation in the source code. That has >not worked as well as it could. Alexandre Julliard has said as much. I >think that having good documentation will help the project. Not having >good documentation can and does hurt Wine in my opinion. I also think >that trying to prevent the creation of that documentation might be >harmful. AJ has stated that documenting the Windows API and internal API calls should NOT be documented just in the source. It bloats the source code terribly and can make code unreadable. I agree that this Wiki should only be used to document the external interfaces to Wine as we implement Windows32/Windows64 API/ABI calls and what we have found in our testing that is different than MSDN. We should NOT duplicate MSDN where is is proper, but rather have a note that states MSDN and other sources have been found to be proper. As to the griping, we need to be public with our progress. This eliminates confusion and also gives new developers a place to start. James McKenzie

3 4