-
-
Notifications
You must be signed in to change notification settings - Fork 125
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
Default Autozoom for LIVE Map #148
Comments
Both these enhancement requests would be possible to implement. The reason we don't show the popover for all devices is we have maps with > 50 devices on them; you can imagine the ensuing clutter ;) The "logic" for the topic with the visible popover is "the last message received from the broker upon connecting". |
@jpmens ok, might be viable to have as a configuration option. Additionally, I seem to recall reading somewhere in the documentation about placing user images somewhere. If those are in place is the 'red dot' replaced with the image? |
No, the red dot on the map stays. The image is bled into the popup overlay when a new location is posted on the live map. |
Based on everything I've learned I think ideal for me would be (for the live reload map):
Essentially just a bunch of faces moving around without any other clutter. |
Is it possible to change the default zoom level? edit: found the parameter in functions.js |
It will be fine if we can have autozoom and user images instead red dots |
With no bubbles by default too :) |
I can address this in #284, and even make it configurable. Please add a short list of your ideas there if this is still relevant for you @travisghansen @stefaanbolle @fab33 🙂 |
Closing as stale. |
Is it possible to have the live map default to autozoom?
Also, is it possible to have the popover visible for all devices by default? I currently have 1 point with the popover visible without manually clicking on each point. I'm unsure what the logic is about which is chose on page load. In my case the device with the oldest checkin.
Thanks!
The text was updated successfully, but these errors were encountered: