Repository navigation
1.2.0: SCOPES_GRATICULE_WIDTH, release (with #8) - #9
Merged
Merged
Conversation
The graticule lines are the only lines the scopes draw (the traces are counts per cell). A new live setting makes them 1-4 output pixels thick; the default 1 draws the same picture as before (golden hashes unchanged). Env var, config file, PATCH /api/v1/scope (graticule_width), a slider in the Scope tab and the Settings description. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017ybuzgBaGxuB5UiaE8dRa4
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017ybuzgBaGxuB5UiaE8dRa4
LeeO86
force-pushed
the
feat/line-width
branch
from
November 5, 2026 03:11
e8f9016 to
4bf5d27
Compare
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.
What
A new live setting,
SCOPES_GRATICULE_WIDTH, for the thickness of the graticule lines. It takes 1 to 4 output pixels. The default is 1, which is the same picture as today.Which lines the scopes draw
Only the graticule lines (
makeRenderPlaninsrc/scope/render.cpp): the solid, thin and dotted scale lines in each panel of every mode. Each one is a single plot row today. The traces are not lines. They are counts per histogram cell (point density), so they stay as they are. Stage 1 has no vectorscope target, no audio lines and no overlay lines. The texts and labels have their own size, which follows the output height.Why pixels, 1–4
Today a line is 1 px at every output size. So "times the default" and "pixels" mean the same thing, and a whole number of pixels stays sharp, with no half-covered rows. 4 px is already heavy at 1080. A wider line covers rows around its row: 2 means the row and the one below, 3 means one row above and one below. Lines are cut at the plot edge. Where wide lines overlap, each pixel is drawn once and the brighter line wins.
A size that grows with the output height (like the text scale) was the other option. I did not choose it: it would change the default picture at UHD, and a fixed pixel count is easier to understand.
Where it is set
PATCH /api/v1/scopewith the fieldgraticule_width, shown inGET /api/v1/scope.Tests
graticule width, for luma, the YCbCr parade and the RGB overlay:widthrows at the 0 % line in the empty plot.npm run buildof the web UI passes.Docs
README and SPECIFICATION (§4.5 and the settings table), CHANGELOG under Unreleased.
🤖 Generated with Claude Code
https://claude.ai/code/session_017ybuzgBaGxuB5UiaE8dRa4