Skip to content

v0.4.2 — overlay text off the GL path, VTK behind a flag

Choose a tag to compare

@sleuthy-sloth sleuthy-sloth released this 25 Oct 18:48
· 5 commits to main since this release

Clivus v0.4.2. Free software (GPL-3.0-or-later); research and engineering tooling, not a certified
medical device, and nothing here has been validated for diagnosis.

0.4.1 answered four issues a radiologist hit in 0.4.0. Three of them were reproduced and fixed against a
test. The fourth — on-screen text coming out garbled — never reproduced here, so 0.4.1 shipped a layout
fix that reduced the damage without touching the cause. This release attacks the cause.

What changed

Overlay text no longer goes through the GPU. The corner blocks, measurement labels and ROI statistics
used to be painted inside the GL paint pass. On the reporter's machine individual glyphs came out sheared
into diagonal hatching while every other piece of text in the app stayed crisp, which points at the GL
glyph path rather than at the font. Those overlays now live in a transparent child widget layered over
the canvas and are painted by the same raster engine as the rest of the interface: no GL text, no
backend-specific glyph rasteriser. The overlay takes no mouse input, so dragging to window, panning and
measuring all still reach the canvas underneath.

A new overlay_widget test pins the arrangement: the child exists, covers the canvas exactly, ignores
the mouse, never takes keyboard focus, paints the corner text through the raster engine — and paints
nothing once the frame is gone. Removing the child makes the test fail, which is the only reason to
believe it protects anything.

What the test cannot tell you is whether the reporter's specific Windows backend is now happy. That
needs their machine, and it is the one claim this release deliberately does not make.

The VTK work lands, switched off. Phases 1–4 of the migration are in the tree: the volume and frame
handover with a DICOM-correct value-of-interest lookup table, a frame-based 2D canvas, three linked MPR
planes, GPU volume rendering, and a View menu entry that opens them. None of it is in this exe. It builds
only with -DCLIVUS_BUILD_VTK_CANVAS=ON; the app keeps drawing with the original canvas, and the legacy
canvas stays the default until pixel parity is proven.

Landing it now bought the thing it never had: compilation. Against VTK 9.3 the handover test passes, and
the parity gate — the legacy render() bytes compared with the VTK pipeline, normal and inverted, narrow
and wide windows — matches within one grey level with colour bytes exact. The Qt widgets remain
uncompiled anywhere, because Debian's VTK is built against Qt 5 and this app is Qt 6; that needs a VTK
built with Qt 6 on the Windows or macOS builder.

What is not verified

  • The garbled-glyph report itself. The code path is gone; the reporter's machine has not seen this
    build. Nothing here should be read as "that backend is fixed".
  • The packaged exe has not been launched on Windows hardware. CI compiles and packages it; the
    smoke test on a real desktop is still the open item in docs/VALIDATION.md, exactly as in 0.4.1.
  • The VTK widgets. Reviewed line by line, never compiled: no host available to us has a Qt 6 VTK.
    Experimenting with them is not possible in this build anyway.
  • The parity gate has a blind spot. It cannot see a width vs width - 1 range error — that
    mutation passes with a max difference of one grey level, and it is precisely the DICOM difference the
    migration doc cites to justify its own lookup table. Gross errors it does catch: an ignored inversion
    fails at 255 levels across 3069 of 3072 pixels. Both facts, with the mutation runs, are in
    docs/VTK-INTEGRATION-EVIDENCE.md; testing the lookup table's bounds directly is follow-up work.

Pi build for this release: 285/285 objects, ctest 31/31 offscreen, including the new target.


Package note: the zip was refreshed after publication so that READ-ME-FIRST.md tells you to run the included vc_redist.x64.exe first on a machine that has never had a C++ application installed (clivus.exe imports MSVCP140.dll and VCRUNTIME140.dll). The executable is unchanged.