Suggestion: the callingHandler

Scott Raney raney at
Sat May 31 21:54:01 EDT 2003

On Sat, 31 May 2003 curry <curry at> wrote:

> How about a function that returns the name of the handler that called 
> the current handler? For example, this would be useful when a handler 
> needs to reset each time a different handler calls it, or to keep 
> track of different sets of data for each handler that calls it.

You can get this information with the executionContexts function.  I
hesitate to even mention it, however, because it was designed for
debugging purposes *only*: using it for conditional execution would
be, IMHO, heinous.  Use an optional parameter instead unless you want
your status as an xTalk wizard permanently revoked.

> Curry

Scott Raney  raney at
MetaCard: You know, there's an easier way to do that...

More information about the use-livecode mailing list