Hello,
Alexander Kochetkov wrote:
> The code like
> static inline MyObject *impl_from_IMyInterface(IMyInterface *iface)
> {
> return (MyObject*)((char*)iface - FIELD_OFFSET(MyObject,
> IMyInterface_iface));
> }
>
> could be replaced with
> static inline MyObject *impl_from_IMyInterface(IMyInt
Hi all,
The code like
static inline MyObject *impl_from_IMyInterface(IMyInterface *iface)
{
return (MyObject*)((char*)iface - FIELD_OFFSET(MyObject,
IMyInterface_iface));
}
could be replaced with
static inline MyObject *impl_from_IMyInterface(IMyInterface *iface)
{
return container_of(MyO
On Sat, Dec 29, 2007 at 09:26:47PM +0200, Saulius Krasuckas wrote:
> ...
> > If something will not work for you please fill a bug report at
> > http://bugs.winehq.org . In case if builtin DCOM support doesn't work as
> > expected you can run "winetricks dcom98" to use native DCOM instead (you
* On Thu, 25 Oct 2007, L. Rahyen wrote:
> * On Thursday October 25 2007 08:08, Fong, Man To wrote:
> >
> > > The communication protocol, pre-defined by TCS manufacturing, is
> > > DCOM. Since the communication protocol is not opened by the
> > > manufacturer. We must install the API provided by
- Original Message -
*From:* Adelle Hartley <[EMAIL PROTECTED]>
*To:* wine-devel@winehq.org
*Sent:* Mon, Dec 10 2007 at 19:06 +0200
*Subject:* COM
> Hi all,
>
> I have some COM DLLs which work fine with VB6 applications on wine.
>
> Is it possible to instantiate a windowsy COM object from
Adelle wrote:
> I have some COM DLLs which work fine with VB6 applications on wine.
> Is it possible to instantiate a windowsy COM object from a linuxy
> application written in some form of C++ (eg, for compilation with gcc)?
Erm, maybe you could write a winelib app, but
you might have to use the
On Thursday October 25 2007 08:08, Fong, Man To wrote:
> > Dear Sir / Madam,
> >
> > We are developing a software which is running on Linux platform. The
> > software will retrieve the information from TETRA Connectivity Server
> > (TCS) which is running on Window 2003 server. The communication
> >
On Thu, 13 Jan 2005 15:21:27 -0600, Robert Shearman wrote:
> But you'll get a warning because the WineD3DResource functions will take
> a different type iface variable as their first parameter. You could cast
> it to the correct type, but you'll lose all type checking on the
> function and I wou
>So, IWineD3DSurface should inherit from IWineD3DResource which in
>turn should inherit from IUnknown. Then you fill out the vtable
>appropriately for overrides. Isn't object orientation in C fun :)
>
>typedef struct
>{
> IWineD3DSurfaceVtbl *lpVtbl;
> DWORD refcount;
>
>} WineD3DS
Mike Hearn wrote:
On Thu, 13 Jan 2005 20:33:10 +, Ann and Jason Edmeades wrote:
Whats the solution?
In d3d8 I would have coded IWineD3DSurfaceImpl_GetParent as
IWineD3DResourceImpl_GetParent(iface, pParent) because the Impl versions
were prototyped - Is this the only way to solve this?
Ann and Jason Edmeades wrote:
I have code which looks like:
HRESULT WINAPI IWineD3DSurfaceImpl_GetParent(IWineD3DSurface *iface,
IUnknown **pParent) {
return IWineD3DResource_GetParent((IWineD3DResource *)iface, pParent);
}
IWineD3DResource_GetParent is a macro:
#define IWineD3DSurface_GetParent(
On Thursday 13 January 2005 22:09, you wrote:
> >Jason seems to have:
> >- IWineD3DSurface inherits from IWineD3DResource
> >- IWineD3DResource inherits from IUnknown
>
> Yep...
>
> >Jason, why IWineD3DSurface inherits from IWineD3DResource ?
>
> Well wine has
>
> /*
On Thu, 13 Jan 2005 20:33:10 +, Ann and Jason Edmeades wrote:
> Whats the solution?
>
> In d3d8 I would have coded IWineD3DSurfaceImpl_GetParent as
> IWineD3DResourceImpl_GetParent(iface, pParent) because the Impl versions
> were prototyped - Is this the only way to solve this?
I'm kind of co
>Jason seems to have:
>- IWineD3DSurface inherits from IWineD3DResource
>- IWineD3DResource inherits from IUnknown
Yep...
>Jason, why IWineD3DSurface inherits from IWineD3DResource ?
Well wine has
/***
**
* IDirect3DSur
>>I have code which looks like:
>>
>>HRESULT WINAPI IWineD3DSurfaceImpl_GetParent(IWineD3DSurface *iface,
>>IUnknown **pParent) {
>>return IWineD3DResource_GetParent((IWineD3DResource *)iface, pParent);
>>}
>>
>>IWineD3DResource_GetParent is a macro:
>>#define IWineD3DSurface_GetParent(p,a)
>>
On Thursday 13 January 2005 21:43, Robert Shearman wrote:
> Ann and Jason Edmeades wrote:
> >Hiya,
> >
> >In the wined3d code I have, for example, a class surface which inherits a
> >lot of methods of Resource. Most of these methods can be called as-is, and
> > I have code which looks like:
> >
> >
Ann and Jason Edmeades wrote:
Hiya,
In the wined3d code I have, for example, a class surface which inherits a
lot of methods of Resource. Most of these methods can be called as-is, and I
have code which looks like:
HRESULT WINAPI IWineD3DSurfaceImpl_GetParent(IWineD3DSurface *iface,
IUnknown **pPar
> Likewise, what's the current status of Installshield support,
> and how much work would it be to fully support
> Installshield-based installers? I don't see any
> open Installshield bug reports, maybe I should file
> one against the apps I have that don't install at
> the moment. (Or would that
Dan Kegel wrote:
Likewise, what's the current status of Installshield support,
and how much work would it be to fully support
Installshield-based installers? I don't see any
open Installshield bug reports, maybe I should file
one against the apps I have that don't install at
the moment. (Or would
Ann and Jason Edmeades wrote:
Have a look at dlls/quartz/pin.h
I have emulated C++ style inheritance by creating a structure that is
included at the start of every derived implementation and then
constructing the vtable at compile time and linking to the base
functions. If you wanted to do the same
>Have a look at dlls/quartz/pin.h
>I have emulated C++ style inheritance by creating a structure that is
>included at the start of every derived implementation and then
>constructing the vtable at compile time and linking to the base
>functions. If you wanted to do the same for d3d{8,9} and wined3d
Ann and Jason Edmeades wrote:
However, this would seem something which is so common - ie inheritence is
used all over the place. How do people handle this? I've looked through a
few places in the code and cant see how this can be done. I could 'pretend'
by initializing the Vtbl as I create the com
Robert Shearman wrote:
Changelog:
Fix for infinite loop that could occur if _invoke_onereq failed.
Please don't apply this patch. I'll submit a better and more complete
one in a minute.
Rob
Mike Hearn wrote:
CCing to wine-devel as the original reply will be forwarded soon too by
Jeroen ..
On Fri, 2004-07-23 at 17:58 +0200, Jeroen Janssen wrote:
I had a short look at the 'world of com' patch, and it looks like there
is something in there that implements the IRemUnknown stuff. Is th
Jeroen Janssen wrote:
Robert Shearman wrote:
Jeroen Janssen wrote:
Hello,
I'm mailing the both of you with a small (com) example attached.
It is a client/server/proxystub example (with binaries), so you need to
/RegServer the server and regsvr32 the proxy.
Now I first manually start the server in a
Forwarding this to the wine-devel mailinglist.
Robert Shearman wrote:
Jeroen Janssen wrote:
Hello,
I'm mailing the both of you with a small (com) example attached.
It is a client/server/proxystub example (with binaries), so you need to
/RegServer the server and regsvr32 the proxy.
Now I first m
CCing to wine-devel as the original reply will be forwarded soon too by
Jeroen ..
On Fri, 2004-07-23 at 17:58 +0200, Jeroen Janssen wrote:
> I had a short look at the 'world of com' patch, and it looks like there
> is something in there that implements the IRemUnknown stuff. Is there
> any easy
On Thu, 22 Jul 2004 17:38:43 +0100, Robert Shearman wrote:
> Unfortunately, you have stumbled into one of the most confusing areas of
> the Win32 API that I think only one person in the world fully
> understands (Don Box in case you are wondering).
Yeah. I'm starting to suspect that Don kept pil
Jeroen Janssen wrote:
I am not sure, but there seems to be a difference in the outproc handling
of the CoCreateInstance call?
This goes ok:
hr = CoCreateInstance(CLSID_Component1, NULL, clsctx, IID_IX, (void**)&pIX) ;
However this seems to go wrong?:
hr = CoCreateInstance(CLSID_Component1, NULL, cl
> From: Mike Hearn <[EMAIL PROTECTED]>
>> Maybe my 'real' problem is that based upon the logging, I also see a
>> CFProxy Unhandled interface for the first interface that the client is
>> trying to access (but I need to know more about how COM/wine deals with
>> this).
>
> Are you sure you're using
On Thu, 22 Jul 2004 14:45:31 +0200, Jeroen Janssen wrote:
> Maybe my 'real' problem is that based upon the logging, I also see a
> CFProxy Unhandled interface for the first interface that the client is
> trying to access (but I need to know more about how COM/wine deals with
> this).
Are you sure
> IRunnableObject does not have anything to do with COM marshalling; it is
> an OLE thing. MSDN says this about it: "The *IRunnableObject *interface
> enables a container to control the running of its embedded objects". So
> basically, I don't see any reason why CFProxy (IClassFactory proxy)
> shou
Jeroen Janssen wrote:
Hello,
I'm trying to run 2 programs:
1) is a COM server program
2) is a COM client program
Now, program 2) tries to access a COM component from 1) (outproc).
It seems some marshalling is being done, but eventually I get:
fixme:ole:CFProxy_QueryInterface Unhandled interface:
{0
33 matches
Mail list logo
