VaultSort 5.4.0-beta.21

What's New

• Notes are written on paper now. The editor and the preview sit on an off-white sheet instead of the dark card, because Markdown syntax was effectively invisible before — the colours used for headings, links and emphasis are built for a light background, and on the dark card they sat at contrast levels far below what is readable. Everything on the sheet is now well clear of the accessibility floor, and the editor carries faint ruled lines locked to its own line height.
• Colour tags for notes. Give a note one of six colours to group it at a glance. Each colour carries its name in the label, and the palette was picked so no two are indistinguishable to a colourblind reader rather than simply chosen to look nice. Tagging a note does not count as editing it — the note's size and last-modified time are untouched.
• An outline for long notes. Every heading in the note, listed beside it; click one to jump there. It works in the editor and in the rendered view, it re-reads as you edit, and it ignores headings that are really comments inside a code block.
• Notes appear in the folder that holds them. "Folders and files" listed exactly that and silently left notes out, so a folder holding one note read as "1 item here" above an empty list. It is also why deleting a folder could come as a shock — the note it took was never shown as being in there. Notes are now listed with everything else in the folder.
• Updates can install themselves, without interrupting you. Off unless you turn it on, in Preferences › Updates. With it on, a new version downloads quietly in the background and is applied when you next quit VaultSort, so the version you come back to is already the new one — no dialog asking to download, and none asking to restart. VaultSort also re-checks every few hours while it is open, so a session left running for days still finds a release. Leave it off and nothing changes: you are asked before anything is downloaded, and asked again before anything is installed.
• An update tells you it is there. When a new version is available or ready, a button appears at the top right of the window. Clicking it goes straight to Updates, where you can restart and take it immediately rather than waiting for your next quit.
• Settings categories moved to a list down the side. The row of tabs along the top had run out of room — the newest one was cut off the right edge and could not be reached, and it was worse on Windows, where the file-manager tab's name is longer. Every category is now visible at once, with room for more, and long names are shown in full instead of being cropped.

Bug Fixes

• Moving a Vault now moves the Vault and nothing else. This is the serious one. If the folder holding your Vault also held your own files — a Vault at the root of an external drive, or in Documents — moving it would take those files along: copying them into the new Vault, deleting them from where they were, removing the folder, and then reporting that nothing had been left behind. The move now touches only the Vault's own files, and the old folder is removed only if that leaves it empty. The same wrong assumption let a routine tidy-up on unlock delete files of yours that merely resembled the Vault's temporary ones; it now matches only the Vault's own. (Vaults created or moved from here on are placed in a VaultSort Vault folder inside the location you pick, rather than directly into it.)
• A folder you moved a Vault out of is usable again straight away. VaultSort remembered it as a Vault until the next restart, so Organize, Clean and secure delete went on refusing everything inside it — and choosing that same folder to move the Vault back into was refused as already holding one, which is exactly step two of moving a Vault and moving it back.
• Outline entries land on the right heading. A heading containing bold, italic, code or a link — which in a Markdown note is most of them — jumped nowhere at all. Headings below the third level appeared in the outline but could not be jumped to. Two sections with the same name both went to the first one. All three are fixed.
• A failed update no longer leaves the progress bar stuck. When a download failed part way, the bar sat frozen at whatever percentage it had reached for the rest of the session, with nothing to say the update had not happened. It now says the update could not be completed and that you are still on your current version.
• Choosing a folder on a network drive that is not reachable fails quickly. The check for "is this folder inside a Vault" ran before the check for "is this even a reachable location", so picking a path on a NAS that was switched off waited for the network to give up, once per folder level, before showing the refusal it could have shown immediately.