Lloyd Ramseyer
Lloyd Ramseyer
I'm going to close this issue, since this will be implemented differently. Take a look at this project, as it interacts with the [Vaporview API](https://github.com/Lramseyer/vaporview/blob/main/API_DOCS.md). [https://github.com/heyfey/sv-pathfinder](https://github.com/heyfey/sv-pathfinder)
I'm going to be honest, I don't actually have any VCD files with analog data in them to test this out ...which is a little ironic considering all of the...
OK, so it sounds like you're asking for multi bit waveforms to be viewed as analog data? I should also support 2's compliment while I'm at it. I'll work on...
Thanks @tafkos for the test file! It really helped. These features are in the 1.3.0 pre-release build. Give it a try and let me know what you think. I'll get...
Fixed in 1.3.0
I use a parsing library to load waveform dumps, and to reload a document, it would need to re-parse the netlist hierarchy. For small files, this won't be a problem....
I haven't forgotten about this, and I will be looking into this issue when I get back from Latch Up. But I should point out (in case you're unaware) that...
Good news! This feature will be in the 1.4.0 release. You can download test builds with the feature enabled [here](https://github.com/Lramseyer/vaporview/releases/tag/1.4.0-rc).
1.4.0 is released and on the VScode marketplace, so I will close this feature!
This is definitely something I have thought about and plan to implement. I will probably allow users to expand multi-bit signals as if they were modules. My only concern is...