Skip to content

v0.4.3 — smooth stack scrolling

Latest

Choose a tag to compare

@sleuthy-sloth sleuthy-sloth released this 26 Oct 14:58

v0.4.3 — smooth stack scrolling

Scrolling through image stacks no longer re-decodes a file for every step. The radiology
report's "scrolling feels jerky and skips frames" complaint is fixed in the decode pump, with
a regression test that fails without the change.

  • Decoded-frame cache (48 slices or 256 MB, whichever binds first; farthest-from-screen
    evicted): stepping into a decoded slice shows instantly, and scrolling back over shown
    slices costs a copy, not a file read and a decompress. Cleared on any series or folder change.
  • Four-slice look-ahead on a dedicated prefetch pool keeps the next few slices decoded
    ahead of the wheel; the requested slice still never queues behind speculative work.
  • Whole-notch wheel handling: notched wheels behave exactly as before; high-resolution
    wheels and trackpads accumulate to real notches instead of teleporting dozens of slices per
    flick, and trackpad pixel deltas now carry direction instead of always reading as one step down.
  • Per-series annotation cache: the sidecar JSON is read once per series and invalidated on
    save, instead of being re-read on every presented slice while you scroll.
  • The window/level maths is unchanged in output: the branchless form of the three-way clamp was
    verified byte-identical to the previous loop over 104,994 differential cases including
    degenerate windows and boundary pixels, on top of the pinned core checks.

What is NOT verified

  • The exe has never been launched on a Windows machine (docs/VALIDATION.md unchanged on that
    point). CI compiles it and runs the test suite offscreen; no human has scrolled with it.
  • Scroll feel on real hardware (notched vs trackpad) has not been measured on a device; the
    wheel-remainder behaviour is covered by the unit test at the scheduling level only.
  • One offscreen test run on the Linux Pi segfaulted once and never recurred across 17
    subsequent runs; the cause is unknown and unreproduced.
  • Anything VTK remains behind the build flag and is not in this package.