common events trigger too fast

If I run a particular trace for an event I expect to be trigger very often (say expected 1000Hz) then as soon as magic trace starts recording, it stops. As a consequence I get a very limited history.

While my software trigger could be written to only probabalistically trigger I'd like it if magic trace had an option "refuse to trigger until we've been recording for TIME-SPAN".

Review how magic trace handles software triggers and the transition into recording, focusing on what happens when a common event fires immediately. Define where a configurable recording delay would apply, then verify that frequent events no longer end the trace before the requested time span has elapsed.

Written by the indexing model from the issue text.