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 no tween repeat after stop and restart (Fix #39801) #46310

Closed
wants to merge 0 commits into from

Conversation

jmb462
Copy link
Contributor

@jmb462 jmb462 commented Feb 22, 2021

When a tween was stopped, each interpolation in the list was set to active=false
then, the main active bool was set to false.

When starting the tween again, the main active bool was set to true but not each interpolation in the list : so no repeat was happening.

I've added a for loop to reactivate each interpolation in the interpolates list when start() is called.
Need to seek to 0.0 too because we don't want start() to act as resume().

Edit : Due to an huge git mistake, this PR has been closed and a new PR is open... Sorry for that.

@jmb462 jmb462 requested a review from a team as a code owner February 22, 2021 11:07
@jmb462 jmb462 changed the title Fix no tween repeat after stop and restart (Issue #39801) Fix no tween repeat after stop and restart (Fix #39801) Feb 22, 2021
@Calinou Calinou added bug regression topic:core cherrypick:3.x Considered for cherry-picking into a future 3.x release labels Feb 22, 2021
@Calinou Calinou added this to the 4.0 milestone Feb 22, 2021
@akien-mga akien-mga requested a review from KoBeWi February 24, 2021 10:22
@jmb462 jmb462 closed this Mar 2, 2021
@KoBeWi
Copy link
Member

KoBeWi commented Mar 2, 2021

@jmb462 What happened to this PR?

@jmb462
Copy link
Contributor Author

jmb462 commented Mar 2, 2021

@KoBeWi OMG. I'm so stupid with git...
Need to recode the fix and post a new PR I think... (not in my master branch this time).
I'm really sorry...

@Calinou
Copy link
Member

Calinou commented Mar 3, 2021

@jmb462 No worries! This is why it's considered good practice to always use a branch other than master to open pull requests 🙂
This way, you can update your fork's master branch without impacting pull requests you've already opened.

Edit: Superseded by #46609.

@KoBeWi KoBeWi added the archived label Mar 3, 2021
@akien-mga akien-mga removed the cherrypick:3.x Considered for cherry-picking into a future 3.x release label Mar 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants