-
Notifications
You must be signed in to change notification settings - Fork 59
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
Add Info Window #38
Comments
Any news on it? I would really like to have the info windows feature as I really enjoyed using the package so far :) |
+1 for this feature too, it is going to be very useful |
We're not currently using this functionality so it's not getting a ton of attention but would you consider adding in a pull request? Probably the fastest way to getting this in. |
Added in
Or like this:
Documentation to be added soon |
Tested it and it works great. I have one question @husamibrahim. Could you tell me how can I nest a info window inside of a marker so that when I click on a marker it will open an info window? |
may i see the screenshot of this? i cant make this work |
This isn't possible in the current iteration @Baroshem but we can definitely add it. You can open a new issue if you like. |
Please share a reproduction @eskiesirius. You can use https://vite.new/vue. |
@Baroshem Added nesting in
|
@husamibrahim This is just great! Yesterday I managed to create a workaround for the current code to utilize the marker and infowindow like following: <div>
<google-marker :options="options" @click="open = !open"/>
<info-window
v-if="popup && open"
:options="{ ...options, content: popup }"
@closeclick="open = !open"
/>
</div> And today you just added a nested functionality that works even better. I can now utilize the full functionality. Thank you very much! I am really happy that I have selected your library instead of others :) |
It is working now.. it is great! |
@husamibrahim this is great, thank you 🥇 |
Adding the Info Windows feature to this repo is a feature-request for this library. We are happy to accept PR's for this work as there is not immediate demand internally for this feature but we do understand why it might be useful and it will eventually be incorporated.
The text was updated successfully, but these errors were encountered: