On Exit: Do you want to save?
Moderators: jesterKing, stiv
On Exit: Do you want to save?
If the undo stack isn't empty ( ie the user has actually done something to change the scene ), and they go to quit Blender, how about popping up a 'Do you want to save the scene? [Yes] [No] [Cancel] ' dialog box?
I've been caught out with this more than once recently by accident.
Mal
I've been caught out with this more than once recently by accident.
Mal
The old arguement on why this woudn't be possible, was that we would need undo first, so that it is able to detect if an action has been done.
So, maybe it could be done now? It is completely standard behavior, and is very useful. Even if it may store the undo stack in a file - it's another oddity to learn, and even then, it's a hassel to have to dig around to look for that one file, then open it, then resave it to correct position, and then carry on with your work. Besides, as gabio poits out, it doesn't even work on Windows...
So, maybe it could be done now? It is completely standard behavior, and is very useful. Even if it may store the undo stack in a file - it's another oddity to learn, and even then, it's a hassel to have to dig around to look for that one file, then open it, then resave it to correct position, and then carry on with your work. Besides, as gabio poits out, it doesn't even work on Windows...
Website: http://www.shadeless.dk
That's the catch: "you don't have to!". There's a menu entry that does it perfectly fine for you. Except the saving back the file part, but the directory will default to the correct one, you just have to select the correct file.Monkeyboi wrote:it's a hassel to have to dig around to look for that one file, then open it, then resave it to correct position.
Martin
Life is what happens to you when you're busy making other plans.
- John Lennon
- John Lennon
This "mysterious" feeling surrounding blender is not a good thing. UI elements should do exactly what a user expects it to do before they click on it. They shouldn't have to sit there and wondering whether they are about to click a toggle button or a radio style button.z3r0_d wrote:blender isn't supposed to be what people expecthalibut wrote:All other windows programs I have used ask before quitting when changes have been made. It is what people expect, especially new users.
The bottom line is, when windows users click on the close button, many of them are expecting the program to ask to save. As it is, blender is not what some of them expect and as far as they know they have lost their work. Perhaps an option?
- sorry Ilac :p
Last edited by halibut on Sat Nov 27, 2004 2:44 pm, edited 1 time in total.
Please don't put words in other peoples mouths. The only 'bottom line' is that YOU are not everyone so stop speaking for the rest of us 'windows' users. I love the fact that Blender just quits when I want it too. And please note that i use Blender daily at work so the possibility of 'losing' any work costs me/us a lot of time and money - yet it very, very rarely happens and I don't recall it ever happening because I closed Blender without saving.halibut wrote:The bottom line is, when windows users click on the close button, they are expecting the program to ask to save. As it is, blender is not what they expect and as far as they know they have lost their work.
-
- Posts: 0
- Joined: Tue Nov 23, 2004 1:57 am
- Location: Quebec City, Canada
- Contact:
Yes, but as an option. I personally do like that blender doesn't ask anything
When the the system is slow, and i want to free memory, i can just quit blender and be sure that it will quit imediately not like gimp or photoshop with their 25000 popup, 'do you really want to quit ?'

My Portfolio :: www.mentalwarp.com/~fred/
-
- Posts: 0
- Joined: Tue Nov 23, 2004 1:57 am
- Location: Quebec City, Canada
- Contact:
"File unsaved -- yes / no"
then
"Do you Want to quit ? -- yes / no"
then
"Are you sure you want to quit ? -- yes / no"
Sorry, i prefer the blender way, the work is never lost, and my time neither.
A "file unsaved" question is usefull if it's given only when a document is dirty, having unsaved changes (edit ones, not only movement of the UI). Unfortunately, this state is dificult to check in blender, while saving the doc to disc is blazing fast. That why it's done this way.
Nothing irks me more than a progs asking to save changes on an unchanged document (the worst in this aspect could be autocad).
Quit confirmation are usefull if the app takes ages to load and quit. blender can do it in the time you need to read the alert, so why slow things ?
then
"Do you Want to quit ? -- yes / no"
then
"Are you sure you want to quit ? -- yes / no"
Sorry, i prefer the blender way, the work is never lost, and my time neither.
A "file unsaved" question is usefull if it's given only when a document is dirty, having unsaved changes (edit ones, not only movement of the UI). Unfortunately, this state is dificult to check in blender, while saving the doc to disc is blazing fast. That why it's done this way.
Nothing irks me more than a progs asking to save changes on an unchanged document (the worst in this aspect could be autocad).
Quit confirmation are usefull if the app takes ages to load and quit. blender can do it in the time you need to read the alert, so why slow things ?