diff options
| author | user <user@clank> | 2026-08-14 14:25:13 +0200 |
|---|---|---|
| committer | user <user@clank> | 2026-08-14 14:25:13 +0200 |
| commit | 858234c05031a7bffc3ffe2a9b2aa4530d3ff0d7 (patch) | |
| tree | 951d60c94949dc43c468252142a93006663b9f76 /docs/scripting.md | |
| parent | sl0ppty: positional shaders, and a config block to ask for them (diff) | |
| download | slosh-858234c05031a7bffc3ffe2a9b2aa4530d3ff0d7.tar.gz slosh-858234c05031a7bffc3ffe2a9b2aa4530d3ff0d7.tar.xz slosh-858234c05031a7bffc3ffe2a9b2aa4530d3ff0d7.zip | |
sl0ppty: pane states are a table, not three hardcoded knobs
dim_unfocused, drag_grayscale and drag_dim were three knobs describing two
situations, and there was no way to say anything about the third, fourth or
fifth. They are replaced by a table: a state names a chain, and the chain is
exactly as expressive as the global `shaders` block because it is the same
parser.
states {
dragging { }
drop_target { grayscale amount=200; dim amount=140 }
suspended { grayscale amount=180; dim amount=90 }
scrolled { tint amount=30 color="#ffcc88" }
unfocused { dim amount=90 }
}
A pane is usually in several states at once, so exactly one wins: the first to
match, in a fixed order running from the most deliberate to the most ambient.
Fixed rather than read from the block, because it is a ranking by urgency
rather than a preference — a pane you are holding should not be recoloured by
anything, and a mode the whole screen is in outranks an ambient hint about one
pane. They do not stack, which is the same call the drag policy already had to
make by hand: two reasons to be grey compound into a muddy grey that reads as
neither. Defaults are the old drag behaviour and nothing else, so out of the
box this changes nothing.
drop_hover is now separable from drop_target. The pane under the pointer was
already distinguished by its border; it can now differ in colour too, and
defaults to the same chain so it does not have to.
Two states asked for did not survive contact with the code, and it is worth
writing down why:
`dead` cannot exist. app_reap() runs every iteration of the server loop, before
the paint, and closing the last pane closes the tab — so a pane whose program
exits is gone before a frame containing it is ever composed. A `dead` shader
would name something that could never draw. Making it real means keeping dead
panes until they are dismissed, which is a feature about lifetimes and not
about colour.
`suspended` could not be seen either, for a much smaller reason: draw_cb drew
its "press a key to run" label and returned before reaching the shader pass. It
falls through now. A pane that has not started is a state worth colouring, and
its label is the only contents it has.
Diffstat (limited to 'docs/scripting.md')
0 files changed, 0 insertions, 0 deletions
