Since even the smallest iDevices have gigabytes of data for storage, and
since gps routes are numbers (i.e. they should be very small in terms of
storage footprint,) I see no reason why we shouldn't be able to have
hundreds of routes, assuming they are saved in such a way that meaningful
labels are attached to them. There are places I tend to travel only
occasionally whose routes I forget. If I could store them, then the one or
two times a year I need to go there, I'd be able to bring up what I had done
in the past.
I don't feel artificial limits should be placed on information: whether the
number of bookmarks a notetaker can save when reading files, the number of
routes a gps can save, or the number of articles one stores from news
sources. In the end, when designing applications, the limits of the storage
device should dictate the upper bound of the information available.
And, on an unrelated note, I often used the reverse route feature, so hope
it is included sooner than later.
-----Original Message-----
From: gps-talkusers-bounce@xxxxxxxxxxxxx
[mailto:gps-talkusers-bounce@xxxxxxxxxxxxx] On Behalf Of Tanner, David
(DEED)
Sent: Friday, March 01, 2013 6:56 AM
To: gps-talkusers@xxxxxxxxxxxxx
Subject: [gps-talkusers] Re: seeing eye app and routes history
I would definitely agree with addition of the feature for reversing a root.
I have found that feature very helpful on untold numbers of occasions.
Hopefully, it is something that could be added in a update early on in the
continued development of the app.
As far as the number of routes to be remembered, I would go with the ability
to save at least 10 routes. I would think that this would probably be
plenty for most folks. But, that doesn't mean the last 10 routes because in
reality there could be some of those last 10 routes that the user may have
only needed for one time, and would likely never or very rarely use one or
more of them. So, I would suggest a menu choice under the routing menu that
would allow the user to choose to have the currently active route to their
list of selected routes to be available to them until such time as they
decided that they no longer needed that route. As a part of that I would
also suggest that the user should have an option when using one of their
chosen routes to ask that the route be updated occasionally so that any
thing that might have changed on any part of that route that might make any
of the information in the route obsolete would get changed to reflect any
changes including road
or sidewalk construction that might mean that a part of the area normally
traveled on that route would need to change.
-----Original Message-----
From: gps-talkusers-bounce@xxxxxxxxxxxxx
[mailto:gps-talkusers-bounce@xxxxxxxxxxxxx] On Behalf Of Mary Otten
Sent: Thursday, February 28, 2013 6:56 PM
To: gps-talkusers@xxxxxxxxxxxxx
Subject: [gps-talkusers] Re: seeing eye app and routes history
Hi Mike,
Thanks for clarifying that the routes history could be changed. It strikes
me that a couple of things with regard to routes could be useful. One is a
reverse route feature that I think you have on your other apps, and the
other is a favorites or saved routes. In other words, rather than
automatically remembering the last 2 routes or 5 or however many routes, the
user could choose to tell the app which routes to remember, and those would
be what shows up on the routes page.
Mary
Mary Otten
motten53@xxxxxxxxx
To change your email settings (unsubscribe, digest only, or vacation mode):
http://senderogroup.com/social_media/email.htm
Additionally, to unsubscribe send an email to
gps-talkusers-request@xxxxxxxxxxxxx with "unsubscribe" in the Subject.
To change your email settings (unsubscribe, digest only, or vacation mode):
http://senderogroup.com/social_media/email.htm
Additionally, to unsubscribe send an email to
gps-talkusers-request@xxxxxxxxxxxxx with "unsubscribe" in the Subject.
To change your email settings (unsubscribe, digest only, or vacation mode):
http://senderogroup.com/social_media/email.htm
Additionally, to unsubscribe send an email to gps-talkusers-request@xxxxxxxxxxxxx with
"unsubscribe" in the Subject.
