Struct NodeResponse 

pub struct NodeResponse {
    pub row_rect: Rect,
    pub box_rect: Rect,
    pub toggled: bool,
    pub label: Response,
    pub band: Response,
    pub band_drag_started: bool,
}

What happened to a drawn tree row.

Fields

row_rect: Rect

The whole row rect (for hit publishing / drag-target hit-testing).

box_rect: Rect

The collapse-box rect (for hit publishing).

toggled: bool

The [+]/[-] collapse box was clicked (a pure toggle intent).

label: Response

The label response — the DRAG handle and the hover source. Use .drag_started() / .drag_stopped() to reorder and .hovered() for a text-keyed highlight. For “the row was clicked” use Self::clicked, not this: the label’s rect is only its own text.

band: Response

The whole ROW BAND, sensing clicks BELOW everything drawn in the row. egui hands an overlapped point to the last widget registered there and this one is registered first (UiBuilder::sense), so the collapse box, the label and every control the caller put in add_right still take their own clicks — the band only ever receives what none of them wanted, which is exactly the blank space between them.

It is also the row’s KEYBOARD stop: the label is deliberately not focusable, so a row is one Tab stop and Enter/Space on it reports clicked() here.

It senses DRAG as well as click, and it has to: egui withdraws the click from a press that outlives max_click_duration (0.8 s) or drifts past max_click_dist (6 pt) whether or not the widget senses drag, so a click-only band would go dead under exactly the slow, wobbly press an ordinary hand makes. A caller resolves that press through Self::drag_started, as the history and constraint trees do.

band_drag_started: bool

The BAND’s drag started, and its press did not begin on one of the row’s own controls (the collapse box, anything add_right drew). Read through Self::drag_started.

Implementations

impl NodeResponse

pub fn clicked(&self) -> bool

The ROW was clicked — on its text or anywhere else in its band that no control of its own claimed. This, not label.clicked(), is what “the user picked this row” means: a row is a click target across its whole width, and a label’s rect is only as wide as its text. A click SELECTS the row’s object.

pub fn double_clicked(&self) -> bool

The ROW was double-clicked, over the same area as Self::clicked. A double click OPENS the row’s dialog. egui reports the second press as a click as well, so on this frame Self::clicked is true too: a consumer checks this first.

egui’s TRIPLE click counts. egui numbers a click 3 when the click two before it is under 0.6 s old, and a 3 is not a 2 — so a row clicked once and then double-clicked a moment later would otherwise never open.

impl NodeResponse

pub fn drag_started(&self) -> bool

A press on the row turned into a DRAG — on the label or anywhere else along the band. A pane that reorders by drag arms itself from this; a pane that does not still wants it, because a press egui reclassified as a drag is the click it refused to report, and resolving it is the only way a slow click on a row still opens that row.