Each step consists of one or more pages. gtk.assistant.Assistant guides the user
through the pages, and controls the page flow to collect the data needed
for the operation.
gtk.assistant.Assistant handles which buttons to show and to make sensitive based
on page sequence knowledge and the gtk.types.AssistantPageType of each
page in addition to state information like the *completed* and *committed*
page statuses.
gtk.assistant.Assistant is used to represent a complex as a series of steps.
Each step consists of one or more pages. gtk.assistant.Assistant guides the user through the pages, and controls the page flow to collect the data needed for the operation.
gtk.assistant.Assistant handles which buttons to show and to make sensitive based on page sequence knowledge and the gtk.types.AssistantPageType of each page in addition to state information like the *completed* and *committed* page statuses.
If you have a case that doesn’t quite fit in gtk.assistant.Assistants way of handling buttons, you can use the gtk.types.AssistantPageType.Custom page type and handle buttons yourself.
gtk.assistant.Assistant maintains a gtk.assistant_page.AssistantPage object for each added child, which holds additional per-child properties. You obtain the gtk.assistant_page.AssistantPage for a child with gtk.assistant.Assistant.getPage.
GtkAssistant as GtkBuildable
The gtk.assistant.Assistant implementation of the gtk.buildable.Buildable interface exposes the @action_area as internal children with the name “action_area”.
To add pages to an assistant in gtk.builder.Builder, simply add it as a child to the gtk.assistant.Assistant object. If you need to set per-object properties, create a gtk.assistant_page.AssistantPage object explicitly, and set the child widget as a property on it.
CSS nodes
gtk.assistant.Assistant has a single CSS node with the name window and style class .assistant.