FusionTablesLayer not reacting properly when 'options.query.from' is changed.

[zavidovych]

// view.html
<button ng-click="ctrl.updateWindData()">Refresh wind</button>
<button ng-click="ctrl.toggleWind()">Toggle wind</button>
<google-map ...>
  <layer type='FusionTablesLayer' options='ctrl.windLayer.options' show='ctrl.windLayer.show'></layer>
</google-map>

//controller.js
function MapCtrl() {
  this.windLayer = {
    show: true,
    options: {
      query: {
        from: 'FUSION_TABLE_ID_1',
        select: 'location'
      }
    }
  }
}

MapCtrl.prototype.toggleWind = function() {
  this.windLayer.show = !this.windLayer.show;
};

MapCtrl.prototype.updateWindData = function() {
  this.windLayer.options.query.from = 'FUSION_TABLE_ID_2';
};

1. When map is loaded initially, data from FUSION_TABLE_ID_1 is shown.
2. Clicking 'Toggle wind' button toggles layer on and off as expected.
3. Clicking 'Refresh wind' turns off the layer instead of loading and showing data from FUSION_TABLE_ID_2.
4. However clicking 'Toggle wind' 2 times (off then on) after clicking 'Refresh wind' does show the data from FUSION_TABLE_ID_2.

Is it possible to make it so that when model (options.query.from) is updated layer would load and show new data automatically without having to turn layer off and on via 'show' attribute?

Sorry if I'm missing something. Thanks!

[nmccready]

This is probably valid. Can you produce a plunkr w/ your issue.

[nmccready]

My guess is this has to do with the watch depth level. Your using the same reference and the watch is probably shallow, a quick fix on your end would be to close your options, modify them and replace the reference.

[nmccready]

https://github.com/nlaplante/angular-google-maps/blob/master/src/coffee/directives/api/models/parent/layer-parent-model.coffee#L22

Looks like the depth is deep. But the comparison if isn't is checking against the reference.. (Self defeating) , it should use _.isEqual .

[nmccready]

Possibly related? #655 @esclapes ?

[esclapes]

@nmccready it is not related. But I have found this issue as well in my use case.

There is limit of 5 FusionTableLayers to be shown in a map at any given moment. Being able to update a layer query would be handy to work around that limit.

I have being testing and going "up the object", and the behaviour is the same changing the where clause, query element and layer element.

Have a look here: http://jsbin.com/yajodayomijo/2/edit?html,js,output