SidecarOp Type
One asynchronous operation asked of the .NET simulator and not yet answered. It carries its own parameters, which is what lets one reply message serve every operation: the answer names the operation, the table says what that operation was, and the update function works out what to do from the two together. Without them there would be a message type per feature, each carrying the context its own handler happened to need.
Union cases
| Union case | Description |
Full Usage:
OpBuild(top, arraySize)
Parameters:
string
arraySize : int
|
|
|
read everything the snapshot's viewports need - waves over the window, every selected RAM's rows, the panel's signals, the probe, the wanted slices - one operation because it is one promise, in order, over one connection. Carries the snapshot so the completion records what WAS fetched, not what is current by then.
|
|
|
Full Usage:
OpRunForWaves toCycle
Parameters:
int
|
|
Full Usage:
OpStep cycle
Parameters:
int
|
Instance members
| Instance member | Description |
Full Usage:
this.IsOpBuild
Returns: bool
|
|
Full Usage:
this.IsOpFetch
Returns: bool
|
|
Full Usage:
this.IsOpProbe
Returns: bool
|
|
Full Usage:
this.IsOpRunForWaves
Returns: bool
|
|
Full Usage:
this.IsOpStep
Returns: bool
|
|