-
Notifications
You must be signed in to change notification settings - Fork 1.1k
FAQ
Please also check the website's FAQ list.
If you feel like anything's missing or could be clarified, or if you'd like to add a new Q&A to the FAQ list, please contribute!
All control objects are guaranteed to be augmented with their control methods only when the uiGmapIsReady service's promise has resolved.
Note that the uiGmapGoogleMapApi service/promise does not signal that control objects have been augmented with their control methods. Its purpose is to signal that the Google Maps JS API has been loaded (i.e. that the google.maps global object is available).
Please see the API reference for details on uiGmapIsReady.
When you provide a window directive with a nested template, it currently (AOTW) uses only the first child element from that nested template. See the showWindow method in WindowChildModel, as well as issues #1340 and #1310. This behavior may eventually change so that all child elements are used by the directive.
For now, if you have more than one top-level element in your nested template, place all those elements inside a single div and make that div the only child of your ui-gmap-window directive element.
If rendering starts before elements are fully sized, the google.maps.Map constructor calculates according to the smaller size. This is most commonly the case with a hidden element, e.g. ng-show. To fix this, use ng-if instead, as this will wait to attach to the DOM until the condition is true, which should be after everything has rendered fully.
Note that in some cases the ng-if condition may need to be "disconnected" from whatever flag value signals showing/hiding of the map element. See issue #1395 for a simple example where this was the case.