Richard,
The executionContexts contains a list of all handlers and objects that
called one of the handlers in the current chain.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
KvK: 50277553
Use Color Converter to convert CMYK, RGB, RAL, XYZ, H.Lab and other
colour spaces. http://www.color-converter.com
Buy my new book "Programming LiveCode for the Real Beginner"
http://qery.us/3fi
Fill out this survey please
http://livecodebeginner.economy-x-talk.com/survey/
On 8/22/2013 21:44, Dr. Hawkins 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?
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
