GuestDrive class
The guest half of the drive wire: one ext.flutterware.act extension,
every call a transaction — act, settle, observe — whose reply is the whole
bundle. There is deliberately no separate screenshot-then-tap pair to
correlate: two calls against a live app are two moments, and the gap
between them is where computer-use's bugs live.
Calls are serialized on a queue: two drivers interleave as transactions, never as overlapping gestures.
Constructors
- GuestDrive({Drive? drive, GuestInspector? inspector, HumanActions? humanActions})
Properties
- drive → Drive
-
final
- hashCode → int
-
The hash code for this object.
no setterinherited
- humanActions → HumanActions?
-
Wired when the human's taps between tool steps should ride the bundle
as
humanentries; without it the journal stays tool-steps-only.final - inspector → GuestInspector?
-
Wired when the tree rides the bundle; without it
treeis absent and everything else still works.final - runtimeType → Type
-
A representation of the runtime type of the object.
no setterinherited
Methods
-
debugDispatch(
Map< String, String> params) → Future<Map< String, Object?> > - One transaction, without the extension around it.
-
noSuchMethod(
Invocation invocation) → dynamic -
Invoked when a nonexistent method or property is accessed.
inherited
-
registerExtensions(
) → void -
Registers the extension. Call once, before
runApp. -
toString(
) → String -
A string representation of this object.
inherited
Operators
-
operator ==(
Object other) → bool -
The equality operator.
inherited
Static Properties
-
The
navigateverb's registration point. A routing system — the app's own, or a package like router_outlet — sets this to jump straight to a screen; unset,navigaterefuses loudly rather than tap-hunting.getter/setter pair
Constants
- beatMaxSide → const int
- What a beat's picture is capped at, against an agent step's 900. A beat is scanned in a timeline rather than read for fine print, and the cap scales the render, so it bounds the encode and the bytes together.