Closed wumaolinmaoan closed 3 weeks ago
[!WARNING]
Rate limit exceeded
@wumaolinmaoan has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 8 minutes and 28 seconds before requesting another review.
β How to resolve this issue?
After the wait time has elapsed, a review can be triggered using the `@coderabbitai review` command as a PR comment. Alternatively, push new commits to this PR. We recommend that you space out your commits to avoid hitting the rate limit.π¦ How do rate limits work?
CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our [FAQ](https://coderabbit.ai/docs/faq) for further information.π₯ Commits
Reviewing files that changed from the base of the PR and between 8bef28d88dcc49627b4d5690010cfa9f9e5b0126 and cf2f7f6064bd23fa6cc27ef583de9052c35a9075.
The pull request introduces significant changes to the handling of item visibility and activation across multiple classes in the effects-core package. Key modifications include renaming methods related to visibility management, such as changing showItems
to onEnable
and hideItems
to onDisable
. The visibility checks have been replaced with activity checks, using methods like setActive
instead of setVisible
. These changes affect the CompositionComponent
, VFXItem
, and related classes, streamlining how visibility and activity states are managed throughout the system.
File | Change Summary |
---|---|
packages/effects-core/src/comp-vfx-item.ts |
Renamed showItems to onEnable and hideItems to onDisable . Updated visibility management to use setActive(true/false) instead of setVisible(true/false) . |
packages/effects-core/src/components/component.ts |
Updated isActiveAndEnabled to use this.item.isActive() instead of this.item.getVisible() . Adjusted setVFXItem logic to reflect the new active state checks. |
packages/effects-core/src/composition.ts |
Renamed setVisible to setActive , updating method calls accordingly. Enhanced comments for clarity. |
packages/effects-core/src/plugins/timeline/playables/activation-mixer-playable.ts |
Removed showRendererComponents and hideRendererComponents . Simplified processFrame to directly set boundItem active state based on input detection. |
packages/effects-core/src/plugins/timeline/playables/sub-composition-mixer-playable.ts |
Replaced calls to compositionComponent.showItems() and hideItems() with direct setActive(true/false) calls on compositionComponent.item . |
packages/effects-core/src/vfx-item.ts |
Renamed visible to active , changing access modifier to private . Updated methods to reflect the new active state management (getVisible to isActive , etc.). |
web-packages/imgui-demo/src/object-inspectors/vfx-item-inspector.ts |
Updated visibility checks from activeObject.getVisible() to activeObject.isActive() , aligning GUI interactions with the new method names. |
web-packages/test/unit/src/effects-core/composition/composition.spec.ts |
Changed test assertions from getVisible() to isActive() for item visibility checks, reflecting the updated logic. |
CompositionComponent
class in this PR are related to the main PR as both involve modifications to the CompositionComponent
class, particularly in how properties and methods are structured and utilized.CompositionComponent
class, specifically focusing on handling track bindings, which aligns with the changes in the main PR regarding method updates and internal logic.hitTest
method of the CompositionComponent
class directly relate to the changes made in the main PR, which also involves hit testing logic.Composition
class that affect the end state management, which is relevant to the overall functionality of the CompositionComponent
class in the main PR.π In the realm of effects, we hop and play,
With items active, come what may!
From visible states to active calls,
Our changes echo through the halls.
So letβs celebrate, with joy and cheer,
For a vibrant world, we hold so dear! π
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Summary by CodeRabbit
New Features
setVisible
method for controlling component visibility in theVFXItem
class.Bug Fixes
VFXItem
objects correctly.Documentation
Tests