if the user saves a file and then presses quit, the program asks if it should save before quitting. This is unnecessary if the file has not been changed since the last save.
I often save new versions (with a new date, new time) before quitting. It’s quite irritating to see the “unsaved-changes” dialog box popping up again and again.
Could we please remove it? (If the last save is the current version, then no “save-on-exit”)
Quick question: when you save those dated versions, is “Save as Rhino 8 file” (or an earlier version) checked in the Save As dialog?
If it is, the prompt is on purpose. A Rhino 8 file can’t hold everything a Rhino 9 model can, so Rhino doesn’t count that save as a complete copy of your work. It keeps the model marked as changed, and that’s why Exit asks again.
Rhino 8 does the same thing. If you save as a Rhino 7 file there, Exit will ask too. You probably never noticed because in Rhino 8 you were saving in the current version.
If you save as a Rhino 9 file, the model is marked as saved and Exit closes without asking. If you also need a Rhino 8 copy, save that one first and the Rhino 9 file last, and you’ll get out the door without the prompt.
It should not, as the file was already saved and no commands entered afterwards. (I did virtually nothing, only moved the mouse to the “x” in the corner.)
In Rhino 8 it works. No dialog comes up and Rhino quits.
Following your instructions, I am not seeing the same thing here… Hitting the X box immediately after saving just closes Rhino 9 immediately, no warning message.
If you open a new file, create a box, and save the file as SaveAs and then quit, a dialogue will come up.
If you open a new file, create a box and save the file as Save and then quit, no dialogue will come up.
I think in both cases there should be no dialogue … But maybe the logic behind the SaveAs prohibits this.
If I have a file called work261019.3dm and I have been working on it for two hours and today’s date is 261020 and I want to save a new “incremental copy” so that I can go back if something does not work out … What do I do? I do SaveAs and write “work261020.3dm”. And the filename changes in the left corner of the Rhino window to “work261020.3dm”. That’s all fine. I would expect that. But then when I hit Quit, it asks if it should save the file again before quitting.
(If I used “Save a copy” … the dialogue would make sense.)
Also, as I said before, Rhino 8 did not work like this.
@dale I have duplicated what @erik6 has reported in his recent posts.
Rhino 9 is not behaving as you described.
Rhino 9 always keeps the model marked as changed after SaveAs is used, even if the SaveAs was as a Rhino 9 file and the contents of the model has not changed since SaveAs. When the user clicks to exit the “Save changes” dialog appears.
Simple example:
Open Rhino 9
Create an object. (This step is optional)
SaveAs a Rhino 9 file.
Click to exit and the “Save changes” dialog appears.
Thanks Erik and David. You’re right: SaveAs leaves the model marked as changed even when it’s saved as a Rhino 9 file, so my earlier explanation doesn’t cover what you’re seeing.
For now, running Save once after SaveAs clears it, and Exit won’t prompt.