[r1-dev] Marker only visible after changing initial coordinates

[francisdb]

In my controller I have the following code

$scope.searchLocation = {
        latitude: parseFloat(getParameterByName("latitude")),
        longitude: parseFloat(getParameterByName("longitude"))
};

And my template has this

<marker coords="searchLocation"></marker>

After loading the page the marker is not visible, only after changing the latitude and/or longitude values the marker appears.

Is this a bug or should I do this differently?

[nmccready]

Looking into this now.

[nmccready]

Confirmed bug

[nmccready]

This is related to the chatter in this pull. Look at #83

If we are worried about trying to create items when the map is fully created.. we should use another mechanism >and not timeout. We should chain in a event handler on tilesloaded and do things after that.

Basically the map is not fully rendered yet and the marker's coords were set before the map was ready. You can fix this by setting your scope values when the tilesloaded event is hit. Use the events: {} option to have a handler on tilesloaded. This would work for the time being, and I will see if I can tie it into the directive as well. Originally there was a timeout to delay the marker rendering . However if you doing tons of markers this is really slow.

[nmccready]

I think I will add the timeout back to the marker directive. IE if you need to use alot of markers use the markers directive.

[nmccready]

Fixed with e5f287f

[francisdb]

Just confirming this is fixed