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
{{ message }}
This repository has been archived by the owner on Feb 6, 2024. It is now read-only.
There are frequently multiple events at the same geographic location, and we'd like to support being able to select each one. Additionally, at further-out zoom levels markers that are geographically close to each other become too close to easily select a single one.
The suggestion from @lederer is that tapping on the map marker should cycle through any markers in the same stack, as should swiping on the popup card at the bottom of the map, with dots on the popup to indicate that it is swipe-able.
The text was updated successfully, but these errors were encountered:
flibbertigibbet
changed the title
Allowing selecting events at the same destination from the Events & Destinations maps
Allowing selecting events at the same destination from the Events map
May 16, 2018
@maurizi is the swiping action for the cards all that's left to do on this one? There's in-built marker cycling working on marker tap, right? If so, we could either update the title here, or close this out for a new issue for swipe-able popup cards.
The z-index of tapping on different markers isn't quite there (I'd think we'd always want the marker "stack" to appear blue when one is selected), but may perhaps be good enough.
There are frequently multiple events at the same geographic location, and we'd like to support being able to select each one.
Additionally, at further-out zoom levels markers that are geographically close to each other become too close to easily select a single one.The suggestion from @lederer is that tapping on the map marker should cycle through any markers in the same stack, as should swiping on the popup card at the bottom of the map, with dots on the popup to indicate that it is swipe-able.
The text was updated successfully, but these errors were encountered: