wxWidgets Discussion Forum

As this is a GUi application under Windows, it should look for WinMain, not main. Check the project properties at Linker -> System and make sure "Subsystem:Windows" is selected.

Your code looks ok, the problem is mostly how you insert pSizer_0_0 into another sizer. E.g. if you put it into a vertical sizer, set the wxEXPAND flag so that it takes the whole width.

Using wxALIGN_RIGHT like Manolo wrote will not work in this case. This is only allowed in a vertical boxsizer and serves a (slightly) different purpose. Your code looks ok, the problem is mostly how you insert pSizer_0_0 into another sizer. E.g. if you put it into a vertical sizer, set the wxEXPAND ...

The error message could indicate that there is an actual problem in the code.

I just start the basic/example wxWidgets project

What are you referring to? Where does this sample come from?

Can you build and run the "minimal" sample that comes with wxWidgets?

The linker command line looks a little strange, but as i'm only an occasional MinGW user i can't tell if it's wrong. Here's what i get when building a minimal test with CB: mingw32-g++.exe -LC:\Users\Test\Desktop\wx312\lib\gcc_lib -o bin\Debug\test1.exe obj\Debug\test1App.o obj\Debug\test1Main.o obj...

Are you going to open a ticket for this?

Did you also add ole32.lib and uuid.lib?

What does the linker command line look like?

This looks like a bug indeed. It works if you use CallAfter for the inner method call: if (s.ToDouble(&n)) { n *= 2; CallAfter([=] { bool ok = ChangePropertyValue(_pProp_2, n ); // This line will be executed and return true, but UI doesn't change. // wxPropertyGrid::SetPropertyValue works // wxPGPro...

The missing references are inside Windows libraries. Add Oleacc.lib and Ole32.lib to the linker inputs. (liboleacc.a and libole32.a for MinGW). If other undefined references pop up, Google "msdn + missing reference" and it will find a page that shows which library you need to add. E.g. https://docs....

Converting a wxString into another wxString using any of these methods is just bad. Don't do it.

Append all incoming data into a wxMemoryBuffer and then convert the data to a wxString.

What type is strBuf? It looks like it's a wxString which would be wrong. wxString is unsuitable as a generic byte container. If you're receiving data from an external source, you should have a (unsigned) char buffer and and number of valid bytes in it. (or a wxMemoryBuffer if you want to use a wx cl...

Try sorting the includes so that all wx headers are included first, then all others. wx/wx.h or wx/wxprec.h should always be the first wx header. Including wx/defs.h should not be necessary.

Which platform are you using? wxDataViewCtrl uses a generic implementation under Windows and wraps native controls under OSX and GTK. While it may be possible to change the behavior under Windows, it's probably not possible under the other platforms.

Did you get the error when building wxWidgets or your application?
Please post the exact error messages.