Stack Save As issue

[Peter M. Brigham]

The problem with this tack is that often you will have stack references in your scripts that will break.

-- Peter

Peter M. Brigham
pmbrig at gmail.com
http://home.comcast.net/~pmbrig

On Dec 3, 2012, at 9:27 PM, Robert Sneidar wrote:

> Save as a different name. Save as will open the "new" stack in memory, which will conflict with the present stack with the same name. 
> 
> Bob
> '
> 
> On Dec 3, 2012, at 8:10 AM, Peter Haworth wrote:
> 
>> Whenever I use the IDE Save As menu item to save a stack in a different
>> file (or do it by script), I get the IDE messages about a stack with the
>> same name as one already in memory being loaded.  It seems that the IDE
>> attempts to load the "saved as" version of the stack after saving it.
>> 
>> Is anyone else seeing this? It doesn't seem consistent with how Save As
>> works in other programs.
>> 
>> This is with LC 5.5.0
>> 
>> Pete
>> lcSQL Software <http://www.lcsql.com>
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at 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 at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode