You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
emrg: the app icon's hub has a dark blotch and the branches are lit from five directions #2609
The app icon's central hub carries a dark blotch at every size, and the five branches are lit from five different directions.
What is observed
packaging/assets/icon.svg paints the hub before the five branches. Each branch's round line cap therefore lands on top of the hub's face, all five converging at its centre, and each branch's own gradient starts at its darkest stop (#047857) exactly there. The result is a smudge of overlapping dark ends in the middle of a shape that is drawn to read as one bright sphere.
The branch gradient is also declared in the default objectBoundingBox units, so each of the five paths resolves branchGrad against its own bounding box. Five boxes, five directions: the light falls across the five branches at five different angles and the fan does not read as one lit structure.
Third, the upward branch's node sits 16° from its two neighbours, so at small sizes those three nodes merge into one blob.
What is expected
The hub reads as a clean sphere: the branches emerge from behind it, nothing is painted on its face.
One light source for the whole fan: every branch darkens toward the hub and brightens toward its node, all reaching full brightness at the same radius.
The nodes stay separated and the structure stays legible at 48 px, which the crowded top three prevent.
What the change must satisfy
packaging/assets/icon.svg is replaced whole, keeping the existing body geometry (the 56 inset, the 912 square, rx 206) and every existing coordinate, stroke width and colour stop; only the two defects above and the crowded branch change.
The derived products — icon.png, icon-512.png, icon-256.png, icon.icns, icon.ico — are regenerated by bash packaging/gen-assets.sh and are never edited by hand. They stay untracked, as the build produces them.
check_icon_opaque keeps discriminating in both directions after the regeneration: it still refuses a render that lost its alpha channel or baked an opaque background into the corners, and still refuses a blank one.
The repository suite passes and CI is green on all three platforms.
Activity
argszero commentedon Oct 27, 2026
Handled by #2610