Skip to content

v0.2.1

Choose a tag to compare

@marc-korte marc-korte released this 19 Aug 23:15
· 11 commits to main since this release
e9e66f7

A maintenance release for the three problems reported in
#3, all of them
reproduced on a Manta. There is no firmware requirement beyond 0.2.0's, and nothing
about how links are stored has changed, so upgrading is a straight replacement.

The folder picker can be used more than once

Closing the picker does not unmount its view, so after one successful link the button
stayed greyed out and the "Closing…" message stayed on screen for every later visit,
until the device was restarted. The picker's state is now reset once the host has
finished closing, and again when it is next opened, so work started in one visit can no
longer apply its result to the next.

Links stay responsive after leaving and returning to a note

Tapping a link was unreliable in a way that looked random but was not: it depended on
how much was on the page. The plugin stopped listening for taps whenever the note
context read back empty, which is what happens during any excursion, including the one
the plugin itself causes by opening a folder. Coming back, it had to wait for a
heartbeat and then re-read the whole page, measured at one second for a light page and
over three for a busy one, and every tap in that window was silently discarded. A
heavier note meant a longer dead spell, which is why one note felt reliable while
another ignored half the taps.

A missing note context is now tolerated for a minute before the plugin stands down, so
returning to a note no longer costs a blind window.

Opening the picker no longer jumps into a folder

The tap that opens the picker from the lasso toolbar is itself a touch on the screen,
and the toolbar appears right next to the word being lassoed. That tap was therefore
being hit-tested against the note, and it opened the link underneath. Doing so threw you
into the file manager and destroyed the lasso, which is why the picker afterwards
answered the link button with

No lasso rect: {"error":{"message":"No Lasso action has been performed. …","code":904}}

Both symptoms were the same fault seen from either end. Navigation is now suppressed
while the plugin's own interface is up. The suppression is armed by the toolbar buttons,
kept alive by touches in the picker, expires by itself if the host takes the view away,
and leaves a short grace period after closing so that the closing tap cannot navigate.
When the lasso really has been lost, the picker explains how to retry instead of
printing the raw error.

Installing

Copy SupernoteFolderShortcuts.snplg to the device and install it from the Supernote
plugin manager, as with previous versions.