Contents Up Previous Next

Configuration

The following lists the options configurable in the file include/base/wx_setup.h. Some settings are a matter of taste, some help with platform-specific problems, and others can be set to minimize the size of the library.

General features
X features
Windows and NT features


General features

ENHANCED_FONTS Define to be 1 to have pre-defined fonts in wxEnhDialogBox.
USE_BUTTONBAR If 1, the wxButtonBar class is compiled.
USE_CLIPBOARD If 1, clipboard code is compiled (Windows only).
USE_CONSTRAINTS If 1, the constaint-based window layout system is compiled.
USE_DOC_VIEW_ARCHITECTURE If 1, wxDocument, wxView and related classes are compiled.
USE_DRAG_AND_DROP If 1, drag and drop code is compiled (Windows only).
USE_DYNAMIC_CLASSES If 1, the run-time class macros and classes are compiled. Recommended, and necessary for the document/view framework.
USE_ENHANCED_DIALOG If 1, wxEnhDialogBox code is compiled.
USE_EXTENDED_STATICS If 1, wxStaticItem code is compiled for enhanced panel decorative items. Not rigorously tested, and not documented.
USE_HELP If 1, interface to help system is compiled.
USE_FORM If 1, wxForm code is compiled.
USE_GAUGE If 1, the wxGauge class compiled.
USE_GLOBAL_MEMORY_OPERATORS If 1, redefines global new and delete operators to be compatible with the extended arguments of the debugging wxObject new and delete operators. If this causes problems for your compiler, set to 0.
USE_GNU_WXSTRING If 1, the enhanced GNU wxString and regular expression class are compiled in place of the normal wxString class. See contrib/wxstring for details.
USE_IMAGE_LOADING_IN_MSW Use code in utils/dib to allow dynamic .BMP loading under MS Windows.
USE_IMAGE_LOADING_IN_X Use code in utils/image to allow dynamic .BMP/.GIF loading under X.
USE_RESOURCE_LOADING_IN_MSW Use code in utils/rcparser to allow dynamic .ICO/.CUR loading under MS Windows.
USE_IPC If 1, interprocess communication code is compiled.
USE_MEMORY_TRACING If 1, enables debugging versions of wxObject::new and wxObject::delete if the value of DEBUG is defined to more than 0.
USE_METAFILE If 1, Windows Metafile code is compiled.
USE_PANEL_IN_PANEL If 1, experimental panel-in-panel code is used for common dialog boxes. Not recommended, since tab traversal can suffer.
USE_POSTSCRIPT If 1, PostScript code is compiled.
USE_POSTSCRIPT_ARCHITECTURE_IN_MSW Set to 1 to enable the printing architecture to make use of either native Windows printing facilities, or the wxPostScriptDC class depending on the wxApp::SetPrintMode setting.
USE_PRINTING_ARCHITECTURE If 1, wxPrinter, wxPrintout and related classes are compiled for the print/preview framework.
USE_RESOURCES If 1, win.ini or .Xdefaults-style resource read/write code is compiled.
USE_SCROLLBAR If 1, wxScrollBar class is compiled. Not rigorously tested, and not documented.
USE_SPLINES If 1, spline code is compiled.
USE_TOOLBAR If 1, the wxToolBar class is compiled.
USE_TYPEDEFS If 1, a typedef will be used for wxPoint instead of a class declaration, to reduce overhead and avoid a Microsoft C++ memory bug.
USE_VLBOX If 1, wxVirtListBox code is compiled for a virtual listbox item. Not rigorously tested, and not documented.
USE_WX_RESOURCES If 1, wxWindows resource file (.WXR) code is compiled.
USE_XFIG_SPLINE_CODE If 1, XFig-derived code is used for spline drawing. If 0, AIAI code is used, which is slower.
USE_XPM_IN_X If 1, XPM (colour pixmap) facilities will be compiled and used in wxBitmap under X.
USE_XPM_IN_MSW If 1, XPM (colour pixmap) facilities will be compiled and used in wxBitmap under MS Windows.
WXGARBAGE_COLLECTION_ON If 1, wxWindows is made compatible with a experimental garbage collector (needs MrEd distribution). Not recommended for general use.


X features

DEFAULT_FILE_SELECTOR_SIZE Let Motif choose the size of XmFileSelectionBox. Otherwise, size is 500x600.
PIXEL0_DISABLE Define to disallow allocation of pixel 0 (wxXOR problem).
USE_GADGETS Use gadgets where possible rather than Widgets for items. Default is to use Gadgets.
USE_BUTTON_GADGET Use gadgets for buttons. This can intefere with default button selection, so the default is zero.
USE_NOTICES Under XView, use Notice package where possible instead of normal dialog boxes.
wxFSB_WIDTH Width of file selector box, if fixed.
wxFSB_HEIGHT Height of file selector box, if fixed.


Windows and NT features

Windows 95 update: dialogs can be marked with the Win95 3D look by specifying the DS_3DLOOK. But this doesn't apply to panels. The WIN32 SDK documentation says that the style WS_EX_CLIENTEDGE can be used for controls, to give them all 3D looks. However, this doesn't appear to work (and causes strange 2-column behaviour in wxListBox). Even marking the executable as Windows 4.0 only gives a wxChoice items a 3D look. So it seems that for now, CTL3D is still required for Windows 95 applications.

CTL3D It is recommended that CTL3D is used under Windows, since the 3D effects are good-looking and will be standard with Windows 4.0. If you want to use it and don't already have CTL3D installed, copy the files in contrib/ctl3d to appropriate places (ctl3dv2.lib/ctl3d32.lib into your compiler lib directory, ctl3d.h into an include directory, and ctl3dv2.dll into windows/system). You may need to find a compiler-specific version of ctl3dv2.lib or ctl3d32.lib. Define CTL3D to be 1 in wx_setup.h and link your executables with ctl3dv2.lib or ctl3d32.lib.

If both CTL3D and FAFA are set to 1, then all controls except wxButton will use CTL3D and have 3D appearances. wxButton will have the ability to use bitmaps. This is the recommended configuration.

FAFA_LIB Define this to be 1 if you wish to use the Fafa enhanced control library (in the contrib directory). The Fafa library is mandatory for use of bitmap buttons.

An application using the Fafa library must include fafa.rc in the its RC file. Otherwise, some controls will not show up.

EDITABLE_TEXT_WINDOW If 1, allow ONLY an editable wxTextWindow and compile out the large-file support. That is, always use the standard EDIT control. Defaults to 0.
USE_COMMON_DIALOGS If 0, disables common dialogs. Defaults to 1; would rarely be changed.
USE_GREY_BACKGROUND If 1, will use grey for panel and dialog backgrounds (Julian Smart's preferred setting). Grey is used by CTL3D anyway. If this is set to 0 and USE_FAFA is set to 1, you may see unsatisfactory display of some control backgrounds.

If both CTL3D and FAFA are set to 1, then all controls except wxButton will use CTL3D and have 3D appearances. wxButton will have the ability to use bitmaps. This is the recommended configuration.

USE_KEYBOARD_HOOK If 1, sends OnCharHook message to wxApp and active wxWindow classes.
USE_ITSY_BITSY If 1, compiles in code to support tiny window titlebars.
USE_BITMAP_MESSAGE If 1, compiles bitmap support for wxMessage using the FAFA library.
USE_ODBC If 1, compiles wxDatabase and wxRecordSet classes for ODBC access. Requires sql.h, sqlext.h files if set to 1 (see topic on database support).