Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

path not being displayed in map #617

Closed
teknofreek opened this issue Jan 25, 2015 · 4 comments
Closed

path not being displayed in map #617

teknofreek opened this issue Jan 25, 2015 · 4 comments

Comments

@teknofreek
Copy link

hi, im using angularjs + ionic framework + leaflet.js. i want to show paths, i followed the paths example code, but the path is just not showing up. i added the modules in the same order as in the example ...the map centers to the given location and also shows markers if i specify there but the paths don't appear, what am i doing wrong?

@MarkAPhillips
Copy link
Contributor

if you are using promises ensure the following - I had this issue today that was driving me nuts e.g.

$scope.paths = {};
$promise.then(function() {

       angular.extend($scope, {
                    paths: {
                        c1: {
                            weight: 2,
                            color: "#ff612f",
                            latlngs: { lat: 1, lng: -2 },
                            radius: 50,
                            type: "circleMarker"
                        }
                    }
                });        
 }

if you exclude the initialisation paths will not be shown - I think this also the case for markers - please can this be documented - thanks

@michaelkrog
Copy link

+1

@nmccready
Copy link
Contributor

This issue was moved to angular-ui/ui-leaflet#44

@nmccready nmccready reopened this Oct 29, 2015
@tombatossals
Copy link
Owner

I'm going to rework&redesign angular-leaflet-directive to be compatible with Leaflet v1.0. It will mantain almost all its functionality, and will be compatible with the current features of the directive, but I must start from a fresh point, so I'm going to close this issue. If you think it must be worked with the new version, please reopen it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants