On Sun, Sep 4, 2016 at 11:40 AM Uwe Hermann <[email protected]> wrote:
> On Sat, Aug 06, 2016 at 09:34:21PM +0000, Mike Meyer wrote: > > I've just pushed an all-singing, mostly dancing csv output module to > The "Xsigrok" option is gone for now, that shouldn't really be needed. > The csv input module should ideally be able to automatically load > anyhing the csv output module produces, worst-case with the proper > settings for delimiters etc. If that's not the case, input/csv might > need some fixing, I guess. > That's not the case at all. Right now, csv input doesn't handle analog values at all. That's why I never submitted a patch - this stuff was waiting on me to get csv input working properly. That's also why the comment was Xsigrok - X'ed out until I figured out if it was needed, and what it should be if so. I've been trying to figure out how that should work, and had about decided that the output module needs a change to support it properly. The problem is that analog columns have meanings beyond "on/off". To set that properly, it really needs headers saying what they are. So the default csv output should include headers ala the analog output module, and then the CSV input can check those to figure out column values/types. I also need to figure out (or be told) what should happen if the headers aren't there. That's just the basics, though - it also needs to handle an optional time column, and possibly a more flexible column selection that start/count.
------------------------------------------------------------------------------
_______________________________________________ sigrok-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sigrok-devel
