[mkgmap-dev] Last level not empty, why not anymore?
From Felix Hartmann extremecarver at googlemail.com on Wed Aug 12 08:52:10 BST 2009
How comes that the newest mkgmap versions write in information into the last level, instead of leaving it empty? I do think that this prohibits using layers in Mapsource as maps without empty level seem to show up allways on top, instead according to their mapname/mapid. 3 weeks ago this behaviour still was fine. There could be several other problems related to not leaving the last level empty, though I have not found any except the draw priority issues in Mapsource.... I'm not sure since when the problem came up exactly - because I currently got problems accessing my main pc remotely, From around 25 weeks ago to 10 days ago I did not update my mkgmap version because some of my own patches were not compatible with the continue patch and mkgmap would not build anymore. 10 days ago I switched to newest mkgmap version and put in the continue patch - otherwise my mkgmap version is equal to svn. So sometime in between 10 days ago and 25 days ago this behaviour was changed. (so in between rev 1080 and 1124). Felix
- Previous message: [mkgmap-dev] <kein Betreff>
- Next message: [mkgmap-dev] Last level not empty, why not anymore?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list