Which stack called the library stack ?

How can I find out which stack called a library stack from the script of the library stack ? thanks... John Dixon ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url

Re: Which stack called the library stack ?

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 ___

Re: Which stack called the library stack ?

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

Re: Which stack called the library stack ?

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

Re: Which stack called the library stack ?

--- On Fri, 9/24/10, John Dixon dixo...@hotmail.co.uk 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

RE: Which stack called the library stack ?

opened, for some reason the colour of the field when first 'clicking' into it changes the colour to the suspended colour ... all subsequent clicks after the first one and everything is fine... So, the reason for me asking 'Which stack called the library stack' was that I was hoping I could trap

Re: Which stack called the library stack ?

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 ?

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

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

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

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

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 the engine,

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

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