I do not understand exactly what you mean, but I will give it a go. It sounds like you work with a copy of a stack to update it, then replace the older copy with the newer one, but LC is remembering the older one.
There is a property of a stack called destroyStack, an unfortunate name because it only destroys the copy in memory. I believe the corresponding checkbox is Purge Stack On Close. If this is unchecked, closing the stack will still leave it in memory, so that any future reference to it will reopen it. I am unsure if my understanding of what you are doing is correct, but I would reconsider how you are going about things if you are replacing one stack with another just like it. In any case, check that checkbox and see if that doesn't help. Bob On Jul 28, 2011, at 10:05 PM, Joe Lewis Wilkins wrote: > Hi everyone, > > I'm struggling; maybe I should say "fighting" with LC. I have an app in which > I do some things that create new cards in one of the sub-stacks. In the > process of refining things I want to swap the original stack with the one > that has the new cards, but LC always remembers the larger stack. After a > while, I'm usually able to have the smaller one used, but it's a real effort. > Have I missed some simple way of doing this. In most other programs, I would > be able to just replace the large one with the small one. I can do it in this > case too, but the small one is never seen. > > TIA, > > Joe Wilkins > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
