X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/15a2de7e4fc86bf81c57c64d7de31a6882e3384c..b70362998b8f562923f6ed6708f06537ac056cd4:/docs/html/faqmsw.htm diff --git a/docs/html/faqmsw.htm b/docs/html/faqmsw.htm index f266bf1ba6..5a117ed58c 100644 --- a/docs/html/faqmsw.htm +++ b/docs/html/faqmsw.htm @@ -1,7 +1,8 @@ + -wxWidgets 2 for Windows FAQ +wxWidgets for Windows FAQ @@ -12,7 +13,7 @@ -wxWidgets 2 for Windows FAQ +wxWidgets for Windows FAQ @@ -28,10 +29,10 @@ See also top-level FAQ page.
  • What about Windows CE?
  • What do I need to do for Windows XP?
  • What compilers are supported?
    • -
  • Which is the best compiler to use with wxWidgets 2?
    • +
  • Which is the best compiler to use with wxWidgets?
  • Is Unicode supported?
  • Does wxWidgets support double byte fonts (Chinese/Japanese/Korean etc.)?
    • -
  • Can you compile wxWidgets 2 as a DLL?
    • +
  • Can you compile wxWidgets as a DLL?
  • How can I reduce executable size?
  • Is wxWidgets compatible with MFC?
  • Why do I get errors about setup.h not being found?
    • @@ -44,33 +45,27 @@ See also top-level FAQ page.
  • Why are menu hotkeys or shortcuts not working in my application?
  • Why can I not write to the HKLM part of the registry with wxRegConfig?
  • Is MS Active Accessibility supported?
    • -
  • Why does Visual C++ complain about corrupted project files??
    • +
  • Why does Visual C++ complain about corrupted project files?
  • Visual C++ gives errors about multiply defined symbols, what can I do?
    • -
  • Why do I get compilation erros when using wxWidgets with DirectShow?
    • +
  • Why do I get compilation errors when using wxWidgets with DirectShow?
  • How do I handle Windows messages in my wxWidgets program?

    • Which Windows platforms are supported?

    -wxWidgets 2 can be used to develop and deliver applications on Windows 3.1, Win32s, -Windows 95, Windows 98, Windows NT, Windows 2000, and Windows XP. A Windows CE -version is being looked into (see below).

    +wxWidgets can be used to develop and deliver applications on Windows 95, Windows 98, Windows NT, +Windows 2000, Windows XP, and Windows Vista. A Windows CE +port is also available (see below).

    -wxWidgets 2 is designed to make use of WIN32 features and controls. However, unlike Microsoft, -we have not forgotten users of 16-bit Windows. Most features -work under Windows 3.1, including wxTreeCtrl and wxListCtrl using the generic implementation. -However, don't expect very Windows-95-specific classes to work, such as wxTaskBarIcon. The wxRegConfig -class doesn't work either because the Windows 3.1 registry is very simplistic. Check out the 16-bit -makefiles to see what other files have been left out. -

    -16-bit compilation is supported under Visual C++ 1.5, and Borland BC++ 4 to 5. +16-bit compilation is only supported for wxWidgets 2.4 and previous versions, +using Visual C++ 1.5 and Borland BC++ 4 to 5.

    -wxWidgets 2 for Windows will also compile on Unix with gcc using Wine from WineHQ. +wxWidgets for Windows will also compile on Unix with gcc using Wine from WineHQ. The resulting executables are Unix binaries that work with the Wine Windows API emulator.

    -You can also compile wxWidgets 2 for Windows on Unix with Cygwin or Mingw32, resulting +You can also compile wxWidgets for Windows on Unix with Cygwin or Mingw32, resulting in executables that will run on Windows. So in theory you could write your applications using wxGTK or wxMotif, then check/debug your wxWidgets for Windows programs with Wine, and finally produce an ix86 Windows executable using Cygwin/Mingw32, @@ -78,10 +73,19 @@ without ever needing a copy of Microsoft Windows. See the Technical Note on the

    What about Windows CE?

    -This port is largely complete. For further information, see the wxEmbedded page.

    +This port supports Pocket PC 2002/2003 and MS Smartphone 2002/2003, using +Embedded Visual C++ 3 or 4. For further information, see the wxMSW section in +the wxWidgets Reference Manual, and also the wxEmbedded page.

    What do I need to do for Windows XP?

    +From wxWidgets 2.5, the XP manifest is included in wx/msw/wx.rc and +so your application will be themed automatically so long as you include wx.rc +in your own .rc file.

    + +For versions of wxWidgets below 2.5, you need to provide the manifest +explicitly, as follows.

    + In the same directory as you have your executable (e.g. foo.exe) you put a file called foo.exe.manifest in which you have something like the following: @@ -119,10 +123,6 @@ line:

    1 24 "winxp.manifest" -In wxWidgets 2.5, this will be in the wx/msw/wx.rc and -so will happen automatically so long as you include wx.rc -in your own .rc file.

    - For an explanation of this syntax, please see this article. @@ -130,7 +130,7 @@ article.

    What compilers are supported?

    -Please see the wxWidgets 2 for Windows install.txt file for up-to-date information, but +Please see the wxWidgets for Windows install.txt file for up-to-date information, but currently the following are known to work: