How does a command find out who called it?

Ralph DiMola rdimola at evergreeninfo.net
Wed Feb 1 15:30:21 CST 2012


Ken,

Thank you for that little tidbit!!!!!! I was going crazy debugging and try
to figure out the message path in these cases. I wanted the message to fire
off after the handler finished. It bit me for sure. You just made my day!

THANK YOU AGAIN

Ralph DiMola
IT Director
Evergreen Information Services
rdimola at evergreeninfo.net

-----Original Message-----
From: use-livecode-bounces at lists.runrev.com
[mailto:use-livecode-bounces at lists.runrev.com] On Behalf Of Ken Corey
Sent: Wednesday, February 01, 2012 4:10 PM
To: use-livecode at lists.runrev.com
Subject: Re: How does a command find out who called it?

On 01/02/2012 21:03, Ken Ray wrote:
> Take away the "in 0 secs" and it should work fine (I get two lines, one
referring to the button that issued the 'send' and the other referring to
the stack). I'm guessing the "send in time" aspect messes with the
executionContexts.
>
> BTW: Why would you send something in 0 secs? Just curious. if you want it
to be processed right away, why not just "send" it?
>

If you just do a 'send "blah"' it happens right then before the rest of 
the handler. Whereas if you 'send "blah" in 0 seconds', it only runs 
once this handler is finished.  A minor detail, but a potential biteme.

My library is being called from a script, not from a send, so there's 
definitely plenty of breadcrumbs in the executionContext to find my way 
back.

Thanks guys!

-Ken

_______________________________________________
use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode




More information about the use-livecode mailing list