The default filtering functionality is exposed as an extension. The current filtering implementation works by providing an updated FilteringState after each call to its functions. You can use this filtering state to keep track of filtering state.
optionalstateKey: A way of splitting up commands coming from different controls (model explorer, filters, selection) so the viewer filtering api can know whether to reset its internal state or not
optionalincludeDescendants: Whether to include the descendants of the provided object ids
optionalghost Whether to ghost the rest of the objects
optionalstateKey: A way of splitting up commands coming from different controls (model explorer, filters, selection) so the viewer filtering api can know whether to reset its internal state or not
optionalincludeDescendants: Whether to include the descendants of the provided object ids
optionalghost Whether to ghost the rest of the objects
optionalstateKey: A way of splitting up commands coming from different controls (model explorer, filters, selection) so the viewer filtering api can know whether to reset its internal state or not
optionalincludeDescendants: Whether to include the descendants of the provided object ids
optionalstateKey: A way of splitting up commands coming from different controls (model explorer, filters, selection) so the viewer filtering api can know whether to reset its internal state or not
optionalincludeDescendants: Whether to include the descendants of the provided object ids
optionalghost Whether to ghost the rest of the objects