Re: [Gnucap-devel] gplot (was: wave storage)

[Abhinav singh]

Hi Felix

The frozen command prompt indicates that WIN_MAIN::_is_proceed flag
doesn't getting reset but it should get reset as soon as we click on
New button.

Please mention what changes you made if any may be it is because of
that as it is working good on my system and can you please mail me the
test circuit file you are using with plugin.

thanks,
abhinav

On 10/5/14, Felix Salfelder <address@hidden> wrote:
> On Sun, Oct 05, 2014 at 01:51:30AM +0530, Abhinav singh wrote:
>> How it works?
>> [..]
>
> thanks.
>
>> Yes, because you can only run one main window or otherwise you have to
>> start a new thread for running another main window.
>
> multiple windows require multiple threads. but gtk takes care of this.
> i think it's best to start just one pthread. but i'm not sure whether
> multiple windows make sense already -- maybe i want a command window or
> something like it later on.
>
>> > also, the layout of the main window suggests that multiple tabs are
>> > intended to contain various plots. how much of this is working? and
>> > what
>> > is the empty area on the left supposed to be?
>>
>> Yes there is a main window which contains multiple tabs and with the
>> old code base (before rework of wave storage) its working absolutely
>> fine.
>
> i havent come to rework anything in particular. so the old codebase is
> just the current codebase? i haven't changed much of the functionality
> that i'm aware of.
>
>> Empty area is for variable list. A list which contains all the
>> variable plotted in currently selected tab or wavepanel. From this
>> list you directly add or delete waveform in the wavepanel.
>
> so something should appear on the left side? here, it doesn't. can you
> point me to the code responsible for this?
>
> also, i didn't manage to see multiple tabs. the Readme mentions a "new"
> button, here it does not have any effect (and the command prompt remains
> frozen).
>
>> Can you please tell me what exactly the error is occurring when you
>> are trying to run it with new code base.
>
> there are some things that i consider curious, e.g. the frozen command
> prompt. but i'd not call it an error before i know how it is intended to
> work.
>
> cheers
> felix
>