Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

some tiles not refresh after zoom #52

Closed
shihuacai1989 opened this issue Jul 22, 2014 · 13 comments
Closed

some tiles not refresh after zoom #52

shihuacai1989 opened this issue Jul 22, 2014 · 13 comments

Comments

@shihuacai1989
Copy link

the version of osmdroid is 4.3. I run the project on the Samsung t520, which the version of android is 4.4.2
mapView.getController().setZoom(5), then I wait for seconds, some tiles is not show, then i move the map, all tiles show.
someone meet this problems?

2014072201

@kurtzmarc
Copy link
Contributor

Do you have this problem with the OpenStreetMapViewer app? If not, what are you doing differently? Are you using offline tiles?

crankycoder added a commit to crankycoder/MozStumbler that referenced this issue Oct 23, 2014
…etty invasive non-API compatible changes

 * removed slf4j logger from osmdroid and replace it with the mozilla logger
 * Aggressively prune down the osmdroid codebase to just the parts that are essential so that we can properly test components.
 * Fixed some bad exception logging in HttpUtil::get
 * Discarded the LRUMapTileCache::TileRemovedListener as it's never used
 * Removed < GINGERBREAD support from the LRUMapTileCache::remove method
 * Added some comments to recycling ReusableBitmapDrawable instances - I'm pretty sure we *only* use ReusableBitmapDrawable instances
 * Added more warning level logging to see what's going on with download errors in the TileDownloaderDelegate.
 * Removed useless logging message when the SmartFSProvider fails to load anything.
 * Threading has been simplified now so we don't have separate disk IO threads and network download IO threads.
 * We just have IO threads as networking and caching is tightly coupled together within the SmartFSProvider.
 * All threading is actually handled by an ExecutionService within the MapTileModuleProviderBase
 * Dropped MapTileFilesystemProvider as it's no longer used.
 * Dropped MapTileFileStorageProviderBase and adjusted the class inheritance.
 * All error logging now requires either an exception (possibly null) to be passed in as the last argument.
 * Some error logging events have been demoted to just warnings as no actual error has occurred.
 * Removed unused constants
 * changed noisey log level messages to debug
 * bump the size up of the size of the MapTileCache in the abstract TileProvider by 100 tiles.
 * In debug builds - I've added Map and Cover prefixes to the tile overlays so that you can see which tile are actually being used.
 * The BitmapTileSourceBase will now label tiles based on a BuildConfig parameter
 * Swapped out DefaultApacheHttpClient for HttpUrlConnection when downloading tiles

 * I've disabled the handleTile method in the ZoomInLooper as well as
   the ZoomOutLooper so that they no longer do anything.  This forces
   tiles to load from disk or network instead of trying to rescale
   pre-existing tiles and storing/loading them from an LRU cache which
   may evict tiles.

   I believe the bugs in ZoomInLooper and ZoomOutLooper are causing
   the long standing bug in osmdroid listed here:
   osmdroid/osmdroid#52
@secondflying
Copy link

I have the same problem. My problem is that when add another TilesOverlay, then when zoom in or zoom out, the map is incomplete. I move the map then all tile is shown.

@spyhunter99
Copy link
Collaborator

i've noticed that behavior too. maybe need to manually call refresh on secondary tile ovelrays

@secondflying
Copy link

@spyhunter99, do you know how to refresh the secondary tile ovelray manually?

@spyhunter99
Copy link
Collaborator

try mapview.invalidate

@secondflying
Copy link

@spyhunter99 ,I modify the source code, add mapview.invalidate() at the end of DefaultOverlayManager.onDraw() method, and solved my problem, thanks.

@spyhunter99
Copy link
Collaborator

although that solution may work, essentially, it should end up calling the
ondraw method again. It may be better to do an overlay scan and look for
overlays that extend tilesoverlay, then force a redraw on those

On Thu, Jan 28, 2016 at 11:04 PM, secondflying notifications@github.com
wrote:

@spyhunter99 https://github.com/spyhunter99 ,I modify the source code,
add mapview.invalidate() at the end of DefaultOverlayManager.onDraw()
method, and solved my problem, thanks.


Reply to this email directly or view it on GitHub
#52 (comment).

@ThisIsMyWay
Copy link

Is there any solution provided for this problem? Because I propably encountered similar issue and I don't know if I should open new ticket. I described it on stackoverflow. http://stackoverflow.com/questions/35393295/zooming-in-out-some-tiles-not-rendering-osmdroid-offline-maps

@hlaurent
Copy link

Having the same issue with MBTiles layers. I can try to solve this as you describe with a mapview.invalidate but I have a related issue where onZoom is not being fired if you do a double or a 2 finger pinch to zoom.

@spyhunter99
Copy link
Collaborator

please retry with 5.4.1

@spyhunter99
Copy link
Collaborator

#496 related

@spyhunter99
Copy link
Collaborator

please retry with the latest version (after reading that related ticket). it may be related to threading and queue sizes. Since this ticket is now very old with no feedback. I'm going to close it. Reopen or comment back if this is still an issue for you @hlaurent

@RicardoCostaContin
Copy link

same to me using 5.6.5. zoom, then move and have a lot gray area. zoon out and in...and shows.using offline map tiles

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants