-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Skip flush in renderAdvanced if the container doesn't have an enabled… #7760
Skip flush in renderAdvanced if the container doesn't have an enabled… #7760
Conversation
… filter or enabled mask
|
But pixijs/packages/display/src/Container.ts Lines 586 to 589 in 7ee2be5
We could also improve the check in |
I suppose that’d be the proper patch.
|
Then the question is: do we move this block in pixijs/packages/display/src/Container.ts Lines 618 to 631 in 7ee2be5
This would be a breaking change probably. |
Hmm, never mind. I see what you're doing here. If there are no filters enabled and no masking is done, we could do an early return right? |
We could also move the flushes out of |
If all filters and the mask are disabled, the container could be rendered non-advanced and should not trigger flushes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice one. Any reason for being in draft?
I wasn't sure if this is the best solution. I'd prefer to do the flushing in the filter/mask system instead of in Container. |
There were two mistakes in my code:
This check is very long and ugly. We should really let the mask/filter system do the flushing. |
Description of change
I think we can skip the flushes in
renderAdvanced
if the container doesn't have an enabled filter or enabled mask.Pre-Merge Checklist
npm run lint
)npm run test
)