Hi Wayne
That final message was a direct result of DANGLE/CCPN crashing. I guess you could say it happened when quitting the (entire) program, but it did that on it's own.
When trying to start DANGLE that entire CCPN program get's a grey shadow and there is a Windows popup that the program just crashed. When you click that away all CCPN windows close. (That's also why I sent a screen capture, the windows is not responsive anymore so I couldn't copy the error message into the email)
Matthias
On Nov 17, 2010, at 2:16 , Wayne Boucher wrote:
> Hello,
>
> We think that this is because some Dangle data files were missing from the original 2.1.5 Windows release. The latest release (build 4594, available at http://www.ccpn.ac.uk/ccpn/software/downloads-v2/) should work ok.
>
> That final message about the "NULL tstate", I hope that only occurred when quitting the (entire) program. We've just started noticing this kind of error when we're running unrelated PyQt programs (PyQt being an alternative GUI library to the currently used Tkinter) when we exit, and although it's bad (errors are always bad) it shouldn't be causing a problem. The missing Dangle files are the real problem, hopefully.
>
> Wayne
>
> On Wed, 17 Nov 2010, Matthias Huber wrote:
>
>> I'm running CCPN 2.1.5 with all updates installed under Windows.
>> When trying to run DANGLE CCPN crashes and produces the attached error message.
>> (on the Mac DANGLE runs without problems on the same project).
>>
>> Matthias
>>
>>
>>
|