@jax-data-science/sci-image-visualizer 0.2.4 → 0.2.5

package/lib/implementations/osd/openseadragon-visualizer.service.d.ts

@@ -153,6 +153,16 @@ export declare class OpenSeadragonVisualizerService extends BaseStoreVisualizer
     /** Only grayscale images get a colormap (RGB tiles pass through untouched). */
     private isGrayscaleImage;
     private colormapSub;
+    /** Bumped by every display invalidation. A recolor round captures it and, after
+     *  each `await`, abandons the tile once a newer round has started. Writing a
+     *  superseded context back is not merely wasted work: OSD's conversion sees a
+     *  canvas the newer round already replaced, throws `DOMException`, and
+     *  `_handleConversionError` DESTROYS the cache record and unloads the tile
+     *  (unlike the drawer's rasterBlob path, it does not re-prepare). Enough of
+     *  those and the viewer goes white mid-drag. */
+    private displayToken;
+    /** Pending coalesced invalidation (see {@link scheduleInvalidate}). */
+    private invalidateHandle;
     /** Latest per-channel display state (window/gamma/visibility) from the store,
      *  read synchronously by recolorTile. Channel 0 drives grayscale windowing;
      *  R/G/B (indices 0-2) drive RGB per-channel windowing. */
@@ -301,6 +311,12 @@ export declare class OpenSeadragonVisualizerService extends BaseStoreVisualizer
      *  flooding OSD with "[CacheRecord] … InvalidStateError" and wasting work on tiles
      *  that aren't on screen. The other cached slices are marked stale and re-tinted
      *  lazily when revealed. Composite/grayscale invalidate the world as before. */
+    /** Collapse a burst of display-state changes into ONE invalidation on the next
+     *  frame. Dragging a window slider emits per pixel of travel, and each round
+     *  restores and re-processes every tile of every channel — so the burst is both
+     *  wasted work and the race that breaks cache records (see {@link displayToken}).
+     *  The store write stays live, so the pane itself remains responsive. */
+    private scheduleInvalidate;
     private invalidateDisplay;
     private destroyViewer;
     /** This backend's region renderer (the SVG overlay), once a plot is mounted. */

package/lib/toast-outlets.d.ts

@@ -0,0 +1,23 @@
+/**
+ * Keys for the toast outlets the library renders for itself.
+ *
+ * PrimeNG delivers a message to a `<p-toast>` only when the keys match — a
+ * keyless message reaches a keyless toast and nothing else. The library used to
+ * emit its notices with no key, or with jit-ui's own keys (`app-toast`,
+ * `center-toast`), which meant its user-facing feedback silently depended on the
+ * host mounting the right markup. In jit-ui it did; in every other host —
+ * including this repo's browser example — errors and results went nowhere, so a
+ * failed or no-op action looked like a dead button.
+ *
+ * These keys are owned by the library and their outlets are rendered by
+ * {@link VisualizerComponent}, so the feedback works in any host. A host that
+ * wants these notices somewhere else should not render an outlet with the same
+ * key — two matching outlets show the message twice.
+ */
+/** General notices: save results, validation, action outcomes. Default position. */
+export declare const VIZ_TOAST_KEY = "sci-viz-notice";
+/**
+ * Failures that must interrupt: rendering/tile errors that leave the viewer in a
+ * bad state. Centered and sticky, matching how these were surfaced before.
+ */
+export declare const VIZ_ALERT_TOAST_KEY = "sci-viz-alert";

package/lib/visualizer.component.d.ts

@@ -32,6 +32,31 @@ export declare class VisualizerComponent implements OnInit, OnChanges, AfterView
      *  one key would each render the same message — a duplicate toast. A unique
      *  key per instance scopes the toast to the component that raised it. */
     private static nextToastId;
+    /**
+     * The library also raises notices from places that have no instance of their
+     * own to key against: {@link PlotlyService} is `providedIn: 'root'`, and the
+     * region editor is a child dialog. Those use the fixed
+     * {@link VIZ_TOAST_KEY} / {@link VIZ_ALERT_TOAST_KEY} outlets.
+     *
+     * For the same reason the per-instance key above exists, exactly ONE mounted
+     * visualizer may render those shared outlets — otherwise a message from the
+     * root service would be shown once per live viewer (jit-ui runs a main view
+     * and a pipeline-preview at the same time). The first to init claims them and
+     * releases on destroy, so the surviving viewer picks them up.
+     */
+    private static readonly liveInstances;
+    readonly vizToastKey = "sci-viz-notice";
+    readonly vizAlertToastKey = "sci-viz-alert";
+    /**
+     * Whether this instance renders the shared outlets. The owner is simply the
+     * oldest live visualizer — a `Set` iterates in insertion order, so when the
+     * owner is destroyed the next one takes over on its following change-detection
+     * pass. Tracking a set rather than a single owner matters: with a lone
+     * `owner` reference, tearing down the owner while a sibling was already
+     * initialised would leave nobody rendering the outlets, and every notice from
+     * the root service would silently vanish again.
+     */
+    get ownsSharedToasts(): boolean;
     isStackEvent: EventEmitter<any>;
     isGrayscaleEvent: EventEmitter<any>;
     /** Which toolbar groups to show. A partial override merges over the full set,
@@ -100,6 +125,25 @@ export declare class VisualizerComponent implements OnInit, OnChanges, AfterView
      *  every point click, which re-runs inference). */
     private samToastShown;
     readonly samToastKey: string;
+    /**
+     * Outlet for the library's own result/error notices.
+     *
+     * PrimeNG routes a message to a `<p-toast>` only when the keys match — a
+     * keyless message reaches a keyless toast and nothing else. These notices used
+     * to be emitted with no key, so they rendered only in hosts that happen to
+     * mount a bare `<p-toast>` (jit-ui does, in its file-tree component). Every
+     * other host — including this repo's own browser example — dropped them
+     * silently, which made a failed or no-op segmentation look like a dead button:
+     * the sticky progress toast is cleared in the same tick by hideSamToast, and
+     * the message explaining why never appeared anywhere.
+     *
+     * Keyed to this component instance so the library renders its own outlet and
+     * is not dependent on host markup. Deliberately NOT the sticky toast's key:
+     * {@link hideSamToast} clears that key in the `finally`, which would wipe the
+     * result the moment it was posted, and the sticky toast's custom template is
+     * built for the live status + progress bar.
+     */
+    readonly resultToastKey: string;
     /** Subscriptions to the point tool's live feeds (status/busy/download). */
     private samPointSub;
     /** Vertex eraser radius in image-pixel coordinates. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jax-data-science/sci-image-visualizer",
-  "version": "0.2.4",
+  "version": "0.2.5",
   "description": "Browser-based scientific image visualization for Angular — gigapixel whole-slide (OpenSeadragon), 2D/3D (Plotly) and WebGPU (napari-js) rendering, with region/annotation editing and in-browser SAM segmentation.",
   "keywords": [
     "angular",