RE: figuring out the previous handler

[Irv Kalb]

There is no built-in mechanism.  (Ancestor is not the right thing).

The easiest way to do this is to pass a different value (probably a 
symbol) from the two different  places:

on mouseUp
  SomeHandler(<some values>, #mouseUp)
  ....
end
on <whatever the target of your sendSprite is>
  SomeHandler(<some values>, #sendSprite)
 ...
end
Then in the code you posted below have a parameter that gets this 
value and branches on it:

on SomeHandler <standard parameters>, symPreviousHandler
   case symPreviousHandler of:
       #mouseUp:
         gTools.mRecordData("set")
       #sendSprite
         gTools.mRecordData("get")
       ...
     end case
  ...
Irv



At 4:25 PM -0500 12/9/03, Mendelsohn, Michael wrote:
 > Do you need the handler to know, or do you need to know for debugging
purposes?
I need the handler to know the previous handler, as in:

if lingoPreviousHandler = "mouseUp" then -- or some such wording
 gTools.mRecordData("set") -- something clicked caused to go here.
else if lingoPreviousHandler = "sendSprite"
 gTools.mRecordData("get") -- something else happened, so go here.
end if
-- arguments.caller in place of "lingoPreviousHandler" would handle this
fine
[To remove yourself from this list, or to change to digest mode, go 
to http://www.penworks.com/lingo-l.cgi  To post messages to the 
list, email [EMAIL PROTECTED]  (Problems, email 
[EMAIL PROTECTED]). Lingo-L is for learning and helping with 
programming Lingo.  Thanks!]


--

Multimedia Wrangler.
[To remove yourself from this list, or to change to digest mode, go to 
http://www.penworks.com/lingo-l.cgi  To post messages to the list, email [EMAIL 
PROTECTED]  (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping 
with programming Lingo.  Thanks!]