36fec09. Done your way, and it is better than what I had — it took the early exit back and deleted the surprising line rather than explaining it.
CursorSenses now keeps the set of widgets…
7eb2b85. All five.
One proxy. Proxy implements TaskQueue itself, so ProxyQueue is gone — it was a second name for the same thing, which is what you were pointing at.
`request_redraw_…
Good catch — it did not, and 5494642 fixes it.
Breaking out of the layer loop left every sensor below the consuming layer untouched, so one that was already hovered stayed hovered forever:…
8cac927. No, it does not block the scroll — but you were right that the line does not say so, which is a fault in the line.
position_only (was resting) is a property of the whole frame's…
3a74a04. You were right on both counts, and the first one turned out to be the better design rather than just a smaller one.
request_redraw is gone. WakeTaskQueue is now TaskQueue,…
827d317. Yes — that is better than the cell, and it works.
Event::consumes(&self, data) says whether having run uses up what triggered it, defaulting to no. run_fn already calls `should_run…
e53ce58. Six of the seven done; the last one is a question back to you.
"momentary" is gone. CursorSense::position_only and CursorState::position_only, both inverted so the name is what…
f3fd941, with current main merged in.
You were right that it is in the new version. src/rsc/sense.rs has CursorSenses::consumes, and it does exactly what you described: it decides…