Stacks and Sub Stacks
phil at pdslabs.net
Wed Sep 25 14:04:34 EDT 2019
On 9/25/19 7:43 AM, Sannyasin Brahmanathaswami via use-livecode wrote:
> if you have this in the message box.
> put the openstacks
> you only get the
> 1. presently open binary stacks
> 2. any script only stack that you explicitly have open in the IDE
Some more options:
This returns a list of all [binary] stacks in memory, both main & sub,
whether they are open or not.
put the mainStacks
Returns a list of all mainstacks in memory, including script-only
stacks, whether open or not.
> But, can you we a list of all stacks available to the message path "right now"
> We can query the stack files, but they are included with stack, but not necessarily open.
And the stackFiles may list some stacks that no longer exist in those
locations. ' The stackFiles of stack "myStack" ' is a user-supplied
setting. It can get out of sync with reality pretty quickly as an app's
folder tree changes. (but I guess you could script it to keep it current)
My $0.02 -
> Another say to put this is when doing a
> start using "MyControls.livecodescript"
> …later on, how do you query for all stacks "open" by "start using"
> You probably mean script-only stacks.
> Substacks are just stacks, but they live in the same file as the mainStack. It helps with organization, and when you save one, you save them all. You can only have one mainStack, but as many subStacks as you like.
> For me, I have projects that use substacks for, say, data entry. The subStack is built just for that purpose.
> When making a standalone, substacks are included in the final package.
> Just practice a bit.
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode