From e9fb83d4ee3b24350994e736f3ffce6204fe8069 Mon Sep 17 00:00:00 2001 From: Tim Schaub Date: Mon, 18 Feb 2013 11:58:43 -0700 Subject: [PATCH] Use post render frame for tile pruning We should discuss whether post render functions must be run after each render frame or not. If these can be run after multiple render frames, it would make sense to increase the timeout. As it is, it looks like post render functions are run for every render. Hard to see what the benefit is in this case. --- src/ol/renderer/canvas/canvasvectorlayerrenderer.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/ol/renderer/canvas/canvasvectorlayerrenderer.js b/src/ol/renderer/canvas/canvasvectorlayerrenderer.js index 6e7a4f4414..da1c1f64b6 100644 --- a/src/ol/renderer/canvas/canvasvectorlayerrenderer.js +++ b/src/ol/renderer/canvas/canvasvectorlayerrenderer.js @@ -334,7 +334,7 @@ ol.renderer.canvas.VectorLayer.prototype.renderFrame = this.renderedExtent_ = tileRangeExtent; if (!this.pendingCachePrune_) { this.pendingCachePrune_ = true; - goog.global.setTimeout(goog.bind(this.pruneTileCache_, this), 0); + frameState.postRenderFunctions.push(goog.bind(this.pruneTileCache_, this)); } };