Re: Full support for executionContexts (was Re: Which stack called the library stack ?)

2010-09-24 Thread Dar Scott
On Sep 24, 2010, at 5:14 PM, Mark Wieder wrote: ... By removing the offending paragraph in the executionContexts dictionary entry, RunRev would effectively be making a commitment to including descriptions of any changes to the value in the engine revision report for new versions. Or at least ap

Re: Full support for executionContexts (was Re: Which stack called the library stack ?)

2010-09-24 Thread Mark Wieder
Dar- Friday, September 24, 2010, 3:16:11 PM, you wrote: > On Sep 24, 2010, at 4:00 PM, Mark Wieder wrote: >>> I wish that RunRev would bless the format of the property or provide >>> other properties or functions that provide context information. >> >> I do too, but it's deep in the bowels of t

Full support for executionContexts (was Re: Which stack called the library stack ?)

2010-09-24 Thread Dar Scott
On Sep 24, 2010, at 4:00 PM, Mark Wieder wrote: I wish that RunRev would bless the format of the property or provide other properties or functions that provide context information. I do too, but it's deep in the bowels of the engine, so changing it is likely to break everything. I rather coun

Re: Which stack called the library stack ?

2010-09-24 Thread Mark Wieder
Dar- Friday, September 24, 2010, 2:49:31 PM, you wrote: > Important: The value of the executionContexts may be changed in > future versions of Revolution, it is not recommended to write code > that depends on its contents. It has ever been thus. The format of the executionContexts changed slig

Re: Which stack called the library stack ?

2010-09-24 Thread Dar Scott
On Sep 24, 2010, at 3:18 PM, Richard Gaskin wrote: John Dixon wrote: How can I find out which stack called a library stack from the script of the library stack ? The executionContexts will return a list of the calling chain. Unfortunately, the LiveCode dictionary contains this statement:

RE: Which stack called the library stack ?

2010-09-24 Thread John Dixon
ry stack' was that I was hoping I could trap for which stack was suspended or not and handle it that way... regards John Dixon > Date: Fri, 24 Sep 2010 14:25:42 -0700 > From: janschen...@yahoo.com > To: use-revolution@lists.runrev.com > Subject: Re: Which stack called t

Re: Which stack called the library stack ?

2010-09-24 Thread Jan Schenkel
--- On Fri, 9/24/10, John Dixon wrote: > > How can I find out which stack called a library stack from > the script of the library stack ? > > thanks... > > John Dixon >     Are you wondering which script issued the 'start using' command? Or which script calls one of the handlers in your libr

Re: Which stack called the library stack ?

2010-09-24 Thread Richard Gaskin
John Dixon wrote: How can I find out which stack called a library stack from the script of the library stack ? The executionContexts will return a list of the calling chain. -- Richard Gaskin Fourth World LiveCode training and consulting: http://www.fourthworld.com Webzine for LiveCode de

Re: Which stack called the library stack ?

2010-09-24 Thread Dar Scott
On Sep 24, 2010, at 2:11 PM, John Dixon wrote: How can I find out which stack called a library stack from the script of the library stack ? A way that works in some cases is to look at the target and climb owners until you get to a stack. If you are wanting to do callbacks, you might cons

Re: Which stack called the library stack ?

2010-09-24 Thread DunbarX
Any stack can be a library stack. It just means that stack is in use, so its stack scripts are available in the hierarchy. The "stacksInUse" property lists all stacks that are used this way, and gives the order they are placed. Craig Newman ___ use-rev