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 Sep 26, 2022. It is now read-only.
Currently there is one event which fires inside the setBearing function. In the case of the touchRotate feature, this event fires repeatedly making it hard to react to the event with a single decisive response since it is harder to know when the rotation has completed.
This request for feature is:
Have multiple rotate related events including rotateStart, rotateMove, rotateEnd which fire when the map is being rotated as opposed to just the one event which fires at the end of the setBearing function call.
The text was updated successfully, but these errors were encountered:
That sounds like a nice idea, rotateMove would probably just be "rotate" though. Also, you could use a throttle / debounce function too, depending on what you are trying to achieve
True, a throttle / debounce approach would totally work. It would just be really nice to not have to do that and just let the rotation actions dictate the end. Thanks for considering!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently there is one event which fires inside the setBearing function. In the case of the touchRotate feature, this event fires repeatedly making it hard to react to the event with a single decisive response since it is harder to know when the rotation has completed.
This request for feature is:
Have multiple rotate related events including rotateStart, rotateMove, rotateEnd which fire when the map is being rotated as opposed to just the one event which fires at the end of the setBearing function call.
The text was updated successfully, but these errors were encountered: