Module component_lifecycle 

How a widget takes part in closing its window and components: unsaved work, persistence checkpoints, component close reports and deferred window close.

A widget providing ComponentLifecycle answers for its subtree; the defaults do what an ordinary container did (reach the children), so an override names only what differs.

Traits

ComponentLifecycle

A widget owning components, documents or a window-close policy.

WindowActivation

A presentation can request activation without changing its document or owner.

Functions

checkpoint_components

Checkpoint every component under widget; returns the errors.

close_components

Close every component under widget.

finish_admitted_close

Finish an admitted close under widget.

on_window_close_requested

widget’s answer to an ordinary window close request.

take_component_close_reports

Drain close reports under widget.

take_replacement

The component widget’s own component asked to show in its place.

take_save_status_presentation

Whether the record widget’s own component shows changed durability, which the root has synced with and a frame must present.

take_window_activation_intent

Consume an activation request through the root’s existing capability door.

take_window_close_intent

Whether widget approved a deferred window close.

unsaved_documents

Unsaved external documents under widget.