executionContexts is way more useful. Bob S
> On Oct 25, 2019, at 11:14 , Mark Wieder via use-livecode > <use-livecode@lists.runrev.com> wrote: > > On 10/25/19 11:00 AM, Richard Gaskin via use-livecode wrote: >> Tom Glod wrote: >> > But is there a function that I can call inside a handler that will >> > tell me the name of the handler? >> I'm curious: what are you doing that needs this? > > Not Tom, but... > > I do this all the time when I need to print a debugging message to the > messagebox. Sometimes handlers abort before getting to important statements > and by placing these statements at various points I can tell whether or not a > handler got triggered. > > put param(0) & cr after msg > > -- > Mark Wieder > ahsoftw...@gmail.com > > _______________________________________________ > 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
