ANSI/Unicode problem

I just committed my latest changes to the wx.NET source
base.
Probably, I found a solution to the ANSI/Unicode problem
with
string conversion. The basic idea is to let wxWidgets do
the
conversion from and to UTF 16 which is the native char set
of the .NET framework. wxWidgets knows whether something
needs
to be converted or not.
I tested in particular collaboration with ANSI since this
is
much more complex. Some other fixes concerned data type
<long>
in callbacks (listctrl) and broken .mo files in the
internat
example.
Most of the string conversion still has to be replaced. The
preferred way of providing strings for the wx-c.dll is to
generate a wx.wxString() and pass the wxObject of this
string
to the native dll. So, wx-c functions should receive
<const wxString*>
instead of <const wxChar*>.
Another remark to the conversion of Booleans:
Apparently, Booleans are marshalled by default as
UnmanagedType.Bool.
So, wx-c functions either have to use <int> as
unmanaged code to deal
with this, or the MarshalAsAttribute needs to be used in
order to
specify an alternative unmanaged type. On some occasions, I
used for
instance InmanagedType.U1 to marshal Booleans as
<unsigned char>.



------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wxnet-developers mailing list
Wxnet-developerslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxnet-
developers