And so says Reed Hedges on 07/09/05 10:08... > Lalo Martins wrote: >>- nickentry->SetValue(avatar->getNick().c_str()); >>+ nickentry->SetValue(wxString(avatar->getNick().c_str(), >>*wxConvCurrent)); > > Why use wxConvCurrent instead of wxConvUTF8? I got the impression from > the wx docs that wxConvCurrent depends on the (GUI) platform, so on a > unicode platform you'd be telling it your strings from VOS were unicode, > when they aren't. I only read the wx docs with a normal depth, no > backwards bending, maybe I am wrong :)
I copied this verbatim from some examples in the documentation, so I may be wrong, but from what I understand: wxConvCurrent may be the appropriate conversion to turn a (char) string into unicode (wxConvUTF8), if your build is unicode-enabled; or it will be a dummy conversion otherwise. So this expression returns unicode when it needs unicode, and single-byte when it needs single-byte. best, Lalo Martins -- So many of our dreams at first seem impossible, then they seem improbable, and then, when we summon the will, they soon become inevitable. -- http://www.exoweb.net/ mailto:[EMAIL PROTECTED] GNU: never give up freedom http://www.gnu.org/ _______________________________________________ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d