Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Unicode conversion (attention all devs)
tiwag:
--- Quote from: byo on August 05, 2005, 11:29:57 pm ---I try to compile changed sources in both Unicode and NonUnicode versions of wxWidgets (and after that in wx2.4 and wx2.6 to make sure it will work everywhere). Unfortunately all project can't be compiled in Unicode but separate files can :)
--- End quote ---
Hi byo
what unicode library have you built ? which OS are you using ?
currently i work only in Windows,
i thought about to build a "wxMSW-2.4.2-monolithic-unicode-DLL-debug" library
for testing the CodeBlocks VERSION_1_0_UNICODE .
i would like to discuss with you how to setup the best debug-environment for our new "baby"
in the future i would like to test also in Linux,
just now i have set up an Ubunto Hoary in a VM-ware box
it runs but i'm far away from compiling and testing something...
so testing in Linuxs means "mid-term future" for me
maybe starting in October 05 ... we'll see
byo:
--- Quote from: tiwag on August 06, 2005, 12:14:46 pm ---what unicode library have you built ? which OS are you using ?
currently i work only in Windows,
i thought about to build a "wxMSW-2.4.2-monolithic-unicode-DLL-debug" library
for testing the CodeBlocks VERSION_1_0_UNICODE .
i would like to discuss with you how to setup the best debug-environment for our new "baby"
in the future i would like to test also in Linux,
just now i have set up an Ubunto Hoary in a VM-ware box
it runs but i'm far away from compiling and testing something...
so testing in Linuxs means "mid-term future" for me
maybe starting in October 05 ... we'll see
--- End quote ---
I also work on Windows, testing on wx 2.6.1 (monolithic,dll)
I tried to run on Gentoo linux (with wx 2.6.1) but can't get it working (it crashes immediately - it was even discussed somewhere on the forum). Hmm, no, I've run it on 2.4 but it doesn't store configuration or something like that (it crashes when closing stardet but before saving configuration I suppose). But it wasn't sattisfying for me since my wxSmith plugin works only under 2.6.
Hmm, there's also one thing need mentioning - when building wxWidgets in debug mode (when assertions are enabled) it shows some assertions at the beginning (something about unknown parameters - when parsing command line) and some after but I don't remember them currently.
byo:
Code from group 15 sent to rickg22 - You can update my info ;)
rickg22:
New macro defined!
I defined a new macro in "settings.h":
_U(). Use it to convert non-literal char* strings to wxString. Use it for reading attributes from TiXmlNode's.
--- Code: ---#ifdef wxUSE_UNICODE
#define _U(x) wxString((x),wxConvUTF8)
#define _UU(x,y) wxString((x),y)
#else
#define _U(x) (x)
#define _UU(x,y) (x)
#endif
--- End code ---
i.e.:
--- Code: ---const char* incompatible = "This is an incompatible string";
wxString compatible = _U(incompatible);
// wxString conftype = conf->Attribute("ConfigurationType"); // before
wxString conftype = _U(conf->Attribute("ConfigurationType")); // after :)
--- End code ---
I just hope I'm not reinventing the wheel here :P
byo:
--- Quote from: rickg22 on August 06, 2005, 10:05:23 pm ---
--- Code: ---#ifdef wxUSE_UNICODE
#define _U(x) wxString((x),wxConvUTF8)
#define _UU(x,y) wxString((x),y)
#else
#define _U(x) (x)
#define _UU(x,y) (x)
#endif
--- End code ---
--- End quote ---
I guess that we should use wxConvUTF8 by default. I've seen that Ceniza uses wxConvLocal. Which one is better ? (Perhaps we will find out when localized versions of C::B will be released ;) ).
Hmm, I shouldn't worry about it. If it will be inside settings.h, jut few seconds and it will be changed :lol:
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version