[manuelmayer-dev]

Requested by the maintainer (no issue).

Summary

UI nodes can now declare pointer-down, pointer-move, pointer-up and tap to receive raw per-finger positions every 16 ms and multi-finger taps, so plugins can build a touchpad. A pointer-move still waiting for a slow plugin is replaced by the newer one in the host and the plugin runtime instead of queuing without bound.

Testing

Full Release build and test suites pass, plus runtime, web client and legacy touch shim specs. Verified end to end with a scratch plugin on a disposable host, driven from Chrome and a real tablet over the LAN, including moving and clicking the macOS cursor from the widget.

Plugin SDK / API compatibility

Added UiComponentEvents.PointerDown, PointerMove, PointerUp and Tap, three UiComponentModifiers constants, the UiPointerSample, UiPointerDown and UiPointerUp structs, and four readers on UiEventData.

• No public, non-obsolete SDK or plugin protocol contract was removed or changed
• Contracts were only extended additively (new members with defaults, new optional fields, new message types)
• Anything being retired carries [Obsolete] and [MacroDeckDeprecated], is in the deprecation registry, and still works
• A plugin compiled against the previous SDK still loads and behaves identically (source and binary compatible)
• The conformance suite passes and the sample plugin builds and runs unchanged
• Any intentional break was explicitly agreed beforehand and is described below

Notes

A plugin that already declared its own event named tap or pointer-* now claims the pointer on its tile, the same as when drag was added. The Companion App needs a matching change.

Checklist

• Tests were added or updated where needed
• The change was verified manually where appropriate
• Documentation was updated if the change affects documented behaviour
• I reviewed and understand every submitted change