v1 + v1 - OK, here's the matched pair - patches for both the splitter
and mkgmap.
With these in place, the mapsource mouse works as expected across all
tile boundaries right up to the outer boundaries. No weird overlap
of tile and overview map. Spot on.
Please could some others give this a test
On 25.01.2010 23:05, Mark Burton wrote:
v1 + v1 - OK, here's the matched pair - patches for both the splitter
and mkgmap.
With these in place, the mapsource mouse works as expected across all
tile boundaries right up to the outer boundaries. No weird overlap
of tile and overview map. Spot on.
Felix,
So we need the splitter even if the tile needs no splitting. Correct?
Maybe my problems with the legend map relate to me not passing it trough
the splitter. Will try out if it makes a difference.
A side effect of using the splitter is that it rounds the boundaries of
the tiles.
So
On 25.01.2010 23:20, Mark Burton wrote:
Felix,
So we need the splitter even if the tile needs no splitting. Correct?
Maybe my problems with the legend map relate to me not passing it trough
the splitter. Will try out if it makes a difference.
A side effect of using the splitter
Felix,
The fix to the splitter plus the patches DID it. However why is the map
flooded if I don't put an natural=land all around it. I'm using =polygons
Have you got any idea on this?
I should think that your little natural=coastline poly on the RHS just
below the middle is causing the
On 25.01.2010 23:38, Mark Burton wrote:
Felix,
The fix to the splitter plus the patches DID it. However why is the map
flooded if I don't put an natural=land all around it. I'm using =polygons
Have you got any idea on this?
I should think that your little natural=coastline poly
