Skip to content

refactor: use end state effect#747

Merged
MakinoharaShoko merged 2 commits intoOpenWebGAL:devfrom
HardyNLee:fix-alpha
Aug 12, 2025
Merged

refactor: use end state effect#747
MakinoharaShoko merged 2 commits intoOpenWebGAL:devfrom
HardyNLee:fix-alpha

Conversation

@HardyNLee
Copy link
Copy Markdown
Contributor

介绍

将 animationObject 中的 getEndFilterEffect 改为 getEndStateEffect,以便获得完整的终态 Effect
removeAnimationWithSetEffect 中,使用 getEndStateEffect 避免强行打断动画时,意外获取了当前态的位置,缩放,旋转,不透明度,模糊属性

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Summary of Changes

Hello @HardyNLee, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refactors the animation system to ensure that the complete end state of an animation is accurately captured and applied, particularly when an animation is interrupted. By transitioning from a filter-specific state retrieval to a comprehensive end-state retrieval, the changes prevent visual inconsistencies and improve the reliability of animation handling.

Highlights

  • Refactoring Animation State Retrieval: The method for retrieving the end state of an animation has been refactored from getEndFilterEffect to getEndStateEffect. This change signifies a shift from only capturing filter effects to capturing the complete final state of an animation, including transform properties like position, scale, rotation, and opacity.
  • Improved Animation Interruption Handling: When an animation is forcibly interrupted (e.g., via removeAnimationWithSetEffect), the system now correctly applies the animation's intended end state. Previously, it might have inadvertently captured and applied the current, intermediate state's position, scale, rotation, opacity, and blur properties, leading to visual glitches. The getEndStateEffect now provides the comprehensive final state, ensuring a smooth transition.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request refactors animation handling to correctly capture the final state by replacing getEndFilterEffect with a more comprehensive getEndStateEffect. My review identifies a critical issue where getEndStateEffect is used without being defined, which would cause a runtime error. I've provided a suggested implementation. I also included a minor suggestion to improve code quality and maintainability in PixiController.ts.

Comment on lines 129 to +133
return {
setStartState,
setEndState,
tickerFunc,
getEndFilterEffect,
getEndStateEffect,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

critical

The getEndStateEffect function is missing. This function is intended to return the final state of the animation as an ITransform object. The code currently references this function but it's not defined, which will cause a runtime error.

Here's a suggested implementation to be placed before the return statement.

  function getEndStateEffect() {
    const endSegment = timeline[timeline.length - 1];
    const { duration, ease, ...transform } = endSegment;
    return transform;
  }

@MakinoharaShoko MakinoharaShoko merged commit 91d8fe7 into OpenWebGAL:dev Aug 12, 2025
1 check passed
KonshinHaoshin pushed a commit to KonshinHaoshin/WebGAL_Eastmount that referenced this pull request Nov 7, 2025
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