--- "Dimitrie O. Paun" <[EMAIL PROTECTED]> wrote:
> Just for my edification, what would happen to your tree (or what
> chances would entail) if you just switched to our headers?
Our User32/Win32k/GDI32 would break in most interesting ways. ;P
Thats not WINEs fault though. It owes to bad design de
On December 3, 2003 10:57 am, Vizzini wrote:
> We're still working out a plan for sharing headers; unfortunately it's
> not as easy as just using Wine's headers.
I know things are not always as easy as they seem, and I must
apologize for reopening this issue, but there's something I
miss. Namely,
Hello Dimi,
--- "Dimitrie O. Paun" <[EMAIL PROTECTED]> wrote:
> It's a bug in your headers, and it's not present in the Wine
> headers (one again, why aren't you guys using our headers?)
I am sorry about the confusion and noise on the ReactOS side. I think
Its going to come down to just using the
On Wed, 2003-12-03 at 08:46, Dimitrie O. Paun wrote:
> On December 3, 2003 06:47 am, Jonathan Wilson wrote:
> > typedef const PROPSHEETPAGEA *LPCPROPSHEETPAGEW;
> > should (I believe) be this line:
> > typedef const PROPSHEETPAGEW *LPCPROPSHEETPAGEW;
> >
> > If this is a bug, can someone fix it?
>
On December 3, 2003 06:47 am, Jonathan Wilson wrote:
> typedef const PROPSHEETPAGEA *LPCPROPSHEETPAGEW;
> should (I believe) be this line:
> typedef const PROPSHEETPAGEW *LPCPROPSHEETPAGEW;
>
> If this is a bug, can someone fix it?
It's a bug in your headers, and it's not present in the Wine
heade
cc-ing WINE list in case its also present in the WINEHQ CVS
this line:
typedef const PROPSHEETPAGEA *LPCPROPSHEETPAGEW;
should (I believe) be this line:
typedef const PROPSHEETPAGEW *LPCPROPSHEETPAGEW;
If this is a bug, can someone fix it?
If its not, can someone explain why this construct is prese