Re: [Gnucap-devel] Gnucap Integrated waveform displayer Details

[Abhinav singh]

> Message: 1
> Date: Thu, 12 Jun 2014 22:25:47 -0400
> From: al davis <address@hidden>
> To: address@hidden
> Subject: Re: [Gnucap-devel] Gnucap Integrated waveform displayer
>         Details
> Message-ID: <address@hidden>
> Content-Type: Text/Plain;  charset="iso-8859-1"
>
> On Wednesday 11 June 2014, Abhinav singh wrote:
> > Though store command shows v(1) and v(2) are stored in list
> > but it is of no use because we can't find a wave associated
> > with this nodes. Please correct me if i am wrong.
> >
> > If above is true then,after each simulation data gets changed
> > and previous data get deleted.
>
> True.
>
> It should be changed.
>
> > So if we directly using the
> > WAVE for plotting then how we will be able to retain the
> > previous transition plot as plot changes dynamically with
> > change in data.
> > Though i implemented it using WAVE directly and its working
> > fine but again it created the same problem we only able to
> > view single window at a time.
>
> It seems to me that a plot already displayed should stay
> displayed, but you cannot do any more with it


If we want the same then why dont we save the plot in temporary file
and it will change if user do the same type of simulation again
otherwise remains as such.This seems a better option to me instead of
creating whole dataset related to each simulation.


> -------------------
> similarly, the plot window should allow some interaction on graphs, like
> change colors, style or delete them. (read: it should be possible to
> add these features some day).


How you wants to do it by using an interface or through command window?


> > A simpler way is to save a tran set, an ac set, etc .. but that
> > would overwrite when you run the same command again.
>
> one set of waves for each simulation type does not really improve the
> situation. why not just copy a wave to the gtk process as-needed and
> attach a meaningful identifier? this is still a hundred times better
> than brute-force store everything, like other simulators do.

 I tried it but failed may be i was doing something wrong.What
actually happen gtk widgets redraw with every expose event so it
retrace whole drawing procedure and if data get changed anyhow then we
dont get desired output.