Conversation
- Seed mode in LapTimer, BluetoothManager, and RaceHistoryStore that pre-populates lap data + flight-battery telemetry + race history when the app is launched with -screenshotTimer or -screenshotHistory. - TimerView hooks the launch args to refresh metricsSnapshot and present the history sheet automatically. - All seed code is gated behind #if DEBUG so Release builds never see it and the App Store binary is unaffected. - docs/screenshot-capture.md documents the end-to-end workflow: simulator boot, status bar override, launch args, capture, ASC upload, and how to tweak the seed values for future UI changes. Background: 1.0.1+build11 needed fresh App Store screenshots because the session-bar readouts grew. Captured 01-timer + 02-history per locale from iPhone 16 Plus sim and reused the composite shot 3 from v1.0. This commit preserves the tooling so the next release that touches visible UI can regenerate in minutes instead of rebuilding the seed code by hand. Co-authored-by: Claude Opus 4.7 <[email protected]>
Catches the manual up with the 1.0.1 features that have visible
Settings surfaces, plus the workflow change they imply:
- **Section 5 — Pairing the M5StickS3**: new step 3 telling first-time
users to flip **Use bridge** on before drilling into the M5StickS3
row (it's hidden on a fresh install until the toggle goes on).
- **Section 10 — App → Lap announcer (Audio)**: new "Count down final
seconds" toggle + "Start at" stepper (5–15 s, default 10) for the
spoken countdown ("ten, nine, ..." / "じゅう、きゅう...").
The automatic "Last lap!" / "ファイナルラップです" cue at
remaining = 0 is noted on the existing "Announce lap times" entry.
- **Section 10 — Device → Use bridge**: new H3 above the existing
M5StickS3 entry, documenting the master switch that gates the
M5StickS3 / Goggle pairing / OSD layout drilldowns. Off by default
on fresh installs (no Bluetooth permission prompt for users who
don't own a bridge); existing users keep it on after upgrading.
- The three drilldown entries (M5StickS3, Goggle pairing, OSD layout)
now note "Only visible when **Use bridge** is on" so the doc lines
up with what users actually see in Settings.
Mirrored in en.md and ja.md.
Co-authored-by: Claude Opus 4.7 <[email protected]>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
1 participant
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.
This PR exists to bring
mainup to develop after 1.0.1 build 11 ships, so the production user manual at https://saqoosha.github.io/HDZap/ describes features users can actually find on the App Store. Merging earlier would publish docs that talk about TTS countdown / bridge toggle / "Last lap!" cue while users only have access to 1.0.0 build 9 — confusing and arguably misleading.No iOS build, no
MARKETING_VERSIONbump, no new TestFlight upload — just a docs + DEBUG-tooling promote.What's in this sync
Two squashed commits, both already on
develop:#70 — App Store screenshot capture tooling (DEBUG-only) —
4bbec4fseedForScreenshot(…)methods onLapTimer,BluetoothManager,RaceHistoryStore, gated by#if DEBUG.-screenshotTimer/-screenshotHistoryreproduce the exact App Store screenshot state in the iOS Simulator.docs/screenshot-capture.mddocuments the full workflow.#71 — Document TTS countdown + bridge toggle in user manual —
de08a54en.mdandja.md.Diff summary
Release procedure
--merge, not squash), matching the existing develop → main release pattern (Release 1.0.1 (build 10) #66, Release 1.0.1 build 11 #69).mainrebuilds and redeploys:v1.0.1+build11tag stays where it is (it pins the original cut, not this docs catch-up).Test plan
mainPages deploy refreshes within a couple of minutes of merge.