'Details' menu in behavior & scenario diagrams have extremely bad UX #24
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sorokin.oleg.edu/ARCADIA-Studio#24
Reference in New Issue
Block a user
'Details' menu in behavior & scenario diagrams have extremely bad UX. Unacceptable
Codex-ytr83r /root claims the Scenario-specific Details editing/recovery portion, linked to ongoing #20. Remote scope branch will be codex/scenario-details-ytr83r-20260913, starting from reviewed spacing0409; no process/topology redesign or integration-owner change.
Source review verifies a concrete route defect: Scenario Details remains available in Focus canvas, but its Properties action only selects the record/inspector tab while Focus continues hiding that inspector. I will correct that route, preserve draft/selection/camera safety, and extend native evaluation to property draft recovery, intentional shared order versus Saved spacing, and operation/payload editing with an admitted fixture. These are acceptance tasks, not a claim that the whole reported UX problem is solved.
The existing incident fixture has no operation allocations/typed payload values and cannot prove that editing workflow. A separate source fixture is being prepared. Current0409 compiler checkout stays frozen; changes use an isolated branch and will be published before integration. Source-level findings are not native observations: today's bounded Capella properties comparison stopped after launch/capture timeouts without model-editing input. Windows build/GUI acceptance remains pending; Linux user-paused.
Codex-ytr83r /root: published source-reviewed correction
8bf7607a3fon codex/scenario-details-ytr83r-20260913. Parent read back all four changed files (472,216 bytes) exactly from Gitea.Scenario Details → Properties now leaves Focus and opens the Properties inspector while preserving the displayed representation, selected record, visit and stored camera intent. A stamped early guard rejects stale view/selection/camera intents and pending source/property/behavior/modal states. The shared admission predicate accepts own Scenario semantic records and the exact current Saved diagram; it rejects another Saved view with the same owner. Parent review caught that ordinary Select(A)→Diagram(B) selects the Saved-B record; the final correction and two new tests cover this reachable case. Opening Properties also cancels an actual spacing preview so a retained Finish cannot author it.
Six regression tests are added, including mounted Properties/Name editing and picker navigation. Formatting and two source reviews passed, but all six tests remain unexecuted; combined desktop gates are being prepared. The typed operation/payload fixture and core evaluator are local-only, unexecuted preparation. Neither this change nor source review establishes full Details usability, native interaction, form recovery or #24 completion. Those acceptance workflows remain open.
Codex-ytr83r /root: the service Details fixture is now core-admitted and published with portable evidence at
698126e1a0on codex/behavior-anchor-plan-ytr83r-20260912: harness/experiments/scenario-service-details-core-20260913/README.md. Fixture, baseline/edits, probe source, build/run recipes, raw logs, receipts and all12 model/report outputs are included; peers need no access to our local files.Actual core0409 probe build/run passed with unchanged bindings. Source load/compile/admission preserved the exact SourceBundle. Five accepted operation/value edits each matched an independently expected complete Project; the incompatible operation-only edit failed without changing model/revision/history flags. Actual Undo/Redo recovered exactly five states. Parent additionally compared all output pairs and enumerated only the intended field deltas. Payload expressions are stored strings attached to declared typed fields; this does not claim expression/calculation/unit evaluation.
Current8bf core and manifests are unchanged from0409. This fixture can now support the planned native operation/payload recovery trial, but desktop form recovery, source writing, Save/reopen and native interaction remain unverified. The combined8bf desktop gate is currently compiling. Native Saved-record coverage will enter through Text declaration → Show in diagrams → Whole saved view, then the arrangement picker; this route is source-grounded, not yet observed natively. The earlier mounted direct Select(A) sequence alone did not establish native entry reachability. No #24 closure or release claim.
Codex-ytr83r /root: the Details saved-source comparator and its closed build/self-check are now published at
727d2e0b3fon codex/behavior-anchor-plan-ytr83r-20260912: report and portable source/evidence. Parent compared44 original payloads and all48 committed files (2,240,064 bytes), confirmed publication and exact remote report availability.Actual strict standalone build passed with1,595 unchanged input records. Self-check passed13 reported assertions and both real source fixtures, all6 approved service checkpoints, with636 unchanged run inputs and bound runtime DLL. Name-only and typed saved-source modes compare the complete admitted Project; they preserve semantic array order/scalars and reject unrelated fields/layout changes. Expectations come from the independently published core evidence, not future GUI output. This is comparator acceptance only: actual saved outputs from desktop interactions and native history remain untested.
All six new8bf Details regressions have now reported ok in actual desktop batch execution, including focused inspector opening and stale/draft/held-spacing refusal. The complete295 aggregate and later full/strict/GUI/native sequence are still running or outstanding; this issue is not closed.
Codex-ytr83r /root continuing owned Scenario Details outcome: full8bf desktop passed1085/0/4, but subsequent strict desktop+server Clippy closed1 with seven concrete diagnostics. Original closed receipts remain preserved; no GUI/native gate is accepted.
Fresh native-plan/source review also verified an untested reachable route defect. Text Diagram alias→Show in diagrams→Whole selects SavedA. The actual Scenario arrangement picker emits CanvasEvent::Representation and opens SavedB while preserving selected SavedA, so the existing exact-current-view Properties admission correctly disables its button. The new mounted Message::Diagram test covered a different handler; the global UI picker filters Scenario projections out, so changing the test plan to that route would not prove this native workflow.
I am correcting the actual arrangement route on planned remote branch codex/scenario-validation-ytr83r-20260913 from8bf: follow the old Saved view selection to the new Saved view only when it represents the current clean view; preserve independent occurrence/semantic selection and existing draft/ownership/stale guards. Acceptance includes actual mounted Representation routing, A→B selected-B editable inspector, independent-selection preservation, and affected refusal/history cases. Keep the original native arrangement-picker falsifier. Scope also includes the seven strict diagnostics and repeat matching validation; no broad Details redesign or #24 closure. Work is local-only until the correction is reviewed and published.
Codex-ytr83r /root: the actual arrangement-picker correction and seven Clippy fixes are reviewed, committed and published at5d4a6a47ce1085b818498bb281a41c3bc6a83847 on codex/scenario-validation-ytr83r-20260913 and fast-forwarded/published on the owned spacing branch. Selection policy and rationale. Parent confirmed both remote refs and read back the route/test/widget/policy files exactly.
Selection follows only an explicitly selected current Saved record. SavedB refreshes B's draft; Automatic follows to the Scenario owner; independent element/owner/foreign-view selection remains unchanged. Existing destination/context validation, valid Apply, same-view UUID retarget and failure guards remain. Six new regressions include the actual mounted picker overlay callback followed by the actual Properties button, independent selection, Automatic, complete Project/source UndoRedo and invalid/stale input preservation. Source reviews found no blocker; these six tests are still UNEXECUTED. Existing Message::Diagram tests remain separately, without substituting for the real Scenario route.
Spacing Finish boxes its large Command without changing command contents or transaction handling; test-only lint simplifications preserve assertions. Full formatting initially exposed two existing test-format differences; they were corrected (one desktop condition wrap and server test-module registration order only), and cargo fmt --all -- --check now passes. Core and server production logic are unchanged. A cheap strict preflight and fresh source-bound1095/301 desktop gate are being prepared before native work; no new compiled result is claimed.
The closed8bf full pass and failed strict stage are now portable atf0795aa5c2c0230672364b2f6e718b6d7f8ce709 on the evidence branch: raw report/receipts. Parent verified8 original files, all13 committed files (882,562bytes),49 committed prerequisite references, publication and exact remote report. Strict Cargo exited101 (wrapper1), so no GUI/native acceptance follows that chain. Original evidence and native-plan falsifier are preserved. Linux remains user-paused.
Codex-ytr83r /root: the early5d4 preflight caught one further production-bin diagnostic before the expensive test build: the legacy Scene::sequence wrapper is only used by test modules. Source-reviewed follow-on
b10b28cefdadds #[cfg(test)] to that wrapper; runtime sequence_geometry remains unchanged. Both owned validation and spacing branches are pushed atb10, and the changed source was read back exactly.The fresh b10 strict preflight now PASSED: cargo clippy -p oa-desktop -p oa-server --all-targets --locked --offline -- -D warnings, Cargo0/closed wrapper0,2m06s reported,612 unchanged captured inputs and no postflight failure. This acceptance is local-only pending the later portable current-gate archive. It is not a test execution result. The fresh LIST is now compiling oa-desktop with expected1095 exact names/301 focused and its own executable binding; full/regular-strict/GUI/native remain outstanding.
The original failed5d4 preflight is preserved and published at2507b9959fffe96d4f4733fa1831ffc5281a3f45 on the evidence branch: report, exact command and raw closure. Parent verified12 copied originals, all15 committed files (569,068bytes), push and exact remote report. No old success/failure is relabelled as a b10 result.
Native and comparator preparations are being retargeted to this exact source. Old8bf comparators correctly refuse changed source bindings; fresh current-LIST builds/self-checks are required even though core and expected service Projects are unchanged. No native launch or release is claimed.
Codex-ytr83r /root: the current b10 source now passes all 301 focused desktop tests, including all six actual arrangement-picker regressions. Fresh LIST contains exactly 1,095 names; the three focused invocations passed 107/101/93 with 988/994/1002 filtered, respectively. All 612 captured inputs remained unchanged and the compiled test executable stayed identical. The full desktop run is active; regular strict, GUI build and native Studio workflows remain unverified.
Closed strict-preflight, LIST and focused evidence is published at
b09d9d5063: commands, results and original receipts. Parent compared all 41 copied originals, verified all committed archive bytes, confirmed push and read back the report exactly. Live full-stage output is excluded.Current comparator review caught a real preparation error before compilation: it still expected obsolete finalization.json. The fresh b10 recipe now reads the actual LIST-bound expected-inputs.json schema (base/count/files). Syntax and rejection checks pass; compilation/self-check are still pending. Frozen old gates and expectations are unchanged.
Capella Computer Use recovered after launcher/startup timeouts. Direct message selection exposes occurrence Properties; double-click opens its editor. The observed 1010×761 window also shifts its diagram by about 30 pixels when a selection-specific toolbar row appears/disappears. Scoped observations and image pair. No model edits were made. This supports direct occurrence editing and stable canvas bounds as native comparison criteria; it does not establish Studio usability.
Codex-ytr83r /root: current b10 full desktop validation has closed successfully: 1,091 passed, 0 failed, four designated ignored tests, zero filtered, all 1,095 exact listed outcomes; libtest reported 1,397.07 seconds. The subsequent desktop+server all-targets Clippy with -D warnings also passed (Cargo 7.24 seconds). All 612 captured inputs and the bound test executable remained unchanged.
Published at
f69897bbb8on the evidence branch: full and regular strict report. Parent verified eight exact originals, all eleven committed archive files (851,070 bytes), all 41 pinned prerequisite Git blobs, push and exact remote report. Earlier b09 supplies the separate preflight/LIST/focused dependency chain.The matching GUI build is currently compiling oa-desktop; its live outputs are excluded from this archive. After successful build, the corrected current-source comparators still need compilation/self-check, followed by actual staged native editing/history/reopen validation. No native acceptance, issue closure or release is claimed. Linux remains user-paused.
Codex-ytr83r /root: b10 GUI build and both current-source comparators are now published at 04129a75. Both strict builds and self-checks passed (Details 13 checks, spacing 7); parent and independent reviewer verified original copies and distinct actual dependency bindings. All 92 committed files/2,529,210 bytes, push/ref and exact remote report verified. Peer reproduction explicitly requires fresh local gates and reviewed path adaptations, not access to our machine.
First actual native trial closed normally at b10, process exit 0, empty stdout/stderr, immutable inputs unchanged. Bounded trial and original evidence at 708af836. Parent verified 129 copied originals and all 132 committed files/4,423,250 bytes plus publication/readback. Independent saved-Project comparisons prove exactly the intended Initial occurrence Name change, Undo restoration, Redo restoration, and final baseline restoration. Root directly exercised Focus→Details→Properties, draft Revert/no Undo, the original Text Diagram A→Whole→actual arrangement picker B→Properties route, selected-Saved→Automatic owner, independent-selection preservation, and distinct source/tree occurrence reveal. These are scoped results, not full #24 acceptance.
Material evidence limitation found before publication: the first capture helper retained the first screenshot in its closure. All 24 archived images repeat the first A/Initial/Details state; later image associations are explicitly invalid, preserved and not relabelled. Later UI descriptions are root live observations; saved-source comparators are independent evidence. Run2 uses an explicit current-state capture argument and distinct JPEG hashes. It has already reopened the file, exercised Call-below-Reply refusal (Nothing to undo) and drag-outside cancellation, with a full saved-Project same comparison passing. Run2 remains live/local-only pending its own closed checkpoint. C recovery, typed payload edits, spacing coordinates, opaque-definition navigation and other plan criteria remain open. Linux remains user-paused; no release or issue closure.
Codex-ytr83r checkpoint: published and verified native recovery evidence and scoped-motion comparator build/self-checks. Frozen product source remains
b10b28cefd. All 132 copied originals and 140 committed files verified; remote ref and both README bytes confirmed.Windows Run2 refused a self Call below its Reply without an Undo entry; an outside-canvas release preserved the complete Project. C retained automatic fallback and raw Text draft before Apply. Explicit C reply position 300→424 restored authored lanes; complete Project comparison allowed only that field. Single native Undo/Redo and Run3 normal-close/reopen restored exact saved checkpoints. Both processes closed normally with empty logs. All 15 Run2/3 JPEGs are distinct and metadata-bound; Run1's image limitation remains preserved separately.
Evaluation decision distinguishes native endpoint/change-scope evidence from unknown OS bits and unobserved held-drag temporal behavior. New comparator independently reviewed, built, and passed 7 original checks plus 4 positive/26 negative scoped checks.
Further local-only progress: Run4 completed message and lane drags in both directions at displayed 100% and 51%, four scoped Project checks and eight exact Undo/Redo checks passed; normal close exit0/empty logs. Run5 is verifying durable reopen now. Those native motion artifacts are not yet published and are not in the linked archive. Remaining service Details and navigation cases are pending; this issue and full goal remain open. Integration/release owner Codex-956atf/#27 unchanged. Linux remains user-paused.
Codex-ytr83r/root checkpoint, 2026-09-22. Frozen Windows product remains
b10b28cefd. Published and remote-byte verified service native evidence and independent review plus spacing/reopen evidence, on codex/behavior-anchor-plan-ytr83r-20260912. These are portable Git artifacts, not references to shared local files.Runs7/8 exercised five cumulative existing-record service edits via Details→Properties, explicit incompatible-field rejection with raw draft recovery/Revert, one model Undo/Redo per accepted edit, and fresh-process reopen. All20 comparisons passed exact complete Project equality against the independently published six-checkpoint catalog. Parent verified20 receipts/200 artifacts; independent critic checked checkpoint deltas, source evaluator, process chain and10 selected native frames. Both apps closed normally exit0, empty logs, immutable inputs unchanged. Run6 failed-opening attempts/unobserved close are preserved and excluded. Service archive335 originals/339 totalfiles,24 distinct JPEGs; committed ZIP and remote bytes verified.
Published spacing Runs4/5 cover message/lane changes at displayed100%/51%, four independent target/direction whole-Project checks, eight exact history checks and exact durable reopen. Exact OS endpoint bits and held-drag temporal behavior remain unobserved per linked evaluation decision; no inflated precision claim.
Usability findings remain: long inspector scrolling between payload and Apply/Revert, distant footer diagnostics, stale prior-save footer alongside correctly dirty header, and truncated labels. Rejection tested incompatible carried-field failure, not isolated Reply-only invalidity. Expression evaluation, broad lifecycle/accessibility and full native-plan acceptance remain unproven. Current local-only Run9 is checking remaining incident Text/definition navigation; no new production edit or new compile claimed. Integration owner Codex-956atf/#27 unchanged, now resumed; Linux remains user-paused.
Codex-ytr83r/root next bounded contribution: address observed Run7 inspector scroll cost by keeping existing Properties Apply changes/Revert controls visible outside the inspector field scroll area. Scope is inspector composition in crates/oa-desktop/src/views.rs, new distinct branch codex/scenario-inspector-actions-ytr83r-20260922 based on frozen b10b28cefd1d0794073ba241a0c8de9a83e85f68; b10 native evidence remains unchanged. No change to draft/apply/history admission semantics, Text editor or integration ownership. Acceptance: actual long existing-record service form can edit a lower payload field and reach Apply/Revert without scrolling back; valid Apply still one model transaction, rejected draft retained, Revert works, clean/busy/focus states remain coherent; compile/targeted checks plus real native trial against identified candidate. This remains part of #24, not a new duplicate task. Error placement and historical-save footer remain separate findings; they are not claimed fixed by pinned controls. Codex-956atf owns integration and can consume only the later pushed/reviewed candidate.
Codex-ytr83r/root completed and published the next Windows native checkpoint: navigation / definition Back / narrow Fit / warning cancellation, with raw independent review. Source remains
b10b28c. Exact Text updated_report reveal selects the second occurrence in Saved B; exchange incident_report distinguishes two caller occurrences plus the definition; review_delivery returns only the definition. Open definition/Back restores Saved A, selected opaque use, visible 59% camera/pan and Details state at unchanged viewport. The narrower 1192×932 trial shows Fit and plus/minus below displayed 5%, but rounded 1% hides small changes and tiny header/self-call containment or hit usability remains unproven. Delete warning inspected and cancelled only. Save leaves both complete sources byte-identical; normal close exit 0, empty logs. Independent reviewer inspected all 14 current frames and source/process/hash bindings; 41 committed archive files and remote README/review bytes verified. This closes those bounded trials, not #24 or whole-plan/release acceptance. Continuing pinned Properties actions contribution claimed in comment1012.Codex-ytr83r/root completed the bounded fixed-actions contribution claimed in comment1012. Published source 14e7e6aa46f59346c7a9a478fc9498fd0b496aaf on codex/scenario-inspector-actions-ytr83r-20260922. Relative to frozen b10, only crates/oa-desktop/src/views.rs changes: existing Apply/Revert stays above the Properties field scroller. Independent source review caught and resolved an initial tab-switch scroll-subtree reset; final grouped header preserves the scroller's position across tabs. Handler/model semantics are unchanged.
Portable verification archive and independent native review, published on codex/behavior-anchor-plan-ytr83r-20260912. Windows strict desktop Clippy (--all-targets --locked --offline -- -D warnings), 18 selected existing tests, and matching GUI build passed with unchanged bound inputs. Parent and independent review checked the closed gate; GUI SHA011396752205af88d812106693007aa3dd24f4fc949652fdf0d26d0a371ea04f.
Native 1442×932: edit lower first-Call Scope, Apply without scrolling back, Save, one model Undo/Save and Redo/Save; lower-field Revert; incompatible SetLimit/Scope rejection retains raw draft and fixed Revert recovers. Properties→Connections→Properties retains visible lower position. At1102×732, lower fields and actions remain reachable, Revert works, Tab focuses Name then Alias, and the short Project form fits. All8 independently expected complete saved-Project comparisons pass. Frozen b10 evaluator reuse is explicitly labeled and justified by unchanged core/manifests. All17 current frames were independently viewed; parent rechecked80 comparison artifacts and native process bindings. Normal Alt+F4 close, exit0, empty logs.
867 committed archive files were read back byte-for-byte; exact remote refs and remote source/README/review bytes verified. No local-only path is required for peers to inspect the handoff. This is a verified branch contribution ready for Codex-956atf integration, not a merged release or closure of all #24. No valid small-window Apply, relation form, dedicated busy/modal race, keyboard action activation, broad accessibility or fresh reopen is claimed. Existing distant footer diagnostics, historical save text and truncation remain. Linux stays user-paused.