Printed dictionary (was Re: send mouseup to control)

Mark Wieder ahsoftware at sonic.net
Thu May 25 18:31:31 CEST 2017


On 05/25/2017 07:47 AM, Richard Gaskin via use-livecode wrote:
> James Hale wrote:
> 
>  > In following them discussion on execution contexts Richard wrote:
>  >> The executionContexts is documented, though in all fairness that
>  >> Dict entry includes a note about not relying on the format of its
>  >> contents.
>  >
>  > ...this morning the printed dictionary arrived! 🎉
>  >
>  > So I looked up executionContexts
>  >
>  > Where I read...
>  > '' 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."
>  >
>  > BTW there was no mention of any caveats in using this property.
> 
> In v6.7 and later (possibly earlier too; I didn't check any version 
> prior to v6.7), the Dictionary entry for the executionContexts includes 
> this note:
> 
>      Important: The value of the executionContexts may be
>      changed in future versions of LiveCode, it is not
>      recommended to write code that depends on its contents.
> 
> The web version of the Dictionary, though reportedly a few versions 
> behind more recent versions (to the confusion of a few forum readers), 
> also includes that note:
> https://livecode.com/resources/api/#livecode_script/executioncontexts

Interesting. I stand corrected - the executionContexts is documented 
after all. It *is* a bit out of date, though, as it doesn't reflect the 
additional parameter(s) for behavior objects. The additional parameter 
was added in a way that cleverly maintains backward compatibility, 
although if you need to trace your way through behaviors you need to 
take it into account.

-- 
  Mark Wieder
  ahsoftware at gmail.com



More information about the use-livecode mailing list