Can't move a point where a connection touches an element in various diagrams #33

Open
opened 2026-09-13 16:42:36 +00:00 by sorokin.oleg.edu · 5 comments
Owner

You can't move the point where a connection arrow touches (enters) an element in OA diagrams. But in SA diagrams you can (by moving ports)
The same issue is true for State Machine diagrams also
Maybe this issue is present in other diagram types, but I am not sure
This needs to be fixed. The user should be able to move this "point", just like he can move element ports in SA diagrams

You can't move the point where a connection arrow touches (enters) an element in OA diagrams. But in SA diagrams you can (by moving ports) The same issue is true for State Machine diagrams also Maybe this issue is present in other diagram types, but I am not sure This needs to be fixed. The user should be able to move this "point", just like he can move element ports in SA diagrams
Collaborator

Codex-ytr83r/root claims the connection attachment-point editing outcome. Remote repository sorokin.oleg.edu/ARCADIA-Studio; distinct work branch codex/edge-anchors-ytr83r-20260922 starts from published ordinary/Text3f9e6a18af96b5cd10940da4093be8da28b9c835. No existing claim appears in #33. Initial scope: inspect ordinary OA/SA routing and state-machine endpoint gestures, distinguish visual attachment placement from semantic reconnection, and audit applicability to Process/Scenario rather than assume the same gesture fits every notation.

Acceptance: an engineer can deliberately reposition a connection attachment on its existing element boundary, see the actual preview, cancel safely, and commit one undoable layout change without changing semantic endpoints; independent Saved views remain isolated, source/API roundtrips retain placement, and actual native editing/save/reopen is verified. Contract, representation restrictions and parity must be resolved before adopting schema changes. Existing SA semantic-port movement must keep working. This includes implementation and validation, not only a design note.

Partition: no takeover of Codex-956atf's #16 resize/port-capacity policy or #27 integration ownership; no auto-arrange optimization (#32), general multi-selection (#29), or unrelated Text/transition work. State bends #23 are inspected as an existing interaction seam, not silently claimed as completed. I will report shared interface impacts before overlapping edits; all handoff code/evidence will be pushed because peers are on separate machines. Linux remains user-paused.

Codex-ytr83r/root claims the connection attachment-point editing outcome. Remote repository sorokin.oleg.edu/ARCADIA-Studio; distinct work branch codex/edge-anchors-ytr83r-20260922 starts from published ordinary/Text3f9e6a18af96b5cd10940da4093be8da28b9c835. No existing claim appears in #33. Initial scope: inspect ordinary OA/SA routing and state-machine endpoint gestures, distinguish visual attachment placement from semantic reconnection, and audit applicability to Process/Scenario rather than assume the same gesture fits every notation. Acceptance: an engineer can deliberately reposition a connection attachment on its existing element boundary, see the actual preview, cancel safely, and commit one undoable layout change without changing semantic endpoints; independent Saved views remain isolated, source/API roundtrips retain placement, and actual native editing/save/reopen is verified. Contract, representation restrictions and parity must be resolved before adopting schema changes. Existing SA semantic-port movement must keep working. This includes implementation and validation, not only a design note. Partition: no takeover of Codex-956atf's #16 resize/port-capacity policy or #27 integration ownership; no auto-arrange optimization (#32), general multi-selection (#29), or unrelated Text/transition work. State bends #23 are inspected as an existing interaction seam, not silently claimed as completed. I will report shared interface impacts before overlapping edits; all handoff code/evidence will be pushed because peers are on separate machines. Linux remains user-paused.
Collaborator

Codex-ytr83r/root — inspected exact3f9 ordinary/State/Process/Scenario routing, with independent maps and a contract critic. Implementation boundary for #33: add optional source_attachment/target_attachment {side, offset} to each view's EdgeRoute; no semantic endpoint/port identity changes. Absent means automatic; authored fractions follow projected owner bounds and survive move/resize/reconnect as edge-end presentation. Real semantic ports remain authoritative; folded promotion suspends authored routing. Shared contour geometry will account for round/diamond/bar/X state symbols, and coincident self ends must route without panic. State's existing semantic reconnect remains distinct from an explicitly labelled attachment-adjustment action. Reset one attachment preserves bends/label/opposite end; Reset routing clears the whole route.

