wxWidgets Discussion Forum

That GetCount thing is not mentioned in WX_2_6_BRANCH changes.txt...

You don't HAVE to include any licenses but your own (if you wish to have that, you probably do), at least as far I know - IANAL. In fact, if you do include the wxWindows license and don't make it very clear that this is for the used library, it might mean that your application is under the wxWindow ...

--disable-precomp-headers to configure for that one.
mingw-3.4 has broken precompiled header support.

If you are using wxX11-2.6.2, then don't. Unfortunately it doesn't show fonts :( You should try using the mature and officially supported wxGTK port, built against GTK+ 2.x. If you really want to use wxX11, then you could try out wxX11-2.6.3 RC1 or later. Release Candidate 2 is planned for this week...

Sorry that I didn't give an explanation for the resolution change. I did it for the reason that David explained. It is set to "Worksforme" when the developer has it working without doing anything to make it work (including applying a patch). More often used for bugs (still rarely though), ...

I am inheriting my connection class from both wxSocketClient and wxEvtHandler. So I have a is-a relationship to wxSocketClient, not a has-a one. Just noting here, in case it might be helpful to someone, that we had to do the deriving as follows in wxMUD: class Connection : public wxEvtHandler, publi...

You should really want an unicode build of wxGTK-2.6.3 RC1 or above (not patched 2.6.2 has a crash case in wxGetTranslation).
Otherwise, refer to the previous posters

./configure run will create it for you from setup.h.in, as appropriate (configure settings affect it).
Also don't mix 2.6's setup.h with 2.4's.

SetBackgroundStyle(wxBG_STYLE_CUSTOM) perhaps?
You can see the manual or (now downloadable) wxBook for details.

Yes, wxX11-2.6.2 has this font problem.
For wxX11 one could get at least 2.6.3 RC1.
Of course wxGTK is the proper answer unless you have special needs.
wxGTK is a stable officially supported port, while exactly that can't be really said to wxX11.

I simply could never reproduce this. Neither bug 1287999 or your reported one.

I did that in my project. VS2005 was bitchy about it in unicode builds.
Currently I ended up doing But I fear that xgettext won't parse that as I'd wish it to. My project isn't yet set up for i18n.

I suggest getting rid of every occurance of wxDC::BeginDrawing and wxDC::EndDrawing. They do absolutely nothing in wx2.6 and they don't exist or are deprecated in CVS HEAD (as such this class won't compile against wx CVS HEAD, at least not with --disable-compat26 that I use).

No particular need to break non-unicode builds by using always a wchar_t there, unconditionally disregarding wxwidgets build type.

Perhaps you could even write some of the documentation for the class? At least list the public members and what they or something. If not latex, then just text - I or someone else can do the necessary converting.