[wxWidgets.git] / docs / html / faqmac.htm


<HTML>

<HEAD>
<TITLE>wxWindows 2 for Mac FAQ</TITLE>
</HEAD>

<BODY BGCOLOR=#FFFFFF TEXT=#000000 VLINK="#00376A" LINK="#00529C" ALINK="#313063">

<font face="Arial, Lucida Sans, Helvetica">

<table width=100% border=0 cellpadding=3 cellspacing=0>
<tr>
<td bgcolor="#004080" align=left height=24 background="images/bluetitlegradient.gif">
<font size=+1 face="Arial, Lucida Sans, Helvetica" color="#FFFFFF">
<b>wxWindows 2 for Mac FAQ</b>
</font>
</td>
</tr>
</table>

<P>

See also <a href="faq.htm">top-level FAQ page</a>.
<hr>
<h3>List of questions in this category</h3>
<ul>
<li><a href="#release">When is wxMac 2.x due to be released?</a></li>
<li><a href="#macplat">Which Mac platforms are supported?</a></li>
<li><a href="#macosx">How is the Mac OS X port different from the Classic Mac OS port?</a></li>
<li><a href="#macclassic">How are improvements to the Classic Mac OS port integra ted into the Mac OS X port?</a></li>
<li><a href="#compilers">What compilers are supported?</a></li>
<li><a href="#filetypes">How does CVS handle file types/creators under Mac OS 8.x /9.x?</a></li>
<li><a href="#filetypesx">How does CVS handle file types/creators under Mac OS X? </a></li>
<li><a href="#cwpro53">What steps are required to build wxMac using CodeWarrior P ro 5.3?</a></li>
<li><a href="#buildx">What steps are required to build wxMac under Mac OS X?</a></li>
<li><a href="#settings">What important settings are required in the CodeWarrior P roject Preferences?</a></li>
<li><a href="#smarterrors">What are the smart preprocessing errors with the Apple Developer Tools?</a></li>
<li><a href="#aboutmenu">How does wxMac support the standard Apple About menu item and Help menu?</a></li>
</ul>
<hr>
<h3><a name="release">When is wxMac 2.x due to be released?</a></h3>

There is a <a href="dl_mac2.htm">preview</a> available.
The author of this port is <a href="mailto:csomor@advancedconcepts.ch">Stefan Csomor</a>.
<P>

<table border=0 cellpadding=5>
<tr>
<td bgcolor="#004080">
<font face="Arial, Lucida Sans, Helvetica">
<font size=2>
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 <a href="dl_mac2.htm#dev">development snapshot</a> or the sources from the <a href="cvs.htm">CVS trunk</a>.
</font>
</font></td>
</tr>
</table>

<P>

<h3><a name="macplat">Which Mac platforms are supported?</a></h3>

wxWindows 2 can be used to develop and deliver applications on Classic Mac OS (e.g. Mac OS 8.x/9.x) both as Carbon and non-Carbon applications.
<P>
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.
<P>

<h3><a name="macosx">How is the Mac OS X port different from the Classic Mac OS port?</a></h3>

wxMac for Mac OS X shares code both with wxMac for Mac OS and common Unix code in wxWindows. The aim is to use the same Mac OS Carbon code both for Classic Mac OS and for Mac OS X while leveraging the fact that Mac OS X is a BSD Unix.
<P>
This hybrid approach was suggested by Apple to the <a href="http://www.mozilla.org/ports/fizzilla/">Fizzilla</a> team working on <a href="http://www.mozilla.org/">Mozilla</a> for Mac OS X.
<P>

<h3><a name="macclassic">How are improvements to the Classic Mac OS port integrated into the Mac OS X port?</a></h3>

Since the source code is shared between the two ports, any Carbon compliant improvements to wxMac for Classic Mac OS are automatically available in the Mac OS X port.
<P>
The following points should be considered when improving wxMac:
<ul>
<li>Non Carbon compliant changes for Classic Mac OS will most likely break the Mac OS X port. <em>Such changes should be tested using the Carbon targets in the CodeWarrior projects for Classic Mac OS.</em>
<li>Non Carbon compliant changes for Mac OS X will most likely break the Classic Mac OS port. <em>Such changes should be tested using CodeWarrior under Mac OS 8.x/9.x.</em>
</ul>
<P>

<h3><a name="compilers">What compilers are supported?</a></h3>

Under Classic Mac OS, MetroWerks CodeWarrior Pro 5.3 or 6 are required to build wxMac.
<P>
Under Mac OS X, the Developer Tools are sufficient to build wxMac. CodeWarrior Pro 6 can also be used to build the Carbon targets.
<P>

<h3><a name="filetypes">How does CVS handle file types/creators under Mac OS 8.x/9.x?</a></h3>

Before checking out the wxWindows code using a CVS client under Mac OS 8.x/9.x, be sure your computer is set up to treat <code>xpm</code> and <code>xbm</code> images correctly:
<ul>
<li>bring up the Internet control panel, select the <i>Advanced Options</i> tab, click on the <i>File Mapping</i> icon from the list at the left and see if there are is an entry for ".xpm" files and another for ".xbm".
<li>if an entry exists, click <i>Change...</i> and make sure <i>File Type</i> is <code>TEXT</code> (just those four capital letters); correct it if necessary. If there is no entry, make one with type set to <code>TEXT</code> and creator set to anything you like; reasonable choices include <code>GKON</code> (Graphic Converter) or <code>CWIE</code> (CodeWarrior).
<li>if you want to edit <code>xpm</code> or <code>xbm</code> files in CodeWarrior, set up a file mapping in the CodeWarrior project settings for analogous to ".h" files.
</ul>
<P>

<h3><a name="filetypesx">How does CVS handle file types/creators under Mac OS X?</a></h3>

The Mac OS X CVS client does not handle file types and creators at all (just like every Unix command line CVS client). This is an issue only when the checked out files will also be used under Mac OS 8.x/9.x.
<P>
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:
<ul>
<li>decode and decompress the file <code>wxWindows/docs/mac/TypeAsMetrowerksText.sea.hqx</code>
<li>drag the wxWindows CVS sandbox directory onto the autotyper and most of the files will be typed according to the file extension
</ul>
<P>

<h3><a name="cwpro53">What steps are required to build wxMac using CodeWarrior Pro 5.3?</a></h3>

The latest build for Carbon support lead to a few changes that you will have to follow in order to successfully compile the code.
This is also necessary even if you don&#39;want to build the Carbon targets.

<ol>
<li>you need CodeWarrior Pro 5.3, i.e. 5.0 with all the upgrades
<li>you have to download the Universal Interfaces 3.3.2 or later from the Apple Developer web site, Universal Interfaces 3.4 is required for Carbon Printing support
<li>put the Universal folder into the MacOS Support folder and replace older versions
<li>remove from the MacOS Support folder the separate OpenTransport folder
<li>open the file MacOS Support:MacHeaders:MacHeaders.c and add the line
        <pre>#include &lt;ControlDefinitions.h&gt;</pre>
        after the line
        <pre>#include &lt;Controls.h&gt;</pre>
<li>rebuild all MacHeaders from the MacHeaders.mcp project in the same folder
</ol>
<P>
Build the projects (<code>makemac6.mcp</code> for CodeWarrior Pro 6; <code>makemac.mpc</code> for CodeWarrior Pro 5) in the following five directories:
<ul>
<li>wxWindows:src:
<li>wxWindows:src:jpeg:
<li>wxWindows:src:png:
<li>wxWindows:src:tiff:
<li>wxWindows:src:zlib:
</ul>
<P>

<h3><a name="buildx">What steps are required to build wxMac under Mac OS X?</a></h3>

You need to have the Apple Developer Tools installed. The Developer Tools CD is one of the 3 CDs that are delivered with Mac OS X but must be installed in addition to the default Mac OS X installation.
<P>
Building wxMac completely without configure is not supported.
<P>
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:
<ul>
<li><code>mkdir macbuild</code>
<li><code>cd macbuild</code>
<li><code>../configure</code> <b>or</b> <code>../configure --enable-debug</code>
<li><code>make</code>
</ul>
<P>

<h3><a name="settings">What important settings are required in the CodeWarrior Project Preferences?</a></h3>

