Mark Burton wrote:
Hi Felix,
Well, I don't have much to offer at this time regarding this problem.
Given that the issue has gone away in recent versions of mapsource, it
makes me think that it is a bug/feature/limitation in the garmin code
which they have subsequently fixed.
Well 6.14.1 was not a fix but a complete rewrite. It introduced rather
more errors than it fixed. This is the very first time I have seen it
doing something better than 6.13.6.
Obviously, we want your map to work with old gps or mapsource too so it
would be very good to find a workaround.
I would assume that this bug also crashes Nuvi/Oregon/Dakota and other
"new" gps (in comparison to old like Vista HCx/60/76/Edge - which will
all crash on this tile).
Someone would have to try out.
I'm not saying that it can't be a bug in our code, but if we focus
only on looking for a bug we may miss clues as to what the real
problem is.
So, the attached patch has the effect of reducing the size of the map
subdivisions to be 1/4 of what they are now. I don't expect it to make
any difference but if you could please try the patch, at least it would
rule that out.
Well one thing that this patch makes, is much much bigger filesize
(around 30% increase).
Furthermore it really crashes Mapsource. Not even possible to move out
anymore.
After panning around a bit and choosing a well working zoomscale,
Mapsource moves not to the well working one, but out at 1000km
After panning around at 7km just one step before the "critical" 5km
Mapsource crashed completely: Crashlog (mapsourcecrash.txt) is attached.
If there is no huge error in this patch, it was the worst that ever
happened.
Also now Mapsource 6.15.6 shows no more tile and eventually crashes.
mapsource 6.15.6 crashlog is attached too.
Maybe reversing the patch and increasing subdivision size would help?
Cheers,
Mark
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev