RPUIVisualConsentStep

The UI representation of RPVisualConsentStep

In general, you don’t need to instantiate an visual consent step widget directly. Instead, add an visual consent step to a task and present the task using a task widget. When appropriate, the task widget instantiates the visual consent step widget for the step.

Inheritance

• Object
• DiagnosticableTree
• Widget
• StatefulWidget
• RPUIVisualConsentStep

Constructors

RPUIVisualConsentStep

const RPUIVisualConsentStep({

1. Key? key,
2. required RPVisualConsentStep step,

})

Properties

step

RPVisualConsentStep step

final

Methods

createState

1. @override

RPUIVisualConsentStepState createState()

override

Creates the mutable state for this widget at a given location in the tree.

Subclasses should override this method to return a newly created instance of their associated State subclass:

@override
State<SomeWidget> createState() => _SomeWidgetState();

The framework can call this method multiple times over the lifetime of a StatefulWidget. For example, if the widget is inserted into the tree in multiple locations, the framework will create a separate State object for each location. Similarly, if the widget is removed from the tree and later inserted into the tree again, the framework will call createState again to create a fresh State object, simplifying the lifecycle of State objects.