I've encountered a strange issue with tile bitmap caching in Map Suite 4.5.
If I have caching enabled, and I pan the map, I'll sometimes get small gaps in the map where the roads just end, then start again. I've taken a screenshot of what it looks like, which is below:
As you can see almost all of the roads appear to end in this small horizontal area resulting from the pan (that blank area corresponds to the amount I panned to the north). Now the weird thing is, this renders fine for a split second, but then it shows a gap. I believe this is due to the fact that the vector rendering is correct, but the cached image is not, so when it switches to the cached image it starts showing the gap. I could be completely wrong, however, as I'd imagine what the vector renderer displays is the exact same data stored in the subsequent cached tile.
I've found the tile images in question for both breaks in the orange highway, and you can clearly see the gap is present in the cached PNG images.
It's not just the orange highway that is cutoff either, even the individual streets (white) are cut off. After panning around quite a bit, I end up with a ton of broken roads and gaps in the map, which are then cached indefinitely until the cache is manually cleared--resulting in a poor looking map.
The layers I'm rendering are all from the ThinkGeo World Map data disc, and I am using the code provided with said disc to render the different states (with caching enabled). WorldMapKitRenderLayer is the class in question doing the brunt of the work, and I have modified it very little (essentially just turning off some unused layers)
Is this no longer a problem in subsequent versions of Map Suite? Is there a way to fix the caching so the gaps are no longer present?
Any help would be greatly appreciated.
Thanks,
Matt