Struct re_blueprint_tree::BlueprintTree

pub struct BlueprintTree {
    blueprint_tree_scroll_to_item: Option<Item>,
    candidate_drop_parent_container_id: Option<ContainerId>,
    next_candidate_drop_parent_container_id: Option<ContainerId>,
}

Holds the state of the blueprint tree UI.

Fields

blueprint_tree_scroll_to_item: Option<Item>

The item that should be focused on in the blueprint tree.

Set at each frame by Self::tree_ui. This is similar to ViewerContext::focused_item but account for how specifically the blueprint tree should handle the focused item.

candidate_drop_parent_container_id: Option<ContainerId>

Current candidate parent container for the ongoing drop. Should be drawn with special highlight.

See Self::is_candidate_drop_parent_container for details.

next_candidate_drop_parent_container_id: Option<ContainerId>

Candidate parent container to be drawn on next frame.

We double-buffer this value to deal with ordering constraints.

Implementations

impl BlueprintTree

pub fn show( &mut self, ctx: &ViewerContext<'_>, blueprint: &ViewportBlueprint, ui: &mut Ui )

Show the Blueprint section of the left panel based on the current ViewportBlueprint

fn tree_ui( &mut self, ctx: &ViewerContext<'_>, blueprint: &ViewportBlueprint, ui: &mut Ui )

Show the blueprint panel tree view.

fn scroll_to_me_if_needed(&self, ui: &Ui, item: &Item, response: &Response)

Check if the provided item should be scrolled to.

fn default_open_for_data_result(group: &DataResultNode) -> bool

If a group or spaceview has a total of this number of elements, show its subtree by default?

fn contents_ui( &mut self, ctx: &ViewerContext<'_>, blueprint: &ViewportBlueprint, ui: &mut Ui, contents: &Contents, parent_visible: bool )

fn root_container_tree_ui( &mut self, ctx: &ViewerContext<'_>, blueprint: &ViewportBlueprint, ui: &mut Ui )

Display the root container.

The root container is different from other containers in that it cannot be removed or dragged, and it cannot be collapsed, so it’s drawn without a collapsing triangle.

fn container_tree_ui( &mut self, ctx: &ViewerContext<'_>, blueprint: &ViewportBlueprint, ui: &mut Ui, container_id: &ContainerId, parent_visible: bool )

fn space_view_entry_ui( &mut self, ctx: &ViewerContext<'_>, blueprint: &ViewportBlueprint, ui: &mut Ui, space_view_id: &SpaceViewId, container_visible: bool )

fn space_view_entity_hierarchy_ui( &self, ctx: &ViewerContext<'_>, blueprint: &ViewportBlueprint, ui: &mut Ui, query_result: &DataQueryResult, node_or_path: &DataResultNodeOrPath<'_>, space_view: &SpaceViewBlueprint, space_view_visible: bool, projection_mode: bool )

fn add_new_spaceview_button_ui( &self, ctx: &ViewerContext<'_>, blueprint: &ViewportBlueprint, ui: &mut Ui )

Add a button to trigger the addition of a new space view or container.

fn handle_root_container_drag_and_drop_interaction( &mut self, blueprint: &ViewportBlueprint, ui: &Ui, contents: Contents, response: &Response )

fn handle_drag_and_drop_interaction( &mut self, ctx: &ViewerContext<'_>, blueprint: &ViewportBlueprint, ui: &Ui, contents: Contents, response: &Response, body_response: Option<&Response> )

fn handle_empty_space_drag_and_drop_interaction( &mut self, blueprint: &ViewportBlueprint, ui: &Ui, empty_space: Rect )

fn handle_drop_target( &mut self, blueprint: &ViewportBlueprint, ui: &Ui, dragged_item_id: Contents, drop_target: &DropTarget<Contents> )

fn is_candidate_drop_parent_container(&self, container_id: &ContainerId) -> bool

Is the provided container the current candidate parent container for the ongoing drag?

When a drag is in progress, the candidate parent container for the dragged item should be highlighted. Note that this can happen when hovering said container, its direct children, or even the item just after it.

Trait Implementations

impl Default for BlueprintTree

fn default() -> BlueprintTree

Returns the “default value” for a type.