Mike Trinder comments

Results 4 comments of


                                            Mike Trinder

Async layer Image Tiles never generate 'loadstart' events if draw() is called again before getURLasync() returns the first time

I should add, this behaviour is new to v2.12

Async layer Image Tiles never generate 'loadstart' events if draw() is called again before getURLasync() returns the first time

Aha - found why .draw() gets called twice: in Map.js, setBaseLayer() first calls this.baseLayer.setVisiblity(true) at line 1233 (which calls redraw() on the Layer) then it later calls this.setCenter(center, newZoom, false,...

Async layer Image Tiles never generate 'loadstart' events if draw() is called again before getURLasync() returns the first time

OK - I can see how the TileManager might help by making sure draw() is only called once when shifting baseLayers but it doesn't address the logic error in Tile/Image.js...

Async layer Image Tiles never generate 'loadstart' events if draw() is called again before getURLasync() returns the first time

Sorry - been on other projects. Yes. Using a closure is the only correct solution to async stuff. And your solution tries to ensure both the reload and load events...