Re: wine dev packages

Jason Green wrote: I just added the Fedora Core 5 and Ubuntu Dapper sections yesterday, and I believe that they are at least 95% accurate, although I might have missed one somewhere. If someone can add the package names required for a gentoo build (or possibly create and maintain wine-cvs packa

Re: GDI32: using the embeded bitmap in antialias mode

2006-03-13 (월), 04:10 +0900, Byeong-Sik Jeon 쓰시길: > If format == WINE_GGO_GRAY16_BITMAP at the "WineEngGetGlyphOutline()", > set on "FT_LOAD_NO_BITMAP". > I mistake. When format == WINE_GGO_GRAY16_BITMAP, skip that set on "FT_LOAD_NO_BITMAP".

Re: ddraw design flaw

Stefan Dösinger wrote: > Hi, >> I have found a design flaw in ddraw and described it in my 'World of >> Warcraft 0.10 Public Test Real (PTR)' thread. Why has nobody adressed >> this issue? In my eyes it is a severe design flaw if an application >> can't unload ddraw.dll without side effects (especi

Re: [Bugzilla] Add note to not paste logs and back traces.

James Trotter wrote: On 3/12/06, *Jesse Allen* <[EMAIL PROTECTED] > wrote: Yeah, that's bad, but so is this AppDB page: http://appdb.winehq.org/appview.php?versionId=1177 People seem to think that the AppDB comment sections are a good place to post

Re: RFC: Make SetThreadContext work properly

Sunday, March 12, 2006, 7:18:30 AM, Dimi Paun wrote: > Hi Alexandre, >>From a quick look at the code, it seems that you've already fixed > the problem addressed by Mike's patch: > http://wiki.winehq.org/Make_SetThreadContext_work_properly > revision 1.53 > date: 2006/01/11 20:36:17; author:

wine dev packages (was: Can't run DirectX games on x86_64 Linux)

Jason Green wrote: > Correct, wine will compile and run without a lot of features and never > warn you that they don't exist. See this wiki page for an example of > what your include/config.h file should probably look like: > > http://wiki.winehq.org/Recommended_Packages > > I just added the Fedor

RFC: Make SetThreadContext work properly

Hi Alexandre, >From a quick look at the code, it seems that you've already fixed the problem addressed by Mike's patch: http://wiki.winehq.org/Make_SetThreadContext_work_properly revision 1.53 date: 2006/01/11 20:36:17; author: julliard; state: Exp; lines: +38 -24 Alexandre Julliard <[EMAI

Re: My guess why Munich doesn't like Wine

On 3/12/06, Dan Kegel <[EMAIL PROTECTED]> wrote: > > Given that the world kind of treats this as a must, > perhaps it could be added as a criterion for > a 1.0 release. Say, where's the existing page > describing our release criteria? The page we had was for a 0.9 release, I suppose the criteria

Re: [Bugzilla] Add note to not paste logs and back traces.

On 3/12/06, Jesse Allen <[EMAIL PROTECTED]> wrote: On 3/11/06, Vitaliy Margolen <[EMAIL PROTECTED]> wrote:> What? You mean having all the pastes in this bug: http://bugs.winehq.org/show_bug.cgi?id=4131> adds to it's readability? This is just one bug that I could think of.> Also note that the bigge

Re: Francois Gouget : user32: Handle WM_ENDSESSION in DefWinProc().

On Sat, 11 Mar 2006 19:23:14 -0800, you wrote: >Pardon intrusion by this Wine user into this technical discussion. > >Is the problem with Pegasus Mail (PM) that is mentioned below something that >is >new with Wine 0.9.9? I know that I saw termination of "the complete program" >whenever I sent a

Re: [Bugzilla] Add note to not paste logs and back traces.

On Sat, 11 Mar 2006 12:30:39 -0700, you wrote: >> Not pasting back traces will make following the bug list by email rather >Well it might be true, but to a point. Most of the debug traces are too >wide and e-mail wraps them (so does maillist archive). That _does_ make >it nearly impossible to se