fmTrace 1.86

1.86 (762) 23 August 2026

State probes on by default, one IPC socket per FileMaker process, and a Tracking tab that links straight into Script History.

State probes are captured by default. When a script step has no value of its own to record, fmTrace now falls back to a state probe, so steps that used to appear empty on the timeline carry something useful. The menu toggle that used to gate this is gone — it is simply on.
Script History from the Tracking tab. The active database now has a direct link into its own Script History window, so you can go from a recording to how the script changed without hunting for the right file.
fmtrace:// deep links. The viewer registers a URL scheme, so a link can open Script History on a specific database. A cold launch routes correctly and opens a window rather than starting up empty.
Capture kind on every eval row. Each captured value now records which class of capture produced it, and the viewer shows it.

The value checkbox appears for every row that captured a value. Some steps that had a captured value were not offering the checkbox that opens it in the inspector.
One IPC socket per FileMaker process. The socket is now named ipc-<pid>.sock, so two copies of FileMaker Pro no longer contend for the same endpoint.
An empty captured value is stored as empty, not as nothing. A step that legitimately produced an empty string now shows as empty rather than as having captured nothing at all.
UTF-8 text handed to FileMaker is declared as UTF-8. Non-ASCII values in captured text no longer come back mangled.
Eval-target lookup is gated on the step’s resolved type, and the type is resolved once and shared — a step whose type could not be resolved no longer produces a bogus capture.

The .fmtrace schema is now version 4: step_runs carries eval_kind, and eval_kind accepts probe. Recordings from earlier builds still open.