wxWidgets Discussion Forum

Hi.

Did you try updating your sizers after changing the buttons labels ? Regards
Xav'

Hi. If your compiler (gcc) can be found from the path, you can just open a command prompt, change the working directory to the corresponding sample folder, and run "mingw32-make.exe -f makefile.gcc". If you want to use CodeLite, you can create a new project in the sample directory and add the ".cpp"...

Hi. Did you try setting the background color before showing the frame ? #include "main.h" IMPLEMENT_APP(MyApp) bool MyApp::OnInit() { wxFrame *mainframe = new wxFrame(NULL, wxID_ANY, wxString("Main Window"), wxPoint(wxDefaultPosition), wxSize(1152, 648)); mainframe->SetBackgroundColour(wxColor(73, 7...

Hi. You have 2 solutions : Convert your source code file to UTF-8 without BOM (is you want to use specials unicode characters, you must have them correctly encoded) The "copyright" character has its own treatment in the wxAboutDialogInfo class : if you write info.SetCopyright(_("v1.0b. Copyright (c)...

Hi Thank you! Both ways did it. What - of both alternatives (renaming the wx-dir or changing the build options) - is the "better" way? Being able to switch between 32- and 64-bit target WITHIN C:B, wouldn't it be better to change the pointing to the wx-libs withing C:B too? Regards Both solutions ha...

nji wrote: But then building in C:B, none of the choices (monolithic, unicode etc.) does the job.

The official binaries are "non-monolithic unicode dll" builds.

Regards
Xav'

Hi. I installed the newest C:B (gcc), and then WxWidgets (3.0.3) as binaries (include and lib). I assume you've downloaded the official binaries. So, in your wxWidgets's installation dir, you should have , in the "lib" folder, a sub-directory named " gcc xxx TDM[_x64]_dll ". (the 'xxx' part correspo...

Manolo wrote:Compiling your own code on Windows is just a little more tricky than on Linux because of lacking wx-config.

I've build a version of wx-config for Windows (started from CodeLite's sources) :
http://x.psoud.free.fr/?/soft/wxconfig.html

Regards
Xav'

Hi.

The better way to get these flags/parameters is to compile the "minimal" sample that comes with the sources.

If you use the same command line to build the sample than the one used to build the libs, you'll obtain the correct command line to compile and link the sources.

Regards
Xav'

Hi.

I've just tested on a Linux Mint "Debian Edition" (LMDE) with wxWidgets 3.1.1, and it works correctly.

Witch version of wxWidgets are you using ?
And where does it come from (official repos, own build, ...) ?

Regards
Xav'

Hi That "ugly grey border/background" is the colour of the wxFrame, which I'm sure does not appear randomly, but consistently. Doesn't it? Just to add that it is the default background color of a window under Windows (this is not a wxWidgets related thing). If you don't want that, add a wxPanel as t...

Hi.

As you added `wx-config --libs` as a linker rule, you should add `wx-config --cxxflags` to the compiler rules.

Also, check that these 2 commands give you the corrects parameters (try to enter them in a terminal window).

Regards
Xav'

Hi. It seems the gcc makefile has an error (well, perhaps more than one, but one can be corrected to allow your build). It seems that the build process is trying to link with the opengl wxwidgets lib instead of the aui one. You can correct this : line 342 of the makefile (and only there) replace $(_...

Hi.

You can rebuild your release libs with the "DEBUG_FLAG=0" command line options : all debug asserts will be removes (but you'll also have to add this to the command line for building your app.
You can also add "wxDEBUG_LEVEL=0" while building your app in your IDE's compiler options.

Regards
Xav'

Hi. As doublemax said, you need to creare an application bundle. But if you want to make some tests without creating a bundle, you just need to make a call to "SetFile" : SetFile -t APPL YourExecutableFile Note that you will also have to make this call if you create a bundle. Regards Xav' Edit: this...