You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are developing an alternative wave form viewer: https://gitlab.com/surfer-project/surfer and once it is mature enough, it would be nice to add support for it in VUnit. Right now there are the --gtkwave-fmt and --gtkwave-args arguments that determines which format is used and how GTKWave is called. However, I'd like to open a discussion about what the best way to implement a switch for wave form viewer would be?
My spontaneous idea is to rename --gtkwave-fmt to --wave-fmt or --viewer-fmt (still supporting both, but only document the latter) and then have a --viewer-argument (which may default to GTKWave). Possibly also rename --gtkwave-args to --viewer-args and pass whatever is there to the select viewer?
Any ideas or input regarding this?
The text was updated successfully, but these errors were encountered:
We are developing an alternative wave form viewer: https://gitlab.com/surfer-project/surfer and once it is mature enough, it would be nice to add support for it in VUnit. Right now there are the
--gtkwave-fmt
and--gtkwave-args
arguments that determines which format is used and how GTKWave is called. However, I'd like to open a discussion about what the best way to implement a switch for wave form viewer would be?My spontaneous idea is to rename
--gtkwave-fmt
to--wave-fmt
or--viewer-fmt
(still supporting both, but only document the latter) and then have a--viewer
-argument (which may default to GTKWave). Possibly also rename--gtkwave-args
to--viewer-args
and pass whatever is there to the select viewer?Any ideas or input regarding this?
The text was updated successfully, but these errors were encountered: