![]() |
2008-01-16
, 03:02
|
|
Posts: 1,245 |
Thanked: 421 times |
Joined on Dec 2005
|
#161
|
![]() |
2008-01-16
, 03:04
|
|
Posts: 1,245 |
Thanked: 421 times |
Joined on Dec 2005
|
#162
|
When I drive with N800 + Mapper + GPS, I want to see a map moving towards my the direction in which I am going. i.e. the blue dot should always move upwards.
Is it possible ?
I have tried auto center options -- lead and lat/lon but it just keeps the dot in center. The map moves anywhere but not upwards (or downwards, I should say).
Any clue ?
![]() |
2008-01-16
, 03:13
|
|
Posts: 150 |
Thanked: 6 times |
Joined on May 2007
|
#163
|
Heading is also indicated by the blue line coming out of the dot that indicates your location. If it's not big enough for your tastes, considering increasing the Draw Width in the Settings dialog.
![]() |
2008-01-16
, 03:15
|
Posts: 81 |
Thanked: 115 times |
Joined on Jan 2008
|
#164
|
![]() |
2008-01-16
, 03:17
|
|
Posts: 1,245 |
Thanked: 421 times |
Joined on Dec 2005
|
#165
|
MM2 uses gdbm database to save the card space and make the interface simple, the drawback is that gdbm is not that efficient. Every time you fetch a key or data, it allocates memory twice - read from the file and make a copy then give it to you, user has to free the memory - this approach is not necessary in this application. I delete that in my windows gdbm library, since MS runtime simply refuses to free the memory and crashes. Redundant memory allocation of gdbm is a slow factor.
Hash value calculation is quite consuming in gdbm, which depends on the key length. The MM2 uses 12 byte key, it seems too long, there is no difficult to condense it to 8 byte length, it can save some time.
The most important, there is basically no cache management in gdbm, every time you fetch a key or data, it goes into reading file. It really slow you down. So implementing cache management is definitely a good way to smooth things up.
From my point of view, it may be improved if we have a SW architecture like
GUI <--> cache management <--> downloading/file read/save
The best way to speed up the app is to avoid the three doing intensive jobs all together at the same time, so when GUI is busy the SW doesn't do saving, when downloading GUI should be told to wait, the central piece should be the cache manager.
The Following User Says Thank You to gnuite For This Useful Post: | ||
![]() |
2008-01-16
, 03:25
|
|
Posts: 1,245 |
Thanked: 421 times |
Joined on Dec 2005
|
#166
|
Is there some way to defrag or optimize the maps .db files? MM2 used to work very quickly when I first started using it, but now I downloaded many maps and the .db file is 900mb and displaying of maps is much slower now, especially when changing zoom levels.
![]() |
2008-01-16
, 03:42
|
Posts: 81 |
Thanked: 115 times |
Joined on Jan 2008
|
#167
|
Depending on the size of the database, this operation might take a while....
![]() |
2008-01-16
, 03:47
|
Posts: 26 |
Thanked: 2 times |
Joined on Nov 2007
|
#168
|
![]() |
2008-01-16
, 04:01
|
Posts: 33 |
Thanked: 16 times |
Joined on Dec 2007
|
#169
|
![]() |
2008-01-16
, 04:07
|
Posts: 33 |
Thanked: 16 times |
Joined on Dec 2007
|
#170
|
Is there some way to defrag or optimize the maps .db files? MM2 used to work very quickly when I first started using it, but now I downloaded many maps and the .db file is 900mb and displaying of maps is much slower now, especially when changing zoom levels.