v0.1.0-beta.32

Panels open at the top again, the keyboard no longer stops to save, and an
action that could not be carried out now says so instead of reporting success.

Panels start where you expect

• Reopening the clipboard or the phrases panel could land you where you had
  scrolled to last time. The cause was a flick that kept coasting after the
  panel was dismissed and dragged the list back down. The list now stops with
  the panel, and every way of opening it starts at the top.
• The first tap after reopening the clipboard was swallowed. It commits.
• The same coasting affected the symbols, emoji, custom symbol and edit panels.
• Pressing the phrases key while the panel is already open now returns the
  panel to its opening state instead of leaving your last selection, sort and
  expanded category in place.
• The clipboard and phrases panels take the same back control as the edit
  panel, with a label next to it. On a panel too narrow to hold the label the
  label gives way, and the control keeps a full-size touch target rather than
  shrinking to the width of its icon.

The nine-key reading column

• Locking a syllable now marks it in the reading column on the left, and the
  column scrolls far enough to show it. The column shows four rows at a time,
  and seven syllables put the marked row outside them.
• The mark itself was drawn in a green too pale to make out against the column.
  It is drawn in a color that stands out.

A larger system font

• At font sizes of 1.3x and above the Clipboard and Phrases labels wrapped
  inside their pill and the second line was cut off. They shrink to fit.
• At 1.4x and above the clipboard top bar ran past the panel and pushed the
  clear control out of view. The bar stays inside the panel.
• In a narrow landscape window the batch-selection header and its count wrapped
  and were clipped. They stay on one line and are shortened with an ellipsis.

Password fields

• Text copied inside a password field no longer enters the clipboard history.
  The check for this existed but was never applied where the system clipboard
  is read.
• The symbol and emoji panels no longer count what you pick inside a password
  field, because what you pick there may be part of the password, nor in any
  field whose app asks for no personalized learning — the same rule word
  learning follows. Elsewhere the Common tab still fills from what you use.

The keyboard no longer stops to save

• Focusing a text field re-read the whole user dictionary and all learned data
  on the thread that draws the keyboard, every time either had changed on disk.
  That reading has moved to the writer thread.
• Adding, deleting, importing or clearing on the word list page parsed both
  stores twice and rewrote them before the tap returned. The page returns
  immediately and the work happens on its own thread. The list you see is read
  back after the write, so a change that could not be saved leaves its row in
  place and says so.
• Exporting the word list no longer runs on the drawing thread.

A deletion that could not be finished is kept

• Deleting a word touches two stores. When the learned half could not be
  written, the word came back on the next start. The deletion is now written
  down and completed the next time the store is read.
• A word list you import never carries someone else's deletions into yours, and
  a file that holds nothing but deletions leaves your list alone. Restoring a
  backup does not carry them across either: an archive puts its words back
  without acting on deletions made wherever it came from, and a deletion this
  device still owes survives the restore.
• A word list you export leaves out the deletions it still owes, so the file
  you share does not carry words you have just deleted. The backup archive
  leaves them out too.

Backing up and restoring

• A store that cannot be read is left out of the archive, and the app names
  which ones were left out.
• A damaged backup file is reported as damaged rather than as a disk fault.
• A restore that carries a part it cannot read is refused before anything is
  written: nothing on the device changes, and the app names the parts.
• Your settings are put back last, once every store is in place.
• A restore that could not be finished, including one cut short by the process
  being killed, is taken back off the device rather than left half applied.
• A restored word list is loaded back into the running keyboard, so the
  suggestions follow the archive instead of what the keyboard held before.
• Only one restore runs at a time. A second one started while the first is
  still going is turned down and says why.
• A backup or restore that is still running stays on the page you come back to,
  and its result reaches that page rather than being lost. If Aegis was stopped
  while one was running, the page says so instead of turning forever.
• The list of what a backup covers, and the list of anything it had to leave
  out, use the same names for your data that the settings screens do.
• Choosing a file to export to and then leaving the app no longer discards the
  export in silence.

When a store cannot be read

• Learned data that cannot be read said it was not being shown, while the list
  underneath was showing it. It now says what is true in each case: what the
  keyboard still holds, or that nothing was loaded. It says the data is kept
  rather than that the keyboard is still using it, which was not true with
  automatic learning turned off.
• The clipboard history, the saved phrases and the recently used symbols and
  emoji are no longer written over when their file could not be read, so a file
  that is merely unreadable today is not emptied tomorrow. The phrases panel
  says so when this is why it is empty, and the clipboard panel now also says
  that nothing you copy is recorded until the file can be read again.
• A clip whose text could not be read is no longer reported as gone from the
  device. The two are told apart.
• When a deletion in the clipboard or phrases panel is written, the keyboard
  waits a set number of seconds for that write rather than however long it
  takes, and says the change could not be saved if it has not finished by then.
• A file with damaged text in it now counts as unreadable. It used to be read
  with the damaged characters silently replaced, which looked like success.
• A word that could not be stored says so instead of reporting it added.
• A clipboard change that could not be written says so, and a change to your
  saved phrases now names the phrases rather than the clipboard history.
• Saving a phrase while the phrase file cannot be read said the phrase was
  already there. It says the file could not be read.
• Clearing the recently used symbols or emoji says so when it could not be
  done, and the panel keeps showing them rather than emptying in front of a
  message that says they are still there.
• Importing phrases that could not be saved says the phrases could not be
  saved, instead of blaming a file it could read perfectly well.
• Exporting the word list on a phone that has not learned anything yet says
  there was nothing to carry, and no longer creates an empty file first.
• The message for a word the dictionary would not take now names both limits it
  actually enforces, on the word and on its pinyin.
• The clipboard files have one owner inside the app, so a restore and the panel
  cannot write over each other.

Privacy

• Setting up a new phone with Android's device-to-device transfer no longer
  carries any of the app's data across. The rule meant to keep it out covered
  only part of the app's storage, which left the dictionary, learned data,
  clipboard history, saved phrases and settings eligible to be copied. Cloud
  backup was already off. The app's own backup file remains the way to move
  them.

Setup screen

• It no longer lists English completion and correction, which the app does not
  do.