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.
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?
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.
Agreed, the same has happened to me as well multiple times (lost acquired data).