wxWidgets Discussion Forum

In my application I add : -framework QTKit -framework Quicktime -framework CoreAudio -framework AudioToolbox -framework AudioUnit -framework AppKit -framework Carbon -framework Cocoa -framework IOKit -framework System -framework CoreMIDI disclaimer: my application is a multimedia application, here I...

wxChar is just a typedef to either char* or wchar_t*. I see little use in using wxChar now in 2.9

If you need more chars, the idea is just to make sure what encoding your compiler/textfile are using. Then you

A more complete example, if you haven't seen it yet : http://wiki.wxwidgets.org/Printing

In wx 2.9, especially if your strings will contain ASCII, just do const char* MY_STRING = "a string"; (if you need non-ASCII chars, it's still possible, you just need to be careful with encoding matters) in 2.9, a char* is implicitely convertible into a wxString. So it will be passable whe...

or in wx 2.9, use the new wxWebView. I think that will be much less painful than using wxStaticText in a scrolling area (and even if you need to display some controls inside, you could always display them as HTML and then post back the values to a custom protocol handler)

Maybe the menus and toolbar etc. can be handled by a separate class. Then you can have a MDI frame and a non-MDI frame, and both of these classes will instanciate the menu/toolbar class, which means they both will have the same menus and toolbars without code duplication. Makes any sense?

And more generally I think if you have thousands of items you should be looking for another solution. wxGrid or wxDataViewCtrl come to my mind, those will be much lighter since they don't actually create physical widgets for each row, they just add a scrollbar and then draw the currently visible par...

I think you have an extra set of quotes in this : CFLAGS="\"${GCC_FLAGS}\"" CXXFLAGS="\"${GCC_FLAGS}\"" CPPFLAGS="\"${GCC_FLAGS}\"" LDFLAGS="\"${GCC_FLAGS}\"" OBJCFLAGS="\"${GCC_FLAGS}\"" the compiler...

Is that using sizers, or absolutely-positionned elements? If you manually position things it's quite possible that some things are larger with one theme than with another.

There seems to be something wrong in the way you setup the list control. Is is possible you are creating a list control and passing it options that can't go together?

Otherwise without a small code sample it's hard to tell

In wx 2.8, a non-translated string would be wxT("foo"). In 2.9 usually it's fine to just use "foo".

1. Some issues have indeed in the past been seen when trying to build static-monolithic, under OSX. However the good news is that monolithic is totally useless when you build static : the very nature of static linking is that you will end up with a single executable containing it all. And wx-config ...

The easiest way is probably to remove the wxPanel that contains all your widgets (you should have one) with ->Destroy(), and then create a new one. That should be straightforward

I think this approach is problematic, because global variables are intialised early when laoding the program, which means you will be using wxString before wxWidgets is initialised. Under some systems this may be OK, but there are some systems where this may just crash or assert (I don't remember wh...

Oh, just, maybe a derived question from point #4 : I got the idea that OSX allowed to build a kind of binaries containing both 32 AND 64-bit codes. Is-it true and, if yes, do you think it's an interesting way ? I imagine it should dramatically increase the binary size... Yes, OSX does support fat b...