Tisty 1.9.3
The store is untouched: it reads and writes what 1.9.0 already did, so one
machine can take this whenever it likes and the others can wait.
What arrived is on screen without being touched first
A document written on another machine reached the disk and the window went on
showing the list it had — for hours, with somebody watching it. Moving between
documents brought it up at once. So did closing and opening the app. Nothing was
missing and nothing was late: nothing was being drawn.
Asking for the tasks reprojects the store before answering. Asking for the
documents did not — it served whatever the session was holding in memory. Both
questions go out together and nothing orders them, so whenever the documents won
the race they came back as they were before, the window compared them with what
it already had, found no difference, and drew nothing. Tasks appeared and
documents did not.
Coming back to the window asked only for the tasks, too. It asks for both now,
and it does so when the window is seen again rather than only when it takes the
keyboard: on a Mac, a window uncovered by moving another one aside never takes
it.
A round that hangs no longer stops the ones behind it
Against a cloud folder a round can hang for as long as that folder likes, and
the window held the door shut while it did: every later round queued up behind
one that never came back, which is how an app in front of you goes quiet for
hours and then, when the folder finally answers, catches up all at once. Past
the minute it was already calling slow, the way is let go of. What was owed is
owed still, and a round that answers busy asks again rather than passing for one
that ran.
It looks at the folder often enough
The window glances at the shared folder every thirty seconds while it is on
screen. A glance is the size and the time of the folder's own segments — three
files, no byte of them read, five milliseconds on a Google Drive folder — so
what lands there is carried within the half minute instead of waiting for the
quarter hour. It lets go of the session before walking a folder that can take
its time, so nothing else waits behind it, and it reads the marks again after
each round rather than taking its own writing for somebody else's.
Nothing is read back over what you are writing
The other half of showing things sooner is not showing them on top of somebody.
A body is saved a moment after the typing stops, and between that save and the
next keystroke the window used to be free to read the document back from disk —
which lost what had just been pasted and dropped the caret at the end. The
document in hand is left alone while it is being written in, refresh or no
refresh.
Tags an assistant can look at before coining another
Also here, from before: tags hands back every tag already in use, the most
used first, with how often each appears. Capitals and accents change nothing —
subjects that are counted, not tags: six is already a lot, a subject takes as
many words as it needs, and a word that merely appears is no subject. A document
takes no tag field at all: it is tagged by writing #word in its own text.
Full Changelog: v1.9.2...v1.9.3