The delete button was deleting all points between the first and last,
which, when you use the "when was I here" button, could span days
or months that you don't want to delete. So, after doing a spatial
query, the delete button will only delete the points that are shown.
This primarily helps when you want to use the "when was I here" button,
to remember a previous day when you were at the same location.
Besides that, seeing the current realtime location provides helpful
context to historical tracks.
I had an incident where I was tampering with the database on my
computer, being synced over Syncthing, and I caused a conflict that
made the app stop recording, even though the app UI continued to show
the normal recording icons. Closing and re-opening the db connection
when leaving the house would have helped prevent that.
Since trkpt will stop capturing points, it will not reach the later
part of the handler that commits when a new point is 30 seconds
after the previous commit.
Added a 30-meter distance check to prevent big editing disasters
but I'm not fully satisfied with this feature yet. I think this
is a little better than before though.
The text of the notification will still say the most recent location,
but in going from fullpower to dead I want the time of the notification
itself to be the moment of rip.
Recently I took a 90 minute drive, and trkpt missed about 15
minutes of it. It wasn't until now that I realized it probably
went into doze mode due to the low accelerometer movements.
If the device is plugged in it does not doze, but to achieve the
no-friction goal we should not be required to take it out of our
pocket and plug in all the time for fear of missing points.
voussoir