Both button and move data can be present in mouse updates, especially in Absolute mode.
At the moment, when a click happens, the coordinates of that click are never passed back via a callback, because State is first checked, and if non-zero, movement is never processed.
Two solutions seem possible:
1) Move to passing a more stroke-like object instead of just state or x/y
2) Remove the ELSE clauses from the checks in the mouse processing loop, and process movement before clicks.
Both button and move data can be present in mouse updates, especially in Absolute mode.
At the moment, when a click happens, the coordinates of that click are never passed back via a callback, because State is first checked, and if non-zero, movement is never processed.
Two solutions seem possible:
1) Move to passing a more stroke-like object instead of just state or x/y
2) Remove the ELSE clauses from the checks in the mouse processing loop, and process movement before clicks.