Closed kloin closed 8 years ago
This is definitly something to do with the process trip path on the server, or the JSON stuff on the client. It seems to get slower as the trail is longer.
This happens when loading a trail the first time, but works instantly once cached, So I am assuming this is happening due to some network request
Happens everytime on the "MyTrip" page, but that will be because It is not being cached (I think)
Seems to be the processResult method at line 664 of MapViewer.
So some interesting stuff. When the map data is cached it takes about 400 ms When the map data is not cached, the process result method takes like 15000 ms.
Ended up just putting the Loop inside a Runnable thread, posting it with a handler
Related to
#62
It seems that the map is freezing while the request is being sent to the server, and awaiting a result.