return sheet with all latters capitalised

The waves to offer on the schematic's right-click menu for the component clicked on: none unless a wave simulation is running and holds exactly one copy of that component.

The waves to show when a wave simulation starts with nothing chosen. An empty viewer is never what the user wants: it makes the first thing they see after pressing Start a sentence telling them to press a different button. First choice is the simulated top sheet's own ports - inputs, then outputs, then Viewers. They are the signals every design has and the ones a beginner came to look at. An access path is empty exactly for components that are not inside any custom component instance, which is how "on the top sheet" is decided. A top sheet can have no ports at all: a whole CPU is often a ROM, a RAM and a couple of subsystem instances, wired to each other and to nothing outside. The `3cpu` demo's `eep1` is exactly that. Falling back to Viewers **anywhere in the design** answers it, because a Viewer is placed for one reason only - somebody wanted to watch that net - so wherever they are, they are the signals the author of the design thought were worth looking at.

The custom component instance a component sits directly inside, if any. An access path is ordered from the root of the simulation, so its last element is the instance the component is immediately within.

Get names for waves that are from Input ports TODO: unify this with DrawBlock and widthInferror logic

Get port names for waves that are from Input ports. Appended to comp.Label

Get name for a wave. Names are generated from component label, port name, and bit width of wave.

Get names for waves that are from Output ports TODO: unify this with DrawBlock and widthInferror logic

Get port names for waves that are from Output ports Appended to comp.Label

Make Wave for each component and port on sheet

sheet.component.port, which is what a waveform is called. The SHEET is named, not the instance of it: which instance a waveform belongs to is said by where its row sits in the selector and by the combo box beside it, so a name carrying the instance as well said the same thing twice - and said it as a path of labels nobody asked to read. Where that leaves two waveforms with one name, the viewer disambiguates them on hover.

What to write beside the cursor for the wire it is resting on: the signal's name and its value at `cycle`. None when the simulation cannot answer - the wire is on a sheet it holds more than one copy of, carries no wave of its own, or has not been simulated as far as this cycle. getName, not nameWithSheet: the waveform viewer prefixes the sheet because its rows are drawn away from the design and come from all over it, so a bare "Q" there could be any of them. Here the label is on the wire, on the sheet the user is looking at, and the sheet name is the one thing the position already says. It is also the longest part of the name, on a label that has to fit beside the pointer without covering the circuit.

Modal that, when active, shows the ports of one component picked on the schematic, which of them are displayed as waveforms, and allows that to be changed. Opened from the right-click menu on that component.

Button to activate RAM selection modal.

Modal that, when active, allows users to select RAMs to view their contents.

Button to activate wave selection modal

Toggle if a RAM's contents is selected for viewing. The selection is read from the model the update is applied to, not from the one this element was rendered with, so that a change made between the two is not undone here.

The signal a wire of the open sheet carries, as an index into a simulation's waves. A wire is driven by one output port, so the wire's value is that port's. Which copy of the port depends on how many times the open sheet is instantiated in the design being simulated: with more than one there is no single answer, so none is given - the same rule wavesOfComponent applies to the schematic's right-click menu.

The value of one wave at one cycle, written as the waveform viewer's value column writes it. The step index wraps: the step simulator uses its data arrays as a circular buffer, so a long step simulation is holding only the last MaxArraySize cycles. The waveform simulator does not wrap - its array is sized for the whole run - so there the modulo does nothing.

The waves to offer for one component on the canvas, and the number of copies of that component the simulation holds. A component in a sheet instantiated more than once has one copy per instantiation, and none of them is offered.

Choose waves for a wave simulation that has none. Applied only when the user has selected nothing at all - no waves and no RAMs - so a deliberately pared-down selection is never added to, and a selection saved with the sheet is never overridden.