Providing an error message if file update cannot be executed

renedo

I had a problem in my Windows configuration: for some clumsy reason, a directory in my shared library of fotos had only Read acces from one PC. I had some strange behavior from Tonfotos before I discovered the issue and correct it. The problem is that I got no information from Tonfotos that it was impossible to update the tonfotos files after a face name modification. From the user view, everything seemed perfect, the name was changed, the list of fotos with the old name and the new name were rightly updated in the PC where the modification had been done. The local date base was correct, but not the tonfotos files in the library, and consequently the other PC was not updated.
It took me some time to understand the issue, I had to look inside the tonfotos files, analyze the data and guess their structure to discover that the tonfotos file was not updated and to understand there was no Write access. I would have appreciated to have an error message from tonfotos after the failed name modification!
I guess the behavior would be the same if I tried to update a location or any metadata in the picture file.
Is it possible to provide error messages in such case in a next version of tonfotos?

Andrey

renedo You definitely have a point, though I am not sure it is as simple as this. Some people might intentionally connect their archives in read-only mode, and constant error messages will make this completely unusable. But there is definitely something to think about.

renedo

Thanks for your quick answer. I understand the use case where an archive is accessible in read-only mode. In that situation, the add/modification/remove of person face, name, location, title, category is forbidden. An attempt from the user to modify something in the library should receive an information like “you are not allowed to perform this action”. It is not a “constant error message”, it is only generated when the user intends to perform a forbidden action.
Of course, if there are internal Write attempts generated by Tonfotos (I have no knowledge of the internal algortithms of tonfotos), they should not display constantly an error message.