Skip to content
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

Add command to reload VCD #12

Open
Lramseyer opened this issue Jul 4, 2024 · 3 comments
Open

Add command to reload VCD #12

Lramseyer opened this issue Jul 4, 2024 · 3 comments

Comments

@Lramseyer
Copy link
Owner

@hi0t

I couldn't find a button or command to reload the vcd. If there is no such function, it would be a good idea to add it. If the data file has been updated, you have to close it, then open it and configure viewing again.

@Lramseyer
Copy link
Owner Author

Lramseyer commented Sep 5, 2024

I haven't forgotten about this! I am in the process of migrating to the node version of fs.read() which should allow me to get around the 2GB limit, as well as reloading vcd files.

There are 2 types of reloads that I was thinking about implementing:

  • "Fast" reload - where the file has been appended, and we only need to load in the new data
  • Total reload - where the vcd file was overwritten.

I assume that the "fast" reload is your intended use case?

@hi0t
Copy link

hi0t commented Sep 9, 2024

I rather meant a full reload. The scenario is as follows - we make some edits to the test bench (this may even be deleting and adding signals). After launching the modified test bench, we want to press a certain button that will reboot the vcd. Accordingly, the already configured signals in the current window should remain and simply update their state. It is likely that vaporview should try to find all the already configured signals by name in the updated vcd and display them again.

@Lramseyer
Copy link
Owner Author

OK, I'll look into full reload!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants