On Thu, Jun 15, 2000 at 11:56:14PM -0700, Francois Gouget wrote:
> On Thu, 8 Jun 2000, Andreas Mohr wrote:
> > what about WINSPOOL.DeviceCapabilities(/A/W) ?
>
> Yes. I think it's the same thing except that:
> * DeviceCapabilities is correctly declared in winspool.h
> * DeviceCapabilities i
On Thu, 8 Jun 2000, Andreas Mohr wrote:
> Hi,
>
> as there are already going on some prolonged discussions about this matter,
>
> what about WINSPOOL.DeviceCapabilities(/A/W) ?
>
> I guess it's the same here...
>
> (an app I have needs DeviceCapabilities)
Reminded that this was not answ
Hi,
as there are already going on some prolonged discussions about this matter,
what about WINSPOOL.DeviceCapabilities(/A/W) ?
I guess it's the same here...
(an app I have needs DeviceCapabilities)
Andreas Mohr
Alexandre Julliard wrote:
> MCIWndCreate is simply an alias for MCIWndCreateA, presumably for
> compatibility with apps compiled before #ifdef UNICODE was
> invented. So we should make both point to MCIWndCreateA in the spec
> file, there's no need for a separate definition or a prototype.
But a
Francois Gouget <[EMAIL PROTECTED]> writes:
> From their header file actually. It contains the following comment:
>
> *Thus for the api MCIWndCreate, there are in fact two apis,
> *MCIWndCreateA and MCIWndCreateW. If you call MCIWndCreate, this will be
> *re-routed to MCIWndC
On Mon, 5 Jun 2000, Bradley Baetz wrote:
> Francois Gouget wrote:
[...]
> > I guess this is what happened. They forgot to split it to A/W when
> > they switched to Win32. So after they had to keep it with for
> > compatibility. But what type should they give it: LPCSTR or LPCWSTR. In
> > fac
Francois Gouget wrote:
>
> For HDRAWDIB they use a typedef which is not how they do it for all
> the other handles. Anyway, if they do it this way it means I should
> probably leave it as is :-(
OK. I'll change that in my patches then. Thanks.
>
> I guess this is what happened. They fo
On Mon, 5 Jun 2000, Bradley Baetz wrote:
> Francois Gouget wrote:
> >
> > On Sat, 3 Jun 2000, Bradley Baetz wrote:
>
> >
> > > Also, is there a reason that you
> > > typedef'd HDRAWDIB in vfw.h, rather than using the macro in windef.h? I
> > > just copied everyone else, so I'm quite sure I'v
Francois Gouget wrote:
>
> On Sat, 3 Jun 2000, Bradley Baetz wrote:
>
> > Also, is there a reason that you
> > typedef'd HDRAWDIB in vfw.h, rather than using the macro in windef.h? I
> > just copied everyone else, so I'm quite sure I've missed something
> > somewhere. Some of the HANDLE types a
On Sat, 3 Jun 2000, Bradley Baetz wrote:
> Francois Gouget wrote:
[... msvideo patches...]
> Can I ask you to please skip these buts? They clash with my msvideo
> patches (3 weeks to the end of exams!)
Sure. I think Alexandre has not yet applied them as I am supposed to
revise them.
> Also
On 2 Jun 2000, Alexandre Julliard wrote:
> Francois Gouget <[EMAIL PROTECTED]> writes:
>
> > So what I did is have winuser.h include winbase.h anyway but I
> > really don't like this. Maybe I should really go add a '#include
> > "winbase.h"' in all the Wine files that need it.
>
> That wo
Francois Gouget wrote:
>
> Hi,
>
> Here's the first batch of missing prototypes I added based on the
> indications given by winapi_check.
> Here's the ChangeLog:
>
> * dlls/msvideo/msvfw32.spec
>MCIWndCreate conflicts with the corresponding A/W macro
>
> * dlls/msvideo/msvi
Francois Gouget <[EMAIL PROTECTED]> writes:
> So what I did is have winuser.h include winbase.h anyway but I
> really don't like this. Maybe I should really go add a '#include
> "winbase.h"' in all the Wine files that need it.
That would be preferable yes.
--
Alexandre Julliard
[EMAIL PRO
13 matches
Mail list logo
