Skip to content

v0.3.0

Choose a tag to compare

@marc-korte marc-korte released this 27 Aug 13:44
· 7 commits to main since this release

The tap path is rebuilt. Links are hit-tested against the note as it stands at the
moment of the tap, instead of against invisible windows laid over each link, and a
narrow read-only raw-input fallback covers the firmware cases where the SDK stops
reporting complete gestures.

Validated on a Manta A5 X2: stylus and finger taps each open their folder, and a PDF
or EPUB excursion followed by Last Opened Note and an immediate finger tap
navigates correctly. Nothing about how links are stored has changed since 0.2.0, so
upgrading is a straight replacement.

Linked objects can be moved and stay tappable

The invisible overlay windows swallowed finger events, so a linked object could not be
dragged at all, and their rectangles came from the last refresh, so the tappable area
stayed behind whenever the object did move. Taps are now hit-tested against the live
page, which makes the clickable area the link's own rectangle by definition and lets it
follow the object.

A lasso move is not published until the rectangle actually changes. While a moved
object stays selected the Note app can keep returning the old rectangle, or briefly
return fewer links. The page is held dirty until it settles, the old hit area is
preserved if the move is cancelled, and that dirty state survives a document excursion
so the first tap after returning uses the committed moved rectangle.

The first tap after a PDF or EPUB no longer disappears

Manta firmware can hand the SDK listener only an orphan UP after returning from a
document, and can suppress a raw touchscreen axis whose value did not change. A
read-only raw-input fallback retains the absolute axes across that handoff and feeds
complete single-finger taps through the same context, scale, ownership and hit-testing
guards as SDK motion events. It accepts single-finger taps only and does not modify the
firmware's own monitor.

One slow read cannot block every later refresh

Context reads have a two-second deadline driven by an Android Handler, which keeps
running while Supernote pauses JavaScript timers. Context probes run independently of
page reads, page reads are single-flight, and a clean tap miss no longer starts another
full-page scan.

Fewer ways to lose a tap

First reads wait for the native page rather than only the reported path, after hardware
traces showed provisional empty pages at 531ms and 1026ms with the note finishing its
load at 1525ms. PEN_UP payloads are recycled so the native element cache cannot fill
and blind the plugin. Tap claims can only be released by their owner, including when an
input handler throws. Page scale is not treated as measured until the SDK probe
succeeds. The folder picker has an owner-stamped single-flight guard, so rapid presses
cannot create duplicate links and delayed work from an old picker visit cannot close a
newer one.

Known limitation

On very large pages a full scan can take around twelve seconds, which is well past the
budget a tap is allowed to wait for one. A tap that has to wait on a scan there may be
dropped, and need a second tap. See #7.