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

fixed #17876: [bug][Tween] callFunc before updateUntil may be invoked more than once. #18179

Merged
merged 1 commit into from
Jan 14, 2025

Conversation

dumganhar
Copy link
Contributor

Re: #17876

Changelog


Continuous Integration

This pull request:

  • needs automatic test cases check.

    Manual trigger with @cocos-robot run test cases afterward.

  • does not change any runtime related code or build configuration

    If any reviewer thinks the CI checks are needed, please uncheck this option, then close and reopen the issue.


Compatibility Check

This pull request:

  • changes public API, and have ensured backward compatibility with deprecated features.
  • affects platform compatibility, e.g. system version, browser version, platform sdk version, platform toolchain, language version, hardware compatibility etc.
  • affects file structure of the build package or build configuration which requires user project upgrade.
  • introduces breaking changes, please list all changes, affected features and the scope of violation.

@dumganhar dumganhar requested a review from minggo January 13, 2025 08:30
@dumganhar dumganhar changed the title fixed #17876: [bug] callFunc before updateUntil may be invoked more than once. fixed #17876: [bug][Tween] callFunc before updateUntil may be invoked more than once. Jan 13, 2025
Copy link

⚠️ Package size ⤴ 76 bytes, old: 5245887, new: 5245963

Interface Check Report

This pull request does not change any public interfaces !

if (t < 1) {
this._elapsed -= dt;
} else {
this._elapsed = this._startTime + this._duration;
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If t is 1, that indicates the current ActionInterval action is at the end, so its _elapsed should be start time + duration.

isDone (): boolean {
return (this._elapsed >= this._duration);
override isDone (): boolean {
return this._elapsed >= this._duration && !this.isUnknownDuration();
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If an action 's duration is unknown, we should not mark it as DONE until it isn't an unknown duration action.

@minggo minggo merged commit b4c572b into cocos:v3.8.6 Jan 14, 2025
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants