How to lose your work in a couple of clicks (dirty flag)

[Richard Gaskin]

Ralph DiMola wrote:

 > I see this as a departure from other SW. I read "Don’t save" as
 > "Don't save now" not as "Don't save ever".

I don't see those.  When I make a standalone on a stack with unsaved 
changes, the options I see are "Don't Save", "Cancel", and "Save".


 > I just made my first non-mobile standalone(since 2012) just the other
 > day. And I was surprised to see the stack get closed and get
 > re-opened as JLG documented. At the time I thought the IDE went crazy
 > but every other desktop build did the same thing and I said to myself
 > "Hmmm, that's interesting...". Stacks don't get closed on mobile
 > builds. Maybe that is why I was confused.

The MC IDE's Standalone Builder would build in-place, without needing to 
close and re-open.  But this was because it was much more limited, since 
the LC SB allows options for making all sorts of changes to the stack 
file before building, requiring that the build actually happens on a 
copy and not the original you're working on.

That said, as I noted here a few weeks ago some testing I'd done 
revealed that there's actually no problem within the engine with having 
two stacks open with the same name, but there is a limitation with the 
algo the topstack function uses which can produce odd results in an 
otherwise beautiful and simple system.
http://quality.livecode.com/show_bug.cgi?id=18793

While that's under review, the current SB will close the stack you're 
working on, build the standalone from an invisible copy, then re-open 
when it's done.

Yes, not how consumer apps work, but then again end-users aren't tasked 
with building standalones, so there are many ways the operations LC 
supports requires a different UI/UX than end-user software.

The main thing is that the save prompt seems to do what we're asking of 
it, either saving or discarding changes according to the option we choose.


 >> Workflow question: under what circumstances do you find it useful
 >> to build a standalone that doesn't reflect the >current state of
 >> the stack?
 >
 > I see your point Richard and can’t come up with a very useful
 > scenario, but one could click the wrong button whilst in the middle
 > of a hot-fix panic.

Not so much a point, but an honest question.  We all do things 
differently, and sometimes there can be good reasons for folks wanting 
to do something that's different from how I do things.

For myself, I have a habit of hitting the Enter key when I see that 
dialog, so I've managed to compensate for the risks introduced by my fat 
fingers. :)

-- 
  Richard Gaskin
  Fourth World Systems
  Software Design and Development for the Desktop, Mobile, and the Web
  ____________________________________________________________________
  Ambassador at FourthWorld.com                http://www.FourthWorld.com