Use consistent tile coordinate keys
Tile coordinate keys from ol.tilecoord.toString() are different than the ones from Array.prototype.toString(). Both were used, potentially causing problems. This change makes them consistent and removes the now unnecessary ol.tileCoord.toString() function.
This commit is contained in:
@@ -59,7 +59,6 @@ goog.require('ol.renderer.dom.Map');
|
||||
goog.require('ol.renderer.webgl.Map');
|
||||
goog.require('ol.size');
|
||||
goog.require('ol.structs.PriorityQueue');
|
||||
goog.require('ol.tilecoord');
|
||||
goog.require('ol.vec.Mat4');
|
||||
|
||||
|
||||
@@ -937,7 +936,7 @@ ol.Map.prototype.getTilePriority =
|
||||
if (!frameState || !(tileSourceKey in frameState.wantedTiles)) {
|
||||
return ol.structs.PriorityQueue.DROP;
|
||||
}
|
||||
var coordKey = ol.tilecoord.toString(tile.tileCoord);
|
||||
var coordKey = tile.tileCoord.toString();
|
||||
if (!frameState.wantedTiles[tileSourceKey][coordKey]) {
|
||||
return ol.structs.PriorityQueue.DROP;
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user