mirror of
https://github.com/storytold/vectorcraft.git
synced 2026-11-14 07:46:07 +00:00
dotCooCoo
ac10c51381
When a recovery copy could not be written, the status bar said only "Couldn't save recovery data: <error>", and a copy that failed on the background worker showed as "Saving recovery data for <title> failed: <error>". Neither said which folder was in use or how to pick another. The message keeps the error text (and the document's title when one copy fails), then names the folder copies go to, says whether it is the default recovery folder or the folder set in Preferences, and names the setting that picks another folder: Preferences → File Handling → Data Recovery → Folder (recoveryFolder). The recovery code writes the same line to the log. The folder is the one in use when the round started, so a preference changed while a copy runs does not change the folder the message names. A copy that fails now reports its own message, so the job's result is Ok rather than an error, and the job no longer adds "<label> failed: <error>" over it. A store the host installed (browser storage) has no folder to name: its failed copy shows "Saving recovery data for <title> failed: <error>", as a copy on the worker did before, also when the copy was written without the worker. - engine: recovery::folder returns the folder in use and whether the recoveryFolder preference names it; recovery::store uses it. - Four @msg rows in each complete-message catalog, and in the bg, bs, da and id catalogs, which translate the old message. - Control replies to a client confined to read roots show a recovery folder outside them, and the paths under it, by the folder's name, as they already show other paths outside the roots. That covers the folder in use and the last eight folders a failure message named. - docs/target-app-parity.md: a line next to the Data Recovery Folder preference.