Release 1.4.1: a Bonded checkbox in the terminal tables
tests / ubuntu-latest · py3.11 (push) Successful in 54s
tests / ubuntu-latest · py3.13 (push) Successful in 58s
tests / archlinux:latest (push) Successful in 41s
tests / debian:12 (push) Successful in 1m10s
tests / fedora:latest (push) Successful in 42m6s
tests / ubuntu:24.04 (push) Successful in 1m15s
tests / NixOS (FHS wrapper from docs/NIXOS.md) (push) Skipped
Build PCM package / build (push) Successful in 11s
tests / ubuntu-latest · py3.11 (push) Successful in 54s
tests / ubuntu-latest · py3.13 (push) Successful in 58s
tests / archlinux:latest (push) Successful in 41s
tests / debian:12 (push) Successful in 1m10s
tests / fedora:latest (push) Successful in 42m6s
tests / ubuntu:24.04 (push) Successful in 1m15s
tests / NixOS (FHS wrapper from docs/NIXOS.md) (push) Skipped
Build PCM package / build (push) Successful in 11s
The config's per-terminal bonded key becomes editable in the dialog (previously file-only, shown as a text suffix): checked, the terminal's contacts short into one internally joined lug - the total value stays prescribed, the per-contact split is a solve outcome. Same-name rectangle groups seed it checked as before; unchecking one falls back to the per-cell area share, and checking a single-contact terminal gives it an equipotential-lug contact instead of uniform injection. Save config... writes the flag back (removed when unchecked - false is the schema default). With this, every non-structural terminal option (active, values, v_oc, contact layer, bonded, comment) is table-editable. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
@@ -368,12 +368,18 @@ terminal for what-if runs without deleting anything: an unchecked row
|
||||
takes no part in the solve, may leave its value cells blank, and is
|
||||
still saved (as `"active": false`) so it can be re-enabled later — the
|
||||
totals line counts disabled rows. A free-text **Comment** column
|
||||
annotates each terminal and is saved along with it. Rectangles that **share one name
|
||||
become a single *bonded* terminal** — one table row, one total
|
||||
current, and the per-rectangle split is a solve outcome (a multi-pin
|
||||
package whose pins are joined by internal metal: the total draw is
|
||||
known, which pin carries how much is exactly what the solve
|
||||
determines). OK solves;
|
||||
annotates each terminal and is saved along with it. A **Bonded** checkbox per row
|
||||
toggles the lug model (the config's `bonded` key): checked, the
|
||||
terminal's contacts are shorted into one internally joined lug — the
|
||||
total value stays prescribed, the per-contact split is a solve
|
||||
outcome — and a single-contact terminal checked gets an
|
||||
equipotential-lug contact instead of uniform injection. Rectangles
|
||||
that **share one name become a single terminal with Bonded seeded
|
||||
checked** — one table row, one total current, per-rectangle split
|
||||
solved (a multi-pin package whose pins are joined by internal metal:
|
||||
the total draw is known, which pin carries how much is exactly what
|
||||
the solve determines); uncheck it to fall back to the area-share
|
||||
split. OK solves;
|
||||
**Save config…** writes the whole setup to a config file whose name
|
||||
you pick per save (pre-filled with the loaded config, else
|
||||
`fill_res_config.json`) so the values survive between runs — named rectangles are saved as live `rect:NAME`
|
||||
|
||||
Reference in New Issue
Block a user