Re: Stack Save As issue

I've entered this into the QCC as bug# 10581. Pete lcSQL Software On Mon, Dec 3, 2012 at 6:47 PM, Ralph DiMola wrote: > Pete, > > Same Here. I have resigned to closing then re-opening LC whenever I do a > Save As, > > Ralph DiMola > IT Director > Evergreen Information Ser

Re: Stack Save As issue

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

RE: Stack Save As issue

Pete, Same Here. I have resigned to closing then re-opening LC whenever I do a Save As, Ralph DiMola IT 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:

Re: Stack Save As issue

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

Re: Stack Save As issue

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