JoinWiring (issie)

JoinWiring Type

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

What the joins of an array design sheet come to.

Record Field	Description
`Ends` Full Usage: `Ends` Field type: `JoinEnd list`	EVERY end, matched or not, in every copy: which channel each join component is on in each copy of the array. What that is for is naming - a copy's ports are the channels it is actually joined by, and copy 3's carry in is not the one drawn on the sheet. Field type: `JoinEnd list`
`Matched` Full Usage: `Matched` Field type: `(JoinEnd * JoinEnd) list`	A JoinOut end and the JoinIn end taking from it: one wire between two copies. Field type: `(JoinEnd * JoinEnd) list`
`Problems` Full Usage: `Problems` Field type: `ArrayProblem list`	What is wrong with the joins, if anything. The wiring above is still the best reading of them, so a sheet being edited can still be drawn; analyseState is what refuses to simulate. Field type: `ArrayProblem list`
`UnmatchedIn` Full Usage: `UnmatchedIn` Field type: `JoinEnd list`	JoinIn ends no copy supplies. Each becomes an INPUT on the sheet's outline. Field type: `JoinEnd list`
`UnmatchedOut` Full Usage: `UnmatchedOut` Field type: `JoinEnd list`	JoinOut ends no copy takes from. Each becomes an OUTPUT on the sheet's outline. Field type: `JoinEnd list`