Why the Save dialogue in OS X
gregory.lypny at videotron.ca
Thu Jun 17 14:39:37 CDT 2004
Thanks for responding. If by "belt-and-suspenders" you mean
unpredictable, then you're right. It seems to happen to a couple of
the stacks in my project but not all. And for those couple of stacks,
not all the time. I've got other projects where this does not happen
at all. I'm not convinced that something is not amiss, perhaps some
sort of message passing that I'm doing in some stacks and not others.
I'm a little concerned that this will create confusion and be an
annoyance to my users when I build a stand alone. Many different
stacks are opened and closed as simple information windows. The idea
of saving makes no sense for these because there is nothing to save.
And if there was, I thought that closeField and closeStack handlers
could pretty much ensure that data won't be lost.
On Jun 17, 2004, at 11:02 AM, Jeanne A. E. DeVoto replied:
> At 12:56 AM -0400 6/17/2004, Gregory Lypny wrote:
>> I'm not sure why I keep getting the save dialogue ("Do you want to
>> save changes to stack ...") when I close certain stacks by clicking
>> the red close button. No changes have been made to the stacks.
> The engine doesn't provide a "changed since last save" flag, so the
> IDE takes a belt-and-suspenders approach to deciding whether the
> stack might have been changed.
> Fairly often, this results in Rev asking to save when nothing has
> changed - but that's better than having it fail to ask when it needs
More information about the use-livecode