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
Audit spec values so DrawTabData is the source of truth #54
Audit the spec values in DrawTabData so the Explorer can be trusted as the source of truth. The DrawingTabletDocs notes pages now show their specs from this data (generated Specs tabs), and the notes only add context. So a wrong value here shows up wrong everywhere.
Why now
The DrawingTabletDocs Specs rollout compared hand-written notes against this data and found errors on both sides (TheSevenPens/DrawingTabletDocs#67):
Data errors:
Artist Pro 19 GEN2 (MD180UH): wrong included pens.
I scanned all 394 tablets. The checks were: range checks, active area against body size, display aspect ratio, pixel density, included pens against pen-compat, missing core fields, and differences between same-size models in one family. 99 tablets have a notes page.
Huion H610 and Kamvas RDS-160: the body is smaller than the active area.
269 core fields are missing across the remaining tablets, mostly older Wacom models.
Next: a source pass over the 99 notes-page tablets, comparing each record against its manufacturer spec page or manual (the MANUFACTURERPRODUCTINFO / MANUFACTURERUSERMANUAL links). The same pass can sort each gamut figure into coverage or area (#51) and record coatings (#56).
Color depth:Display.ColorBitDepth keeps the panel's native depth (6, 8 or 10). A new Display.ColorBitDepthFRC holds the depth the manufacturer claims with FRC, and is set only when they say FRC ("8-bit + FRC", "1.07B colors" on an 8-bit panel). The Specs row reads "8-bit (10-bit with FRC)" when both are set, and "10-bit" for a true 10-bit panel. Recheck the 20 tablets recorded as 10-bit today, since some are likely 8-bit + FRC.
Buttons means programmable buttons only. Count multimedia keys in their own field, and scrollers in their own field.
Depth ranges ("19~26.7 mm"): store a distinct min and max. If only one value is given, it is the max.
Hover ranges: undecided. Count how many sources give a range first.
A single accuracy figure with no center/corner split: store it as center accuracy.
A built-in fold-out stand counts as Legs only, not IncludedStand.
Report rate: store both wired and Bluetooth. If only one value is given, it is the wired one.
These map to the numbered questions Seven was asked:
HS610: merge. Merge the "H610" record (huion.tablet.h610) into the existing huion.tablet.hs610, keeping its 12 buttons and 1 touch ring, delete the H610 record, and point the pen-compat entry for "H610" at HS610. Seven: the HS610 is discontinued.
Intuos 1 ADB (GD-…-A): yes. Copy the digitizer specs from the -R/-U versions: 1024 levels, EMR, ±0.25 mm center accuracy, hover, report rate.
UltraPad: yes. Use Wacom's 1997 figures:
6×8 weight 862 g
12×12 size 406 × 419 × 51 mm
12×18 weight 3402 g
18×25 active area 635 × 457.2 mm at 100 lines/mm
Hover ranges: yes. On the two Magic Drawing Pads, store a min and a max like depth: 10 and 20 mm.
Inspiroy 2 L group keys: yes, their own field. Seven: they are "switcher" keys, not assignable in the normal sense for shortcuts.
Go live: yes. Merge the spec-audit-2 batch (audit fixes, conventions, and the answers above) into DrawTabData master and DrawingTabletDocs syncbranch.
Activity
TheSevenPens commentedon Oct 2, 2026
Mechanical pass (2026-10-02)
I scanned all 394 tablets. The checks were: range checks, active area against body size, display aspect ratio, pixel density, included pens against pen-compat, missing core fields, and differences between same-size models in one family. 99 tablets have a notes page.
Fixed in #58
data-qualitynow checks for this.Needs a source check (tablets with a notes page)
Needs a source check (no notes page)
Next: a source pass over the 99 notes-page tablets, comparing each record against its manufacturer spec page or manual (the
MANUFACTURERPRODUCTINFO/MANUFACTURERUSERMANUALlinks). The same pass can sort each gamut figure into coverage or area (#51) and record coatings (#56).Generated by Claude Code
TheSevenPens commentedon Oct 2, 2026
Conventions decided by Seven (2026-10-02)
Display.ColorBitDepthkeeps the panel's native depth (6, 8 or 10). A newDisplay.ColorBitDepthFRCholds the depth the manufacturer claims with FRC, and is set only when they say FRC ("8-bit + FRC", "1.07B colors" on an 8-bit panel). The Specs row reads "8-bit (10-bit with FRC)" when both are set, and "10-bit" for a true 10-bit panel. Recheck the 20 tablets recorded as 10-bit today, since some are likely 8-bit + FRC.Generated by Claude Code
feat: spec conventions from the #54 review
feat: Display.ColorBitDepthFRC (native depth vs FRC-claimed depth)
TheSevenPens commentedon Oct 2, 2026
Seven's answers (2026-10-02 21:27 UTC)
These map to the numbered questions Seven was asked:
Generated by Claude Code
Merge branch 'spec-audit-2': spec audit source checks and conventions (…