Director
> Evergreen Information Services
> rdim...@evergreeninfo.net
>
>
> -Original Message-
> From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On
> Behalf
> Of Peter Haworth
> Sent: Monday, December 03, 2012 1:10 PM
> To: How to use LiveCode
>
The problem with this tack is that often you will have stack references in your
scripts that will break.
-- Peter
Peter M. Brigham
pmb...@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
: Monday, December 03, 2012 1:10 PM
To: How to use LiveCode
Subject: Stack Save As issue
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
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
Yes, I'm seeing that, too.
- Charles
On 2012-12-03, at 12:10 PM, 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
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 e
