Bug 634 - Run/Stop should not be the same button
Summary: Run/Stop should not be the same button
Alias: None
Product: PulseView
Classification: Unclassified
Component: Acquisition (show other bugs)
Version: unreleased development snapshot
Hardware: All All
: Normal normal
Target Milestone: ---
Assignee: Nobody
Depends on:
Reported: 2015-08-25 20:18 CEST by Martin Ling
Modified: 2016-10-06 11:17 CEST (History)
3 users (show)


Note You need to log in before you can comment on or make changes to this bug.
Description Martin Ling 2015-08-25 20:18:44 CEST
Currently the Run button is the same as the Stop button - once pressed it changes from Run to Stop and vice versa.

This is fine in principle except that it can also spontaneously turn from Stop to Run, when the configured sample limit has been reached.

This has now caught me out several times - I set a reasonable limit, press Run, catch the event I want, and then press Stop, only to find it's changed to Run the instant before I pressed it and I'm now overwriting my capture.

I think these should be two separate buttons.
Comment 1 Soeren Apel 2015-08-25 20:21:51 CEST
To me, this issue would disappear with http://sigrok.org/bugzilla/show_bug.cgi?id=624 being solved:

-) Set sample limit to "unlimited"
-) Start capturing until event occurs
-) Press button to stop capture

Would this be an acceptable solution for you?
Comment 2 Martin Ling 2015-08-25 20:47:28 CEST
Not all devices can support unlimited capture - many capture into internal buffers of a fixed size.

Even where not required by the hardware, there are plenty of reasons to use a fixed sample count and it should be possible to stop a capture without this risk of accidentally restarting it.
Comment 3 Uwe Hermann 2015-08-28 19:03:37 CEST
Agreed, the same has happened to me as well multiple times (lost acquired data).