X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/1d6d8f171781297827bdafbc0f92c032a16c8e7c..c45b7e75d1833c93200ca2d4e518954e48ec936e:/include/wx/msw/wince/setup.h diff --git a/include/wx/msw/wince/setup.h b/include/wx/msw/wince/setup.h index 196353ee0d..b468eef0dd 100644 --- a/include/wx/msw/wince/setup.h +++ b/include/wx/msw/wince/setup.h @@ -32,7 +32,7 @@ // Default is 0 // // Recommended setting: 0 (please update your code) -#define WXWIN_COMPATIBILITY_2_2 1 +#define WXWIN_COMPATIBILITY_2_2 0 // This setting determines the compatibility with 2.4 API: set it to 0 to // flag all cases of using deprecated functions. @@ -146,9 +146,9 @@ // // Default is 0 // -// Recommended setting: 0 (unless you only plan to use Windows NT/2000/XP) +// Recommended setting: 1 #ifndef wxUSE_UNICODE - #define wxUSE_UNICODE 0 + #define wxUSE_UNICODE 1 #endif // Set wxUSE_UNICODE_MSLU to 1 if you want to compile wxWindows in Unicode mode @@ -181,6 +181,19 @@ // global features // ---------------------------------------------------------------------------- +// Compile library in exception-safe mode? If set to 1, the library will try to +// behave correctly in presence of exceptions (even though it still will not +// use the exceptions itself) and notify the user code about any unhandled +// exceptions. If set to 0, propagation of the exceptions through the library +// code will lead to undefined behaviour -- but the code itself will be +// slightly smaller and faster. +// +// Default is 1 +// +// Recommended setting: depends on whether you intend to use C++ exceptions +// in your own code (1 if you do, 0 if you don't) +#define wxUSE_EXCEPTIONS 0 + // Set wxUSE_EXTENDED_RTTI to 1 to use extended RTTI // // Default is 0 @@ -1048,9 +1061,26 @@ // (notably, wxNotebook pages) #define wxUSE_UXTHEME_AUTO 0 -// Set to 1 to if you're developing for MS SmartPhone +// Set to 1 if you're developing for MS SmartPhone #define wxUSE_SMARTPHONE 0 +// Set to 1 if you want to maintain a PocketPC-style UI on +// Windows CE .NET. If 0, wxWindows will use a commandbar +// for the menubar, and a normal separate toolbar as per the +// desktop implementation. If 1, wxWindows will combine +// the toolbar and menubar as per the PocketPC implementation. +// +// Note that at present, the dynamic loading of PocketPC +// shell functions on WinCE .NET is not yet done, and a +// simple commandbar implementation is used instead of the +// PocketPC one. The intention is to use the PocketPC style +// when available (when wxUSE_POCKETPC_UI is 1). +// +// So if you're using WinCE .NET, and wxUSE_POCKETPC_UI is 0, +// you will be able to create separate toolbars and menubars, +// but _not_ the combined toolbar/menubar. +#define wxUSE_POCKETPC_UI 1 + // ---------------------------------------------------------------------------- // obsolete settings // ----------------------------------------------------------------------------