that sounds like it doesn't need to change to "unsaved",
That is a really silly and dangerous idea, of course visibility (the state of the "Visibility" property) should be stored and hence changes of it require a save.digitalgoose wrote: ↑Mon Oct 05, 2020 2:18 pm -- including minor changes such as visibility toggles -- introduce an asterisk to the document name and prompt the user with the "Unsaved document" popup when closing the document.
This leads to some user uncertainty about whether to save the document. I propose that insubstantial changes such as visibility state should not "count" when it comes to the unsaved document prompt.
Absolutely not, what a dangerous and ridiculous idea.
It is absolutely imperative that you know exactly what a file will look like when someone else first opens it. When either teaching someone how to use FreeCAD or showing a product to a potential user/customer, then it is important to know exactly what they will be seeing when they first open the file. Not just hidden property status but also camera angle, zoom level etc. Never under estimate how stupid the general public (and especial very intelligent people) can be when using a computer. By knowing exactly what they will see on first opening the file can be one useful tool to understand what they are talking about when discussing it over the phone for example.
An example that really happened to me (variations on this have happened many times)
"What do you think of the shape of the handle on 'part B'?"'
"I don't know, something is wrong with your file, it does not show Part B, it's there in the list on the left but is not there in the window, must be a bug in FreeCAD or your file must be corrupt."
"What are you talking about? It's right there on the left of Part A"
"No definitely not, must be a bug in FreeCAD"
"Garbage it's there... wait click on 'zoom fit all'" (didn't think of that at first because I didn't think a user could be that stupid.)
"Oh wow, now I see it"
Another issue I just noticed, camera position is saved but does not set the file to an "unsaved" state. This is dangerous, if anything changes the file then it should change the file state by default.
It doesn't in standard FreeCAD 0.19. It sounds like you are talking about one of the third party add ons. If so then that is a matter to bring up with the relevant developer of that add on.
I am testing in today's 0.19 from the daily PPA.
OS: Ubuntu 18.04.5 LTS (KDE/plasma)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.
Build type: Release
Branch: unknown
Hash: 0f7979f4ae91f0a6127fb0a8dd3c1ba8b183b52f
Python version: 3.6.9
Qt version: 5.9.5
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/Australia (en_AU)