New user trying to get things set up "for real" after just playing with LapTimer for a couple weeks in the car. I'm attempting to create a set of POI's in v14.1 on iPhone 3GS and having some trouble. Each time I exit LapTimer my POI's disappear. The track still appears in the Lap List, but the POI's are gone and don't appear on the map either.
Prior to downloading v14.1 this did not happen. In fact, I had downloaded an existing track map succesfully in the old version (sorry, didn't pay attention to which one it was) and this track also no longer has POI's after the upgrade. Not sure if this helps pinpoint the issue, but some info to consider.
I had another user reporting this. POIs are made persistent when LapTimer is sent to background using the Home button. In case LapTimer is not sent to background but crashes or it is finished using the iPhone's task bar, or it cannot save due to memory restrictions - it gets no chance to save and will roll back to the last know version when started the next time.
Please do the following to verify that POIs are saved:
Add any POI in LapTimer
Press the Home button to send LT to background
Wait a few seconds
Bring forward the task bar (double Home press)
Kill the LapTimer process
Lauch LT again - check the POIs are there
Please make sure you have not set the 'Revert POI to Bundle' in LapTimer's Expert Settings. This will overwrite any change with the original POI database.
I'm very interested in getting a reproducible description where LapTimer does not save the POIs. So far I have not been able to reproduce this on my test device.
In reading your response, I realize I misspoke - It's iPhone 3G, not 3GS so it's using 4.2.1 OS, which doesn't have the capacity to leave LapTimer running in the background. Maybe this helps further the diagnostics!
Harry I did a test and a set of POI's will remain IF there is lap data associated with them. If no laps then they are removed upon exit. I added a POI to an existing set (that had lap data associated with it) successfully.
Think I have found the issue. The saving procedure for the POI database differs on the multitasking and non multitasking iOSes. While a save is forced on multitasking devices, saving a database is done on non multitasking devices if the database is considered 'changed'. There was a bug in LT that not marked the DB as changed when a POI was created but not changed afterwards (which is the case for POI created in Map, GPS View etc. as long as they are not edited afterwards, and for POIs loaded 'as is').
So the work around is indeed changing something in one of the POIs - this marks the DB as changed. Finishing LT afterwards, will save the database and all POIs included.
Please check and let me know. I will add this fix to the next LapTimer version released.
Sounds like we are nearly there. If I create a new POI, assign it to a track (or allow it to reside in Unassigned), and even if I go back and edit the POI to adjust its exact coordinates or trigger type etc. it will not be saved until the track it belongs to also has data recorded with it. Perhaps there's still the possibility of a database remaining marked "unchanged" even if the POI gets edited after creation? I have had them disappear even if edited!