For some reasons the CodeWarrior project settings may get changed and this may lead to the inability to compile a certain target. In order to verify the settings click on the target tab, double click on the respective target and then select the following items on the tree-view on the left. Here are the important checks:

<ol>

<li>under <code>Target/Access Paths</code>, make sure the first user include does not have a folder icon for recursive search.

<li> under <code>Language Settings/C/C++ Language</code>, make sure that the only checked items are:
<ul>
<li><code>Enable C++ Exceptions</code>
<li><code>Enable RTTI</code>
<li><code>Enable bool Support</code>
<li><code>Enable wchar_t Support</code>
<li><code>Relaxed Pointer Type Rules</code>
<li><code>Use Unsigned Chars</code>
</ul>

<li>under <code>Language Settings/C/C++ Warnings</code>, make sure that the only checked items are:
<ul>
<li><code>Illegal Pragmas</code>
<li><code>Extended Error Checking</code>
<li><code>Inconsistent Use of 'class' and 'struct' Keywords</code>
<li><code>Hidden Virtual Functions</code> but be aware that the framework itself has some of these beauty spots
</ul>

<li>under <code>Linker/PPC Linker</code>, make sure that the following items are checked:
<ul>
<li><code>Dead-strip Static Initialization Code</code> in order to avoid including libraries that are not needed, especially as things like <a href="http://developer.apple.com/opengl/index.html">OpenGL</a> get added to the projects and sources
</ul>

</ol>
<P>

<h3><a name="smarterrors">What are the smart preprocessing errors with the Apple Developer Tools?</a></h3>

Smart preprocessing is activated with the <code>-cpp-precomp</code> 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:
<ul>
<li><code>cpp-precomp: warning: errors during smart preprocessing, retrying in basic mode</code>
</ul>

This error is due to the smart precompiler which does not fully understand C++ syntax and reverts to basic preprocessing when a smart preprocessing error occurs.
This error can sometimes be corrected or avoided by modifying the source code. However, leaving these errors is not a problem since the preprocessor automatically switches to basic preprocessing if necessary.
<P>

<h3><a name="aboutmenu">How does wxMac support the standard Apple About menu item and Help menu?</a></h3>

Because wxWindows does not have a specific API for the <i>About</i> menu item or the <i>Help</i> menu, the Mac OS port uses some static variables to help the engine make the right decisions:
<ul>
<li>It assumes that the <i>About</i> menu item is part of a <i>Help</i> menu.
<li>The title of the <i>Help</i> menu is stored in <code>wxApp::s_macHelpMenuTitleName</code>, it defaults to "&Help", but you can change it in your constructor to your specific menu title.
<li>The item Id of the <i>About</i> menu is stored in <code>wxApp::s_macAboutMenuItemID</code>, it defaults to <code>wxID_ABOUT</code>, but can be changed as well to suit your needs.
<li>The other items of the wxWindows help menu are appended to the Mac OS <i>Help</i> menu and the translation of Ids is handled transparently for your application.
</ul>
<P>

</font>

</BODY>

</HTML>
Commit	Line	Data
4e4dc03d	1
ce3ed50d JS	2	<HTML>
	3
	4	<HEAD>
	5	<TITLE>wxWindows 2 for Mac FAQ</TITLE>
	6	</HEAD>
	7
4e4dc03d	8	<BODY BGCOLOR=#FFFFFF TEXT=#000000 VLINK="#00376A" LINK="#00529C" ALINK="#313063">
ce3ed50d JS	9
	10	<font face="Arial, Lucida Sans, Helvetica">
	11
4e4dc03d	12	<table width=100% border=0 cellpadding=3 cellspacing=0>
ce3ed50d	13	<tr>
4e4dc03d JS	14	<td bgcolor="#004080" align=left height=24 background="images/bluetitlegradient.gif">
	15	<font size=+1 face="Arial, Lucida Sans, Helvetica" color="#FFFFFF">
	16	<b>wxWindows 2 for Mac FAQ</b>
ce3ed50d JS	17	</font>
	18	</td>
	19	</tr>
	20	</table>
	21
	22	<P>
	23
	24	See also <a href="faq.htm">top-level FAQ page</a>.
	25	<hr>
31523f51 GD	26	<h3>List of questions in this category</h3>
	27	<ul>
	28	<li><a href="#release">When is wxMac 2.x due to be released?</a></li>
	29	<li><a href="#macplat">Which Mac platforms are supported?</a></li>
	30	<li><a href="#macosx">How is the Mac OS X port different from the Classic Mac OS port?</a></li>
	31	<li><a href="#macclassic">How are improvements to the Classic Mac OS port integra ted into the Mac OS X port?</a></li>
	32	<li><a href="#compilers">What compilers are supported?</a></li>
	33	<li><a href="#filetypes">How does CVS handle file types/creators under Mac OS 8.x /9.x?</a></li>
	34	<li><a href="#filetypesx">How does CVS handle file types/creators under Mac OS X? </a></li>
	35	<li><a href="#cwpro53">What steps are required to build wxMac using CodeWarrior P ro 5.3?</a></li>
8b283bb8	36	<li><a href="#buildx">What steps are required to build wxMac under Mac OS X?</a></li>
31523f51 GD	37	<li><a href="#settings">What important settings are required in the CodeWarrior P roject Preferences?</a></li>
31523f51 GD	38	<li><a href="#smarterrors">What are the smart preprocessing errors with the Apple Developer Tools?</a></li>
8b283bb8	39	<li><a href="#aboutmenu">How does wxMac support the standard Apple About menu item and Help menu?</a></li>
31523f51 GD	40	</ul>
	41	<hr>
	42	<h3><a name="release">When is wxMac 2.x due to be released?</a></h3>
ce3ed50d	43
8b283bb8	44	There is a <a href="dl_mac2.htm">preview</a> available.
31523f51 GD	45	The author of this port is <a href="mailto:csomor@advancedconcepts.ch">Stefan Csomor</a>.
	46	<P>
	47
	48	<table border=0 cellpadding=5>
	49	<tr>
4e4dc03d JS	50	<td bgcolor="#004080">
4e4dc03d JS	51	<font face="Arial, Lucida Sans, Helvetica">
31523f51 GD	52	<font size=2>
31523f51 GD	53	Please note that the version of wxMac in CVS is more robust and nearly feature-complete compared with the packaged 2.0 release.
8b283bb8	54	Until a new release is made, it is recommended that you download the wxMac 2.3.1 <a href="dl_mac2.htm#dev">development snapshot</a> or the sources from the <a href="cvs.htm">CVS trunk</a>.
31523f51	55	</font>
8b283bb8	56	</font></td>
31523f51 GD	57	</tr>
	58	</table>
	59
	60	<P>
	61
	62	<h3><a name="macplat">Which Mac platforms are supported?</a></h3>
	63
	64	wxWindows 2 can be used to develop and deliver applications on Classic Mac OS (e.g. Mac OS 8.x/9.x) both as Carbon and non-Carbon applications.
	65	<P>
	66	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.
	67	The Mac OS X port is based on and, for the most part, merged with the Carbon code for Classic Mac OS.
	68	<P>
	69
	70	<h3><a name="macosx">How is the Mac OS X port different from the Classic Mac OS port?</a></h3>
	71
	72	wxMac for Mac OS X shares code both with wxMac for Mac OS and common Unix code in wxWindows. The aim is to use the same Mac OS Carbon code both for Classic Mac OS and for Mac OS X while leveraging the fact that Mac OS X is a BSD Unix.
	73	<P>
	74	This hybrid approach was suggested by Apple to the <a href="http://www.mozilla.org/ports/fizzilla/">Fizzilla</a> team working on <a href="http://www.mozilla.org/">Mozilla</a> for Mac OS X.
	75	<P>
	76
	77	<h3><a name="macclassic">How are improvements to the Classic Mac OS port integrated into the Mac OS X port?</a></h3>
	78
	79	Since the source code is shared between the two ports, any Carbon compliant improvements to wxMac for Classic Mac OS are automatically available in the Mac OS X port.
	80	<P>
	81	The following points should be considered when improving wxMac:
	82	<ul>
	83	<li>Non Carbon compliant changes for Classic Mac OS will most likely break the Mac OS X port. <em>Such changes should be tested using the Carbon targets in the CodeWarrior projects for Classic Mac OS.</em>
	84	<li>Non Carbon compliant changes for Mac OS X will most likely break the Classic Mac OS port. <em>Such changes should be tested using CodeWarrior under Mac OS 8.x/9.x.</em>
	85	</ul>
	86	<P>
	87
	88	<h3><a name="compilers">What compilers are supported?</a></h3>
	89
	90	Under Classic Mac OS, MetroWerks CodeWarrior Pro 5.3 or 6 are required to build wxMac.
	91	<P>
	92	Under Mac OS X, the Developer Tools are sufficient to build wxMac. CodeWarrior Pro 6 can also be used to build the Carbon targets.
	93	<P>
	94
	95	<h3><a name="filetypes">How does CVS handle file types/creators under Mac OS 8.x/9.x?</a></h3>
	96
	97	Before checking out the wxWindows code using a CVS client under Mac OS 8.x/9.x, be sure your computer is set up to treat <code>xpm</code> and <code>xbm</code> images correctly:
	98	<ul>
	99	<li>bring up the Internet control panel, select the <i>Advanced Options</i> tab, click on the <i>File Mapping</i> icon from the list at the left and see if there are is an entry for ".xpm" files and another for ".xbm".
	100	<li>if an entry exists, click <i>Change...</i> and make sure <i>File Type</i> is <code>TEXT</code> (just those four capital letters); correct it if necessary. If there is no entry, make one with type set to <code>TEXT</code> and creator set to anything you like; reasonable choices include <code>GKON</code> (Graphic Converter) or <code>CWIE</code> (CodeWarrior).
	101	<li>if you want to edit <code>xpm</code> or <code>xbm</code> files in CodeWarrior, set up a file mapping in the CodeWarrior project settings for analogous to ".h" files.
	102	</ul>
	103	<P>
	104
	105	<h3><a name="filetypesx">How does CVS handle file types/creators under Mac OS X?</a></h3>
	106
	107	The Mac OS X CVS client does not handle file types and creators at all (just like every Unix command line CVS client). This is an issue only when the checked out files will also be used under Mac OS 8.x/9.x.
	108	<P>
	109	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:
	110	<ul>
	111	<li>decode and decompress the file <code>wxWindows/docs/mac/TypeAsMetrowerksText.sea.hqx</code>
	112	<li>drag the wxWindows CVS sandbox directory onto the autotyper and most of the files will be typed according to the file extension
	113	</ul>
	114	<P>
	115
	116	<h3><a name="cwpro53">What steps are required to build wxMac using CodeWarrior Pro 5.3?</a></h3>
	117
	118	The latest build for Carbon support lead to a few changes that you will have to follow in order to successfully compile the code.
	119	This is also necessary even if you don'want to build the Carbon targets.
	120
121	<ol>
122	<li>you need CodeWarrior Pro 5.3, i.e. 5.0 with all the upgrades
123	<li>you have to download the Universal Interfaces 3.3.2 or later from the Apple Developer web site, Universal Interfaces 3.4 is required for Carbon Printing support
124	<li>put the Universal folder into the MacOS Support folder and replace older versions
125	<li>remove from the MacOS Support folder the separate OpenTransport folder
126	<li>open the file MacOS Support:MacHeaders:MacHeaders.c and add the line
127	<pre>#include <ControlDefinitions.h></pre>
128	after the line
129	<pre>#include <Controls.h></pre>
130	<li>rebuild all MacHeaders from the MacHeaders.mcp project in the same folder
131	</ol>
132	<P>
133	Build the projects (<code>makemac6.mcp</code> for CodeWarrior Pro 6; <code>makemac.mpc</code> for CodeWarrior Pro 5) in the following five directories:
134	<ul>
135	<li>wxWindows:src:
136	<li>wxWindows:src:jpeg:
137	<li>wxWindows:src:png:
138	<li>wxWindows:src:tiff:
139	<li>wxWindows:src:zlib:
140	</ul>
141	<P>
142
143	<h3><a name="buildx">What steps are required to build wxMac under Mac OS X?</a></h3>
144
145	You need to have the Apple Developer Tools installed. The Developer Tools CD is one of the 3 CDs that are delivered with Mac OS X but must be installed in addition to the default Mac OS X installation.
146	<P>
147	Building wxMac completely without configure is not supported.
148	<P>
149	Building wxWindows directly in the CVS sandbox is not recommended. Instead, wxWindows should be built in a directory configured relatively to the CVS sandbox.
150	For instance, to build wxMac with configure, start in the base wxWindows directory and type:
151	<ul>
152	<li><code>mkdir macbuild</code>
153	<li><code>cd macbuild</code>
154	<li><code>../configure</code> <b>or</b> <code>../configure --enable-debug</code>
155	<li><code>make</code>
156	</ul>
157	<P>
158
159	<h3><a name="settings">What important settings are required in the CodeWarrior Project Preferences?</a></h3>
160
161	For some reasons the CodeWarrior project settings may get changed and this may lead to the inability to compile a certain target. In order to verify the settings click on the target tab, double click on the respective target and then select the following items on the tree-view on the left. Here are the important checks:
162
163	<ol>
164
165	<li>under <code>Target/Access Paths</code>, make sure the first user include does not have a folder icon for recursive search.
166
167	<li> under <code>Language Settings/C/C++ Language</code>, make sure that the only checked items are:
168	<ul>
169	<li><code>Enable C++ Exceptions</code>
170	<li><code>Enable RTTI</code>
171	<li><code>Enable bool Support</code>
172	<li><code>Enable wchar_t Support</code>
173	<li><code>Relaxed Pointer Type Rules</code>
174	<li><code>Use Unsigned Chars</code>
175	</ul>
176
177	<li>under <code>Language Settings/C/C++ Warnings</code>, make sure that the only checked items are:
178	<ul>
179	<li><code>Illegal Pragmas</code>
180	<li><code>Extended Error Checking</code>
181	<li><code>Inconsistent Use of 'class' and 'struct' Keywords</code>
182	<li><code>Hidden Virtual Functions</code> but be aware that the framework itself has some of these beauty spots
183	</ul>
184
185	<li>under <code>Linker/PPC Linker</code>, make sure that the following items are checked:
186	<ul>
187	<li><code>Dead-strip Static Initialization Code</code> in order to avoid including libraries that are not needed, especially as things like <a href="http://developer.apple.com/opengl/index.html">OpenGL</a> get added to the projects and sources
188	</ul>
189
190	</ol>
191	<P>
192
193	<h3><a name="smarterrors">What are the smart preprocessing errors with the Apple Developer Tools?</a></h3>
194
195	Smart preprocessing is activated with the <code>-cpp-precomp</code> 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.
196	When compiling wxMac using the Apple Developer Tools, the following error is displayed for certain files:
197	<ul>
198	<li><code>cpp-precomp: warning: errors during smart preprocessing, retrying in basic mode</code>
199	</ul>
200
201	This error is due to the smart precompiler which does not fully understand C++ syntax and reverts to basic preprocessing when a smart preprocessing error occurs.
202	This error can sometimes be corrected or avoided by modifying the source code. However, leaving these errors is not a problem since the preprocessor automatically switches to basic preprocessing if necessary.
203	<P>
204
205	<h3><a name="aboutmenu">How does wxMac support the standard Apple About menu item and Help menu?</a></h3>
206
207	Because wxWindows does not have a specific API for the <i>About</i> menu item or the <i>Help</i> menu, the Mac OS port uses some static variables to help the engine make the right decisions:
208	<ul>
209	<li>It assumes that the <i>About</i> menu item is part of a <i>Help</i> menu.
210	<li>The title of the <i>Help</i> menu is stored in <code>wxApp::s_macHelpMenuTitleName</code>, it defaults to "&Help", but you can change it in your constructor to your specific menu title.
211	<li>The item Id of the <i>About</i> menu is stored in <code>wxApp::s_macAboutMenuItemID</code>, it defaults to <code>wxID_ABOUT</code>, but can be changed as well to suit your needs.
212	<li>The other items of the wxWindows help menu are appended to the Mac OS <i>Help</i> menu and the translation of Ids is handled transparently for your application.
213	</ul>
ce3ed50d JS	214	<P>
	215
	216	</font>
	217
	218	</BODY>
	219
	220	</HTML>