Filee Files

What's Changed

Updates install themselves

• In an installed copy, Update (bottom of the menu, tray menu, the update notice, Settings → General) now downloads the new installer inside Filee, checks it against the release's SHA-256 file and runs it without the setup wizard. Setup closes Filee, updates it, keeps your settings and engines and starts Filee again. Windows asks for administrator rights once.
• The sidebar, tray menu, Settings → General and the notice show the download progress.
• If the download or the installer fails (no connection, a file that doesn't match its checksum, an installer that won't start), Filee tells you, and after OK it opens filee.sh so you can download the new version there.
• The portable copy still opens the release page: download the new ZIP and unpack it over the old folder.
• Updating to 1.4.0 from an older version still goes the old way. From 1.4.0 on, it's one click.

Default save location

• Settings → General → Default save location: next to the original (as before), in a subfolder such as converted, or in one fixed folder.
• Every preset follows it unless you give the preset its own location (Presets → Output → Save to).
• Built-in presets, and your presets that saved next to the original, follow the default from now on. Since the default starts as "next to the original", nothing changes until you pick another one.

Keep the original file dates for every conversion

• New switch in Settings → General: converted files get the created and modified dates of the original, with every preset (photos, videos, PDFs, archive conversions).
• Not when several files become one (merged PDF, several files packed into one ZIP): that file has no single original.
• The per-preset option from 1.3.1 stays, for keeping dates with some presets only.
• The filee command follows the default save location and this switch too.

Use the engines you already have

• Settings → Engines → Use my copy… next to FFmpeg, calibre, Pandoc, Ghostscript and LibreOffice. Pick the program (ffmpeg.exe, ebook-convert.exe, pandoc.exe, gswin64c.exe or soffice.exe) and Filee uses it instead of downloading its own. Stop using it goes back.
• FFmpeg needs ffprobe.exe in the same folder (most builds have both). Picking a build's main folder finds its bin folder too.
• The filee command uses the same copies.

Pull requests

• In-app updates, default save location, dates for every conversion, your own engines (1.4.0) by @KnifeLemon in https://github.com/KnifeLemon/Filee/pull/30

Full Changelog: https://github.com/KnifeLemon/Filee/compare/v1.3.1...v1.4.0