Finding the calling code/object/script?

[dunbarx at aol.com]

What Mark and Scott said.


Just a comment about documentation. The dictionary says clearly, though it was not findable by me until I knew what property to look for:




A common use of the executionContexts is to obtain the name of the object and handler that called the current handler, this information is available as: line -2 of the executionContexts.


Craig


-----Original Message-----
From: Scott Rossi <scott at tactilemedia.com>
To: LiveCode Mail List <use-livecode at lists.runrev.com>
Sent: Thu, Aug 22, 2013 4:38 pm
Subject: Re: Finding the calling code/object/script?


You might try the executionContexts property (may still be undocumented).

Use this after executing something: put the executionContexts

Shows the objects that handled messages
.

Regards,

Scott Rossi
Creative Director
Tactile Media, UX/UI Design




On 8/22/13 12:44 PM, "Dr. Hawkins" <dochawk at gmail.com> wrote:

>Is there a way to work back up a message to see where a command
>originated?
>
>I am trying to trap a message that used to be valid in my code, that
>isn't.  Earlier versions allowed this message to go straight to a
>field.
>
>So a "send someCommand to fld abc" is no longer valid; it must now
>come in the context of "someCommand arguments" in the code.
>
>Is there a way inside of the handler of someCommand to find out whow
>it was invoked?
>
>-- 
>Dr. Richard E. Hawkins, Esq.
>(702) 508-8462
>
>_______________________________________________
>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
>



_______________________________________________
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