The longest edge of the thumbnail written alongside every photo.
A capture is stored twice now: the full data a player opens, and a small thumbnail
the gallery grid draws — because the grid was pulling every original down the NUI bridge
to fill 123px squares (MICA-110).
320 rather than something nearer the tile, and the reason is that "the tile" is not one
number:
The grid draws at 123 CSS px today, three columns across a 400px screen.
Settings > Display zooms the whole phone by up to MAX_SCALE (1.4), so the same tile
is 172 device pixels at the largest setting. A thumbnail cut to fit 123 would be
visibly soft there, for a setting that has nothing to do with the camera — the same
trap CAPTURE_MAX_DIMENSION exists to avoid.
The phone itself is 400 CSS px wide, so 320 is within 1.25x of full-screen width. That
makes the thumbnail usable as the placeholder the full view shows while the original
is fetched, which is the third half of MICA-110 and the reason not to cut this
number any finer.
So: 2.6x the tile as drawn, 1.9x the tile at maximum zoom, and one number that still
works if the grid ever goes to two columns. It is a ceiling, not a target — see
computeThumbnailSize.
The longest edge of the thumbnail written alongside every photo.
A capture is stored twice now: the full
dataa player opens, and a smallthumbnailthe gallery grid draws — because the grid was pulling every original down the NUI bridge to fill 123px squares (MICA-110).320 rather than something nearer the tile, and the reason is that "the tile" is not one number:
MAX_SCALE(1.4), so the same tile is 172 device pixels at the largest setting. A thumbnail cut to fit 123 would be visibly soft there, for a setting that has nothing to do with the camera — the same trapCAPTURE_MAX_DIMENSIONexists to avoid.So: 2.6x the tile as drawn, 1.9x the tile at maximum zoom, and one number that still works if the grid ever goes to two columns. It is a ceiling, not a target — see
computeThumbnailSize.