Hi, as the title says using SaveAs on a new document doesn’t alter the document name. It just saves out a copy with the new name.
Rhino 6 latest SR
Hi Jorgen- are you SaveAs-ing to V6 format?
-Pascal
I think so, no popup warning about anything else. If you don’t see the behaviour I’ll run some tests.
Hi Jorgen - If you open a V5 file, and SaveAs from V6, you would get this behavior, if you have previously SaveAs-ed to v5 in the session - it will default to saving that v5 format. So far that is all that comes to mind that might have occurred.
-Pascal
I’ll take a look tomorrow!
The machine is a year old and doesn’t have v5, but I might have done something odd once 
Hi Pascal, just tested this again and today all works as usual.
I posted yesterday since I have seen the behavior a few times lately and jumped to the conclusion that this happened every time. I’ll keep my eyes on this to see if I can reproduce it.
1 Like
I have not encountered this issue lately, but I just saw that when I used SaveAs on the document instead of Save, and saved over the file, and then clicked close just after and then the “Save changes…?” showed up.
So it appears that SaveAs doesn’t toggle the documents “any changes made” status to “None”.
Just so you know, and maybe something you want to look into, but then on the other hand using SaveAs to save to the current document name isn’t a very normal user behaviour 
Hi Jorgen - this spurious ‘do you want to save changes’ question that turns up from time to time is annoying and, so far, impossible to track down. It does not seem to be related to any specific action on the users’ part, that I know of. I will test SaveAs to see if that makes it happen reliably.
-Pascal
@pascal can you take a look at V7 regarding the SaveAs and not changing active document to the saved as name?
When I open a file and want to make a copy to continue work on that file I expect SaveAs to set this automatically, so I don’t have to open the newly made document. That’s how SaveAs usually work, but apparently not so in Rhino now.
Edit: And if I then hit SAVE it opens the save dialog (instead of just saving) and uses the original file name as suggestion… So something isn’t behaving correctly.
I canceled the save operation and then deleted some objects in the file and ran SaveAs again, and now it worked as expected, making the newly SavedAs file as the current document.
Hi Jorgen - I’ll take a look - I have not encountered this so far.
@Holo -this seems OK here - SaveAs renames the current file.
This would be expected if the opened file were say, a V6, or earlier, format, but not after a SaveAs, unless that was also to V6 format.
-Pascal
Strange, I don’t encounter it every time either I think… Not too often I use SaveAs though, so I’ll see if I have time tomorrow to do some more testing.
Plugins I have are VisualArq and Bella.
fwiw Bella currently only uses user strings and RenderContent apis, it does not read/write any data to the document, nor does it have any custom user data classes that would do so.
1 Like