Forum Replies Created
-
AuthorPosts
-
July 25, 2022 at 9:01 pm in reply to: Error “Route downloading route from server”. When solution #26146
Today again it does not work.
July 24, 2022 at 5:16 pm in reply to: Error “Route downloading route from server”. When solution #26144This error keeps on coming. Is there a solution soon?
Aaah, yes. Could not find it but glad is already there. Thanks.
For me the search-function is now working fine. The latest release fixed it.
I am a even more happy user now!
ThanksApril 12, 2015 at 2:01 pm in reply to: App still crashing with searching of large number of pins #8027Glad to hear you found the problem and solved it. Looking forward for the next release.
Thanks for your effort.April 7, 2015 at 7:25 pm in reply to: App still crashing with searching of large number of pins #8025I have send the requested archive. Thanks.
Sorry but not resolved. Crashing when searching still happens. When you type the first letter the app crashes immediately.
It would be very nice if handling large numbers off pins could be fixed.
I checked it on IOS 8.3 on iPad 2 and iPhone 6.
Regards,
Geert
I sincerely hope you can find a solution soonest. The workaround works for OnLine searches (adresses f.i.) but not to find a city in the Built-In database (when I am offline) and that is what I use the search mostly for. Is an extra “city” or “adress” button next to the ‘Search All’ bar an option like now the search for coordinates?
Sure solving the crashing issue is probably the best solution of course.
What do you think of not searching the hidden pins? Isn’t that a good idea?
If you need a large test-database (18MB csv-file) I can send mine. Only attaching is not possible because of the 2Mb limit. Please give an address I can send it to.
An intermediate solution could be to not search not visible pins. Then I can switch of the pin-groups with lots of items in it.
Afterall who is interested in search results from pins not visible?
Okay, thanks.
Not a good idea for me. The problem is now I can’t use it anymore because when searching globally, the app crashes immediately at entering the first letter. I have made remarks about this before. This is because of the number of pins I have.I could live with not to be able to search pins but now almost all my search options are gone! Not nice!
Can’t you leave the address search separate? Or at least a search options where the pins are not searched?
Was it not very convenient to choose beforehand what to search and don’t bother about results in databases I am not interested in?
Can you please change it back or at least fix the search crash?
Thanks guys for trying to help; I appreciate.
Afterall I think I will wait for a future update for making the use of large numbers of pins possible.@Terry
I don’t think the way you use should be the way to go. It is a workaround yes, but I hope very temporarily.
My opinion is the crashes are mostly caused by a timeout (too long search timeout) and Apple policy throwing the app out. This is what I read in the CrashLogs fro Apple.@Bucky,
Sorry Buckey, I don;t see a JPEG.
Sure, deleting depends on the number of Pins. But 4 hours for only deleting a group of Pins is very very very long! This should be fixed.You say 17000 Pins is too much and not possible. Are you involved in the development of the App so you know for sure it is not possible or is it only what you think?
Hi Bucky Edgett,
Thanks for your reaction.
Bij browsing the Pins I meand NOT searching in the searchfield but sliding/swiping the listed Pins up until I see the wanted.
I have already organized my Pins in groups like you suggested.
I have however 17000 European campsites in one group. I can’t split this up.It would be nice if the app could handle this number of Pins in one file.
Have you read the Post about deleting this number of Pins takes about 4 hours? Not good either.Regards,
Geert
I have the same issue with large numbers of POI’s (>15000).
When I try to search in the pins, the app crashes.
When I browse the Pin’s, everything is accesible but is is very diffucult ofcourse to find the wanted pin. Some time ago I already have reported this bug.
I then suggested to send a testfile so it would be reproducable but did not hear something back.Thanks.
-
AuthorPosts