|
From: Ron B. <rbu...@ea...> - 2018-10-29 23:18:56
|
Sadly, setting up this filter from the UI doesn't work as far as I can tell. Neither does the filter itself work when I do that, nor does a save or save-as actually put the filter into the .gtkw file. It was the very first thing I tried. I believe the guy who wrote this code manually put the filter into the .gtkw file somehow, and so I've just be copying and modifying his .gtkw file. It's a mystery to me how he figured out how to do it. Of course, it's always possible that I'm just not doing it correctly, and that it's really much simpler than I imagine. :-) At any rate, it doesn't matter to me, because with enough trial and error I managed to get it to work. It needed mods both within the filter and within the .gtkw file(s). Thanks for your assistance, Tony! -- Ron On 10/29/2018 04:14 PM, by...@nc... wrote: > Ron, > > Re-import by hand whatever signals are in listed in your original gtkw > file. That is, import those signals all over again and then save the > new gtkw file for use with FST dumps. Those groups end warnings > probably are because you either explicitly created collapsable groups > or double-clicked on a signal name in order to expand a signal (and > possible collapsed it again prior to save). > > If this is unacceptable, then all you have to do is not use FST. I > don't really suggest this as FST is faster and better. > > Signal naming incompatibility is not a bug in the gtkwave program, but > is a result of how those names are stored in the dumpfile (explicit > flat earth vs hierarchical), so I won't fix this as it's not worth the > effort. > > Thanks, > -Tony > |
