On Fri, Nov 4, 2016 at 12:24 PM, Mark Waddingham <m...@livecode.com> wrote:
> I suspect it will be because you are referencing your stacks by (the old) > filename somewhere else and not name - thus causing the engine to load in > the old file, the stack in which has the same name as the existing stack in > memory. > > 'Saving as' does not create a new stack (in memory) it just saves the > stack which is in memory to disk in a new file. > > Putting it another way, the 'new' stack is already loaded as it is the > same stack as it was before - the only things which have changed is the > stacks filename property and there being a new file on disk. > Hmm. I started with a bare "save as", and had to add other pieces to make it work (but I forget why now). Can I reduce it to just "save as" and be on my merry way? -- Dr. Richard E. Hawkins, Esq. (702) 508-8462 _______________________________________________ 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
