- A project keeps connector types: a name, a colour and lines that run
out -> in or back. Made, edited and deleted (once unused) from the
parts list's new Connectors group and a connector dialog.
- "<type> out" and "<type> in" ports: inside a component a pin per line
on the inner side plus a cable pin to pass the whole cable on to a
part inside; on the component's box one port, coloured like its type.
- One cable joins an out port to an in port of the same type; the
compiler joins line by line, forward and back, at every depth. Ports
of different types never join; mismatched cables are pruned.
- Pins can face the other way (the inner pins of ports); the router
takes them out and in from the side they face.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- A bundle or split whose wires all meet one part sits on its pins with a latch, moves with the part, and comes loose when dragged away; Ctrl+G plugs both ends in when it can
- Cable ends take the spacing of the pins they plug into, or a spacing you set
- Each wire of a cable carries a name (S0..S3, Cout), shown on free cable ends and as dimmed names on what they feed
- Bundles get "Attach input panel"; panel rows get a keyboard key, an on colour, space above and up/down order
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
When a target sat level with another wire's source (Y3 next to S2), the
column order counted that as free, and ties went to the leftmost column:
S3 stepped left of S2, its last run shared S2's row, and the overlap pass
pushed it onto a side lane with a jog before the pin. Now a shared row
costs more than a crossing, ties keep top-to-bottom order, and a tidy
route that would still run along another signal goes to the usual router.
Tests: the reported layout, and no shared lines in tidy mode for every
example circuit.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
- Tidy wiring orders all wires entering one column together and lays
them out as one compact staircase a grid step apart, sliding only
within that gap to avoid running along other signals. Separate
bundles into the same part no longer cross each other.
- Lamps and output pins get a pin on the right that carries the same
signal on; labels move above when it is wired.
- AND, OR, XOR, NAND and NOR (built in, examples or your own, detected
from the truth table) take 2 to 16 inputs. The wide version is a
balanced tree of the two-input gate, so transistors count honestly.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Input panel part: rows of switches, buttons and clocks. "Attach input
panel" docks one to a component with a row per free input; it moves
with the component and follows its pins.
- Copies and new pins continue name series (D0 -> D1, A -> B); unnamed
switches, lamps and pins take the name of the component pin they are
wired to.
- Connecting: target pins are ringed, dropping on a part uses its next
free pin, click-then-click works, and "Connect one by one" (W) wires a
selection's pins in turn.
- Tidy wiring option and "Tidy all wires": sorted, evenly spaced columns
per gap, one trunk per signal, fewer crossings.
- Truth table full screen, CSV download, copy as Markdown, current row
highlighted.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Clicking anything opens its settings: swap parts in place (wires stay on
matching pins), clock frequency per clock, keyboard keys for switches and
buttons, lamp/display colours, note sizes, component names on the canvas,
position, unlink all wires, unpack a component, make an independent copy.
- Wires of different signals never share a line: auto routes pick free
columns or detours, remaining clashes go on separate lanes. Crossings drawn
as bow, triangle, bridge, gap or plain.
- Accounts (email + scrypt password, httpOnly session) with two-way project
sync and conflict copies; per-account limits; cross-site writes refused.
- Compatibility suite: a project and both browser-storage layouts from
release a241adc must load and compute identically.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>