concrete/interaction_handler.py was 310 lines reachable only from
examples/07_pressed_state_demo.py - no library code, no tests. Press and
hover feedback existed but could not be used through the library's own
interface.
Adds to the manager:
handle_hover(point) -> frame if hover changed, else None
handle_touch_down(point) -> frame showing the pressed state
handle_touch_up(point) -> (frame, callback result)
reset_interaction_state()
Returning None when nothing changed visually lets a UI skip a redraw it
does not need - which matters on e-ink.
Press state belongs to one rendered page, so the InteractionStateManager
is bound lazily and rebound whenever the displayed page changes, resetting
the outgoing one so a press cannot survive a page turn.
Wiring it up immediately surfaced a real bug it had been hiding.
LinkText.render passed [origin, origin + size] - a list of two numpy
arrays - to PIL's draw.rectangle, which needs a flat four-scalar box.
Rendering any hovered or pressed link raised
TypeError: coordinate list must contain exactly 2 coordinates
so the entire feature was broken on this PIL version. Fixed by building
the box explicitly, and the two branches now share it instead of
duplicating the call.
Tests cover hover/press/release, no-op paths, that an unchanged hover
reports no change, state rebinding across navigation, reset, and
regressions for the rectangle crash.
916 passed. examples/07_pressed_state_demo.py still runs.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
dtourolleandClaude Opus 5
0ce1aeaa87