Open GoogleCodeExporter opened 8 years ago
I think this is fixed by issue 207 which prevents the behaviour you described.
Original comment by neilboyd
on 17 Jan 2012 at 3:58
I have seen this issue and i noticed that i use the 3.0.5 version. But after
changing to the new 3.0.6 jar the issue is still the same.
i call setTileSource(some tileSource)
and while it is still loading (i see some gray areas on the map)
i switch to a different TileSource with setTileSource (via menu entry or
something)
Then i see tiles from the TileSource befor mixed with the current TileSource
Original comment by mirko.ha...@googlemail.com
on 17 Jan 2012 at 4:39
Issue 207 was fixed after the 3.0.6 release.
Original comment by neilboyd
on 18 Jan 2012 at 6:17
[deleted comment]
The changes in the patch of issue207 are allready inside of my version i use...
Original comment by mirko.ha...@googlemail.com
on 18 Jan 2012 at 1:18
I also have the up to date source and still see this problem. I believe the
tiles from the old provider actualy get written into the wrong filesystem cache
area as I can open up the default viewer and see the same bad tiles without
doing the runtime switch after I have done it once in my app.
Original comment by iforpow...@gmail.com
on 18 Jan 2012 at 6:29
Original issue reported on code.google.com by
mirko.ha...@googlemail.com
on 17 Jan 2012 at 2:33