X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/d61c1a6f21202a9c9927452574cd5c6939255850..2006289b741f13c3d0a89f3758777850135f10e1:/docs/html/faqmsw.htm?ds=sidebyside diff --git a/docs/html/faqmsw.htm b/docs/html/faqmsw.htm index 79b0ce996f..070637bc53 100644 --- a/docs/html/faqmsw.htm +++ b/docs/html/faqmsw.htm @@ -1,7 +1,7 @@ -wxWindows 2 for Windows FAQ +wxWidgets 2 for Windows FAQ @@ -12,7 +12,7 @@ -wxWindows 2 for Windows FAQ +wxWidgets 2 for Windows FAQ @@ -28,33 +28,34 @@ 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 wxWindows 2?
    • +
  • Which is the best compiler to use with wxWidgets 2?
  • Is Unicode supported?
    • -
  • Does wxWindows support double byte fonts (Chinese/Japanese/Korean etc.)?
    • -
  • Can you compile wxWindows 2 as a DLL?
    • +
  • Does wxWidgets support double byte fonts (Chinese/Japanese/Korean etc.)?
    • +
  • Can you compile wxWidgets 2 as a DLL?
  • How can I reduce executable size?
    • -
  • Is wxWindows compatible with MFC?
    • +
  • Is wxWidgets compatible with MFC?
  • Why do I get errors about setup.h not being found?
  • Why do I get errors about FooBarA when I only use FooBar in my program?
  • Why my code fails to compile with strange errors about new operator?
    • -
  • How do I port MFC applications to wxWindows?
    • +
  • How do I port MFC applications to wxWidgets?
  • Why do I sometimes get bizarre crash problems using VC++ 5/6?
    • -
  • How are the wxWindows makefiles edited under Windows?
    • -
  • How do you use VC++'s memory leak checking instead of that in wxWindows?
    • +
  • How are the wxWidgets makefiles edited under Windows?
    • +
  • How do you use VC++'s memory leak checking instead of that in wxWidgets?
  • 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??
    • +
  • Visual C++ gives errors about multiply defined symbols, what can I do?

    • Which Windows platforms are supported?

    -wxWindows 2 can be used to develop and deliver applications on Windows 3.1, Win32s, +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).

    -wxWindows 2 is designed to make use of WIN32 features and controls. However, unlike Microsoft, +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 @@ -64,18 +65,18 @@ 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.

    -wxWindows 2 for Windows will also compile on Unix with gcc using Wine from WineHQ. +wxWidgets 2 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 wxWindows 2 for Windows on Unix with Cygwin or Mingw32, resulting +You can also compile wxWidgets 2 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 wxWindows for Windows +using wxGTK or wxMotif, then check/debug your wxWidgets for Windows programs with Wine, and finally produce an ix86 Windows executable using Cygwin/Mingw32, without ever needing a copy of Microsoft Windows. See the Technical Note on the Web site detailing cross-compilation.

    What about Windows CE?

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

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

    What do I need to do for Windows XP?

    @@ -116,7 +117,7 @@ line:

    1 24 "winxp.manifest" -In wxWindows 2.5, this will be in the wx/msw/wx.rc and +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.

    @@ -127,7 +128,7 @@ article.

    What compilers are supported?

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

    Notice that IMHO the first solution is preferable for VC++ users who can use the VC++ CRT memory debugging features instead. -

    How do I port MFC applications to wxWindows?

    +

    How do I port MFC applications to wxWidgets?

    -Set up your interface from scratch using wxWindows (especially wxDesigner +Set up your interface from scratch using wxWidgets (especially wxDesigner or DialogBlocks -- it'll save you a lot of time) and when you have a shell prepared, you can start 'pouring in' code from the MFC app, with appropriate @@ -293,14 +294,14 @@ modifications. This is the approach I have used, and I found it very satisfactory. A two-step process then - reproduce the bare interface first, then wire it up afterwards. That way you deal with each area of complexity separately. Don't try to think MFC -and wxWindows simultaneously from the beginning - it is easier to +and wxWidgets simultaneously from the beginning - it is easier to reproduce the initial UI by looking at the behaviour of the MFC app, not its code.

    Why do I sometimes get bizarre crash problems using VC++ 5/6?

    Some crash problems can be due to inconsistent compiler -options (and of course this isn't limited to wxWindows). +options (and of course this isn't limited to wxWidgets). If strange/weird/impossible things start to happen please check (dumping IDE project file as makefile and doing text comparison if necessary) that the project settings, especially the list of defined @@ -313,13 +314,13 @@ Editor, in Release mode with optimizations on. If in doubt, switch off optimisations, although this will result in much larger executables. It seems possible that the library can be created with strong optimization, so long as the application is not strongly -optimized. For example, in wxWindows project, set to 'Minimum +optimized. For example, in wxWidgets project, set to 'Minimum Size'. In Dialog Editor project, set to 'Customize: Favor Small Code' (and no others). This will then work.

    -

    How are the wxWindows makefiles edited under Windows?

    +

    How are the wxWidgets makefiles edited under Windows?

    -As of wxWindows 2.1, there is a new system written by Vadim Zeitlin, that +As of wxWidgets 2.1, there is a new system written by Vadim Zeitlin, that generates the makefiles from templates using tmake.

    Here are Vadim's notes:

    @@ -365,7 +366,7 @@ files to be compiled. Some of them are only compiled in 16/32 bit mode. Some other are only compiled with some compilers (others can't compile them) - all this info is contained in this file.

    -So now adding a new file to wxWindows is as easy as modifying filelist.txt +So now adding a new file to wxWidgets is as easy as modifying filelist.txt (and Makefile.ams for Unix ports) and regenerating the makefiles - no need to modify all files manually any more.

    @@ -375,11 +376,11 @@ I don't need it and can't test it, but it should be trivial to create one from vc6.t - probably the only things to change would be the version number in the very beginning and the /Z option - VC5 doesn't support edit-and=continue). This is not an officially supported way -of building wxWindows (that is, nobody guarantees that it will work), +of building wxWidgets (that is, nobody guarantees that it will work), but it has been very useful to me and I hope it will be also for -others. To generate wxWindows.dsp run

    +others. To generate wxWidgets.dsp run

    -

    tmake -t vc6 wxwin.pro -o ../../wxWindows.dsp

    +

    tmake -t vc6 wxwin.pro -o ../../wxWidgets.dsp

    Then just include this project in any workspace or open it from VC IDE and it will create a new workspace for you.

    @@ -393,13 +394,13 @@ directory by 10 (and the number of files to be maintained too).

    -

    How do you use VC++'s memory leak checking instead of that in wxWindows?

    +

    How do you use VC++'s memory leak checking instead of that in wxWidgets?

    Vadim Zeitlin: 
     On the VC++ level, it's just the matter of calling _CrtSetDbgFlag() in the very
-beginning of the program. In wxWindows, this is done automatically when
+beginning of the program. In wxWidgets, this is done automatically when
 compiling with VC++ in debug mode unless wxUSE_GLOBAL_MEMORY_OPERATORS or
 __NO_VC_CRTDBG__ are defined - this check is done in wx/msw/msvcrt.h which
 is included from app.cpp which then calls wxCrtSetDbgFlag() without any
@@ -436,7 +437,7 @@ Currently this is not possible because the wxConfig family of classes is
 supposed to deal with per-user application configuration data, and HKLM is
 only supposed to be writeable by a user with Administrator privileges. In theory,
 only installers should write to HKLM. This is still a point debated by the
-wxWindows developers. There are at least two ways to work around it if you really
+wxWidgets developers. There are at least two ways to work around it if you really
 need to write to HKLM.
    
 
 First, you can use wxRegKey directly, for example:
@@ -490,7 +491,7 @@ bool myGlobalConfig::Write (const wxString& key, const wxString& value)
 
 
    Is MS Active Accessibility supported?
    
 
-This is being worked on. Please see this page
+This is being worked on. Please see this page
 for the current status.
 
 
    
@@ -498,7 +499,7 @@ for the current status.
 
 
    Why does Visual C++ complain about corrupted project files??
    
 
-If you have downloaded the wxWindows sources from the cvs using a Unix cvs
+If you have downloaded the wxWidgets sources from the cvs using a Unix cvs
 client or downloaded a daily snapshot in .tar.gz format, it is likely
 that the project files have Unix line endings (LF) instead of the DOS ones (CR
 LF). However all versions of Visual C++ up to and including 7.1 can only open
@@ -509,6 +510,32 @@ Of course, another possibility is to always use only the Windows cvs client
 and to avoid this problem completely.
 
    
 
+
    Visual C++ gives errors about multiply defined symbols, what can I do?
    
+
+If you get errors like this
+
+
    +MSVCRTD.lib(MSVCRTD.dll) : error LNK2005: _xxxxxx already defined in LIBCD.lib(yyyyy.obj)
+
    
+
+when linking your project, this means that you used different versions of CRT
+(C Run-Time) library for wxWindows (or possibly another library) and the main
+project. Visual C++ provides static or dynamic and multithread safe or not
+versions of CRT for each of debug and release builds, for a total of 8
+libraries. You can choose among them by going to the "Code generation"
+page/subitem of the "C++" tab/item in the project proprieties dialog in VC6/7.
+
    
+To avoid problems, you must use the same one for all
+components of your project. wxWindows uses multithread safe DLL version of the
+CRT which is a good choice but may be problematic when distributing your
+applications if you don't include the CRT DLL in your installation -- in this
+case you may decide to switch to using a static CRT version. If you build with
+wxUSE_THREADS == 0 you may also use the non MT-safe version as it is
+slightly smaller and faster.
+
    
+But the most important thing is to use the same CRT setting for
+all components of your project.
+