handcircus
18-12-2007 12:49:22
Hello,
Several people have mentioned a unicode build (for overlays) but has anyone successfully built one yet? I've made some progress with building Mogre with Unicode - I've successfully compiled OGRE with Unicode enabled, and modified the autogenerated code to enable reading unicode strings for the getters, ala:
But this is where my head starts to melt a little bit. I presume for the setters, the code for "InitNativeStringWithCLRString" in Marshalling.cpp needs a similar function to be implemented for UTF8 strings. But at this stage I'm really out my depth.
Any help would be *greatly* appreciated. Marioko, I see that in your latest post you mention that you are working on a UTF build - do you know when that is likely to be ready? Is there anything I can do to help.
Thanks in advance
Simon
Several people have mentioned a unicode build (for overlays) but has anyone successfully built one yet? I've made some progress with building Mogre with Unicode - I've successfully compiled OGRE with Unicode enabled, and modified the autogenerated code to enable reading unicode strings for the getters, ala:
String^ TextAreaOverlayElement::Caption::get()
{
return gcnew System::String(static_cast<const Ogre::TextAreaOverlayElement*>(_native)->getCaption( ).asUTF8_c_str(),System::Text::Encoding::UTF8);
}
But this is where my head starts to melt a little bit. I presume for the setters, the code for "InitNativeStringWithCLRString" in Marshalling.cpp needs a similar function to be implemented for UTF8 strings. But at this stage I'm really out my depth.
Any help would be *greatly* appreciated. Marioko, I see that in your latest post you mention that you are working on a UTF build - do you know when that is likely to be ready? Is there anything I can do to help.
Thanks in advance
Simon