aboutsummaryrefslogtreecommitdiffstats
path: root/docs/scripting.md
diff options
context:
space:
mode:
authorsl0p <sl0p@sl0p.foo>2026-08-14 00:44:19 +0200
committersl0p <sl0p@sl0p.foo>2026-08-14 00:44:19 +0200
commita7d3d42ecbf5d143bd1f98c379051736f97dc0fa (patch)
treefed88c198ccb2780b1a63e6136d5612e8a51f7b8 /docs/scripting.md
parentsl0ptty: fix the split guide describing the layout from before the split (diff)
downloadslosh-a7d3d42ecbf5d143bd1f98c379051736f97dc0fa.tar.gz
slosh-a7d3d42ecbf5d143bd1f98c379051736f97dc0fa.tar.xz
slosh-a7d3d42ecbf5d143bd1f98c379051736f97dc0fa.zip
sl0ptty: the split guide arms on dwell, not on contact
A pointer crossing a border on its way somewhere else made the screen flash. The guide now waits for the pointer to rest (hover_delay_ms, 250ms by default, 0 to disable). The timer is on pointer stillness rather than on the hovered target, which is what makes a sweep across three borders arm none of them: every motion event that changes the position restarts the clock, so only stopping counts. Holding the button on a border skips the wait, because that is intent rather than passage. This needs the loop to wake when nothing has happened — a pointer that is deliberately not moving generates no events to repaint on — which is the same self-scheduled repaint toasts already needed, so app_next_deadline_ms grew a second reason rather than the loop growing a second mechanism. Four older guide tests waited 60ms and now wait for the dwell; they were asserting on contact because contact was all there was. 398 checks green.
Diffstat (limited to 'docs/scripting.md')
0 files changed, 0 insertions, 0 deletions