Shared interface impact: core model/routing/validation/source defaults + REST/source docs; ordinary diagram.rs/route_edit.rs/app route handler/menu; State canvas/edit/app. #16 owner: this does not modify port-capacity, owner sizing or resize policies, but touches canvas hit precedence/preview and must be composed carefully with your resize work. #27 owner: branch remains based on3f9, separate from Scenario b10/14e and transition lifecycle d0b7c; these are not yet a tested union.

Applicability audit: Process topology is generated card/gutter routing with qualified endpoint addresses and needs its own authored-layout contract; Scenario tips are constrained by lifelines, activation and lifecycle/time notation. These will not be claimed fixed by ordinary/State EdgeRoute support. This checkpoint is a design/ownership handoff, not a completion claim.

Codex-ytr83r/root — inspected exact3f9 ordinary/State/Process/Scenario routing, with independent maps and a contract critic. Implementation boundary for #33: add optional source_attachment/target_attachment {side, offset} to each view's EdgeRoute; no semantic endpoint/port identity changes. Absent means automatic; authored fractions follow projected owner bounds and survive move/resize/reconnect as edge-end presentation. Real semantic ports remain authoritative; folded promotion suspends authored routing. Shared contour geometry will account for round/diamond/bar/X state symbols, and coincident self ends must route without panic. State's existing semantic reconnect remains distinct from an explicitly labelled attachment-adjustment action. Reset one attachment preserves bends/label/opposite end; Reset routing clears the whole route. Shared interface impact: core model/routing/validation/source defaults + REST/source docs; ordinary diagram.rs/route_edit.rs/app route handler/menu; State canvas/edit/app. #16 owner: this does not modify port-capacity, owner sizing or resize policies, but touches canvas hit precedence/preview and must be composed carefully with your resize work. #27 owner: branch remains based on3f9, separate from Scenario b10/14e and transition lifecycle d0b7c; these are not yet a tested union. Applicability audit: Process topology is generated card/gutter routing with qualified endpoint addresses and needs its own authored-layout contract; Scenario tips are constrained by lifelines, activation and lifecycle/time notation. These will not be claimed fixed by ordinary/State EdgeRoute support. This checkpoint is a design/ownership handoff, not a completion claim.
Collaborator

Codex-ytr83r/root checkpoint: source candidate 3aa80de89c is pushed and remote-ref verified on codex/edge-anchors-ytr83r-20260922, based on ordinary/Text3f9. Contract, alternatives and limits: harness/edge-attachments-20260922.md at that commit; native fixture/plan: harness/experiments/edge-attachments-20260922/. Ordinary and State per-view attachment editing, per-end reset/history/source/API parity, contour geometry, cancellation and semantic Port precedence are implemented. Valid Item traces now follow actual visible Port anchors even when their projection omits Port IDs. Process/Scenario applicability remains outside this contract as recorded in1023.

Exact clean3aa80de Windows workspace gate has passed1,819 tests,0failed,7ignored across61 suites and strict workspace all-target Clippy. Independent audit confirmed all four workspace packages compiled from the candidate checkout, new-test membership, log/count agreement and unchanged2,749 tracked input inventory. The prior frozen79cc gate correctly failed the tiny-symbol overshoot regression; correction clamps side-intent measurement to the bounds, retaining the original oracle. Failed attempts are preserved locally. Matching GUI/CLI/evaluator builds are running; native editing/save/reopen acceptance and portable raw evidence publication remain pending. Current verification receipts are local-only, so this is a published source checkpoint, not a completed handoff or integration/release claim. Linux remains user-paused; #16 and #27 ownership unchanged.

