Hi
I'm getting this too and it's getting very frustrating. The problem is I like to go through the weekly points sheet but it keeps losing where I've got up to. If I don't save regularly I lose my updates. If I do save, I lose my place. Accepting what Alex says that it can't be fixed, does anyone have a recommended way of going through a weekly sheet?

Just thinking about this further, maybe use Google maps on another device like my phone while having WizPoints open on my iPad?

Jan

Last edited by Jan (3/20/2015 12:56 pm)

This these issues are generally memory issues on the device, there are a number of things completely outside of my control, one thing for sure is going into another app whilst using either app does have issues this is to do with memory on the device and the way it is controlled by IOS not by the app itself, I see this all of the time and it is a memory issue. Essentially what is going on is IOS when you switch an app to the background believes it is not as important as the foreground app and it will kick that app out of memory if the foreground app needs more memory.

Mapping maps using a massive amount of memory and can quickly exceed what is available, this is a well known issues for both Apple and Google maps.

Apple maps
http://stackoverflow.com/questions/12641658/ios6-mkmapview-using-a-ton-of-memory-to-the-point-of-crashing-the-app-anyone-e

Google maps
https://code.google.com/p/gmaps-api-issues/issues/detail?id=5202

In the version I am working on mapping is embedded into the app so the need for switching is greatly reduced except in the instance where you need streetview, this I cannot control and will not support because it is virtually impossible to keep it from crashing the apps.

Using one device for the app and one for google map is a good idea and works well it is what I do, also in the version I am working on the app saves the position in the revision when the question changes so if there is a crash you will start at that point.

atb

alex
 

Dont worry I understand how frustrating all these things are, I use the apps too for the knowledge so completely understand, as a legacy thing the app (because it worked well on windows like this) loads all the points for a specific revision set into memory and does not save until the end because it allowed the app to be very quick, but this does not work as well on Apple devices like it does on windows, so it will save as it goes along in the next version. Also for sets like the all pointed points set that can be 10,000+ points in a set it will load them in chunks of say 500 points rather than the whole lot in one go so this should see the memory requirement go down, I will also look at chuncking things like the weekly, thinking this through, having a set of say 800 points, if all you are doing is blasting your way from one end to the other then it is not proper revision, I find that doing the set in much smaller blocks of say 50-100 and spending proper time on each one is better in the long run.

One of the issues is memory, these devices whilst they work well are constrained memory wise it is a juggling act to get everything to work fast and reliable at the same time.

atb

alex