Uwe, abraxa, I am growing weary of rebasing my "repeat" branch of pulseview, and rebuilding just so I can have a repeating capture for my daily work.
My typical use case is working on a MIDI system where I use a logic analyzer to monitor a logical MIDI signal that is physically on a SPI link. I sequentially press a sequence of (organ) keys which generate the (hopefully) respective MIDI sequences to verify functionality. I invoke the repeat mode for the logic analyzer so that I don't have to also continually retrigger pulseview. I think this sort of scenario is quite common with people using logic analyzers for all sorts of things. It has been so for me over the last decade or so. I prefer to use pulseview for all my logic analyzers, except for this one issue. I am pleading for this feature to be ported into pulseview in some form. I think this being missing is the single most important omission in pulseview. I don't think my branch is the best possible way to do it, and I don't care if you don't do it exactly as I did it, but I think it is important that it be done. I am certain that others feel this way too. What is important is that it work for all logic analyzers, whether they provide internal support for it or not. Especially the FX2 class, which is what I usually use for this particularly undemanding task. My version operates by simulating clicking on the run button on the controls. That way it inherently can operate any logic analyzer. The biggest drawback to this approach is that after the rearm timer expires, the trace display goes away until there is a new trigger event, and that is undesirable. It would be better if the display remained visible until the new data is delivered from libsigrok. That may dictate the retrigger action be taken within libsigrok, which is OK with me. Also, the way I overloaded the run/stop button to also enable/disable the repeat action is rather opaque and could probably be improved by changing the run/stop button to a run/stop/rearm button, or perhaps two separate buttons. I am not overly proud of how I did it, I just wanted to minimize changes for the branch. abraxa, I recall you wanted to redo this area anyway, so I invite you to do so. I would be willing to help work on it, but I don't know where you want to take it. I will drop by IRC tomorrow if you want to talk about it. I left this on the mailing list because I think it is too long for an IRC message, and wanted it more persistent. My repeat branch is at: https://github.com/Cenkron/pulseview branch repeat I have already rebased it to the most recent pulseview master. Brian Johnson, aka Cenkron ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
