# VectorPaint seven-segment cards: audit lit segments for digits zero to nine
Language: en
Canonical: [VectorPaint seven-segment cards: audit lit segments for digits zero to nine]()
中文：[中文 HTML]()
English: [English HTML]()
Published: 2026-11-06T00:00:00+08:00
Modified: 2026-11-06T12:13:22+08:00
Author: Bison
Build seven independent segments and check ten digit combinations, unlit segments and reduced output without treating static cards as an electronic display.
English translation of the [Chinese original](), translated on 2026-11-06. Original publication dates, attribution, code and version notes are retained.
A seven-segment digit is identified by lit positions rather than a thickened ordinary font. Make ten static cards for 0–9, defining segment names before auditing each. This generates no program, wiring diagram or interactive counter. The app does not verify circuits, and a digit-looking card still needs its segment list checked.
## Fix seven positions and the reading direction
Create a 1200 by 900 pixel canvas with a 200 by 300 pixel prototype digit. Name top a, upper right b, lower right c, bottom d, lower left e, upper left f and middle g, always viewed from the front. Make a labelled source diagram and explain list reading without reversing sides as if viewing a circuit back. These are teaching positions, not hardware pin names. Keep seven independently selectable objects and count them; no decimal point belongs to this source. Establish gaps before making digit copies.
## Standardise lengths and gaps within each orientation
Use one source for three horizontal segments and another for four vertical ones. Orientations need not share identical dimensions, but each family should match. Simple bevels are acceptable without merging corners. Light all seven to inspect the 8 framework, disabling strokes to check fill boundaries rather than letting outlines consume gaps. Centre g without lengthening it merely to fill space. Keep position labels on a separate explanation layer so moving digits cannot carry them into finals. These are graphic parameters, not display manufacturing tolerances.
## Build ten lit sets from one fixed list
Use these sets: 0=abcdef, 1=bc, 2=abdeg, 3=abcdg, 4=bcfg, 5=acdfg, 6=acdefg, 7=abc, 8=abcdefg, 9=abcdfg. Read the list outside the app first, especially 2 versus 5 and 6 versus 9. Copy each card from the full source and change only lit/unlit state rather than redrawing sizes. Label ten cards 0–9 and identify these as the common forms chosen here. Other display glyph variants require a separately stated list rather than silent changes.
## Manage unlit appearance separately from deletion
Unlit segments may remain faint or be hidden in finals; choose one consistent convention. A faint fill is still an object, not transparency, and needs dark-background checks. Do not delete five segments from the only source to display 1 and expect automatic recovery. Retain the full master and name digit groups, checking that selections exclude neighbouring cards. Read all ten without labels, then restore them to catch a card labelled 2 but showing 5. States are maintained manually, without automatic numerical switching.
## Use lit counts as a supplementary check
Count lit segments for 0–9 as 6,2,5,5,4,5,6,3,7,6, then verify positions. Digits 2,3,5 all use five segments, so counts alone are insufficient. Compare 6 and 9: 6 has e without b, while 9 has b without e, with other positions checked against the list. Intentionally swap them in a test to see whether the label masks the error, then restore. This tests diagram reading, not hardware faults. Exclude deliberately wrong copies from finals and do not call matching counts a circuit test.
## Keep matching bounds and baselines across ten cards
Arrange two rows of five with equal card width, margins and label positions. Do not narrow 1’s card because its lit shape is slender. Align bounds before optical balance, without scaling each lit group to equal width. State row order 0–4 then 5–9. A selected sequence such as 0–4 remains a subset, not the full set; preserve all ten sources. Keep labels maintainable independently from segment geometry and check IDs when editing text. Retain a labelled position diagram for later reference.
## Inspect reduced size and transparency separately
Export at the intended size and inspect the actual file for 2/5, 6/9 and narrow gaps. For blur, simplify bevels or source spacing consistently across ten cards rather than squeezing them independently. Check transparency on light/dark backgrounds, including deliberately retained unlit objects; a white backing does not disappear automatically. Name static seven-segment digits, bounds and revision and exclude position labels or error tests. Reopen SVG/PDF in the receiving tool without assuming the extension preserves identical grouping or display conditions.
## Return to position names when a digit reads incorrectly
For 2 resembling 5, inspect b/e versus c/f rather than adding explanatory text instead of repairing it. Compare e/b for 6/9 and hidden state/selection for an incomplete 8. Unequal gaps call for source dimensions, not larger backgrounds concealing errors. Reversed labels require reading-order checks rather than flipping graphics. Repeat set, count, unlabelled-recognition and actual-output checks. Each card should trace to one master, not depend on oversized labels to become recognisable.
## Related tutorials and sources
[VectorPaint grids and guides: composition references for icons and posters](), [VectorPaint optical icon corrections: inspect 16, 32 and 64 pixel output]().
Sources checked on November 6, 2026: VectorPaint 1.0.8, requiring iOS / iPadOS 17.0 or later. Capability scope follows the [official App Store description]() and [Apple public version lookup](). These are exercises and checks you can perform, without a claim of step-by-step physical-device testing or verification in every target environment. Example content is instructional; follow the controls in your installed version.