anyplotlib 0.3.0b1__tar.gz → 0.4.1__tar.gz

{anyplotlib-0.3.0b1 → anyplotlib-0.4.1}/.github/workflows/prepare_release.yml

@@ -11,12 +11,13 @@ on:
         required: true
         type: choice
         options:
+          - finalize      # drop the bN suffix: release the current beta's base as stable (0.3.0b2 -> 0.3.0)
           - minor
           - bugfix
           - major
           - pre-release   # increments the bN counter on the current base version
       beta:
-        description: "Mark as beta pre-release (adds bN suffix; always true for pre-release)"
+        description: "Mark as beta pre-release (adds bN suffix). Ignored for 'pre-release' (always beta) and 'finalize' (always stable)."
         required: false
         type: boolean
         default: false
@@ -67,17 +68,42 @@ jobs:
           minor  = int(m.group(2))
           patch  = int(m.group(3))
           beta_n = int(m.group(4)) if m.group(4) else None
-
-          if bump == "major":
+          on_beta = beta_n is not None
+
+          if bump == "finalize":
+              # Release the current beta's base as stable: just drop the bN
+              # suffix, keep major.minor.patch. e.g. 0.3.0b2 -> 0.3.0.
+              if not on_beta:
+                  raise SystemExit(
+                      f"'finalize' requires a beta base version, but current "
+                      f"version {current!r} has no bN suffix. Use minor / bugfix "
+                      f"/ major to start a new release instead."
+                  )
+              is_beta = False
+          elif bump == "pre-release":
+              # Keep the same base; just walk the beta counter forward.
+              is_beta = True
+              beta_n  = (beta_n or 0) + 1
+          elif on_beta:
+              # We are on a beta of the NEXT release (e.g. 0.3.0b2). The base
+              # major.minor.patch is that upcoming version, so minor/bugfix/major
+              # must bump relative to the LAST STABLE (base - the in-progress
+              # component), not skip a whole version. The common intent from a
+              # beta is 'finalize', so steer the user there rather than guess.
+              raise SystemExit(
+                  f"Current version {current!r} is a beta of the upcoming "
+                  f"{major}.{minor}.{patch} release. To ship it, use bump="
+                  f"'finalize' (-> {major}.{minor}.{patch}). A '{bump}' bump from "
+                  f"a beta would skip {major}.{minor}.{patch} entirely "
+                  f"(e.g. -> {'%d.%d.0' % (major, minor + 1) if bump == 'minor' else '...'}); "
+                  f"that is almost never intended."
+              )
+          elif bump == "major":
               major, minor, patch = major + 1, 0, 0
           elif bump == "minor":
               minor, patch = minor + 1, 0
           elif bump == "bugfix":
               patch += 1
-          elif bump == "pre-release":
-              # Keep the same base; just walk the beta counter forward.
-              is_beta = True
-              beta_n  = (beta_n or 0) + 1
 
           if is_beta:
               if bump != "pre-release":
@@ -88,10 +114,15 @@ jobs:
           PYEOF
           )
 
+          # Derive is_beta from the COMPUTED version (ends in bN?), not the raw
+          # input — so 'finalize' is always treated as stable and a mismatched
+          # beta checkbox can't mislabel the switcher / skip the root redirect.
+          if [[ "$NEW_VERSION" =~ b[0-9]+$ ]]; then IS_BETA_OUT=true; else IS_BETA_OUT=false; fi
+
           echo "new_version=$NEW_VERSION"                  >> "$GITHUB_OUTPUT"
           echo "tag=v$NEW_VERSION"                         >> "$GITHUB_OUTPUT"
           echo "branch=release/v$NEW_VERSION"              >> "$GITHUB_OUTPUT"
-          echo "is_beta=${{ inputs.beta }}"                >> "$GITHUB_OUTPUT"
+          echo "is_beta=$IS_BETA_OUT"                      >> "$GITHUB_OUTPUT"
           echo "Bumping (${{ inputs.bump }}): $CURRENT → $NEW_VERSION"
 
       # ── Bump version strings ─────────────────────────────────────────────
