Further Revit exchange will use the CSV export/import of the Linear plugin instead of Dynamo, as preferred by the internal Revit/CAD steering committee. Mark the Revit documentation as deferred and remove the Dynamo diagnostic scripts, which stay reachable through the tag archive/dynamo-vorueberlegungen. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
40 lines
2.6 KiB
Markdown
40 lines
2.6 KiB
Markdown
# Circuit List Editor Known Limitations
|
|
|
|
- All currently supported Circuit and CircuitDeviceRow editor writes use
|
|
persistent project commands and project-wide toolbar undo/redo, including
|
|
moves, atomic multi-section reorders and explicit renumbering. Undo/redo
|
|
eligibility is restored from server history after a page reload.
|
|
- The project page exposes the paginated revision timeline; the circuit editor
|
|
itself currently exposes only the next eligible Undo/Redo actions.
|
|
- Named and automatic logical project snapshots can be listed and restored
|
|
through the project page with persistent Undo/Redo. Automatic snapshots are
|
|
created every 25 revisions and only their newest 12 entries are retained.
|
|
- Further Revit work is deferred; it will later use the CSV export/import of
|
|
the Linear plugin in Revit, not Dynamo.
|
|
- The Revit/CSV foundation and confirmed initial import are implemented.
|
|
Existing-row assignment, move and detach plus creation of an external-only
|
|
row in an existing or newly created circuit have atomic persistent commands.
|
|
Their API planning and editor UI, follow-up import, conflict review and return
|
|
export are pending.
|
|
- Persistence currently targets local SQLite; PostgreSQL is an architectural option, not an implemented runtime.
|
|
- The global device library supports basic CRUD and copy operations, but has no
|
|
versioning, permissions or controlled synchronization model.
|
|
- Final electrical sizing logic is not implemented yet.
|
|
- No full norm-compliant voltage-drop and protection-dimensioning calculation flow yet.
|
|
- Sorting is view-only until users explicitly apply sorted order.
|
|
- Complete-circuit drag supports one circuit at a time between groups of the
|
|
same category. Cross-category moves and multi-circuit moves across group
|
|
boundaries are intentionally rejected; multi-circuit reorder inside one
|
|
group remains supported.
|
|
- Protection and cable values are planner-owned manual selections. The later
|
|
sizing/warning engine does not yet validate them against load, length or
|
|
voltage-drop rules.
|
|
- Distribution-board `fedFrom` is free text. The print overview derives its
|
|
supply structure and "Σ inkl. unterlagert" only from exact text matches with
|
|
board numbers/names and adds values without an upstream simultaneity factor
|
|
(see `docs/print-view.md`).
|
|
- The print view uses a kbp corporate design derived from logo and
|
|
presentation material. Snapshots do not record an editor, so the cover's
|
|
Planstände list shows the project's current editor for every entry. On screen, long
|
|
board plans are not split into pages; pagination happens in the browser print
|
|
dialog.
|