Paul McNett wrote: > Carl Karsten wrote: >> Paul McNett wrote: >>> Carl Karsten wrote: >>>> johnf wrote: >>>>> On Thursday 31 May 2007 20:48, Paul McNett wrote: >>>>>> 2) If you have a generic event handler that could receive events from >>>>>> several objects, you may well need to know what object emitted the >>>>>> event, so you'd get that reference using evt.EventObject. >>>> I get the concept, but can't see how it would be implemented. what does >>>> the >>>> code look like that uses evt to identify which object the raised the event? >>> Do you mean in the Dabo framework? When a dEvent gets raised using >>> raiseEvent(), the EventObject is sent to the dEvent constructor, where >>> it arrives in the dEvent.EventObject property, making it available from >>> the evt arg in event callback functions (the evt arg is a dEvent instance). >>> >>> But this is stuff that should probably get discussed on dabo-dev, not >>> dabo-users, as the whole point of Dabo is to shield users from having to >>> know such uninteresting minutia. >>> >> no no no.. user side implementation... I was looking for exactly what John >> posted (thanks John): > > But wait, I gave you that in my paragraph above already: "...it arrives > in the dEvent.EventObject property..." and "...the eve arg is a dEvent > instance...".
You gave me a really good clue, but I missed it :) I think I got evt and evt.EventObject mixed up. I was looking at evt for something that I could use to identify what object it came from. Not sure I even looked twice at EventObject. my guess is that my brain said "that is what you are looking at, keep looking." (scary place, isn't it?) Carl K _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
