[thebhef]

Export stopped being "open the OS picker and block the GUI until the
file is on disk". It now opens a dialog that settles the two things a
picker cannot express — what the file is called, and which slice of the
capture goes into it — and then hands the write to a host thread that
reports progress and can be stopped.

The name is the template machinery from the previous change, given a
surface: an editable template with the resolved name beside it as a
label. The preview is the host's answer (preview_export_template), not
a second implementation of the tokens in JS, so an invalid token or
strftime format is rejected with the host's own message and Export… goes
disabled. The template the export was made with is remembered, alongside
the folder and the format.

The format is still chosen in the picker, which is where people
expect it. The sticky last-used format reaches it as filter order,
because the order a save dialog is handed its filters is the only handle
there is on which one it opens with.

The range defaults to both bounds unset: the whole capture, up to
the live edge when the write finishes. A timeline over the capture's
extent carries the bounds, with the capture's own events as clickable
ticks and presets for the whole capture, the trailing 1/5/30 minutes,
and the window a plot is showing. Each bound is also a text field taking
HH:MM[:SS] or bare seconds from the start; a bound sitting on an event
reads back as that event. A capture with no wall-clock anchor takes and
shows seconds-from-start only — there are no instants to name (ADR
0024).

The bound fields are deliberately not the shared Combobox. That
control is a filtered select: its text box is an fzf filter and Enter
prefers the matching option to what was typed, so typing a time selected
the event whose rendered time happened to fuzzy-match it. Here the typed
text is the primary input, so the field keeps the anatomy and inverts
the precedence.

Host-side, save_capture returns as soon as the write starts.
ExportRun carries the three things that are about how a capture is
written rather than about its format — the range predicate, a paced
progress sink, and a cooperative cancel flag — and both writers take
one. The range bounds every content kind alike (frames, notes, and
MDF's file-backed signal samples) so an exported slice is one consistent
capture whose file starts where the slice does. cancel_export flips
the flag, the writer stops at its next frame, and the partial file is
removed: neither writer uses a temp sibling, so a cancelled export
otherwise leaves a truncated capture wearing the name the user chose.
That is the opposite of a cancelled import, which keeps what it read,
and both doc comments now say why.

Worth a reviewer's attention: ExportRun's progress sink is a
Box<dyn Fn> rather than the AppHandle it looks like it should be.
An AppHandle field would be part of the struct's drop glue, and the
writers' tests construct an ExportRun — which linked Tauri's whole
window graph into the lib test binary, whose loader then failed on
comctl32!TaskDialogIndirect (side-by-side ComCtl32 v6, which a test
binary has no manifest for). The test binary would not start at all.
The sink keeps the emitting closure reachable only from the command
that builds it.

Also here: the capture's extent as a host command rather than something
the dialog derives from rows it fetched, the plot's current x window
published for the one preset that needs it, and the status-bar chip that
reports the write and carries its Cancel.

[thebhef]

• Filter the unit picker, and let a composed kind offer its whole class #509 : 2 dependent PRs (#510 , #520 )
• Read the whole unit table out of the library instead of typing it #508
• Name the project in each project-caches row; Delete becomes two-stage #507
• The settings view re-reads what it shows and keeps its place #506
• Draw plot sample markers as squares, collapsed per pixel column #505
• Draw the plot's hover chrome on an overlay canvas #504
• Close the palette before running the picked command #503
• Plumb empty plot areas, per-area event-marker base, and an Events chip #501
• Move the cursor and event readouts out of the data area into gutters #500
• Mark every served sample, and make an enum lane an ordinary series #499
• Serve every window as first, last, min and max, and drop the categorical reducer #498
• Measure what a plain min/max serve does to a held enum code #497
• Filter the Trace panel's rows with the same fzf, in both modes #496
• Rank the trace's rows host-side with the app's own fzf #495
• Let a bus explicitly set to no interface connect as unbound #494
• Let regular collapse/expand work while the database/RBS filter is active #493
• Groom five tasks: four out of the user feedback, plus the trace filter #492
• close out math signal, python server client, export dialog #475
• The example captures are plain git blobs, not LFS objects #490
• The local hardware sidecar is named for what it is, not for one library #489
• The anchor index folds on the flush cadence and survives a relaunch #487
• A BLF export walks the store in chunks instead of snapshotting it #486
• Compose a unit from the ones the app already knows #485
• A pressed chip inside a segment reads as pressed, in every theme #484
• Icon controls and the run toggle replace text buttons in the project panel #483
• A unit is picked as a base and a prefix, wherever one is chosen #482
• A unit is a base unit and a prefix, and every function derives one #481
• The signal mapping panel flags the unit strings nothing can place #480
• The math editor sets the scaling, and the settings view says what a unit string means #477
• A math signal's unit becomes the target its operands convert to #476
• Math signals reach the plot, the signal views and an MDF export #474
• Math signals are created and edited in place under the Computed branch #473
• Math signals compute host-side as a fourth decode provenance #472
• The logger folder's file gridview lists what it holds, recursively #471
• A project logger writes the capture to file while it is connected #470
• An export dialog names the capture and its slice, and the write runs in the background #469 👈 (View in Graphite)
• Host-side template resolution and sticky state for log export #468
• Accept a cannet server from the command line #488
• Correct delivered timestamps for the peer's clock, and detect servers #467
• A python-can application opens a cannet bus by naming a trusted server #466
• Make the wire protocol state its version, and every client check it #491
• The database panel's search box takes a click anywhere in the box #479
• Ctrl+F finds in the settings panel #478
• misc feedback + planning updates #464 : 1 other dependent PR (#465 )
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.