I've noticed that sometimes a row or column is set on a tile that is outside of the image's bounds. This originates from TileView.computeAndRenderTilesInViewport(): the grid is too large. This affects the Tile.mDestinationRect. Later in Tile.decode(), this same row and column is used to render a tile with mStreamProvider.getStream(). Is there a reason why these non-existing tiles are rendered?
The problem that I'm experiencing is that in my project the tiles are loaded with http requests, and our client's server returns white tiles for invalid coordinates. True, this is just a bad design and the server should return an error or empty stream, but maybe other people have issues with this as well.
Thank you for maintaining this library the way you do and always being quick to answer, I appreciate it.
I've noticed that sometimes a row or column is set on a tile that is outside of the image's bounds. This originates from
TileView.computeAndRenderTilesInViewport(): the grid is too large. This affects theTile.mDestinationRect. Later inTile.decode(), this same row and column is used to render a tile withmStreamProvider.getStream(). Is there a reason why these non-existing tiles are rendered?The problem that I'm experiencing is that in my project the tiles are loaded with http requests, and our client's server returns white tiles for invalid coordinates. True, this is just a bad design and the server should return an error or empty stream, but maybe other people have issues with this as well.
Thank you for maintaining this library the way you do and always being quick to answer, I appreciate it.