Codex-ytr83r/root checkpoint: source candidate 3aa80de89c5b79200286926781e8f3a192bc61f4 is pushed and remote-ref verified on codex/edge-anchors-ytr83r-20260922, based on ordinary/Text3f9. Contract, alternatives and limits: harness/edge-attachments-20260922.md at that commit; native fixture/plan: harness/experiments/edge-attachments-20260922/. Ordinary and State per-view attachment editing, per-end reset/history/source/API parity, contour geometry, cancellation and semantic Port precedence are implemented. Valid Item traces now follow actual visible Port anchors even when their projection omits Port IDs. Process/Scenario applicability remains outside this contract as recorded in1023. Exact clean3aa80de Windows workspace gate has passed1,819 tests,0failed,7ignored across61 suites and strict workspace all-target Clippy. Independent audit confirmed all four workspace packages compiled from the candidate checkout, new-test membership, log/count agreement and unchanged2,749 tracked input inventory. The prior frozen79cc gate correctly failed the tiny-symbol overshoot regression; correction clamps side-intent measurement to the bounds, retaining the original oracle. Failed attempts are preserved locally. Matching GUI/CLI/evaluator builds are running; native editing/save/reopen acceptance and portable raw evidence publication remain pending. Current verification receipts are local-only, so this is a published source checkpoint, not a completed handoff or integration/release claim. Linux remains user-paused; #16 and #27 ownership unchanged.
Collaborator

Codex-ytr83r/root checkpoint: native Windows testing of3aa exposed a real immediate post-menu Escape defect in State attachment mode. The correction is pushed as53d01a3d4451b94792986f2dfac56f6f04e111a4 on codex/edge-anchors-escape-ytr83r-20260923 (descends from3aa). Mounted UI event regressions,1,194 desktop tests, strict desktop all-target Clippy and GUI build pass. In a separately staged corrected executable, immediate Escape now returns both source and target attachment modes to Select without a canvas click; combined cancellation save is exact baseline. Edit/Undo/Redo and fresh-process reopen/save are exact complete-Project checks, both processes close normally exit0 with empty logs.

Original broader OA/State native evidence includes independent saved views, per-end reset, curved/diamond symbols, semantic-port precedence and valid reconnect/undo. Four pixel-offset attempts and an invalid reconnect-to-Choice test plan are preserved as failures; the valid reconnect-to-Final was separately predeclared. A shared build-output replacement interrupted one original-run preflight; original staged application remained unchanged and the incident is explicitly recorded, without claiming continuous whole-run immutability. Corrected stage avoids that shared-output binding.

Portable raw evidence and independent final review are being assembled for publication; they are currently local-only. This is a source/validation checkpoint, not yet the final peer-consumable evidence handoff or an integration claim. #16/#27 ownership and Linux pause remain unchanged.

Codex-ytr83r/root checkpoint: native Windows testing of3aa exposed a real immediate post-menu Escape defect in State attachment mode. The correction is pushed as53d01a3d4451b94792986f2dfac56f6f04e111a4 on codex/edge-anchors-escape-ytr83r-20260923 (descends from3aa). Mounted UI event regressions,1,194 desktop tests, strict desktop all-target Clippy and GUI build pass. In a separately staged corrected executable, immediate Escape now returns both source and target attachment modes to Select without a canvas click; combined cancellation save is exact baseline. Edit/Undo/Redo and fresh-process reopen/save are exact complete-Project checks, both processes close normally exit0 with empty logs. Original broader OA/State native evidence includes independent saved views, per-end reset, curved/diamond symbols, semantic-port precedence and valid reconnect/undo. Four pixel-offset attempts and an invalid reconnect-to-Choice test plan are preserved as failures; the valid reconnect-to-Final was separately predeclared. A shared build-output replacement interrupted one original-run preflight; original staged application remained unchanged and the incident is explicitly recorded, without claiming continuous whole-run immutability. Corrected stage avoids that shared-output binding. Portable raw evidence and independent final review are being assembled for publication; they are currently local-only. This is a source/validation checkpoint, not yet the final peer-consumable evidence handoff or an integration claim. #16/#27 ownership and Linux pause remain unchanged.
Collaborator

Codex-ytr83r/root — published ordinary/State attachment contribution and complete portable evidence handoff.

Source: 53d01a3, branch codex/edge-anchors-escape-ytr83r-20260923. Ordered commits above ordinary/Text base 3f9e6a18: 79cc9d5 → 3aa80de → 53d01a3. Importing only the last Escape commit is insufficient. Per-view source/target attachment editing, per-end reset, semantic-port precedence, rounded/diamond/circle contours, guarded cancellation and exact history/source/API persistence are implemented. State semantic reconnect remains separately labelled.

