diff options
| author | user <user@clank> | 2026-08-14 16:53:32 +0200 |
|---|---|---|
| committer | user <user@clank> | 2026-08-14 16:53:32 +0200 |
| commit | 94a72a9bb7abe054b10e6a113f38fc084a1918b4 (patch) | |
| tree | 1e762b4ea373244afb312c2a70413a67d3215fd4 /docs | |
| parent | sl0ppty: status_pad defaults to 4 (diff) | |
| download | slosh-94a72a9bb7abe054b10e6a113f38fc084a1918b4.tar.gz slosh-94a72a9bb7abe054b10e6a113f38fc084a1918b4.tar.xz slosh-94a72a9bb7abe054b10e6a113f38fc084a1918b4.zip | |
sl0ppty: the tab strip answers the pointer
Tabs and +tab were clickable and looked identical whether the mouse was on
them or on the other side of the screen. They light up now, in the same
language the collapsed stack already uses: foreground only, immediately, no
dwell — this is feedback about where the pointer is, not an action being armed.
Colour and weight are kept independent. Weight says which tab you are in,
colour says where the pointer is, so hovering the tab you are already in does
not make it look like you left it. That is the case worth having a test for and
it has one.
Each label is drawn, its width read back, and redrawn in the hover colour only
if that width turns out to be under the pointer. Two paints of a few cells buys
the guarantee that the lit cells are exactly the registered ones — the
alternative was measuring the label separately from drawing it, which is the
same "two implementations of one rect" that D-one exists to prevent.
The pointer test is now shared with the stack header rather than written twice,
since that is three places asking the same question of a rect they are about to
register.
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions
