# Every timestamp in the window lost the units digit of its seconds - #87
Merged
Conversation
The start time is nineteen characters exactly and the column was a hundred and forty pixels, which fits eighteen of them. So 22:03:25 was drawn as 22:03:2 — which reads as a time rather than as a truncation, and is why nobody noticed it until somebody photographed the column and read it. Widened to a hundred and fifty-two. Found by an agent working on column layout, in a file it was told not to touch, and reported rather than worked around. Its other finding is recorded in §11 rather than fixed: a right-aligned caption sits flush against the next column's, so "CPU %" and "Working set" touch. I could not establish from a magnified capture whether the join is a clipped letter or two captions meeting exactly, and the header cell clips and pads within its own bounds — which says they cannot be overlapping. Three changes have now reported it and none has fixed it; it wants measuring in the shared painter rather than another guess, and widening a column until the join stops showing would be the wrong fix twice over.
Hawkynt
force-pushed
the
start-time-width
branch
from
August 21, 2026 20:28
98b147b to
0037eeb
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The start time is nineteen characters exactly and the column was a hundred and forty pixels, which
fits eighteen of them. So 22:03:25 was drawn as 22:03:2 — which reads as a time rather than as a
truncation, and is why nobody noticed it until somebody photographed the column and read it.
Widened to a hundred and fifty-two. Found by an agent working on column layout, in a file it was told
not to touch, and reported rather than worked around.
Its other finding is recorded in §11 rather than fixed: a right-aligned caption sits flush against
the next column's, so "CPU %" and "Working set" touch. I could not establish from a magnified capture
whether the join is a clipped letter or two captions meeting exactly, and the header cell clips and
pads within its own bounds — which says they cannot be overlapping. Three changes have now reported
it and none has fixed it; it wants measuring in the shared painter rather than another guess, and
widening a column until the join stops showing would be the wrong fix twice over.