Two problems:
1) A crash of the wxpython app (DrPython). It appears, when I want to paste a text into a stc window. It is hard to track down, it only appears on gtk. It is very awkward, because is seems to be appear randomly.
2) I need it to track down that crash on gtk.
The app crashes without any warning. So I downloaded that dbg version, to
find the reason. But when I want to start, it refuses the start of the app by the following output:
[Debug] 20:07:00: wxColour::Set - couldn't set to colour string '#000000,face:Mo nospace,size:9'
What can be the reason? Why is there a difference between this two versions? (because on "normal" wxpython, there is no such a problem)
It's a debug log message so it is not generated in the release build. The problem still exists however, it's just silently ignored. Someplace it is trying to set or create s colour using the string above and is failing because it is not the right format for a hex color string, and there isn't a name in the colour table that matches.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
Two problems:
1) A crash of the wxpython app (DrPython). It appears, when I want to
paste a text into a stc window. It is hard to track down, it only appears
on gtk. It is very awkward, because is seems to be appear randomly.
2) I need it to track down that crash on gtk.
The app crashes without any warning. So I downloaded that dbg version, to
find the reason. But when I want to start, it refuses the start of the
app by the following output:
[Debug] 20:07:00: wxColour::Set - couldn't set to colour string
'#000000,face:Mo nospace,size:9'
What can be the reason? Why is there a difference between this two
versions? (because on "normal" wxpython, there is no such a problem)
It's a debug log message so it is not generated in the release build.
Wouldn't it be better to continue the program execution instead of quitting the app?
At the other side, maybe changing the font or the color, so that there is no problem
anymore, would be more appropriate.
···
On Mon, 24 Mar 2008 10:59:54 -0700, Robin Dunn <robin@alldunn.com> wrote:
The problem still exists however, it's just silently ignored. Someplace
it is trying to set or create s colour using the string above and is
failing because it is not the right format for a hex color string, and
there isn't a name in the colour table that matches.
Indeed, that was the error. Of course not the whole string, but only the value of the color is right.
"#000000" (there was also the query of the size of the string (len) should be seven.
···
On Tue, 25 Mar 2008 14:42:58 +0100, Franz Steinhaeusler <franz.steinhaeusler@gmx.at> wrote:
On Mon, 24 Mar 2008 10:59:54 -0700, Robin Dunn <robin@alldunn.com> wrote:
Franz Steinhaeusler wrote:
Hello. I'm glad that such a version exist.
Two problems:
1) A crash of the wxpython app (DrPython). It appears, when I want to
paste a text into a stc window. It is hard to track down, it only appears
on gtk. It is very awkward, because is seems to be appear randomly.
2) I need it to track down that crash on gtk.
The app crashes without any warning. So I downloaded that dbg version, to
find the reason. But when I want to start, it refuses the start of the
app by the following output:
[Debug] 20:07:00: wxColour::Set - couldn't set to colour string
'#000000,face:Mo nospace,size:9'
What can be the reason? Why is there a difference between this two
versions? (because on "normal" wxpython, there is no such a problem)
It's a debug log message so it is not generated in the release build.
The problem still exists however, it's just silently ignored. Someplace
it is trying to set or create s colour using the string above and is
failing because it is not the right format for a hex color string, and
there isn't a name in the colour table that matches.
Hm, I searched the wxwidgets code:
Here is the line:
wxLogDebug(wxT("wxColour::Set - couldn't set to colour string '%s'"), str);
return false;
I can imagine, where the error lies, but:
But why does the program quit here (and not simply output the debug message and continues)?
Or is there afterward a crash, which is not
displayed, so I get the impression, the app ends here?