Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #5349

Re: COM components and events

From "Dirk (Belgium)" <dirk.dot.herijgers@pbprojects.dot.be>
Newsgroups comp.lang.clipper.visual-objects
Subject Re: COM components and events
Date 2013-06-11 11:27 +0000
Organization A noiseless patient Spider
Message-ID <kp71iv$mk4$1@dont-email.me> (permalink)
References <kkque0$542$1@dont-email.me> <kkrgeu$aib$1@speranza.aioe.org> <kp5al5$kpa$1@dont-email.me> <c643cd05-33c3-4f9e-91dc-9dc0a389105f@googlegroups.com>

Show all headers | View raw


Carlos,

Where did you find this ?
Is there a place in the SDK where you can find the combined OCX+EVent ?
Is there some more help about this ?

Dirk

===================

Carlos Rocha wrote:

> On Monday, June 10, 2013 8:49:57 PM UTC+1, Dirk Herijgers wrote:
> 
> > I don't understand how any event is comming into VO ?
> > Could you explain this a little more ?
> 
> I I understood you well, you have an Automation Object, not an
> ActiveX Control (ocx), and VO can't receive events from Automation
> Objects, is this right?
> 
> If so, one way to receive these events is to create an ActiveX
> Control (ocx) in VB6 that holds your object and delegate their events
> to VO. From VO side it works like any other ocx.
> 
> Let's say you generate your Com Object class using VO "Automation
> Server..." wizard and named it ComObject.
> 
> now you should generate the VB6 control using "Setup OLE Control...".
> Let's say you name it OcxObject.
> 
> //----------------------------------------------
> method Init(oOwner) class MyWindow
> local oComObject as ComObject  // the Automation object
> local oOcxObject as OcxObject  // the ActiveX control
> 
> oComObject := ComObject{}
> 
> oOcxObject := OcxObject{self, -1}
> oOcxObject:HyperLabel{#OcxObject, null_string, null_string,
> null_string} oOcxObject:CreateEmbedding("MyComServer.MyObject")
> 
> // pass the ComObject to the VB6 control
> oOcxObject:SetComObject(oComObject)
> 
> return self
> //-----------------------------------------------
> 
> From now on you will receive the event "SomeEvent" in the
> corresponding method:
> 
> // -----------------------------------------------
> method OcxObjectSomeEvent(s, b) class MyWindow
> // do whatever you need here
> return nil
> //------------------------------------------------
> 
> Note the VO event naming convention: the symbol passed to Hyperlabel
> call (#OcxObject) plus the event name (SomeEvent)
> 
> I hope it's clear enough
> 
> __
> Carlos



-- 

Back to comp.lang.clipper.visual-objects | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

COM components and events "Dirk (Belgium)" <dirk.dot.herijgers@pbprojects.dot.be> - 2013-04-19 08:14 +0000
  Re: COM components and events Carlos Rocha <carlos.rocha@doossier.com.removethis> - 2013-04-19 14:22 +0100
    Re: COM components and events "Dirk Herijgers" <dirk.at.@triviant.dot.be> - 2013-06-10 19:49 +0000
      Re: COM components and events Carlos Rocha <jazzda1307@gmail.com> - 2013-06-10 15:20 -0700
        Re: COM components and events "Dirk (Belgium)" <dirk.dot.herijgers@pbprojects.dot.be> - 2013-06-11 11:27 +0000
          Re: COM components and events Carlos Rocha <jazzda1307@gmail.com> - 2013-06-11 09:48 -0700
  Re: COM components and events "Jamal" <jamal@examples.net> - 2013-04-19 12:39 -0400

csiph-web