Wine-Devel

By thread

wine-devel@list.winehq.org

July 2002

112 participants
532 messages

Netbios and Wins support

by Claudiu Costin

Dear friends, Is there anybody working on Netbios/MS Windows Network support? I want to run Outlook with Exchange. I can help testing and hacking, but not writing real code. kind regards, -- Claudiu Costin, claudiuc(a)kde.org Linux-KDE Romania http://www.ro.kde.org

July 31, 2002

Re: PATCH: Convert HMIDI to void*

by Francois Gouget

On Wed, 31 Jul 2002, Michael Stefaniuc wrote: [...] > Could you please verify that HWAVE HWAVEIN HWAVEOUT HMIXER HMIXEROBJ are > also declared with the DECLARE_HANDLE macro? I don't have the windows > headers. Yep. They are declared using DECLARE_HANDLE too. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ In theory, theory and practice are the same, but in practice they're different.

July 31, 2002

Re: PATCH: Convert HMIDI to void*

by Michael Stefaniuc

On Wed, Jul 31, 2002 at 02:25:08PM -0700, Francois Gouget wrote: > On Wed, 31 Jul 2002, Michael Stefaniuc wrote: > [...] > > I expressed myself wrong, with interchangable i meant having > > typedef HMIDI HMIDIIN > > typedef HMIDI HMIDIOUT > > typedef HMIDI HMIDISTRM > > in include/mmsystem.h instead of > > DECLARE_HANDLE(HMIDIIN); > > DECLARE_HANDLE(HMIDIOUT); > > DECLARE_HANDLE(HMIDISTRM); > > I just checked and the windows headers declare the HMIDI* handles using > the DECLARE_HANDLE macro. So that's the way we should do it too. That means my patch is valid and can be applied. Could you please verify that HWAVE HWAVEIN HWAVEOUT HMIXER HMIXEROBJ are also declared with the DECLARE_HANDLE macro? I don't have the windows headers. thanks bye michael -- Michael Stefaniuc Tel.: +49-711-96437-199 System Administration Fax.: +49-711-96437-111 Red Hat GmbH Email: mstefani(a)redhat.com Hauptstaetterstr. 58 http://www.redhat.de/ D-70178 Stuttgart

July 31, 2002

Re: PATCH: Convert HMIDI to void*

by Francois Gouget

On Wed, 31 Jul 2002, Michael Stefaniuc wrote: [...] > I expressed myself wrong, with interchangable i meant having > typedef HMIDI HMIDIIN > typedef HMIDI HMIDIOUT > typedef HMIDI HMIDISTRM > in include/mmsystem.h instead of > DECLARE_HANDLE(HMIDIIN); > DECLARE_HANDLE(HMIDIOUT); > DECLARE_HANDLE(HMIDISTRM); I just checked and the windows headers declare the HMIDI* handles using the DECLARE_HANDLE macro. So that's the way we should do it too. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Any sufficiently advanced bug is indistinguishable from a feature. -- from some indian guy

July 31, 2002

Re: PATCH: Convert HMIDI to void*

by Michael Stefaniuc

