Skip to content
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

Fix: Stop and dispose all running animations #45

Merged
merged 2 commits into from
Nov 25, 2024

Conversation

TesteurManiak
Copy link
Owner

@TesteurManiak TesteurManiak commented Nov 24, 2024

Fix #43

Similar to #44 but doesn't change the behaviour of cancelling an ongoing animation. Deciding to cancel a running animation when a new one is triggered should be discussed separately, as some users might want to chain animations instead of cancelling it.

EDIT: Added a public method stopAnimations() on the controller to cancel all ongoing animations and a property cancelPreviousAnimations which when set to true will perform a call to stopAnimations() before triggering a new animations.

@TesteurManiak TesteurManiak merged commit 1689e4d into main Nov 25, 2024
1 check passed
@TesteurManiak TesteurManiak deleted the fix/dispose-running-animations branch November 25, 2024 07:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Dispose a map while more than one animateTo is running causes a ticker error
1 participant