kicad-developers team mailing list archive

[Nick Østergaard <oe.nick@xxxxxxxxx>]

2015-10-24 16:00 GMT+02:00 jp charras <jp.charras@xxxxxxxxxx>:
> Le 24/10/2015 13:57, Nick Østergaard a écrit :
>> Hi
>>
>> It looks like the message/console dialog was added in rev 6150, I think
>> this commit did not consider users to close the window...  The commit just
>> before, that is 6149 could be related. A third commit related to this is
>> 6163.
>>
>> @Jean-Pierre, all those commits were made by you, would you be so kind and
>> give the changes a second look?
>
>
> I do not have any crash, both on W7 - 32 bits and Kubuntu 14.04 64 bits.
>
> the rev 6150 fixed issues on Windows (python script throwing an
> exception on Windows, and therefore error messages).
>
> I am surprised by this sentence:
> "I need to close that console/status"
> How to close it?
> there is no way in pcbnew to close it: this is a window which is used to
> display python messages, and especially error and warning messages from
> scripts.
> (Obviously, if there is some way to close it, be sure pcbnew will crash
> the first time a message is displayed or when closing the wizard)
>
> Do you know a way to reproduce the crash?

Yes, as I mentioned earlier. Close that window withc is used to
display python messages. I use my window managers shortcut for this,
which is Alt+F4 on windows. Please retest.

I don't really see the need for that message output to be another
dialog window like that, nor why it is shown by defult. But anyway, it
will crash when closed and the python wizard used.

>> Den 23/10/2015 19.42 skrev "Nick Østergaard" <oe.nick@xxxxxxxxx>:
>>
>>> Hi all,
>>>
>>> I have attached a backtrace here generated on linux 6271 (I know this
>>> is an old rev... but the symptoms are the as on latest)
>>>
>>> But it seems that I need to close that "console/status"-like window
>>> and then edit values and it will crash.
>>>
>>> Could it be the #6  0x00007ffff6e3d2db in
>>> wxTextEntryBase::DoSetValue(wxString const&, int) () from
>>> /usr/lib/libwx_gtk2u_core-3.0.so.0 that is actually not allowed when
>>> that window is not active?
>>>
>>> Also, I wonder why it is really there in the first place, it was not
>>> there originally.
>>>
>>> I would be quite greatful if anyone could try to reproduce this.
>
>
>
> --
> Jean-Pierre CHARRAS