fix(widgets): readable HARD in light mode, explicit tyre stints - #39
Merged
Merged
Conversation
- HARD was hard-coded #f0f0f0 (white), invisible on a light theme. It now uses Glance's theme-aware color-highlight, same as the driver codes. - Each entry is a stint (time between pit-lane visits), not a tyre set - a driver can pit for a lap and go back out on the same set, so the same compound repeats. Consecutive same-compound stints are now grouped (HARD×12+4 = two HARD stints), and a legend says the numbers are laps and what a stint is. OpenF1's tyre_age_at_start only proves reuse when non-zero (0 can mean new or unknown), so sets can't be told apart reliably; the wording says "possibly the same set" rather than claiming.
Grouping same-compound stints hid the order they were run in, which is
the useful part. Back to one chip per stint, in order, with a hover
tooltip per stint ("Stint 2: HARD, 4 laps") and a legend saying numbers
are laps and that a stint is the time between pit-lane visits (so the
same compound can repeat, possibly on the same set - OpenF1 only proves
reuse via a non-zero tyre_age_at_start, so sets cannot be told apart
reliably). Render-tested on Glance 0.8.6 against a live paddock-api.
JustMaris
added a commit
that referenced
this pull request
Sep 26, 2026
* fix(widgets): readable HARD in light mode, make tyre stints explicit
- HARD was hard-coded #f0f0f0 (white), invisible on a light theme. It now
uses Glance's theme-aware color-highlight, same as the driver codes.
- Each entry is a stint (time between pit-lane visits), not a tyre set -
a driver can pit for a lap and go back out on the same set, so the same
compound repeats. Consecutive same-compound stints are now grouped
(HARD×12+4 = two HARD stints), and a legend says the numbers are laps
and what a stint is. OpenF1's tyre_age_at_start only proves reuse when
non-zero (0 can mean new or unknown), so sets can't be told apart
reliably; the wording says "possibly the same set" rather than claiming.
* fix(widgets): keep stint order, add per-stint hover detail
Grouping same-compound stints hid the order they were run in, which is
the useful part. Back to one chip per stint, in order, with a hover
tooltip per stint ("Stint 2: HARD, 4 laps") and a legend saying numbers
are laps and that a stint is the time between pit-lane visits (so the
same compound can repeat, possibly on the same set - OpenF1 only proves
reuse via a non-zero tyre_age_at_start, so sets cannot be told apart
reliably). Render-tested on Glance 0.8.6 against a live paddock-api.
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.
Summary
#f0f0f0(white). It now uses Glance's theme-awarecolor-highlight, same as the driver codes.HARD×12+4) but that hides the run order, which is the useful part, so the final version keeps one chip per stint.OpenF1 can't reliably say whether repeated stints are the same tyre set:
tyre_age_at_startonly proves reuse when non-zero (0 means new or unknown). The wording avoids claiming anything about sets.Test plan