🚀 go-pugleaf

"Gary D" <gcdesroches@nctc.com> wrote in message 
news:4366d403@newsgroups.borland.com...

> I added the code for the TTheadList and got it to compile
> without a problem. I still can not call Trigger(); from the server side.

Then you are still not using it properly.  Please show your actual code. 
This is not that hard to implement.  I've already given you the pieces for 
it.  And I know it works because I use it all the time in my own COM 
servers.

> It IS public as you said but it is part of the COM class which I am 
> assuminig means I need to have an instance of the class on the
> server side to be able to access Trigger() from.  MyClass->Trigger(); ??

Of course you do, and you do have such an instance available.  Everytime the 
COM object is instantiated by a client, an instance of your class is created 
on the server side.  That is the whole purpose of the list code I gave you - 
so that your server code has access to all active instances of the class.

> I can get instances of the Implementation but get access violations if I
> try to use it or the server will just lock up.

Then you re not using it correctly.

> calling Trigger() outside the class will simply not compile.
> I get not a member errors etc.

Then you are not accessing it correctly.

> I looked at the client side and see that there is this:
>
>     FEventSink.OnEvent1 = OnEvent1;
>     FEventSink.Connect(FTestEventsImpl);
>
> but I don't know how it works

You did not read the articles I pointed you to, did you?  The client's Sink 
is implemented in terms of the IConnectionPoint interface.  Connect() 
queries the COM object for the IConnectionPointContainer interface, and from 
that then obtains the IConnectionPoint interface for your events.  The 
client then calls IConnectionPoint::Advise(), which psses an IDuspatch 
interface to your server.  On the server side, every time you call one of 
the Fire_...() methods, the client's IDispatch::Invoke() method is called, 
specifying the ID and parameters of the fired event.  All of this is handled 
transparently for you.  The only thing you have to concern yourself with in 
your own code is connecting the Sink to the client side object, and then 
calling the desired Fire_...() methods on the server side.


Gambit