Hi guys, > Am 03.08.2019 um 17:19 schrieb Paul Dupuis via use-livecode > <use-livecode@lists.runrev.com>: > On 8/2/2019 10:33 PM, ambassador--- via use-livecode wrote: >> What are the advantage of instantiating the new stack from data in a prop >> rather than by cloning a substack? > That was my question too.
well the first approach is much much cooler than the latter one, innit? :-) Jokes aside, one advantage is that someone else can create that "template" stack, my customer in this case, and since this is a separate stack file it can thus contain substacks, which can be another big advantage in some situations. > It is a very different way of storing a stack. I have never been representative. 8-) > I imagine that an: open invisible stack (the cSavedStack of stack > "someOtherStack") > would be like a open invisible URL <someStackURL> Yes. > in that it has to be loaded into memory, so it it is not the last line of the > script, I would expect it should be followed by a "wait <sometime> with > messages" to allow all the new stack messages to fire. But as I wrote, if I load a stack from my hd, everything works as advertised!? Anyway, I have a nice workaround and a happy customer. Have a nice weekend. Best Klaus -- Klaus Major https://www.major-k.de kl...@major-k.de _______________________________________________ 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
