Visual indicator while checking for / applying updates #39

New Issue

2026-07-05T21:46:19Z

KofTwentyTwo commented

2026-07-05 21:46:19 +00:00

(Migrated from github.com)

Help → Check for updates currently gives no in-progress feedback: the menu item is clicked and nothing visibly happens until the result dialog appears (up to date / update available / error). On a slow network the app looks unresponsive.

Ask

Show clear progress state through the whole update flow:

Checking — a busy/indeterminate indicator (and disable re-invoking the check) while UpdateService.CheckAsync runs.
Downloading/applying — a determinate or indeterminate indicator while DownloadAndApplyAsync runs (before the restart), so the user knows an update is in progress rather than a hang.
Surface failures inline as well, not only via a modal after the fact.

Notes

Logic lives in gclo/Services/UpdateService.cs (async, already returns structured results) and the menu handler CheckForUpdatesMenuItem_Click in MainWindow.xaml.cs.
A lightweight surface (InfoBar or a status line + spinner) is probably enough; no need for a separate dialog during the check.
Pairs well with the activity-logging issue — every update-flow transition should also be logged.

🤖 Generated with Claude Code

**Help → Check for updates** currently gives no in-progress feedback: the menu item is clicked and nothing visibly happens until the result dialog appears (up to date / update available / error). On a slow network the app looks unresponsive. ## Ask Show clear progress state through the whole update flow: - **Checking** — a busy/indeterminate indicator (and disable re-invoking the check) while `UpdateService.CheckAsync` runs. - **Downloading/applying** — a determinate or indeterminate indicator while `DownloadAndApplyAsync` runs (before the restart), so the user knows an update is in progress rather than a hang. - Surface failures inline as well, not only via a modal after the fact. ## Notes - Logic lives in `gclo/Services/UpdateService.cs` (async, already returns structured results) and the menu handler `CheckForUpdatesMenuItem_Click` in `MainWindow.xaml.cs`. - A lightweight surface (InfoBar or a status line + spinner) is probably enough; no need for a separate dialog during the check. - Pairs well with the activity-logging issue — every update-flow transition should also be logged. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: KofTwentyTwo/gclo#39