Hide unresolved objects when owner filters are active on the Scene Explorer#337
Hide unresolved objects when owner filters are active on the Scene Explorer#337gwigz wants to merge 1 commit into
Conversation
With an owner filter active and Full Region Coverage disabled, camming
around streams new objects in whose ObjectProperties reply hasn't landed
yet. The predicate deliberately let those rows pass ("can't judge what it
doesn't know"), so every newly loaded object leaked into the filtered
list regardless of owner, and child prims of an already-rejected linkset
kept the folder visible the same way. Flag filters (e.g. Light) use local
object data, which is why they were unaffected.
Fail the owner clause instead while props are unresolved. The props fetch
is already queued when a row is built, and applying the reply dirties the
row's filter state, so matching rows appear as their ownership resolves.
Fixes AlchemyViewer#335
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
gwigz
force-pushed
the
gwigz/scene-explorer-owner-filter
branch
from
1fee7ed to
d9fd88e
Compare
|
Warning Review limit reached
Next review available in: 58 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
With an owner filter active and Full Region Coverage disabled, camming around streams new objects in whose
ObjectPropertiesreply hasn't landed yet. The predicate deliberately let those rows pass ("can't judge what it doesn't know"), so every newly loaded object leaked into the filtered list regardless of owner, and child prims of an already-rejected linkset kept the folder visible the same way. Flag filters (e.g. Light) use local object data, which is why they were unaffected.Fail the owner clause instead while props are unresolved. The props fetch is already queued when a row is built, and applying the reply dirties the row's filter state, so matching rows appear as their ownership resolves.
Fixes #335