Notices

Just out of curiosity : Pymapper (http://www.internettablettalk.com/fo...ad.php?t=10185) allows dragging of downloaded maps without black borders. Is it the pygame that makes the difference or the way tiles are stored/accessed ?

would be nice to have in the repository settings the zoom levels supported too.

Pymapper doesn't have to deal with screen rotation. Pymapper probably does the same thing that Maemo Mapper v1.x did, which is load a 4x3 grid of maps into a 1024x768 buffer (or larger?) and pan the view around it. You can't take advantage of the same initial assumption when you're rotating the viewpoint, because now you have to load maps into non-parallel pixel spaces. For example, to load the same 5x4 grid of maps into a buffer to draw (and pan around) on the screen, you'd need 1280x1280 pixels (> 6.5 MB of buffer). And to have the same pannability as the non-rotated situation, you'd need more than 4x3 grid panels, increasing the number of panels that have to be accessed from the (relatively slow) database.

I'm not saying it's not possible to do it more efficiently. It just wouldn't be easy to do now, given the current codebase. I can look into reducing some of the blackness without increasing the memory requirements (by too much), but right now my focus is on stability and features.

I assume that if I am not connected, it doesn't matter if the maps are downloaded, the route cannot be reconfigured, correct?

@Gnuite

YOU ARE A LEGEND MATE. Quite honestly how you find time to not only develop but then maintain, bug fix and hag around in here looking for and answering questions AND most likely hold down a paying job I have no idea. But I am more than thankful for your efforts - especially as NONE of the commercial offerings for navigation do New Zealand any justice at all.

I haven't had time to read every post in this thread (that's what happens when you go away for a couple of days) but here are my initial observations from v2.0 (I haven't even had time to get to the .03 release)!

Yesterday I knocked out 450km on a journey to Auckland and back - here that equates to about 7.5 hours driving on the roads we have! I used Maemo Mapper v2.0 the whole way and found...

- Very stable on my N800 and works just fine with my GPS unit.

- Have you changed the positioning algorithms as I reckon it is about 5m or so more accurate that 1.x?

- Right now it does seem to suck juice quicker than previous versions. Yesterday was about 8 hours up time for the N800 with BT on. The journey drained the battery completely a couple of times. Previous trips I reckon only used 50-70% as much juice. I have no data from it (quite frankly I was paying too much attention to the road ;o) but could this be the device sucking more juice when accessing the DB?

- Definitely v2.0 is using more processing as I can no longer easily run Kagu and Maemo Mapper with any degree of responsiveness from the UI at 100km/h.

- Also it appears that when running at Level 4 to 0 that after a couple of hours up time MM starts to struggle when updating the maps. I have a screenshot when I arrived home (just need to get it online). The timer icons in the top left seem to represent a new map load or position update and after a while these start to build a fair old queue. By the time I pulled into the garage there would have been a good 20+ queued which equated to approx 500m of delayed travelled information. Damn funny walking around house showing me at 50km/h.

Interestingly the UI correctly displayed the position updates, time etc in the GPS info panel.

Is this just a reading from DB issue or the memory stack not clearing down quickly enough to start throwing new stuff in?

- Google Street Maps for rural NZ pretty well are accurate but occasionally roads are missing (not a MM issue but pretty confusing none the less).

- The UI for creating routes is pretty well unusable in the car. Gnuite - don't take that as a criticism I just can see now why commercial GPS nav systems have more Canola'esque UI's. Big buttons rock at 100km/h. (BTW Kagu really sucks at this - you trying hitting the pause button at speed).

Again a top effort and one for which I, and I am sure many others, are truly grateful. Someone near him buy him a pint.

I have actually seen this problem too and I've been using Maemo Mapper for a while. Once I tried several times to drag up and down, but it wouldn't move until I first dragged left or right, then dragged up an down.

I tried several times because I couldn't believe it. But it doesn't always happen.

Correct. The routes are computed by the google maps server. If you're not connected to the net, well, you get the picture.

Gnuite,

I'm experiencing a problem that you fixed somewhere between 1.4.5 and 1.4.7:

I am getting lots of repeated updates of the route (as if I'm off track), even when I am still on track.

Anyone else experiencing this?

Gnuite,

How difficult would it be to set zoom level based on speed *and* make the zoom/speed threshold configurable?

I use Wayfinder and it does this, but it's not configurable. Having both would be great.

Thank you once again, 2.0 very stable and good travel for 1000km already is good so far. If I can buy you a beer anytime Mr Gnuite.