fmTrace 1.87

Community

The fmTrace mailing list, its feed, and how to reach us.

Mailing list

Discussion, release announcements and beta notes happen on the fmTrace mailing list at fmtrace@groups.io.

SubscribeSend an empty message to fmtrace+subscribe@groups.io
Postfmtrace@groups.io
Archivehttps://groups.io/g/fmtrace
RSShttps://groups.io/g/fmtrace/rss

Feeds

Two feeds, for two different things:

  • List RSS — every message posted to the mailing list, discussion included.
  • Releases RSS — one entry per fmTrace release, nothing else. Subscribe to this one if you only want to know when there is a new build.

Support

Write to support@fmtrace.com for anything that does not belong on a public list — crash reports, licensing, a recording you would rather not post to an archive.

Reporting a bug well

fmTrace is in beta and bug reports are genuinely useful. A good one contains:

  • The .fmtrace recording, if the problem showed up in a recording. It carries the scripts, the timings and the captured values, so it usually answers most of the questions we would otherwise ask. Read what is in one before you send it — recordings contain real field data.
  • The fmTrace version, from the About tab in the fmTrace panel.
  • The FileMaker Pro version, and whether the file was local or hosted.
  • What you were doing when it happened, and what you expected instead.
  • The crash report, if it crashed. macOS writes these to ~/Library/Logs/DiagnosticReports/.

Keep the recording you send under roughly 100,000 steps — see Limits.