How many of the artwork's own pixels land on an inch of paper, beside the frame's name.
⚠️ It reads the canvas accessor and re-derives nothing. The pixel count comes from the manifest
and the placed size from native_image_rect — the image's own rect, not the frame's, because the
frame crops — and a second implementation here would be a control disagreeing with the document,
which is the fault TYP-701 and TYP-705 each cost a release.
⚠️ Red below 150 dpi, from k_effective_dpi_error — the same constant validate() raises an error
at. A panel that drew the line somewhere else would tell the designer the image is fine and the
order that it is not.
⚠️ A vector says "vector", not a number. An SVG has no resolution and needs none, so showing 72
would read as a fault in artwork that will print perfectly at any size. An image whose pixel
count is unknown shows nothing at all: "unknown" and "too low" are different answers, and the
missing manifest entry behind it is already its own finding.
How many of the artwork's own pixels land on an inch of paper, beside the frame's name.
⚠️ It reads the canvas accessor and re-derives nothing. The pixel count comes from the manifest and the placed size from
native_image_rect— the image's own rect, not the frame's, because the frame crops — and a second implementation here would be a control disagreeing with the document, which is the fault TYP-701 and TYP-705 each cost a release.⚠️ Red below 150 dpi, from
k_effective_dpi_error— the same constant validate() raises an error at. A panel that drew the line somewhere else would tell the designer the image is fine and the order that it is not.⚠️ A vector says "vector", not a number. An SVG has no resolution and needs none, so showing 72 would read as a fault in artwork that will print perfectly at any size. An image whose pixel count is unknown shows nothing at all: "unknown" and "too low" are different answers, and the missing manifest entry behind it is already its own finding.