wine-devel September 2003

wine-devel@winehq.org

133 participants
342 discussions

something I found that might help GDI hackers
by Jonathan Wilson 10 Sep '03

10 Sep '03

struct GDIHandleBitFields { unsigned long Index:0:10; unsigned long Type:10:5; unsigned long AltType:15:2; unsigned long Stock:17:1; unsigned long Unique:18:8; }; This might help people trying to understand the inner workings of GDI... Its current as of windows XP SP1.

2 1

Re: FAQ: Update the ports section
by Tom 10 Sep '03

10 Sep '03

Francois Gouget wrote: >Changelog: > > >- The following will list the x86 operating systems supported by >+ The following lists the x86 operating systems supported by > > Should be. The following list are the x86 operating systems supported by Tom

7 15

Re: FAQ: Update the ports section
by Ivan Leo Murray-Smith 10 Sep '03

10 Sep '03

I happen to be from the UK, and can tell you that >The following lists the x86 operating systems supported by >the list is now updated >the list is now up to date are all correct.

2 1

Re: FAQ: Update the ports section
by Ivan Leo Murray-Smith 10 Sep '03

10 Sep '03

You must send me some of the stuff you're smoking! "The list are now up to date" doesn't exist in english, you must choose "The lists are now up to date" for a plural "The list is now up to date" for a singular

1 0

Re: [Resend winegcc03] winewrap can handle the default output name
by Dimitrie O. Paun 10 Sep '03

10 Sep '03

On Tue, 9 Sep 2003, Richard Cohen wrote: > Slightly different from last time. > > > Default name that mingw uses is a.exe > > This also stops winewrap from segfaulting when passed no arguments. > > Changelog > Handle default linker output name (a.exe) in winewrap instead of > winegcc I'm still not sure I like this one, as I said, a.out is a gccism, and should be handled in winegcc. winewrap does not have to be command line compatible to the GNU tool (as it currently stands), we can require an output name for it. -- Dimi.

3 4

Re: [DSHOW-08] Implementation of IMemAllocator and IMediaSample (REVISED2)
by Dimitrie O. Paun 10 Sep '03

10 Sep '03

On September 9, 2003 07:37 pm, Robert Shearman wrote: > --- /dev/null Mon Jun 24 01:53:01 2002 > +++ wine/dlls/quartz/list.h Mon Sep 8 00:48:58 2003 The list.h stuff seems to be fairly popular, why not stick a copy in wine/list.h? -- Dimi.

2 1

Re: [winegcc08] Handle -L in a separate array
by Dimitrie O. Paun 10 Sep '03

10 Sep '03

On Tue, 9 Sep 2003, Richard Cohen wrote: > ...rather than adding -L<libpath> to both the DLLs and static libraries > No functional changes. I'm not sure this is correct, as the order of -L and -l may be significant. That is to say, if I do -LdirA -la -LdirB -lb then the system will search for a only in A, not in B, which is not the case if I do: -LdirA -LdirB -la -lb -- Dimi.

2 1

Re: BuildCommDCBAndTimeouts patch
by Jakob Eriksson 10 Sep '03

10 Sep '03

Could you also make test.c into a regression test for inclusion into Wine? That is almost more important than the actual patch to Wine - if we have the conformance test, it ensures changes to Wine in the future does not destroy functionality. regards, Jakob

4 3

Re: Resend: Shlwapi ordinal fixes (Dave Miller)
by Robert Shearman 10 Sep '03

10 Sep '03

On Wednesday 10 September 2003 5:32 am, Dave Miller wrote: > > Remove about a dozen ordinals we have defined which do not seem to be > important. (They vary from one windows version to another) Alexandre, please don't apply. I am doing a big update on the ordinals of Shlwapi and will incorporate these changes into my patch. Rob

1 0

FAQ update
by Tom 10 Sep '03

10 Sep '03

Hi, Thanks for the update.. I got occupied with something and it took me a little longer than I thought. But I have the sync of lostwages to docs faq in my tree. I will now rm -rf it Regards, Tom

6 28

← Newer
1
...
20
21
22
23
24
25
26
...
35
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel September 2003