Skip to content

M2.14 UI: unify navigation and first-run Add IED on Material icon system - #576

Draft
masarray wants to merge 1 commit into
fix/m214-operator-icon-single-source-20261015from
feat/m214-material-icon-unification-20261015
Draft

masarray wants to merge 1 commit into
fix/m214-operator-icon-single-source-20261015from
feat/m214-material-icon-unification-20261015

Conversation

@masarray

@masarray masarray commented Oct 15, 2026 •

Copy link
Copy Markdown
Owner

Visual consistency follow-up to #574

  • Base is M2.14 UI: remove double Events glyph from overlapping icon templates #574 exact green HEAD b725268f; operator-supplied material Events/Alarm/FAT/Browser, NTP single compound clock+server and rail Add IED preserved.
  • Material filled geometries registered as WPF Geometry resources for Explorer, Live, GOOSE and Diagnostics instead of older P2 Lucide overlay. All eight nav destinations now have exactly one explicit first-party geometry Path; responsive caption updates remain intact.
  • First-run central Add IED uses OperatorAddIedIcon in both dynamic hero and older compatibility launcher, rather than LucidePlus. Existing actions and other SCL/Project paths unchanged.
  • P2 old decorator detects existing hand-built Path and refuses to layer a second icon; NTP uses existing single combined clock/server SVG.
  • Tests protect shared Material glyphs, Add IED dynamic icon source, and existing click semantics. No IEC/MMS/RCB/CF logic, ARIEC pin or public main changes.
  • Await exact SHA Windows WPF compile/regression/native/portable smoke, plus user screenshot acceptance.

Verified exact-SHA CI (2026-10-15)

Copy link
Copy Markdown
Owner Author

Cross-thread UI coordination checkpoint, 2026-10-15: This draft is a narrower sibling of comprehensive UI PR #575 (HEAD 7a761feecbda9f943b6078a2a595b8e95295578f). Both solve the eight-tab Material and center Add IED goal, but #575 additionally migrates primary action/P2 workbench icons, includes licensing/provenance and passed 14/14 exact-SHA CI + installer smoke. Latest Browser PR #577 (4be7b51b9040a7a5f1d8ecaa1d90bbc1a3b9d081) is 1 commit above #575 and passed 10/10 checks. Frozen review/checkpoint branch checkpoint/m214-material-icons-browser-20261015 points to #577. Please avoid merging this sibling blindly into #575/#577 and reintroducing redundant templates; preserve it as rollback evidence pending normal owner review. Remaining deep dialog inventory: #578. No public main merge authorized.

Copy link
Copy Markdown
Owner Author

Thread A continuation ownership / M2.14 integration checkpoint. Original Thread A chat reached its limit; continuation now uses verified latest PR #577 4be7b51b9040 (10/10 green; includes consolidated M2.13K stress, CF/phasor A+B, scalar no-angle, SG and Material icons). New draft PR #579 at 07b7b1820aebce84c63cf0f0f2d66cbd8cadc798 targets a measured live shortfall: exact ATCC1.TapChg [ST] DataSet parent stayed Not read despite observed valWTr=3 and posVal=3. Only projection-layer, model-proven ST field summaries added; no change to canonical SSOT, runtime Report ingest, read plans, pin or stable. Five focused tests; Windows CI currently running.

Conflict guard: #576 (sibling icon unification branch) diverged from #575; avoid assuming it is an ancestor of #577 or blindly cherry-picking icon modifications. Reconcile only proven missing UI behavior by comparison, keeping #577 as immutable base and #579 as descendant. No merge to main until Windows CI + physical BCUGE/ZIV acceptance. Remaining field issues: CF/unit evidence and GUI parity; avoid fake scalar angles or invented observations.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant