Oddly, google flagged Scott's message as spam. I only found it when looking after Craig referred to it . . .
On Thu, Aug 22, 2013 at 1:38 PM, Scott Rossi <sc...@tactilemedia.com> wrote: > 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" <doch...@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@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@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode -- Dr. Richard E. Hawkins, Esq. (702) 508-8462 _______________________________________________ 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
