RPVisualConsentStep class
The step used for presenting the consent document to the participant
To use a visual consent step, first create a consent document (RPConsentDocument) with at least one section and attach the document to a visual consent step. Put the visual consent step into a Research Package task, and present it with an RPUIOrderedTask.
Constructors
- RPVisualConsentStep(String identifier, RPConsentDocument consentDocument)
Properties
- consentDocument → dynamic
-
The consent document whose sections determine the order and appearance of scenes in the visual consent step.
read-only
- stepWidget → Widget
-
The widget (UI representation) of the step
read-only, override
- hashCode → int
-
The hash code for this object. [...]
read-only, inherited
- identifier → String
-
A unique identifier of the Step. This identifier connects the Step to its result (RPResult) object.
read-only, inherited
- runtimeType → Type
-
A representation of the runtime type of the object.
read-only, inherited
- text ↔ String
-
The text of the Step. Different types of Steps are using the text text differently. [...]
read / write, inherited
- title ↔ String
-
The title text. Different types of Steps are using the title text differently. [...]
read / write, inherited
Methods
-
noSuchMethod(
Invocation invocation) → dynamic -
Invoked when a non-existent method or property is accessed. [...]
inherited
-
toString(
) → String -
Returns a string representation of this object.
inherited
Operators
-
operator ==(
dynamic other) → bool -
The equality operator. [...]
inherited