wxWidgets Discussion Forum

I think that those .xpm files are wrong though. Take a look at samples/sample.xpm (open with a text editor) to see what they must be like.

You should also move the xpm #includes to the CWebGUI.cpp to avoid multiple declarations should you include CWebGUI.h in other sources.

How are your xpm bitmaps declared in the header files? Looks like you are using "string" when it should be something like "static const char *const xxx_xpm[]". Do your xpm headers actually contain xpm character arrays?

Should you ever need UTF-16 (just in case), build and use the wxXml2 library (syntax is similar to that of wxXml)... http://wxcode.sourceforge.net/components/wxxml2/ Pass 0 flags when saving the file (document.Save(file, encoding, 0)). Otherwise the EOLs will be converted to native (flags default to...

Try using EVT_AUINOTEBOOK_PAGE_CLOSE() instead of wxEVT_COMMAND_AUINOTEBOOK_PAGE_CLOSE().

Then they are not generating UTF-16 to begin with. Some people are really careless with document encoding information :D I'm wondering how they can parse their own documents. They probably don't even use an XML toolkit for generation and parsing. You don't have to use a temp file. You could do it in...

Removing and adding columns on the fly works pretty well, too. Something like this (I have a virtual wxListrCtrl in report mode). void ServiceListCtrl::RebuildColumns() { int nColumns = GetConfiguredColumnCount(); int nCurrentColumns = GetColumnCount(); if (nCurrentColumns > nColumns) { while (nCurr...

So far I've always used wxTextOutputStream for saving so I didn't know that Create() could fail either until I checked. :) I can't imagine writing code like this :lol: wxTextFile file("C:\\blech.txt"); if ((file.Exists() ? file.Open() : file.Create())) ... file.Write(); file.Close(); }

Actually wxXml2 does it _nearly_ right. The only thing wrong with it is that it doesn't encode EOL characters in UTF-16. It writes... 0D 0A instead of... 0D 00 0A 00 The rest of the file is correct (tried it with a hex editor, after insertion of the missing 0s the file can be opened). No idea whethe...

I think that in UTF-16 EVERY character needs to be written as 16bit (I might be wrong), contrary to UTF-8 where only non-ASCII characters are escaped. That's wrong. In UTF16 each character is minimally 16 bits long, but there are some that need more. I know. Just wanted to illustrate that what wx i...

Well, the API is kind of weird :D wxTextFile::Open bool Open(wxMBConv& conv = wxConvUTF8) const bool Open(const wxString& strFile, wxMBConv& conv = wxConvUTF8) const Open() opens the file with the given name or the name which was given in the constructor and also loads file in memory on success. It ...

file.Create(const wxString& strFile) should be used for creation instead of Open().

Bizarre. I don't have such problems with VS 2008 Professional.

I would build the samples/widgets wx demo to see if you run into the same problem there.

I haven't come across UTF-16 encoded XML myself yet, it's probably not too common and UTF-8 works just fine.

Do those files really have to be encoded in UTF-16?

The problem could be somewhere else entirely, maybe code which gets executed before messes up memory so that the realloc() here finally crashes.

I would check other places as well

convFile isn't NULL, but it's not used everywhere. I think that in UTF-16 EVERY character needs to be written as 16bit (I might be wrong), contrary to UTF-8 where only non-ASCII characters are escaped. OutputNode() only converts comments and parameters (OutputString() called with 4 parameters), the ...