-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File I/O support #3
Labels
core
Core application logic
Comments
Why not using something "standard" like sigrok file format for in/out and decoders ? |
azonenberg
added a commit
that referenced
this issue
Feb 26, 2020
…ed; window dimensions, waveform group, and splitter config are serialized. No waveform area config or actual waveform data yet. See #3.
azonenberg
added a commit
that referenced
this issue
Feb 29, 2020
azonenberg
added a commit
that referenced
this issue
Mar 5, 2020
azonenberg
added a commit
that referenced
this issue
Mar 5, 2020
…eparate function. Began work on measurement serialization. See #3.
azonenberg
added a commit
that referenced
this issue
Mar 5, 2020
azonenberg
added a commit
that referenced
this issue
Mar 13, 2020
… file but not configure them or set up any UI. See #3.
azonenberg
added a commit
that referenced
this issue
Mar 14, 2020
…ession" to load a file directly as an argument. Implemented protocol decoder loading. See #3.
azonenberg
added a commit
that referenced
this issue
Mar 14, 2020
…g as we have no groups or splitters. See #3.
azonenberg
added a commit
that referenced
this issue
Mar 14, 2020
azonenberg
added a commit
that referenced
this issue
Mar 15, 2020
…there's no load support yet). See #3.
azonenberg
added a commit
that referenced
this issue
Mar 15, 2020
…econnecting to an existing scope. See #3.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should support both old-school CSV as an interchange format and a protobuf-based (?) native serialization format.
File format design is nontrivial because channels may be sparse, have different sampling rates, etc. We should also save protocol decoder config in some way.
The text was updated successfully, but these errors were encountered: