+ +
| + + +Please note that the version of wxMac in CVS is more robust and nearly feature-complete compared with the packaged 2.0 release. +Until a new release is made, it is recommended that you download the wxMac 2.3.1 development snapshot or the sources from the CVS trunk. + + | +
+ +
+A Mac OS X port is in progress in order to be able to build wxWindows applications using the Apple Developer Tools that are delivered with every copy of Mac OS X. +The Mac OS X port is based on and, for the most part, merged with the Carbon code for Classic Mac OS. +
+ +
+This hybrid approach was suggested by Apple to the Fizzilla team working on Mozilla for Mac OS X. +
+ +
+The following points should be considered when improving wxMac: +
+ +
+Under Mac OS X, the Developer Tools are sufficient to build wxMac. CodeWarrior Pro 6 can also be used to build the Carbon targets. +
+ +
xpm and xbm images correctly:
+TEXT (just those four capital letters); correct it if necessary. If there is no entry, make one with type set to TEXT and creator set to anything you like; reasonable choices include GKON (Graphic Converter) or CWIE (CodeWarrior).
+xpm or xbm files in CodeWarrior, set up a file mapping in the CodeWarrior project settings for analogous to ".h" files.
++ +
+All files checked out under Mac OS X will be untyped and CodeWarrior will not recognize them correctly. To correct this, use the autotyper provided in the CVS sources: +
wxWindows/docs/mac/TypeAsMetrowerksText.sea.hqx
++ +
#include <ControlDefinitions.h>+ after the line +
#include <Controls.h>+
+Build the projects (makemac6.mcp for CodeWarrior Pro 6; makemac.mpc for CodeWarrior Pro 5) in the following five directories:
+
+ +
+Building wxMac completely without configure is not supported. +
+Building wxWindows directly in the CVS sandbox is not recommended. Instead, wxWindows should be built in a directory configured relatively to the CVS sandbox. +For instance, to build wxMac with configure, start in the base wxWindows directory and type: +
mkdir macbuild
+cd macbuild
+../configure or ../configure --enable-debug
+make
++ +
Target/Access Paths, make sure the first user include does not have a folder icon for recursive search.
+
+Language Settings/C/C++ Language, make sure that the only checked items are:
+Enable C++ Exceptions
+Enable RTTI
+Enable bool Support
+Enable wchar_t Support
+Relaxed Pointer Type Rules
+Use Unsigned Chars
+Language Settings/C/C++ Warnings, make sure that the only checked items are:
+Illegal Pragmas
+Extended Error Checking
+Inconsistent Use of 'class' and 'struct' Keywords
+Hidden Virtual Functions but be aware that the framework itself has some of these beauty spots
+Linker/PPC Linker, make sure that the following items are checked:
+Dead-strip Static Initialization Code in order to avoid including libraries that are not needed, especially as things like OpenGL get added to the projects and sources
++ +
-cpp-precomp option and allows much faster preprocessing of the source files by loading precompiled Carbon header files. This option speeds up the compilation of wxMac by a factor of 2 at least.
+When compiling wxMac using the Apple Developer Tools, the following error is displayed for certain files:
+cpp-precomp: warning: errors during smart preprocessing, retrying in basic mode
++ +
wxApp::s_macHelpMenuTitleName, it defaults to "&Help", but you can change it in your constructor to your specific menu title.
+wxApp::s_macAboutMenuItemID, it defaults to wxID_ABOUT, but can be changed as well to suit your needs.
+
diff --git a/docs/html/faqmot.htm b/docs/html/faqmot.htm
index 6250821885..6f907f0bfc 100644
--- a/docs/html/faqmot.htm
+++ b/docs/html/faqmot.htm
@@ -8,10 +8,10 @@
-
-
@@ -53,32 +61,23 @@ system is in preparation.
-
-
-
-
+
-
-
+
+
wxWindows 2 for Motif FAQ
@@ -22,8 +22,16 @@ wxWindows 2 for Motif FAQ
See also top-level FAQ page.
+List of questions in this category
+
+
+
-What version of Motif do I need?
+What version of Motif do I need?
You will need version 1.2 or above. Version 2 should also be fine. Some people
have had a positive experience with Lesstif,
@@ -31,7 +39,7 @@ a free Motif clone. (Note from Julian Smart - I use the Linux version of MetroLi
What features are missing or partially implemented?
+What features are missing or partially implemented?
The following classes are not yet implemented: wxSpinButton, wxCheckListBox, wxJoyStick,
wxGLCanvas.Does Dialog Editor work with wxWindows for Motif?
+Does Dialog Editor work with wxWindows for Motif?
Suport for Dialog Editor is almost there, but there are some wrinkles to iron
-out. You may find it's useful though: compile it and see.
+out. You may find it's useful though: compile it and see.
How do I switch between debugging and release compilation modes?
-
-Unfortunately the makefile system doesn't currently allow you to compile
-for both simultaneously: you need
-to recompile wxWindows and your application having adjusted make.env. However,
-you could rename the binary and release library archives, and adjust your makefiles
-to use the appropriate one (or change a symbolic link).
-Why are windows are not refreshed properly until I resize them?
+Why are windows are not refreshed properly until I resize them?
Very occasionally you can experience this glitch, probably because sometimes the
window tries to resize and repaint itself before the final size is known. The workaround
is to add code like this after window creation and initialization:
-#ifdef __WXMOTIF__
+#ifdef __WXMOTIF__
wxNoOptimize noOptimize;
- window->SetSize(-1, -1, w, h);
-#endif
+ window->SetSize(-1, -1, w, h);
+#endif