Re: Add debugstr_rect alias for consistency with other debugging functions.

2004-08-08 Thread Alexandre Julliard
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes: > Apart for much cleaner code, it's also useful, as I can see many > people do: > #ifdef WINE > #define ERR WINE_ERR > #define TRACE WINE_TRACE > ... > #else > #define ERR printf > #define TRACE printf > ... > #endif > > I have a sent

Re: Problem with ITypeInfo

2004-08-08 Thread Jacek Caban
Dmitry Timoshkov wrote: "Jacek Caban" <[EMAIL PROTECTED]> wrote: No, I don't. In my case I need only this: /* this is where we are coming from */ +ITypeLib2_AddRef((ITypeLib*)pLibInfo); ptiRet->pTypeLib = pLibInfo; ptiRet->index=count; but I call ITypeLib_Release in ITypeInfo_Release

Re: Fix crash in dsound test

2004-08-08 Thread Kevin Koltzau
On Thursday 29 July 2004 01:17 pm, Ferenc Wagner wrote: > Yes, there was a short discussion about this on 23-24 July > on wine-devel. It reached no conclusion, though, and I > didn't try the various MinGW libraries recommended there. > The abundance of MinGW packages always confused me, and at > t

RE: patch: shell32.dll - SHELL_ArgifyW expands env-vars

2004-08-08 Thread Jens Collin
Hi Steven, yes, that's why I only merged enough to solve the problem to ros, and not the whole lib :) I'll see what I can do on regressiontests. / Jens -Original Message- From: Steven Edwards [mailto:[EMAIL PROTECTED] Sent: den 8 augusti 2004 18:34 To: [EMAIL PROTECTED]; [EMAIL PROTECT

Re: patch: shell32.dll - SHELL_ArgifyW expands env-vars

2004-08-08 Thread Steven Edwards
Hi Jens, --- Jens Collin <[EMAIL PROTECTED]> wrote: > * lookup of envoronment-vars in SHELL_ArgifyW in shell32.dll added. > (Such as %SystemRoot%). Do you think you could write some test cases for the shellexecute functions using the wine regression tests? I would like to try and merge the rest o

Re: Wine's OLE/COM doesn't work, and I can no longer use native COM

2004-08-08 Thread Mike Hearn
On Sun, 2004-08-08 at 10:56 -0500, David D. Hagood wrote: > Mike Hearn wrote: > > Install it all as Win98 if possible, and native DCOM like this: > > > > WINEDLLOVERRIDES=ole32,oleaut32,rpcrt4=n wine DCOM98.EXE > > Well, having done so, and having tried setting all the OLE* and RPC* > DLLs to na

Re: Wine's OLE/COM doesn't work, and I can no longer use native COM

2004-08-08 Thread David D. Hagood
Mike Hearn wrote: Install it all as Win98 if possible, and native DCOM like this: WINEDLLOVERRIDES=ole32,oleaut32,rpcrt4=n wine DCOM98.EXE Well, having done so, and having tried setting all the OLE* and RPC* DLLs to native, I am still having the same problem with that app - so I am forced to conj

Re: Add debugstr_rect alias for consistency with other debugging functions.

2004-08-08 Thread Dimitrie O. Paun
On Sat, Aug 07, 2004 at 04:00:25PM -0700, Alexandre Julliard wrote: > Mike Hearn <[EMAIL PROTECTED]> writes: > > > The lack of this confused me for a few minutes, might as well stick it in. > > It's missing because it violates namespace rules. The other debugstr > functions are here for historica

Re: Problem with ITypeInfo

2004-08-08 Thread Dmitry Timoshkov
"Jacek Caban" <[EMAIL PROTECTED]> wrote: > No, I don't. In my case I need only this: > > /* this is where we are coming from */ > +ITypeLib2_AddRef((ITypeLib*)pLibInfo); > ptiRet->pTypeLib = pLibInfo; > ptiRet->index=count; > > but I call ITypeLib_Release in ITypeInfo_Release so I

Re: Add debugstr_rect alias for consistency with other debugging functions.

2004-08-08 Thread Mike Hearn
On Sat, 2004-08-07 at 16:00 -0700, Alexandre Julliard wrote: > It's missing because it violates namespace rules. The other debugstr > functions are here for historical reasons but we shouldn't add new > ones. OK, I suspected that might be the case but inside of Wines code why do we have to prefix

Re: Wine's OLE/COM doesn't work, and I can no longer use native COM

2004-08-08 Thread Mike Hearn
On Sat, 2004-08-07 at 16:02 -0500, David D. Hagood wrote: > Yes, I am - I was under the impression that would give a better shot at > compatability since, when there is a mutually exclusive choice between > the 9X and the NT way, Wine tends to follow the NT way. No, 9x mode is recommended. Progr

Re: Problem with ITypeInfo

2004-08-08 Thread Jacek Caban
Dmitry Timoshkov wrote: "jack" <[EMAIL PROTECTED]> wrote: @@ -3265,6 +3266,7 @@ return NULL; } *ppTypeInfoImpl = (ITypeInfoImpl*)ITypeInfo_Constructor(); + pTypeLibImpl->ref++; Are you sure you need this piece of the patch? It causes the following test program to fail: