AvaDM v1.2.1

Fixes the download progress bar jitter reported in #10, plus two related consistency bugs found
along the way.

Fixed

• Chunk progress bars visually jittered back and forth during a download. The chunk row's
  layout had the progress bar sharing width with an auto-sized speed-text column; since the
  formatted speed string's length genuinely varies ("-", "45.2 KB/s", "1.2 MB/s", ...), every such
  change resized that column and visually squeezed or expanded the bar next to it, indistinguishable
  from the bar's own value moving even though it never did. The speed column is now a fixed width.
• Resuming a download briefly wiped its progress to zero before snapping back. A freshly
  started handle is returned before its own HEAD request/.avadm-footer read has finished, so a
  resumed row could get attached to a still-zero, chunk-less handle and momentarily show 0%/no
  chunks before the real (already-substantial) progress arrived and corrected it.
• A download that failed and auto-retried could leave its row permanently stuck, showing the
  stale failed state indefinitely while the replacement download kept running invisibly in the
  background - and a user resuming that stuck row could end up racing a second handle against the
  first on the same .avadm file. The row now re-syncs once its handle reaches any terminal state,
  and starting a new attempt for an id that already has an active handle now cancels the old one
  first.
• Concurrent chunk-download threads could report progress to the UI out of order, occasionally
  delivering a smaller, stale byte total after a larger one had already gone out.

Full changelog: v1.2.0...v1.2.1

AvaDM v1.2.0

Shows which version you are running.

Added

• Settings > Updates now shows the running build's version, so it's clear which version you're
  on after a self-update (nothing else about the install changes visibly, and an AppImage or
  portable build keeps whatever filename it was originally downloaded under).

Full changelog: v1.1.2...v1.2.0

AvaDM v1.1.2

Fixes login autostart and the Linux applications-menu shortcut for AppImage builds.

Fixed

• The autostart entry and the Linux applications-menu shortcut pointed into a temporary AppImage
  mount. Both were written from Environment.ProcessPath, which for an AppImage is a path inside
  the /tmp/.mount_* FUSE mount that exists only while that process runs. After a reboot the
  desktop reported Could not find the program '/tmp/.mount_.../usr/bin/AvaDM.UI', the shortcut
  did nothing, and AvaDM did not start at login. Both entries now point at the real .AppImage
  file (the same APPIMAGE resolution the updater already used), and the menu shortcut's icon is
  installed to ~/.local/share/icons/hicolor/256x256/apps/avadm.png instead of being referenced
  inside that same temporary mount.
• Existing broken entries repair themselves. At startup AvaDM rewrites an autostart entry or
  menu shortcut that no longer matches where it actually lives — which also covers a portable build
  that was moved or an AppImage that was replaced at a new path. Entries the user turned off stay
  off.

Full changelog: v1.1.1...v1.1.2

AvaDM v1.1.0

v1.1.0

New

• Single-instance enforcement. Launching AvaDM while it's already running no longer opens a second instance — the new launch detects the running one (via an exclusive lock file + named pipe handoff, not a named Mutex, which proved
  unreliable for this on Linux), signals it, and exits. The already-running instance is brought to the front and shows a toast confirming it's already open.
• GitHub button in Settings — quick link to the project's GitHub repo from the Settings page.

AvaDM v1.0.0

Full Changelog: https://github.com/AvaDM-org/AvaDM/commits/v1.0.0