Markers not showing in second (or more) maps about ui-leaflet HOT 4 OPEN

This is happening to me as well, though which map gets the marker seems to be random.

from ui-leaflet.

I figured out some additional details about what is going on here.

On processing the markers for the first map, _addMarkers (markers.js:80) is calling modelChangeInDirective in leafletHelpers.js. This is setting the directive global watchTrap.changeFromDirective to true. modelChangeInDirective uses a timeout to change that value back to false 10ms later, but that is not fast enough to prevent this code:

maybeWatch(leafletScope,'markers', watchOptions, function(newMarkers, oldMarkers){
                        if(watchTrap.changeFromDirective)
                            return;
                        _create(newMarkers, oldMarkers);
                    });

(markers.js:267-271)

...from blocking _create() from being called on the markers for the second map.

I have no idea what modelChangeInDirective is trying to achieve. It seems like maybe it is intended to debounce the watchers or something. Perhaps @nmccready can weigh in.

In any case, for our simple maps that don't do much with events, simply commenting out trapObj[trapField] = true; in leafletHelpers.js:144 doesn't seem to cause any problems and allows the markers to show on multiple maps.

from ui-leaflet.

i had similar problem, but in my project, markers don't show , when i display map second (or more) time.
the problem was solved, when i add unique "group" in parker definition.

let _timeStamp = +new Date();
    vm.markers = users.map((user) => {
        return {  
          lat: user.realLatitude,  
          lng: user.realLongitude,  
          draggable: false,  
          icon: vm.config.local_icons.funskan_icon,  
          group: 'marker_group_${_timeStamp}', // here  
        };  
      });

from ui-leaflet.

Sorry to not provide feedback for so long, but I have long moved on from angular unless working on legacy projects. The main problem boils down to how leafletData is designed. It is a main bottleneck that can have race conditions and lose track of the map and or markers state themselves.

This limitation would require an entire rewrite which at this point is not worth the effort. Main reason being is that I am not using this library for work purposes any longer.

For getting multiple maps to work correctly you're going to want to implement a manager that maps DOM id's to the specific map instance.

An example:

https://github.com/realtymaps/map/blob/master/frontend/map/scripts/services/service.currentMap.coffee

utilized here:

https://github.com/realtymaps/map/blob/57be175fa42dd076520bf6a9c28cf2f6b2953084/frontend/map/scripts/factories/factory.map.coffee

from ui-leaflet.