pete at mollysrevenge.com
Wed Dec 8 14:03:42 EST 2010
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 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.
On Dec 8, 2010, at 10:39 AM, Bob Sneidar wrote:
> 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 compile it.
> On Dec 7, 2010, at 5:52 PM, Peter Haworth wrote:
>> 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 bug I had bee working on was
>> still there did I realise that my changes hadn't been saved.
>> I don't think I've ever come across the lack of save problem when
>> building a standalone before..
>> Pete Haworth
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the Use-livecode