Repository navigation
Improvement: the base update shows its progress and tells you to keep your hands off the Octatrack - #1501
Closed
repeat98 wants to merge 3 commits into
Closed
Improvement: the base update shows its progress and tells you to keep your hands off the Octatrack#1501repeat98 wants to merge 3 commits into
repeat98 wants to merge 3 commits into
Conversation
…r to keep their hands off the Octatrack The update dialog showed the browser's own 4 px progress element, only while a send ran, so most of the update had no visible progress, and nothing said that the Octatrack looks ready after its restart while the base is not saved yet. - One blue bar for the whole update (ProgressBar), with its percentage and a moving sheen while a step reports no figure; the sync dialog uses it too. - A "Hands off your Octatrack" alert for as long as the update runs, and the same words before it starts. - The link reports 'saving' once the container is on the unit, so the page can tell sending it from the write. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
… texts The view before an update was a wall of text: three cards with a sentence each, a warning paragraph, a note above them. Now one intro line, the three steps as one row, and what to do before the start as a line each. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
repeat98
enabled auto-merge
November 13, 2026 09:15
Owner
Author
|
Closed into #1502: all changes that need a new Octatrack base go out as one base update. This branch is merged there with its commits, and its description and test notes are carried over. |
auto-merge was automatically disabled
November 13, 2026 09:25
Pull request was closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ProgressBarinBaseDialogFrame.tsx), with a moving sheen while a step reports no figure. The sync dialog uses the same bar.StagePlan compact), and what to do as a line each (OS file ready, save and stop, hands off, USB Audio off where it applies).savingonce the container is on the unit, so the page tells "sending the base once more" from the write.BaseInstallDialog,LoadDialog,ZoomBaseDialog,octatrack-link,OctatrackHub,owner-note-accept),tsc -band eslint pass.npm run pr:ready: every step passed exceptsdk:check, which reportedtest_volatile_service.py; that test passes when run on its own on this branch (2 tests, OK), and this branch changes nothing undersdk/. I looked at every state of both dialogs as a static page built from their real markup and styles. Not checked: a real update on a unit with this page.The Octatrack's own screens for the update and the sync (a full-screen, key-locked BASE UPDATE screen and a MODWERK SYNC box) are base work and come in a separate pull request with the next base.
🤖 Generated with Claude Code