🚀 go-pugleaf

David Reeve <drscientific@powerup.com.au> wrote:
> 
> I've just been doing something similar, but using the events wizard
> built into D5.  A quick check with MemProof shows the clients aren't
> leaking when they handle an event.
>  
> I'm no COMS guru either..... this stuff is fun, but really boggles my
> tiny brain. However, the Invoke method for the event dispatch looks like
> it might be at odds for the way Delphi handles things. Have a look at
> TServerEventDispatch.Invoke in the ole.pas. Notice that parameters are
> transferred as variant array of type olevariant. Perhaps your
> FControl.InvokeEvent in fact does this? What parameter is the
> eventhandler code in the client looking for?
> 
> Dave

Hi Dave,

Thanks for your response.  That was very perceptive of you to notice
the difference in implementation between my InvokeEvent() method and
the corresponding method in TServerEventDispatch.  I modified my
routine to conform to TServerEventDispatch, and everything still
worked, but unfortunately the memory leak was still present.

I guess it looks like my only recourse is to rewrite the VB OCX
functionality as a Delphi class (or control) and hope the leak doesn't
reappear. :(  But thanks again for your insight!

- Mike