Hi All, Some work has already been done to implement a repeat capture mode for PulseView which automatically rearms the trigger for repeated captures, with an adjustable time delay between when each capture segment completes and the next one starts.
https://sourceforge.net/p/sigrok/mailman/sigrok-devel/thread/cdf7c54b-c509-9162-34fb-2709f5756437%40BrianAndChristine.com/ This feature has not been merged yet, so I'm continuing work on it following the suggestions in the prior email exchange to better fit the UI and architecture. Changes are on github: https://github.com/sigrokproject/pulseview/pull/38 This is a work in progress and I would appreciate some guidance in getting it merged, since I agree that it is a useful feature. Code on this branch can compile and run, but has a problem switching the segment display mode while a repeat capture is running. Open questions - Session states: The new repeat mode means that a capture session may return to `Running` state repeatedly. However `pv::views::trace::View` expects the transition to `Running` state to happen only once per capture and uses it as a signal to reset the state of the UI which interferes with segment display. More states can be added to the session but I don't know whether it is best to do so. See comments in view.cpp. - Configuration UI: Layout, labels, defaults - Icons - Terminology of this feature (both in UI and in code): "Repetitive trigger rearming" is descriptive but verbose. "Retriggering" is concise but doesn't convey the fact that the repetitive capture might not be retriggered immediately after the delay time, rather the trigger condition is *rearmed* and capture may start some time later. Thanks, Ivan
_______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
