important bug

[xml]

if we put a char like

[frrossk]

[quote="xml"]if we put a char like

[xml]

the bug only appears when we try to access the label property of the StaticText:

L2=new wx.StaticText(Panel1, ID_L2, "

[nummish]

That seems similar to the bug I experienced regarding high ascii in the TextCtrl classes.

I wrote a simple test for it, available here.
http://www.0x90.org/~nummish/wx/TestCrash.cs

I was fiddling with the source an I think I mitigated it by passing the length of the string into the wxString constructor. But I'd changed so much at that point and have yet to retry it with the atomic changes.

Try that code with StaticText instead of a TextCtrl.. might be the problem.

iirc, it's even more of a bug in wxGTK, that won't render any of the text at all when it encounters a bad character. (As opposed to a placeholder char)

[xenomorph]

iirc, it's even more of a bug in wxGTK, that won't render any of the text at all when it encounters a bad character. (As opposed to a placeholder char)

I can't reproduce this behaviour on my Debian system (TestCrash works fine, no crash at all). Every "bad" character gets displayed...

Greetings
Xenomorph

[xenomorph]

[quote="xml"]if we put a char like

[xenomorph]

I've already found the error... (my fault)

In wx.NET/Src/wx.NET/wxString.cs change

Code: Select all

                public char this[long i]
		{
			get {return System.Convert.ToChar(wxString_CharAtInt(wxObject, (uint)i)); }
		}

to

Code: Select all

                 public char this[long i]
		{
#if __WXMSW__
			get { return wxString_CharAt(wxObject, (uint)i); }
#else
			get {return System.Convert.ToChar(wxString_CharAtInt(wxObject, (uint)i)); }
#endif			
		}

wx.NET under Windows doesn't get build in unicode mode...
wx.NET under Windows doesn't get build in unicode mode...
wx.NET under Windows doesn't get build in unicode mode...
wx.NET under Windows doesn't get build in unicode mode...
wx.NET under Windows doesn't get build in unicode mode...



Greetings
Xenomorph