On Sun, Oct 9, 2016 at 2:25 PM Roman Seidl <[email protected]> wrote:
> Dear Soeren!
> Does handling a scope need for so many workarounds? I thought that this
>
> would be quite easy assuming one uses a library like sigrok?
>
I've been thinking about using libsigrok for an oscilloscope as well, and
think the better approach is to extend pulseview to be more like an
oscilloscope. Making it a full-blown, multi-channel scope would be a pita.
But I think you can get something really useful out of it.
The first step would be adding more capture limit types to pulseview. They
exist in the library and are supported by sigrok-cli, but there's no way to
use them in pulseview.
Not clear this is needed, but the "Frames" option would probably add a lot
of useful code. Because the behavior you want is to render each frame as it
comes in. I've played with GPL and the new csv output code and some
external scripts to make GPL do this, and it seems to work reasonably well.
Not clear how hard it'd be to make it work properly in pulseview.
But this requires both C++ and GUI work, neither of which I'm comfortable
with.
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