On Wed, Jul 31, 2002 at 10:11:51PM +0200, Eric Pouech wrote: > Michael Stefaniuc a écrit : > > am I right that HMIDI and HMIDIIN, HMIDIOUT shouldn't be > > interchangeable? Would save some conversions. > yes & no > HMIDIIN cannot be used for a HMIDIOUT (anyway, this will be checked > internally by our mmsys implementation: all HMIDI???? handles are stored > in the same table, and we never rely on the HMIDI??? handle type but on > the actual object type) > however, HMIDI can be used for a HMIDIIN (or HMIDIOUT or HMIDISTRM) > handle (see midiConnect for example) I expressed myself wrong, with interchangable i meant having typedef HMIDI HMIDIIN typedef HMIDI HMIDIOUT typedef HMIDI HMIDISTRM in include/mmsystem.h instead of DECLARE_HANDLE(HMIDIIN); DECLARE_HANDLE(HMIDIOUT); DECLARE_HANDLE(HMIDISTRM); I've suspected what you have described from reading the code (but it's always good to get confirmation). > it's true that midimap dll should use HMIDIOUT instead of HMIDI in its > internal data structure Do you want me to change that? bye michael -- Michael Stefaniuc Tel.: +49-711-96437-199 System Administration Fax.: +49-711-96437-111 Red Hat GmbH Email: mstefani(a)redhat.com Hauptstaetterstr. 58 http://www.redhat.de/ D-70178 Stuttgart

July 31, 2002

Re: PATCH: Convert HMIDI to void*

by Eric Pouech

Michael Stefaniuc a écrit : > > Hello, > > am I right that HMIDI and HMIDIIN, HMIDIOUT shouldn't be > interchangeable? Would save some conversions. yes & no HMIDIIN cannot be used for a HMIDIOUT (anyway, this will be checked internally by our mmsys implementation: all HMIDI???? handles are stored in the same table, and we never rely on the HMIDI??? handle type but on the actual object type) however, HMIDI can be used for a HMIDIIN (or HMIDIOUT or HMIDISTRM) handle (see midiConnect for example) it's true that midimap dll should use HMIDIOUT instead of HMIDI in its internal data structure A+

July 31, 2002

Re: Toolbar redraw problem

by dusanv

Guy L. Albertelli wrote: > ----- Original Message ----- > From: "dusanv" <dusanv(a)cadlink.com> > To: "wine-devel" <wine-devel(a)winehq.com> > Sent: Monday, July 29, 2002 4:27 PM > Subject: Toolbar redraw problem > > > >>Hi, >> >>I am seeing a bunch of apps have redrawing problems when a toolbar is >>dragged accross the window. Here's a screen shot: >> >>http://dusanv.net/files/wine-ss.png >> >>Does anyone have any info on this? I'd like to fix it but can't find >>anyhting relevant. >> > > > Could you please create a bug in Wine's Bugzilla http://bugs.winehq.com/. > > And if that is a test program, that would be good to ad also. I suspect that > somewhere during the drag operation, the rectangle invalidated does not > contain the edges. It will be fun to find. > > Thanks, > Guy > Hi, It's the bug #931: http://bugs.winehq.com/show_bug.cgi?id=931 Cheers, D.

July 31, 2002

Re: PATCH: a bit further with a cygwin build (fixed patch)

by Francois Gouget

On Tue, 30 Jul 2002, Rafael Kitover wrote: > Sorry, due to brain-deadness on my part the previous version of this > patch didn't build properly. This version is much cleaner and builds > properly on linux. > +#ifndef HAVE__FSTAT > int _fstat(int fd, struct _stat* buf) > +#else > +int MSVCRT(_fstat)(int fd, struct _stat* buf) > +#endif /* HAVE__FSTAT */ ... > +#ifndef HAVE__STAT > int _stat(const char* path, struct _stat * buf) > +#else > +int MSVCRT(_stat)(const char* path, struct _stat * buf) > +#endif /* HAVE__STAT */ You should systematically use MSVCRT(_fstat) and MSVCRT(_stat). Your previous patch was better :-) Basically, we use MSVCRT(xxx) for all symbols for which we may get a conflict with the native C library headers. On Unix systyems, the _xxx functions are never defined (though there may be a couple of exceptions) so we don't use MSVCRT() for readability's sake. But if you find a system where there is a conflict, then it's best to just systematically use MSVCRT() than to use ifdefs that make it even harder to read. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Any sufficiently advanced Operating System is indistinguishable from Linux

July 31, 2002

Re: dos console apps question

by Vincent Béron

Le mar 30/07/2002 à 00:09, dank(a)kegel.com a écrit : > Eric Pouech wrote: > > however, what you're facing right now is running a DOS program directly > > from the unix prompt (like wine mydospgm.com) > > in this case, there is no way for the parent process to tell something > > to its child, you it's up to you to do it by running the program with > > wineconsole mydospgm.com > > In my favorie case, i.e. running programs like sed.exe or ss.exe > from the unix commandline, what you really want is for Wine to > just get out of the way, do no graphics whatsoever, not even do any X calls > at all, and run the bloody commandline program hooked up to the > existing unix stdin and stdout. When I did some small test cases and needed to test them through ssh (because I don't have a Windows compiler here), I was able to run them correctly with the ttydrv rather than x11drv. I don't know about the stdin/out redirection (or usage), but for what I needed it was fine (I think I was using wine program.exe>somefile, but I'm not sure). As it's been a couple months now, I don't know if the ttydrv is still usable or not. Vincent

July 30, 2002

Re: Toolbar redraw problem

by Dusan Vujosevic

I will add a bit later today it and put in the test app as well. Thanks, D. > > >---- Original Message ---- >From: galberte(a)neo.lrun.com >To: dusanv(a)cadlink.com, wine-devel(a)winehq.com >Subject: Re: Toolbar redraw problem >Date: Mon, 29 Jul 2002 21:09:06 -0400 > >> >>----- Original Message ----- >>From: "dusanv" <dusanv(a)cadlink.com> >>To: "wine-devel" <wine-devel(a)winehq.com> >>Sent: Monday, July 29, 2002 4:27 PM >>Subject: Toolbar redraw problem >> >> >>> Hi, >>> >>> I am seeing a bunch of apps have redrawing problems when a toolbar >is >>> dragged accross the window. Here's a screen shot: >>> >>> http://dusanv.net/files/wine-ss.png >>> >>> Does anyone have any info on this? I'd like to fix it but can't >find >>> anyhting relevant. >>> >> >>Could you please create a bug in Wine's Bugzilla >http://bugs.winehq.com/. >> >>And if that is a test program, that would be good to ad also. I >suspect that >>somewhere during the drag operation, the rectangle invalidated does >not >>contain the edges. It will be fun to find. >> >>Thanks, >>Guy >> >> >> >>

July 30, 2002

Jump to page: