sysml-diagram 0.15.7 → 0.15.8

package/out/main.js

@@ -167246,7 +167246,7 @@ var SysmlDiagramModelProvider = class _SysmlDiagramModelProvider {
   transitionLabel(t) {
     const tn = t;
     const acc = tn.accept;
-    const trigger = acc ? acc.type?.$refText ?? acc.varName : void 0;
+    const trigger = acc ? acc.type?.$refText ?? acc.varName ?? this.triggerExpressionLabel(acc) : void 0;
     const guard = tn.guard?.$cstNode?.text?.replace(/\s+/g, " ").trim();
     const effect = this.effectLabel(tn.effect);
     const parts = [];
@@ -167258,6 +167258,19 @@ var SysmlDiagramModelProvider = class _SysmlDiagramModelProvider {
       parts.push(`/ ${effect}`);
     return parts.length ? parts.join(" ") : void 0;
   }
+  /** The `at` / `after` / `when` trigger of a transition, as written. */
+  triggerExpressionLabel(acc) {
+    for (const [keyword, expr] of [
+      ["at", acc.atTime],
+      ["after", acc.afterDelay],
+      ["when", acc.changeCondition]
+    ]) {
+      const text = expr?.$cstNode?.text?.replace(/\s+/g, " ").trim();
+      if (text)
+        return `${keyword} ${text}`;
+    }
+    return void 0;
+  }
   effectLabel(ef) {
     if (!ef || typeof ef !== "object")
       return void 0;
@@ -173342,10 +173355,22 @@ ${baseIndent}}`;
   // target feature, so each end must be able to hold it (OMG SysML v2 Part 1
   // §7.12 ItemFlow / PayloadFeature). Reported per end, and only when the end
   // resolves unambiguously and carries exactly one written type.
+  //
+  // A MESSAGE is deliberately exempt, though the grammar folds it into the same
+  // statement. OMG SysML 8.2.2.16 gives `flow` FlowEndMembers — a FlowEnd is a
+  // FlowFeature, the feature that holds the payload — while a message's `from`
+  // and `to` are MessageEventMembers: `message m of i : I from evt1 to evt2` is
+  // "parsed as an abstract FlowUsage, but without any flowEnds", its two ends
+  // redefining Message::sourceEvent and Message::targetEvent (8.4.12.2). The
+  // ends of a message are the two OCCURRENCES that exchange the payload, so
+  // demanding that they be able to hold it reports every sequence-diagram
+  // message as an error.
   checkFlowPayload(decl, model, index2, accept) {
     if (decl.$type !== "FlowStmt")
       return;
     const flow = decl;
+    if (flow.flowKind === "message")
+      return;
     const payload = flowPayloadType(flow.payload);
     if (!payload || payload.conjugated)
       return;
@@ -192601,6 +192626,38 @@ body {
 #root { display: flex; flex-direction: column; height: 100%; min-height: 0; }
 .right-panel { display: flex; flex-direction: column; height: 100%; min-height: 0; }
 
+/* issue 225 \u2014 ONE scrollbar in the whole webview. The canvas draws its own bars
+ * (.rf-scrollbar) because it scrolls a transform rather than a box; every other
+ * surface scrolls natively - the Browser View tree, the Grid View table, the
+ * Properties panel, a long context menu - and the host's default bar is a fat
+ * one with arrow buttons, which reads as a second, heavier design beside them.
+ *
+ * These MUST be the standard properties, not the WebKit pseudo-elements. The VS
+ * Code webview host injects an @layer vscode-default block that sets
+ * scrollbar-color on html; scrollbar-color INHERITS, and Chromium ignores the
+ * ::-webkit-scrollbar pseudo-elements for any element that has it - so a WebKit
+ * rule here is dead on arrival on every surface (which is also why the host's
+ * own ::-webkit-scrollbar block in that same style element does nothing). What
+ * beats it is the cascade: an UNLAYERED declaration outranks any layered one
+ * whatever its specificity, so one rule on the root re-colours and thins every
+ * scrolling box in the document, and 'thin' is what drops the arrow buttons.
+ *
+ * Nothing here is a scroll BEHAVIOUR: an element scrolls exactly as much as its
+ * own overflow says. The toolbar is the one deliberate exception - it hides its
+ * bar and overlays .dbar-track, because a laid-out bar there pushes the icons
+ * upward - and an element's own scrollbar-width beats this inherited one. */
+:root { scrollbar-color: color-mix(in srgb, var(--fg-3) 40%, transparent) transparent; }
+/* The two halves are split because only ONE of them inherits. scrollbar-color
+ * does, so the root carries it for the whole document; scrollbar-width does NOT,
+ * so a rule on the root would thin the page's own bar and leave every inner
+ * scrolling box - which is all of them here - at the host default. Hence the
+ * universal selector, still at zero specificity so .dtoolbar keeps winning. */
+* { scrollbar-width: thin; }
+/* Quiet at rest, readable under the pointer - the same pair the canvas bars use. */
+.doutline-tree:hover, .grv-wrap:hover, .dinspector:hover, .rp-body:hover, .dctx-menu:hover {
+  scrollbar-color: color-mix(in srgb, var(--fg-3) 65%, transparent) transparent;
+}
+
 /* issue 165 \u2014 the docked (side) mode renders the same .dtoolbar as tab mode;
  * the old dedicated .rp-header row (with its "Diagram <view>" text) is gone. */
 .dtoolbar-shell {
@@ -193349,7 +193406,53 @@ body {
 /* Plain canvas background. AdaptiveGrid paints two fixed CSS grid layers and
  * updates only their screen-space size/offset; it avoids the two live SVG
  * pattern trees that React Flow otherwise reconciles for every transform tick. */
-.react-flow { width: 100%; height: 100%; background: var(--vscode-editor-background, var(--bg-1)); }
+.react-flow { position: relative; width: 100%; height: 100%; background: var(--vscode-editor-background, var(--bg-1)); }
+/* issue 225 \u2014 the HAND tool is navigation only. React Flow's own flags stop node
+ * dragging and connecting; these rules stop the hand-drawn editing affordances
+ * (port move strips, connector waypoints, the message reorder grip, resize grips,
+ * the frame hover band that reveals connect points) from taking the pointer, so a
+ * drag anywhere is a pan. Clicks, hover cards and the right-click menus keep
+ * working \u2014 placing a connector through the context menu still does. */
+.react-flow.rf-tool-hand .port-drag-hit,
+.react-flow.rf-tool-hand .dedge-waypoints,
+.react-flow.rf-tool-hand .dedge-midpoint,
+.react-flow.rf-tool-hand .dedge-waypoint,
+.react-flow.rf-tool-hand .dedge-handle,
+.react-flow.rf-tool-hand .danchor-pt,
+.react-flow.rf-tool-hand .dport-endpoint-handle,
+.react-flow.rf-tool-hand .message-reorder-grip,
+.react-flow.rf-tool-hand .dframe-hover-band,
+.react-flow.rf-tool-hand .react-flow__handle,
+/* React Flow's own endpoint anchors. The edge array is locked as well (a
+ * per-edge reconnectable outranks the canvas-wide flag), so these normally do
+ * not exist under the hand tool at all; the rule is what makes the guarantee
+ * hold for the frame in which selection and the tool switch disagree. */
+.react-flow.rf-tool-hand .react-flow__edgeupdater,
+.react-flow.rf-tool-hand .react-flow__resize-control { pointer-events: none; }
+/* One cursor everywhere: the pane already gets React Flow's grab/grabbing pair,
+ * so the node surfaces that otherwise advertise a move or a resize must follow it
+ * rather than promise an edit the hand tool will not perform. */
+.react-flow.rf-tool-hand .react-flow__node,
+.react-flow.rf-tool-hand .rf-frame-header,
+.react-flow.rf-tool-hand .rf-node-header,
+.react-flow.rf-tool-hand .rf-lane-header,
+.react-flow.rf-tool-hand .dnode-hit,
+.react-flow.rf-tool-hand .dframe-drag { cursor: grab; }
+.react-flow.rf-tool-hand .react-flow__pane.dragging,
+.react-flow.rf-tool-hand .react-flow__node:active,
+.react-flow.rf-tool-hand .dnode-hit:active { cursor: grabbing; }
+/* issue 225 \u2014 plain scrollbars along the canvas edges. Thin, quiet, and only as
+ * present as the toolbar chrome; the thumb spans the whole track ("full") when
+ * the diagram already fits, which reads as "nothing to scroll". */
+.rf-scrollbar { position: absolute; z-index: 4; background: transparent; }
+.rf-scrollbar-y { top: 0; right: 0; bottom: 10px; width: 10px; }
+.rf-scrollbar-x { left: 0; right: 10px; bottom: 0; height: 10px; }
+.rf-scrollbar:hover { background: var(--bg-1); }
+.rf-scrollbar-thumb { position: absolute; border-radius: 5px; background: var(--fg-3); opacity: 0.34; }
+.rf-scrollbar-y .rf-scrollbar-thumb { left: 2px; right: 2px; }
+.rf-scrollbar-x .rf-scrollbar-thumb { top: 2px; bottom: 2px; }
+.rf-scrollbar:hover .rf-scrollbar-thumb { opacity: 0.6; }
+.rf-scrollbar-thumb.full { opacity: 0.14; }
 .rf-grid-layer { pointer-events: none; }
 svg.react-flow__connectionline { z-index: 1; }
 /* REQ-224 \u2014 bottom control bar (grid toggle, zoom out / live % / zoom in, fit) */
@@ -193361,7 +193464,9 @@ svg.react-flow__connectionline { z-index: 1; }
   border-radius: 5px; cursor: pointer; }
 .rf-ctl-btn:hover { background: var(--bg-hover); color: var(--fg-0); }
 .rf-ctl-btn.on { color: var(--accent); }
-.rf-ctl-zoom { min-width: 42px; text-align: center; font: 600 11px var(--font-mono); color: var(--fg-2); }
+/* issue 225 \u2014 the live zoom readout IS the reset-to-100% button, so it keeps the
+ * readout's width and typeface while taking the control bar's hover affordance. */
+.rf-ctl-zoom { width: auto; min-width: 42px; padding: 0 4px; text-align: center; font: 600 11px var(--font-mono); color: var(--fg-2); }
 .rf-ctl-sep { width: 1px; height: 16px; background: var(--line); margin: 0 3px; }
 .react-flow__node { font-family: var(--font-mono); font-size: 11px; color: var(--fg-0); }
 .react-flow__node-sysml, .react-flow__node-frame { background: transparent; border: none; padding: 0; border-radius: 0; box-shadow: none; }
@@ -196365,7 +196470,7 @@ async function runExport(command) {
 }
 
 // src/main.ts
-var VERSION2 = true ? "0.15.7" : "dev";
+var VERSION2 = true ? "0.15.8" : "dev";
 function display(file) {
   const rel2 = path9.relative(process.cwd(), file);
   return rel2 && !rel2.startsWith("..") ? rel2.split(path9.sep).join("/") : file;