@@ -118,7 +149,7 @@ jobs:
       - name: Update docs/switcher.json
         env:
           VERSION_TAG: ${{ steps.version.outputs.tag }}
-          IS_BETA: ${{ inputs.beta }}
+          IS_BETA: ${{ steps.version.outputs.is_beta }}
         shell: python
         run: |
           import json, re, pathlib, os
@@ -144,7 +175,7 @@ jobs:
 
       # ── Update root redirect for stable releases ─────────────────────────
       - name: Update root redirect (stable releases only)
-        if: ${{ inputs.beta == false && inputs.bump != 'pre-release' }}
+        if: ${{ steps.version.outputs.is_beta == 'false' && inputs.bump != 'pre-release' }}
         env:
           VERSION_TAG: ${{ steps.version.outputs.tag }}
         shell: python
@@ -200,7 +231,7 @@ jobs:
           - Version bumped to \`${TAG}\` in \`pyproject.toml\` and \`docs/conf.py\`
           - \`CHANGELOG.rst\` updated from towncrier fragments
           - \`docs/_root/switcher.json\` updated with the new version entry
-          $([ '${{ inputs.beta }}' = 'false' ] && echo '- Root redirect updated to point to this release' || echo '')
+          $([ '${{ steps.version.outputs.is_beta }}' = 'false' ] && echo '- Root redirect updated to point to this release' || echo '')
 
           ### Review checklist
           - [ ] \`CHANGELOG.rst\` reads well — edit the fragment text directly if needed

{anyplotlib-0.3.0b1 → anyplotlib-0.4.1}/CHANGELOG.rst

@@ -10,6 +10,97 @@ Fragment files in ``upcoming_changes/`` are assembled into this file by
 
 .. towncrier release notes start
 
+0.4.1 (2026-07-26)
+==================
+
+New Features
+------------
+
+- Added ``max_extent=`` to :class:`~anyplotlib.widgets.RangeWidget` and
+  :class:`~anyplotlib.widgets.RectangleWidget` (and the matching
+  ``add_range_widget`` / ``add_rectangle_widget`` factories) — a size cap enforced
+  *while dragging*, so the widget physically stops growing instead of being
+  clamped after the fact. The dragged edge/corner pins and the opposite one stays
+  put, so the selection never jumps under the cursor. ``RangeWidget`` takes a span
+  width in data units; ``RectangleWidget`` takes a scalar (both axes) or a
+  ``(max_w, max_h)`` pair. Default ``None`` leaves widgets unbounded.
+
+  Use it when a widget's size drives real downstream work — e.g. an integrating
+  selector whose span is a number of frames to read.
+
+
+Bug Fixes
+---------
+
+- Fixed the band-style :class:`~anyplotlib.widgets.RangeWidget` being impossible
+  to drag by its body when narrow. Each edge claimed a fixed ±12 px grab zone, so
+  a band under ~24 px wide on screen (routine when zoomed out, or when its span is
+  capped) had no grabbable middle: aiming at the body to translate the band caught
+  an edge and resized it instead. Each edge now takes at most a third of the
+  band's width, leaving the middle third for the move handle. Wide bands are
+  unaffected.
+
+
+0.4.0 (2026-07-18)
+==================
+
+New Features
+------------
+
+- Added :meth:`~anyplotlib.axes.InsetAxes.indicate_point` — the point sibling of
+  :meth:`~anyplotlib.axes.InsetAxes.indicate_region`: a circle-and-cross marker
+  at a data point of the parent plot plus a single leader line to the inset's
+  nearest corner, tracking zoom/pan and hiding the leader while minimized.
+- Added :meth:`~anyplotlib.plot1d.Plot1D.set_legend_fontsize` to control the
+  legend text size on 1-D line plots.
+- Added ``linewidth=`` to every overlay widget constructor and ``add_*_widget``
+  factory on :class:`~anyplotlib.plot2d.Plot2D` and
+  :class:`~anyplotlib.plot1d.Plot1D` (rectangle, circle, annular, crosshair,
+  polygon, vline, hline, range, point) — stroke width in px, default 2, stored
+  and round-tripped like ``color``.
+- Added ``tint=`` to :meth:`~anyplotlib.plot2d.Plot2D.add_layer` and
+  :meth:`~anyplotlib.plot2d.Layer.set` — a ``#rgb``/``#rrggbb`` hex colour that
+  renders the layer as a clear→colour intensity ramp (transparent at low
+  intensity, opaque tint at high, via a 256×4 RGBA LUT) instead of a named
+  colormap; passing ``cmap=`` reverts a tinted layer to colormap display.
+- An :meth:`~anyplotlib.figure.Figure.add_inset` with no title (the default,
+  ``title=""``) now renders with NO title-bar strip at all — a clean bordered
+  plot box, content filling the whole area, instead of a useless empty header.
+  A titled inset is unchanged: its bar renders as before, with click-to-toggle
+  minimize. A title-less inset has no minimize affordance (there is no bar to
+  click), but drag-to-move / drag-to-resize in edit mode still work exactly as
+  before, since those gestures are wired on the inset body, not the bar.
+- Double-clicking a plot's text chrome now reports which element was hit. The
+  ``double_click`` :class:`~anyplotlib.callbacks.Event` gains a ``target`` field
+  naming the hit element — one of ``'title'``, ``'x_label'``, ``'x_ticks'``,
+  ``'y_label'``, ``'y_ticks'``, ``'colorbar_label'`` or ``'legend'`` — so a host
+  can open the right edit affordance for the axis label vs the ticks vs the title
+  vs the colorbar label vs the legend. The axis gutters, colorbar strip and title
+  band each get their own hit-test (2-D panels emit from the separate axis/title
+  canvases; 1-D panels zone-split the single canvas around the plot rect and
+  legend box). A plain plot-area double-click is unchanged and carries no
+  ``target`` (``event.target is None``), so existing handlers keep working.
+- Insets can now be dragged and resized directly in the renderer's edit mode
+  (``edit_chrome``): drag the body to move an inset (a corner-stacked inset
+  converts to a free anchor and its siblings re-stack), or drag the bottom-right
+  grip to resize it (min 64 px per dimension). On release the renderer emits a
+  new figure-level ``inset_geometry_change`` event carrying the final
+  ``anchor``/``w_frac``/``h_frac`` (figure fractions), which
+  :meth:`~anyplotlib.figure.Figure.add_event_handler` handlers can observe to
+  persist the layout. The same geometry is applied programmatically via the new
+  :meth:`~anyplotlib.axes.InsetAxes.set_geometry` (``anchor``, ``w_frac``,
+  ``h_frac``). Off edit mode the affordances are hidden and the inset is inert.
+
+
+Bug Fixes
+---------
+
+- Fixed ``exportPNG`` compositing WebGPU-rendered 3-D panels (``scatter3d`` /
+  ``voxels``) as blank background rectangles — the 3-D render pass is now
+  re-rendered synchronously in-task before the canvas readback, exactly like
+  active-GPU 2-D image panels.
+
+
 0.3.0b1 (2026-07-13)
 ====================
 

anyplotlib-0.4.1/Examples/Interactive/plot_figure_annotations.py

@@ -0,0 +1,87 @@
+"""
+Interactive figure annotations — double-click to add, drag to place
+===================================================================
+
+anyplotlib has a *figure-level* annotation layer that floats above the panels,
+positioned in **figure fractions** (0…1, origin top-left) rather than any
+panel's data coordinates.  Set it with
+:meth:`~anyplotlib.Figure.set_figure_markers`; the supported kinds are
+``"text"``, ``"circle"``, ``"rect"`` and ``"arrow"``.
+
+Turn on ``fig.edit_chrome`` and every annotation becomes draggable in the
+browser.  Combine that with a ``double_click`` handler and you get a simple
+annotate-by-clicking workflow: double-click a feature to drop a labelled
+arrow, then drag it to line it up.  Positions round-trip back to Python via
+:attr:`~anyplotlib.Figure.figure_markers`.
+"""
+import numpy as np
+import anyplotlib as apl
+
+rng  = np.random.default_rng(7)
+data = rng.standard_normal((160, 160)).cumsum(0).cumsum(1)
+data = (data - data.min()) / (data.max() - data.min())
+
+fig, ax = apl.subplots(1, 1, figsize=(520, 520))
+v = ax.imshow(data, cmap="magma", units="px")
+
+# Enable the editable-annotation ("report builder") mode so figure markers are
+# hit-testable and draggable, and the figure emits background/marker events.
+fig.edit_chrome = True
+
+# %%
+# Seed a couple of annotations
+# ----------------------------
+# Each marker is a dict with a ``kind`` and fraction-space geometry.  A text
+# label and an arrow pointing into the image to start with.
+
+fig.set_figure_markers([
+    {"kind": "text", "x": 0.5, "y": 0.06,
+     "text": "Double-click a feature to annotate it",
+     "color": "#ffffff", "fontsize": 14},
+    {"kind": "arrow", "x": 0.20, "y": 0.30, "u": 0.12, "v": 0.12,
+     "color": "#ffd54f", "linewidth": 2},
+])
+
+fig
+
+# %%
+# Double-click to drop a new annotation
+# -------------------------------------
+# On a single-panel figure the panel nearly fills the canvas, so we turn the
+# click's device pixels into a figure fraction with the panel's
+# ``display_width`` / ``display_height`` and append an arrow + label there.
+# Because ``edit_chrome`` is on, the new marker is immediately draggable.
+
+
+def _on_double_click(event):
+    if event.x is None or event.display_width is None:
+        return
+    fx = float(np.clip(event.x / event.display_width, 0.02, 0.98))
+    fy = float(np.clip(event.y / event.display_height, 0.02, 0.98))
+    markers = fig.figure_markers            # current list (a copy)
+    n = sum(1 for m in markers if m["kind"] == "text")
+    markers.append({"kind": "arrow", "x": fx, "y": fy,
+                    "u": 0.08, "v": -0.08, "color": "#40c4ff", "linewidth": 2})
+    markers.append({"kind": "text", "x": fx + 0.08, "y": fy - 0.10,
+                    "text": f"mark {n}", "color": "#40c4ff", "fontsize": 13})
+    fig.set_figure_markers(markers)
+
+
+v.add_event_handler(_on_double_click, "double_click")
+
+fig.set_help(
+    "Double-click on the image to drop a labelled arrow.\n"
+    "Drag any annotation to reposition it (edit mode is on)."
+)
+
+fig  # Interactive
+
+# %%
+# Read the placements back
+# ------------------------
+# After the user drags things around, ``fig.figure_markers`` reflects the
+# current fraction positions — persist them, export them, or feed them into a
+# report.
+
+for m in fig.figure_markers:
+    print(m["kind"], round(m["x"], 3), round(m["y"], 3))

{anyplotlib-0.3.0b1 → anyplotlib-0.4.1}/Examples/Interactive/plot_voxel_grain_explorer.py

@@ -29,7 +29,7 @@ import anyplotlib as apl
 rng = np.random.default_rng(11)
 
 # ── 1. Synthetic 3-D polycrystal: nearest-seed voxel grain map ──────────────
-N = 48                       # volume is N³ voxels, indexed V[z, y, x]
+N = 24                       # volume is N³ voxels, indexed V[z, y, x]
 N_GRAINS = 40
 
 seeds = rng.uniform(0, N, size=(N_GRAINS, 3))            # (z, y, x)
@@ -76,7 +76,8 @@ grain_rgb_u8 = (rgb * 255).astype(np.uint8)               # (N_GRAINS, 3)
 # planes.  This anchors the highlight exactly where the slices intersect,
 # shows real slice contents in 3-D, and scales: the on-plane count is
 # ~3·(N/step)² regardless of N, so it stays fast even for a 256³ volume.
-VSTEP = max(1, N // 48)        # in-plane downsample → ~48² cubes per plane
+VSTEP = max(1, N // 48)        # in-plane downsample, capping at ~48² cubes/plane
+                               # for large N (no downsampling at this N=24)
 
 # Voxel cube size in data units.  A touch larger than VSTEP so the three
 # slabs read as solid sheets rather than a dotted grid.
@@ -140,6 +141,8 @@ v_vol = ax_vol.voxels(
     size=VOXSIZE, alpha=0.55,
     x_label="x", y_label="y", z_label="z",
     bounds=((0, N - 1),) * 3, zoom=1.1,
+    # gpu="auto" (default): ~1.7k cubes is over the ~1k voxel threshold, so the
+    # WebGPU instanced path handles each drag re-slice when WebGPU is present.
 )
 v_vol.set_title("Grain volume — drag a plane to re-slice")
 

anyplotlib-0.4.1/Examples/Markers/plot_transform_markers.py

@@ -0,0 +1,49 @@
+"""
+Coordinate transforms — pin markers to the axes or the screen
+=============================================================
+
+Every ``add_*`` marker method takes a ``transform`` that decides which
+coordinate system its positions live in:
+
+- ``"data"`` (default) — data coordinates; the marker moves and scales with
+  zoom / pan, staying glued to the underlying data.
+- ``"axes"`` — axes-normalised ``(0, 0)`` bottom-left … ``(1, 1)`` top-right;
+  the marker stays in the same corner of the panel no matter how you zoom.
+- ``"display"`` — raw CSS pixels within the panel; a fixed-size decoration.
+
+The ``"axes"`` and ``"display"`` transforms are how you build overlays that
+should *not* track the data — a navigation index in the corner, a scale bar, a
+persistent legend chip.
+"""
+import numpy as np
+import anyplotlib as apl
+
+rng  = np.random.default_rng(1)
+data = rng.standard_normal((128, 128)).cumsum(0).cumsum(1)
+data = (data - data.min()) / (data.max() - data.min())
+xy   = np.linspace(0, 10, 128)
+
+fig, ax = apl.subplots(1, 1, figsize=(480, 480))
+v = ax.imshow(data, axes=[xy, xy], units="nm")
+
+# Data-anchored label — sits at (5, 5) in nm and rides along on zoom/pan.
+v.add_texts(offsets=[(5, 5)], texts=["feature @ (5, 5)"],
+            color="#ffffff", fontsize=12, name="data_label")
+
+# Axes-anchored index — stays pinned to the top-left corner of the panel
+# regardless of zoom (0, 1 = top-left in axes fractions).
+v.add_texts(offsets=[(0.04, 0.96)], texts=["frame 3 / 20"],
+            transform="axes", color="#ffd54f", fontsize=13, name="nav_index")
+
+fig
+
+# %%
+# Try it
+# ------
+# Zoom into the image: the white ``feature`` label moves with the data, while
+# the yellow ``frame 3 / 20`` index stays locked to the corner — because it is
+# positioned in ``"axes"`` coordinates.
+
+fig.set_help("Zoom in: the corner index stays put; the data label moves.")
+
+fig  # Interactive

anyplotlib-0.4.1/Examples/PlotTypes/plot_gpu_voxels.py

@@ -0,0 +1,82 @@
+"""
+GPU-accelerated voxels
+======================
+
+:meth:`~anyplotlib.Axes.voxels` renders shaded translucent cubes for a
+volumetric field.  With ``gpu="auto"`` (the default) anyplotlib uses WebGPU
+instancing when a GPU is available and the cube count is large, so hundreds of
+thousands of voxels stay interactive; otherwise it falls back to the Canvas2D
+path.  Read :attr:`~anyplotlib.Plot3D.gpu_active` after the first frame to see
+which path was chosen.
+
+Here we build a dense spherical shell — enough cubes that the WebGPU path
+kicks in — and drop a draggable :class:`~anyplotlib.PlaneWidget` through it as
+a slice selector.
+"""
+import numpy as np
+import anyplotlib as apl
+
+# %%
+# Build a volumetric field
+# ------------------------
+# Voxel *centres* are passed as three flat coordinate arrays (not a dense 3-D
+# grid), so you only send the cubes you actually want drawn.  We keep the
+# voxels inside a spherical shell and colour them by radius.
+
+N = 64
+g = np.arange(N)
+Z, Y, X = np.meshgrid(g, g, g, indexing="ij")
+r = np.sqrt((X - N / 2) ** 2 + (Y - N / 2) ** 2 + (Z - N / 2) ** 2)
+shell = (r > N * 0.30) & (r < N * 0.42)   # a hollow sphere
+
+xs, ys, zs = X[shell], Y[shell], Z[shell]
+print(f"{xs.size:,} voxels")  # tens of thousands → GPU path under gpu='auto'
+
+# Colour by radius with the viridis-ish default cycle mapped through intensity.
+t = (r[shell] - r[shell].min()) / (np.ptp(r[shell]) + 1e-9)
+colors = np.stack([0.2 + 0.8 * t, 0.4 * np.ones_like(t), 1.0 - 0.8 * t], axis=1)
+
+fig, ax = apl.subplots(1, 1, figsize=(560, 520))
+vol = ax.voxels(
+    xs, ys, zs, colors=colors,
+    size=1.0, alpha=0.35,
+    bounds=((0, N - 1),) * 3,
+    azimuth=-55, elevation=28, zoom=1.1,
+    gpu="auto",                 # WebGPU when available, Canvas2D otherwise
+)
+vol.set_title("Spherical shell — drag to rotate, scroll to zoom")
+
+# %%
+# Add a slice-selector plane
+# --------------------------
+# A :class:`~anyplotlib.PlaneWidget` is a draggable axis-aligned plane.  Voxels
+# lying on it render more opaque, so the current slice pops out of the
+# translucent volume.  Drag it along z in the browser, or move it from Python.
+
+plane = vol.add_widget("plane", axis="z", position=N // 2,
+                       color="#40c4ff", alpha=0.18)
+
+
+@plane.add_event_handler("pointer_move")
+def _on_slice(event):
+    # Fires while the plane is dragged; pw.position holds the live slice index.
+    print("slice at z =", round(plane.position, 1))
+
+
+fig.set_help(
+    "Drag: rotate · Scroll: zoom · R: reset view\n"
+    "Drag the blue plane to slide the z-slice through the shell."
+)
+
+fig  # Interactive
+
+# %%
+# Which render path ran?
+# ----------------------
+# ``gpu_active`` is populated once the browser reports back after the first
+# frame.  It is ``True`` when the WebGPU instanced path is live, ``False`` on
+# the Canvas2D fallback, and ``None`` before the first frame (as when this
+# gallery page is built headlessly).  Force a path with ``gpu=True`` /
+# ``gpu=False`` if you need determinism.
+
+print("gpu_active:", vol.gpu_active)

anyplotlib-0.4.1/Examples/PlotTypes/plot_step_and_log.py

@@ -0,0 +1,43 @@
+"""
+Step lines and log-scale spectra
+================================
+
+Two 1-D options that suit spectral data: a **mid-riser step** line (constant
+within each bin, jumping at bin midpoints) via ``linestyle="step-mid"``, and a
+**logarithmic y-axis** via :meth:`~anyplotlib.Axes.semilogy` (or
+``ax.plot(..., yscale="log")``).
+"""
+import numpy as np
+import anyplotlib as apl
+
+# A noisy binned spectrum.
+rng = np.random.default_rng(0)
+energy = np.linspace(0, 20, 60)
+counts = (np.exp(-(energy - 6) ** 2 / 4) * 1000
+          + np.exp(-(energy - 13) ** 2 / 8) * 400
+          + rng.uniform(0, 20, energy.size))
+
+# %%
+# Step line
+# ---------
+# ``linestyle="step-mid"`` draws a horizontal segment centred on each x value
+# with vertical risers between them — the standard way to show histogram-like
+# spectra without implying interpolation between channels.
+
+fig, ax = apl.subplots(1, 1, figsize=(560, 340))
+ax.plot(counts, axes=[energy], color="#4fc3f7",
+        linestyle="step-mid", label="counts")
+
+fig
+
+# %%
+# Log y-axis
+# ----------
+# ``semilogy`` is shorthand for a log y-scale, which brings out the small
+# secondary peak that the linear plot flattens.  Combine it with the step line
+# for a classic spectroscopy view.
+
+fig2, ax2 = apl.subplots(1, 1, figsize=(560, 340))
+ax2.semilogy(counts, axes=[energy], color="#ff7043", linestyle="step-mid")
+
+fig2