Sat, 10 Apr 2004 11:39:13 +0000
Perhaps it could be rigged to where whenever you edit something an
issaved var is set to 0, when you save it is set to 1 and will remain 1
until something is changed. Then when exiting, if issaved is 0 then it
will prompt, if not it will quickly exit upon request.
I think I could pull it off... then again someone probally already has
detection for if it's saved and dosn't have blender checking before it
> I agree that there should be some kind of confirmation when one quits
> blender with work that has not been saved (which is what most apps
> do). I have been bitten by a similar problem when hustling through a
> series of edits, accidentally hitting the q-key, instinctively
> pressing the Enter key, and then realizing I had just lost my work.
> This was improved when someone changed it so that quitting via the
> keyboard required CTRL-Q instead of the q-key by itself. Even so, I do
> think it would be good to have blender "aware" of unsaved work, and
> prompt the user accordlingly when they exit blender, regardless of
> which exit method is used.
> Jim (russT)
> Bf-committers mailing list