On Mon, Oct 17, 2016 at 12:14 PM, J. Landman Gay
wrote:
> Is the stacks destroyStack property set to true? If not, just closing it
> isn't enough. Also, if it's a substack, it won't ever be removed as long as
> its mainstack is open.
I even tried setting every destroy property I could locate, a
On 10/17/16 11:35 AM, Dr. Hawkins wrote:
the application browser shows the file as a loaded
main stack but clicking to open it causes it to disappear from that pane.
I don't think this is related to the problem, it's a bug in the App
Browser that's been there forever. I'm so used to it that I
On 10/17/16 5:39 AM, Mark Waddingham wrote:
This isn't in fact a bug, just a subtle interaction with the stackFiles
property of your 'Master' stack.
The stackFiles property maps names of stacks to filenames - it basically
means that when the engine resolves a chunk reference 'stack ', if
there i
On Mon, Oct 17, 2016 at 3:39 AM, Mark Waddingham wrote:
> The stackFiles property maps names of stacks to filenames - it basically
> means that when the engine resolves a chunk reference 'stack ', if
> there is no stack in memory with the name , then it will look through
> the stackFiles property
Perhaps the rule of thumb is never use two stacks with the same name in the
same project. You may want to give the template stack a different name, then
store the name of whichever stack you want to work with in a variable, then
update all references to that stack to use the variable.
Bob S
Thanks Mark for that intervention. In the way this is a gotcha that should be
better documented, since one **must** populate the stackFiles property as a
side effect of including the stacks in the project in its standalone settings -
the information in the list of stacks to be included is exactl
On 2016-10-17 11:15, Graham Samuel wrote:
Thanks Jacque - wise words as always. The idea that the delete would
work depending on whether the stack was newly created had not occurred
to me, but seems like a good reason why my simplified tests didn’t
show the problem. I will try again to create a s
Thanks Jacque - wise words as always. The idea that the delete would work
depending on whether the stack was newly created had not occurred to me, but
seems like a good reason why my simplified tests didn’t show the problem. I
will try again to create a simple demo, and hopefully I can file a bu
I don't have an answer for you, but the problem may be related to
something I noticed when LC 7 was released. I have automated scripts
that create and/or update a series of stacks. When changes are completed
to each stack, the script does this:
save stack x
close stack x
delete stack x
Prior
