Fix issues with waveform viewer documentation and mention Surfer #1259
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
|
I want to install and try surfer before approving this change. |
Author
|
Sure. You can also try it in the browser: https://app.surfer-project.org/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There were some inconsistencies in the documentation regarding file formats. "Use the "-fst" extended argument to
activate LXT output" etc.
I also took the liberty to mention our waveform viewer Surfer and therefore renamed the page to "Viewing Waveforms". Still, examples consider GTKWave and there is no Surfer screen shot etc. Still, as Surfer runs on a few platforms where it is hard to get GTKWave to run, I thought it was useful for Icarus Verilog users to know that there are options.