X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/2edb0bdef6238c8c246b6978bc14828b7033d931..b9b8a2b5d79c50af78720589dc96cd7e16cde26e:/docs/html/faqmac.htm diff --git a/docs/html/faqmac.htm b/docs/html/faqmac.htm index 7b4663fb96..4896e7e599 100644 --- a/docs/html/faqmac.htm +++ b/docs/html/faqmac.htm @@ -30,13 +30,15 @@ See also top-level FAQ page.
  • How is the Mac OS X port different from the Classic Mac OS port?
  • How are improvements to the Classic Mac OS port integrated into the Mac OS X port?
  • What compilers are supported?
  • -
  • How does CVS handle file types/creators under Mac OS 8.x/9.x?
  • -
  • How does CVS handle file types/creators under Mac OS X?
  • -
  • What steps are required to build wxMac using CodeWarrior Pro 5.3?
  • +
  • How does CVS handle file types/creators under Mac OS 8.x /9.x?
  • +
  • How does CVS handle file types/creators under Mac OS X?
  • +
  • What steps are required to build wxMac using CodeWarrior P ro 5.3?
  • What steps are required to build wxMac under Mac OS X?
  • What important settings are required in the CodeWarrior Project Preferences?
  • What are the smart preprocessing errors with the Apple Developer Tools?
  • How does wxMac support the standard Apple About menu item and Help menu?
  • +
  • How do I add an icon to my application?
  • +
  • How can I easily switch between different versions of wxWindows in CodeWarrior?

  • @@ -204,6 +206,31 @@ Because wxWindows does not have a specific API for the About menu item or

    +

    How do I add an icon to my application?

    + +If you have Mac OS X, you have the icns editor somewhere in the +Utilities folder. Create an icon using this tool and DeRez it, so that you have a .r +file with a 'icns' resource with id (-16455). Include this .r file in +your project and in the CodeWarrior Settings add a check mark under Linker:Output +Flags/Finder Flags/Has Custom Icon. +

    + +

    How can I easily switch between different versions of wxWindows in CodeWarrior?

    + +Sometimes you want to test your application against different versions +of wxWindows, for example a stable version of wxWindows versus a development version. +The easiest way to do this is to create a symbolic path.

    + +Under Edit-Preferences in General:Source Trees, type a name (for example WXWIN) +and choose a path for it. Now reselect your include and lib paths for a last +time, in the settings for each configuration, but make them relative to the symbolic name. +

    + +From now on you can just change the path associated with the symbolic name. + +

    + +