>>Tell me if you have any suggestion. yes I have something, but I do not know if this the correct discussion round.
I say something what I have seen for long time. This information is from my deeper brain. Gtkwave has included shared memory functions. (I think it is only possible under linux) If ghdl can store the signal in a shared memory the current signals can be refreshed by gtkwave directly into the screen. This is interacting process. The use can follow the simulation online. Rene Am 23.07.2016 um 11:21 schrieb Jonas Baggett: > Hello, > > I made a roadmap for the signal selection feature : > > Version 1.0 : > - Finishing code review with Tristan > - Add signal selection support for other format than ghw > - Add a help description in Simulation_and_runtime.rst and > grt-options.adb > - Should I add a wave option file example in doc/ too ? > > Version 1.1 : > - Create an option that works like --disp-tree but prints the design > tree in > the wave option file format (could be in 1.0 too). > - Simple wildcards (/top/sub1/*, /top/sub*/*) > - Double wildcards (/top/**, top/sub*/**)) > Remark : *** is no more needed since ** will have it's behavior and > the old > behavior of ** can be achieve with */** (top/*/**) which makes more > clear that > we aren't displaying any signals in the first level of /top > > Version 1.2 : > - Simple regexp (top/sub[1-3]/sig[a-z]) > - Negation (! top/sub2/sigk) > > Version 1.3 : > - Selecting element in an array (/top/sub3/my_array(5)) > - Selecting element in a record (/top/sub3/my_record.field) > > Version 1.4 > - Selection of port and architecture signals > (top/sub1/arch/*:port and top/sub1/arch/*:architecture) > > Tell me if you have any suggestion. > > Jonas > > _______________________________________________ > Ghdl-discuss mailing list > Ghdl-discuss@gna.org > https://mail.gna.org/listinfo/ghdl-discuss _______________________________________________ Ghdl-discuss mailing list Ghdl-discuss@gna.org https://mail.gna.org/listinfo/ghdl-discuss
