|
From: Stephen W. <st...@ic...> - 2015-05-13 17:06:41
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 There is the existing $dumpflush command. If it doesn't flush the data out to the file, then adding an fflush() in there somewhere should do the trick. I do not, in general, think the scheduler should be flushing the vcd output, that could potentially be a nasty performance hit. But I see where you are coming from, you want to sometimes flush and refresh an interactive display. I can think of a couple ways of handling that, but the easiest I think is to somehow decide at the start that you want unbuffered output (for example, a +arg to vvp) and turn off buffering to the fopened stream that the vcd dumper uses. On 05/13/2015 09:52 AM, Joshua Street wrote: > I am trying to hook icarus into a graphviewer program, but I would > like to be able to periodically update what's on screen. And yes, > I realized that I am probably not intended to make files in vvp > reliant on those in the vpi folder. > > Is there a recommended path that I could use? I notice that in the > stop handler of vvp you call the $dumpflush command. Anyway after > reading a bit more of the documentation, I think the best way to > get the behavior I want might be to just add a command to the vpi > library and then call it. - -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep." -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlVThJgACgkQrPt1Sc2b3ins2QCgk3REPAV19Wef5R/EdXUD6d0K bhEAoMwY8VDTOailIat47SOzW3vfeqaI =TArt -----END PGP SIGNATURE----- |