You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ] bug report => Search github for a similar issue or PR before submitting
[x] feature request => Please check if request is not on the roadmap already https://github.com/primefaces/primeng/wiki/Roadmap
[ ] support request => Please do not submit support request here, instead see http://forum.primefaces.org/viewforum.php?f=35
Current behavior
When creating the GMap component, there is no way to access the internal map object instantaneously. You can sent the map object using a button to take it via template variable .getMap().
Expected behavior
It would be useful to have the map object available through an Output event emitter
What is the motivation / use case for changing the behavior?
There are cases though, when you need access to the map object as soon as possible (ideally, instantaneously), for example for setting the initial position of the map using map.fitBounds(bounds);
The text was updated successfully, but these errors were encountered:
I'm submitting a ... (check one with "x")
Current behavior
When creating the GMap component, there is no way to access the internal map object instantaneously. You can sent the map object using a button to take it via template variable .getMap().
Expected behavior
It would be useful to have the map object available through an Output event emitter
What is the motivation / use case for changing the behavior?
There are cases though, when you need access to the map object as soon as possible (ideally, instantaneously), for example for setting the initial position of the map using map.fitBounds(bounds);
The text was updated successfully, but these errors were encountered: