On 12/8/10 3:48 PM, Peter Haworth wrote:
Thanks for the explanation. Haven't tried the destroyStack property but
using Close and Remove From Memory wants to close the stack file, not
just the currently active stack window.
So I guess the only way to discard changes to a specific stack window is
Thanks for the explanation. Haven't tried the destroyStack property
but using Close and Remove From Memory wants to close the stack file,
not just the currently active stack window.
So I guess the only way to discard changes to a specific stack window
is to either use Close/Remove From Mem
On 12/8/10 3:00 PM, Peter Haworth wrote:
The standalone is a new situation for me but I have experienced perhaps
a dozen instances of missing saves in the couple of years I've been
using Rev/LC. To be clear, I'm talking about script edit changes here
not card layouts or object property changes. I
The standalone is a new situation for me but I have experienced
perhaps a dozen instances of missing saves in the couple of years I've
been using Rev/LC. To be clear, I'm talking about script edit changes
here not card layouts or object property changes. I definitely try to
save more ofte
On 12/8/10 1:03 PM, Peter Haworth wrote:
Well I'm not sure I'm ready to say that save as standalone NEVER saves
script changes, just that ti didn.t appear to in this particular
instance. I can't figure out what I did differently this time around to
cause that problem. I guess the real message is
You're right, there are things you can do in the IDE that it would be
unaware of.
But these are simple edits made to scripts using the standard script
editor window. I haven't narrowed down the exact circumstances that
cause the IDE to not save those changes but it does happen. I use the
> ... I guess the real message is that you can't rely on the IDE to save
> when it should and you have to deal with it however you can. Personally, I
> think that's a ridiculous situation but it is what it is.
Hello Pete,
One more thing to consider before coming to a negative conclusion about the
Well I'm not sure I'm ready to say that save as standalone NEVER saves
script changes, just that ti didn.t appear to in this particular
instance. I can't figure out what I did differently this time around
to cause that problem. I guess the real message is that you can't
rely on the IDE to
Yep, looking forward to giving glx2 a try
Pete Haworth
http://www.mollysrevenge.com
http://www.sonicbids.com/MollysRevenge
http://www.myspace.com/mollysrevengeband
On Dec 8, 2010, at 10:37 AM, Bob Sneidar wrote:
Also, remember now that GLX2 is open source, and that has an
autos
Oh that's interesting. Save as Standalone does not save your script changes
beforehand. Well that is good to know. Still, I save every time I make a series
of code changes that will compile, like every few lines or so. I think with
GLX2 and Remo, simple hitting the enter key will save and compil
Also, remember now that GLX2 is open source, and that has an autosave feature
as well. Remo (heretofore tRev) also auto saves if I am not mistaken.
Bob
On Dec 7, 2010, at 5:32 PM, Björnke von Gierke wrote:
> Yes that is annoying.
>
> The problem here is that there's no assured way for the L
I'm not totally sure about this now but I think the circumstances
involved using the "Save as Standalone" option. I did that to create
a new standalone and got the usual prompt about saving everything so
assumed everything had been saved. Only after I ran the standalone
and found that the
Yes that is annoying.
The problem here is that there's no assured way for the LC engine to know
wether a stack has been changed. Sure, the IDE tracks mouse clicks, changed
scripts and a few other things. But if for example, you lock messages at the
wrong point, then the IDE is unaware, and thi
I just came across another instance of a pet peeve of mine. I lost a
couple of hours of scripting work because for some reason that isn't
clear to me the IDE doesn't always save everything when you exit. It
asked me if I wanted to save and I confirmed that I did, yet a bunch
of coding cha
14 matches
Mail list logo
