fix(anatomy): V1-2.2 the visible wins on the editor canvas
Owner decision 2026-11-01. The canvas paints and hits every point hitbox, then every zone and trigger, then every visible twin, which captures on what it paints; a junction's disc is no longer taken by the zone drawn after it. The PDF view keeps the document order and its bytes. Click spec: the five fixme run unmarked, six projects incl. a 320 px phone.
This commit is contained in:
1 parent
e67715025c
commit
9c606aa567
13 files changed
+504
-64
No files matched your search
@@ -23,11 +23,22 @@ trigger.
|
||||
| Annotation | Elements |
|
||||
|---|---|
|
||||
| `detail_trigger`, any geometry | one dashed shape: fill and stroke = the colour, `fill-opacity` 0.06, `stroke-width` 2, `stroke-dasharray` `8,4`, `pointer-events` all, `style` `cursor:pointer`, class `detail-zone` |
|
||||
| `point` or `zone` with a circle | a transparent hitbox (the geometry's `r`, `fill` transparent, `stroke` none, `pointer-events` visibleFill, `style` `cursor:pointer`; the R3 form kept for the seed review drawings has no `stroke` and `pointer-events` all) then a visible twin on top (radius `max(2, r − 12)`, the colour, `fill-opacity` 0.65 on the main view / 0.5 on a detail view, stroke `#000` 1.5, `pointer-events` none) |
|
||||
| `point` or `zone` with a circle | a transparent hitbox (the geometry's `r`, `fill` transparent, `stroke` none, `pointer-events` visibleFill, `style` `cursor:pointer`; the R3 form kept for the seed review drawings has no `stroke` and `pointer-events` all) then a visible twin on top (radius `max(2, r − 12)`, the colour, `fill-opacity` 0.65 on the main view / 0.5 on a detail view, stroke `#000` 1.5, `pointer-events` none; visiblePainted in the editor canvas, see below) |
|
||||
| `point` or `zone` with a polygon or a path | one filled shape: fill and stroke = the colour, `fill-opacity` 0.3, `stroke-width` 2, `pointer-events` all, `style` `cursor:pointer` |
|
||||
|
||||
Annotations without geometry draw nothing. Annotations follow the document
|
||||
order of the view. Coordinates are printed as JavaScript prints numbers, never
|
||||
order of the view, in the PDF view and the review drawings. The editor canvas
|
||||
paints and hits them in three passes, each in document order (« the visible
|
||||
wins », owner decision 2026-11-01, V1-2.2): every point hitbox, then every
|
||||
filled shape (zones and triggers), then every visible twin, which captures on
|
||||
what it paints (`pointer-events` visiblePainted). A tap on a point's visible
|
||||
disc selects that point even where a zone or another point's hitbox lies
|
||||
under it; a zone keeps every pixel no visible disc covers, the hitbox ring of
|
||||
a point included; a hitbox ring keeps what neither covers. Until then each
|
||||
annotation's elements followed one another, so a zone painted after a
|
||||
vertebral junction took part of its disc. Visible consequence: a selected
|
||||
point's hitbox, filled by the canvas stylesheet, sits under a neighbouring
|
||||
zone, which tints the part it covers. Coordinates are printed as JavaScript prints numbers, never
|
||||
rounded; a path's `d` is copied as written. Each element has one `<title>`
|
||||
child, "name FR / name EN" (native tooltip), and the attributes below.
|
||||
Owner decision 2026-10-15: until then an unnamed trigger carried the French
|
||||
|
||||
Reference in new issue
Block a user