Reduced version of Component: id, type and label are all a simulation needs. A custom component's port names and instance parameter bindings ride inside TypeS (CustomComponentType.InputLabels/OutputLabels/ParameterBindings), where port number n is by definition index n of the label list - so port names are never duplicated here. The array settings of an ARRAY COMPONENT; absent on an ordinary sheet. An array component is a sheet whose hardware is `Copies` copies of what is drawn on it, one per value of the loop variable. What joins the copies to each other and to the outside is the array IO components - see ComponentType's BusOut, MuxOut, JoinOut and JoinIn. Copies is a plain integer and deliberately NOT a parameter expression. It fixes how many copies there are, and so fixes the ports of every instance of this sheet: an array component has ONE signature per set of bindings, exactly as any other sheet does. Making it an expression would make a sheet's port LIST depend on who instantiated it, which nothing else in Issie has to cope with. Widths remain parameterisable as they are everywhere else.

Type to specify the origin of a custom component

F# data describing the contents of a single schematic sheet.

JSComponent mapped to F# record. Id uniquely identifies the component within a sheet. Label is optional descriptor displayed on schematic.

JSConnection mapped to F# record. Id uniquely identifies connection globally and is used by library.

Value set to None if the connection width could not be inferred.

Keeps track of what cursor to show

Name identifies the LoadedComponent used. The labels define legends on symbol designating inputs or outputs: and are the names of the Input or Output components of the CC sheet. Label strings are unique per CustomComponent. Label position in list determines inputPortNumber or outputPortNumber of label. Multiple CustomComponent instances are differentiated by Component data.

Holds possible directions to sort ports. HLP23: AUTHOR dgs119

Represents the sides of a component

Colors to highlight components Case name is used as HTML color name. See JSHelpers.getColorString lots of colors can be added, see https://www.w3schools.com/colors/colors_names.asp The Text() method converts it to the correct HTML string Where speed matters the color must be added as a case in the match statement

Messages sent from draw block

Type capturing global key press information TODO: use this consistently, with global key listener, throughout Issie.

Static data describing a schematic sheet loaded as a custom component. Every sheet is always identified with a file from which it is loaded/saved. Name is human readable (and is the filename - without extension) and identifies sheet. File path is the sheet directory and name (with extension). InputLabels, OutputLabels are the I/O connections. The I/O connection integers are bus widths. The I/O connection strings are human readable. The strings are guaranteed to be unique in the I/O connection list. I.e. An input label may be the same as an output label, but two input (or output) labels cannot be the same. The position in the I/O connections list is important as it implicitly indicates the port number. For example, the first element in the InputLabels list is related to the Component's Port with PortNumber 0. Two instances of a loaded component have the same LoadedComponent data.

Note that any memory addresses which have not been explicitly set when printing out memory data.

 Option of this qualifies NBitsXOr to allow many different components
 None => Xor
 TODO to reduce technical debt: 
     Rename NbitsXor as NBitsCustom, put all the Nbits ops into this D.U.
     Change catalog entries for all NBits ops to use NBitsCustom, alter load to remain compatibility.

Specify the type of a port in a Component.

Type for an open project which represents a complete design. ProjectPath is directory containing project files. OpenFileName is name of file from which current schematic sheet is loaded/saved, without extension or path LoadedComponents contains the list of schematic sheets, each as a component, one per sheet.

reduced version of CanvasState for electrical comparison, all geometry removed, components ordered

Represents the rotation of a symbol in degrees, Degree0 is the default symbol rotation. Angle is anticlockwise

Stores the rotation and the flip of the symbol, flipped false by default

Info saved by Wave Sim. This info is not necessarilu uptodate with deletions or additions in the Diagram. The wavesim code processing this will not fail if non-existent nets are referenced.

Info regarding sheet saved in the .dgm file

A simulator's handle for reading one signal: dense within one build, meaningless outside it, and issued by whichever simulator is running. Never stored in the model. The renderer asks the simulator to turn SignalIds into handles after each build and quotes handles back when reading data. Keeping it distinct from SignalId is what stops a handle from one simulation being used to read another - which is exactly the mistake an exposed SimArrayIndex makes possible.

The stable NAME of a signal: which port of which component of which instance. This is WaveIndexT without SimArrayIndex, and that omission is the point. SimArrayIndex is a step-array index handed out by one build of one simulation and means nothing outside it, which is why a selection has to be re-resolved by the other three fields whenever the simulation is rebuilt. A SignalId survives a rebuild by construction, so it is what the model should hold.

Bumped by every simulation build. Every cached entry and every reply in flight carries the epoch it belongs to, so an answer from a superseded build is discarded rather than displayed.

Reduced version of Connection: two endpoints, each a component id and a port NUMBER (output-side number at the source, input-side number at the destination).

A whole design: the sheets and which one is the top.

One sheet of a design. Sheet IO *order* is not carried (in Issie it derives from component geometry, which is gone): the receiving side recovers ordering from any instance's TypeS labels, and the top sheet needs none.

Uniquely identifies a wave by the component it comes from, and the port on which that wave is from. Two waves can be identical but have a different index (e.g. a wave with PortType Input must be driven by another wave of PortType Output).

One saved waveform: a component named by the LABELS of the custom component instances entered to reach it, then its own label, and which of its ports. Not ids and not array indices, because this is written to a file and read back against a design that has been edited since. See `WavePath.fs`, which resolves it both ways. The field names are prefixed because F# resolves an unannotated record field to the last type declaring it, and `PortType`/`PortNumber` are `WaveIndexT`'s.

This width is for wire displaying, >8 buswires displayed with 8px thickness. Actual size stored in Port type

Documents user circuit error found during connection width inference

unconfigured replaces Some -1, Error replaces None, Configured of int replaces Some (positive int)

Position on SVG canvas Positions can be added, subtracted, scaled using overloaded +,-, * operators currently these custom operators are not used in Issie - they should be!