InstancePort (issie) | Issie

InstancePort Type

Namespace: global
Assembly: Renderer.dll
Parent Module: PortView
Base Type: obj
All Interfaces: IEquatable<InstancePort> , IStructuralEquatable , IComparable<InstancePort> , IComparable , IStructuralComparable

One port of one instance, with everything a waveform needs that the design cannot supply. The field names are prefixed because a record field resolves to the last type declaring one, and the wave simulator is full of ports, widths and names.

Record fields

Record Field	Description
`PortArrayIndex` Full Usage: `PortArrayIndex` Field type: `DriverIndex`	where this port's data lies in the simulation that answered: the step array... Field type: `DriverIndex`
`PortComp` Full Usage: `PortComp` Field type: `ComponentId`	the DESIGN component this is a port of - which, with the instance, names it Field type: `ComponentId`
`PortCompLabel` Full Usage: `PortCompLabel` Field type: `string`	the label on the component the port belongs to Field type: `string`
`PortDisplayName` Full Usage: `PortDisplayName` Field type: `string`	comp.port(w:0), as the selector lists it and the viewer titles it Field type: `string`
`PortDriver` Full Usage: `PortDriver` Field type: `DriverIndex`	...and the driver, which is what a waveform is read from. This is the build's read HANDLE: the fetch quotes it back, and the simulator answers with no lookup by name at all. An input port's is already the array of the output driving it - the simulator's own linker resolved that, crossing sheet boundaries where the net does. Field type: `DriverIndex`
`PortIs` Full Usage: `PortIs` Field type: `PortType`	Field type: `PortType`
`PortLabel` Full Usage: `PortLabel` Field type: `string`	the port's own name, without the component - what the port-selection dialog shows Field type: `string`
`PortNum` Full Usage: `PortNum` Field type: `int`	Field type: `int`
`PortWidth` Full Usage: `PortWidth` Field type: `int`	Field type: `int`