Create new Dorico file in new directory. Save file. Rename directory that file is in. Dorico becomes confused, can no longer Save but no error is given, thus can no longer Quit with Save, because clicking “Save” in the “Save changes before quitting?” dialogue simply closes with no result (no error either). The only way to Quit Dorico is to then click “Don’t Save” instead.
Usually macOs apps don’t have any problem with files or directories being renamed while open.
Dorico is not plugging into macOS directly, rather through the Qt framework.
That may be the cause.
It is good practice to at least close the file before moving it, in this case.
True however I was trying to Quit which normally works simply (save then dorico quits) but in this case Dorico went back to the typical view without anything being indicated. So after attempting this again and wondering why Dorico wasn’t quitting or saying anything as it should… I realized Dorico had become confused and I worked around it.
Thanks for reporting this. In general, Dorico does handle these kinds of external changes, but it looks like it doesn’t do this correctly during the very first session in which a project exists. If you subsequently close and reopen the project, it will thereafter be able to track external changes to the project name or the path where it is found, but during the very first session after creating and initially saving the project, this doesn’t work properly. We’ll make sure this gets fixed in future.