Evidence: Windows validation and portable archives at bb7edfb, on codex/behavior-anchor-plan-ytr83r-20260912. Both source and evidence are pushed; remote README blob readback matches. All 520 committed archive blobs (28,251,256 bytes), including raw logs and 60 native captures, match prepared originals. Portable verifiers resolve historical machine paths through archived bytes/Git source maps; excluded executable/runtime references are explicitly identified. Peers do not need this machine's .local directory.

Validation is source-specific: 3aa workspace 1,819 passed/0 failed/7 ignored plus strict workspace Clippy; corrected 53d desktop 1,194 passed/0 failed/6 ignored plus mounted Escape regressions, strict desktop Clippy/build. Original native has 25 passing and four retained failed comparisons; corrected native has five exact full-Project comparisons, immediate source/target menu Escape, edit/Undo/Redo and fresh-process reopen/save. All five runs closed normally exit0 with empty logs. Independent gate, source, native and handoff reviews are included.

Read the archive's limitations: original invalid Choice reconnect plan and four precision attempts stay failed; valid Final reconnect was separately predeclared. Shared-target replacement caused one aborted preflight and is disclosed; corrected staging avoids that binding. Combined cancellation B checkpoint, retrospective close metadata, dense/truncated labels and limits of held-input coverage remain explicit. Linux is user-paused.

Integration audit gives actual shared-file seams and combined checks. Codex-956atf retains #27/#16 ownership. This is delivered branch-specific work awaiting integration; #33 remains open because integration and the broader notation-specific Process/Scenario scope are not certified by this contribution.

Codex-ytr83r/root — published ordinary/State attachment contribution and complete portable evidence handoff. Source: [53d01a3](http://217.177.34.108:3000/sorokin.oleg.edu/ARCADIA-Studio/commit/53d01a3d4451b94792986f2dfac56f6f04e111a4), branch codex/edge-anchors-escape-ytr83r-20260923. Ordered commits above ordinary/Text base 3f9e6a18: 79cc9d5 → 3aa80de → 53d01a3. Importing only the last Escape commit is insufficient. Per-view source/target attachment editing, per-end reset, semantic-port precedence, rounded/diamond/circle contours, guarded cancellation and exact history/source/API persistence are implemented. State semantic reconnect remains separately labelled. Evidence: [Windows validation and portable archives at bb7edfb](http://217.177.34.108:3000/sorokin.oleg.edu/ARCADIA-Studio/src/commit/bb7edfbf01b43577b01d4dc7f6b8dd9240145759/harness/experiments/edge-attachments-53d01a3-20260923/README.md), on codex/behavior-anchor-plan-ytr83r-20260912. Both source and evidence are pushed; remote README blob readback matches. All 520 committed archive blobs (28,251,256 bytes), including raw logs and 60 native captures, match prepared originals. Portable verifiers resolve historical machine paths through archived bytes/Git source maps; excluded executable/runtime references are explicitly identified. Peers do not need this machine's .local directory. Validation is source-specific: 3aa workspace 1,819 passed/0 failed/7 ignored plus strict workspace Clippy; corrected 53d desktop 1,194 passed/0 failed/6 ignored plus mounted Escape regressions, strict desktop Clippy/build. Original native has 25 passing and four retained failed comparisons; corrected native has five exact full-Project comparisons, immediate source/target menu Escape, edit/Undo/Redo and fresh-process reopen/save. All five runs closed normally exit0 with empty logs. Independent gate, source, native and handoff reviews are included. Read the archive's limitations: original invalid Choice reconnect plan and four precision attempts stay failed; valid Final reconnect was separately predeclared. Shared-target replacement caused one aborted preflight and is disclosed; corrected staging avoids that binding. Combined cancellation B checkpoint, retrospective close metadata, dense/truncated labels and limits of held-input coverage remain explicit. Linux is user-paused. [Integration audit](http://217.177.34.108:3000/sorokin.oleg.edu/ARCADIA-Studio/src/commit/bb7edfbf01b43577b01d4dc7f6b8dd9240145759/harness/experiments/edge-attachments-53d01a3-20260923/integration-review.md) gives actual shared-file seams and combined checks. Codex-956atf retains #27/#16 ownership. This is delivered branch-specific work awaiting integration; #33 remains open because integration and the broader notation-specific Process/Scenario scope are not certified by this contribution.
Sign in to join this conversation.
No labels
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sorokin.oleg.edu/ARCADIA-Studio#33