Hey @damientopin,
Thank you for the suggestion, I’ve added these to our development request list for future consideration.
Although we don’t have an admin-only option for the overlay, we do have a general setting to control this within our options under Maps > Settings > Advanced > Greedy Gesture Handling. If you enable this option the gesture overlay will be disabled and the standard mouse events will function.
With that said, as mentioned, I can see how more granular control over this would be helpful and we’ll add that in a future version.
In the meantime, if you prefer to switch that off using the setting above, but still want it enabled for the frontend, let me know and I can look into a custom script which enables it only on the frontend for you.
Thread Starter
damdam
(@damientopin)
Hello @dylanauty, thanks for your quick answer!
/// Default behaviors
Being able to disable it makes the map way more comfortable to use. Everyone is used to Google Maps so I don’t understand why this Greed Gesture Handling is the default. Personally I would only add the toggle to control the front-end and set up the rest as such:
– admin: no overlay is needed. At least I don’t see the reason why as we mostly edit those maps on a computer. Having to draw polylines is already combersome enough.
– front-end desktop: no overlay by default with an option to activate.
– front-end mobile: Maybe, overlay by default, with an option to deactivate.
– fullscreen (desktop or mobile): no overlay as it’s not needed.
/// Animation
Also having the overlay animation play 5s the first time and 1s or .5s seconds after that would be less frustrating.
/// Opposite mobile behavior ?
Maybe, on mobile the behavior could be the opposite. One finger to control the map, as normal, and 2 fingers over the map to slide the page, in case the map covers the whole screen and we get stuck. My solution has always been to not cover the screen.
For now, I’ll switch that overlay off for sure.
Hi @damientopin
I definitely see your point, and I think they make a lot of sense, I’ve added all of these to my notes on the feature, and we’ll definitely consider this when we branch out the feature set.
The initial feature was developed by Google and was enabled by default as it was considered the “standard” at the time. We ported that feature to our other engines, to ensure feature parity, but we simply replicated the feature at the time of release.
We found that most people wanted this feature on, for the mobile sites, but we definitely can/should expand on this with more settings.
We’ll be sure to do so, thank you for your ideas, they really are appreciated!
