This is probably a matter of taste, but current behaviour is unpalatable to me.
With a new file, File/Save to a location you do not have write permission, give it a proper filename in the save dialogue.
Gets a dialogue box with the following (and in console)
Failed to open file for writing /usr/share/openscad-nightly/examples/Basics/sphere-chopped.scad (Permission denied)
OK so far.
But it then progresses to give the Tab/Title the new filename.
I would expect it to be an atomic operation, if the save fails, the 'untitled.scad' instance stays as it was.
This also happens with Save-As, the editor takes on the new filename, even though it does not exist.
Also the * in the Tab/Title, signifying editor has changes, is no longer shown,
although if you close it, you do get the 'file changed' prompt.
This was on Debian w 2020.12.15.
This is probably a matter of taste, but current behaviour is unpalatable to me.
With a new file, File/Save to a location you do not have write permission, give it a proper filename in the save dialogue.
Gets a dialogue box with the following (and in console)
OK so far.
But it then progresses to give the Tab/Title the new filename.
I would expect it to be an atomic operation, if the save fails, the 'untitled.scad' instance stays as it was.
This also happens with Save-As, the editor takes on the new filename, even though it does not exist.
Also the
*in the Tab/Title, signifying editor has changes, is no longer shown,although if you close it, you do get the 'file changed' prompt.
This was on Debian w 2020.12.15.