Add checkboxes to allow delete or archive action to be scheduled for
after a rematch is done. The UI's a bit awkward. NA tips help,
but it may be possible to make it easier to understand.
The assertion's clearly blocking testing, but I'm not sure it's not an
error for two move explanations to want to co-exist. For now they're
concatenated.
I was getting language name and iso code confused so adding a new type
to keep them separate. Keep string type for crossing JNI boundary and
passing as param e.g. in URLs and Bundles.
I want receiver to know when message was originally created. This adds
timestamp to messages and passes it via send proc. Client needs to
send it where possible. So far, MQTT format can't include it without
change, so I'm adding a new proto version. This change can read the
new version. Once that's well-enough distributed I can start sending
using it. Other transmission types than MQTT are for later.
Logic to set the fire time in the future wasn't firing when display of
the nag was diabled, so timers fired every few ms because they always
existed in the past.
Because I can't filter for file type, user may ask to open the wrong
thing. So put up an alert with a "try again" button. And include the
name of the chosen file for clarity.
After a hard-reset I can't open an archive file if I'm looking for
x-zip, because, I guess, the mime type is something the OS records
rather than deduced from the file. With this change, I can export,
hard-reset, and then import the file to get my settings and games
going again.
Main problem, aside from the explanations being stubbed out, is that
zip file overwriting doesn't work: once an entry is in the file, it'll
be there when the file's overwritten even if that entry is
excluded. This happens even if I create the file in memory and then
overwrite using the bytes.
