X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/c2d48b36a65f1f9adda42027cc02d7ace47890dc..d61c1a6f21202a9c9927452574cd5c6939255850:/docs/html/faqmsw.htm diff --git a/docs/html/faqmsw.htm b/docs/html/faqmsw.htm index 7cf90ae7ec..79b0ce996f 100644 --- a/docs/html/faqmsw.htm +++ b/docs/html/faqmsw.htm @@ -1,4 +1,3 @@ - @@ -35,6 +34,7 @@ See also top-level FAQ page.
  • Can you compile wxWindows 2 as a DLL?
  • How can I reduce executable size?
  • Is wxWindows 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?
    • @@ -44,6 +44,7 @@ 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??
    • @@ -63,25 +64,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 TWIN32 from Willows, -although TWIN32 is still in a preliminary state. The resulting executables are -Unix binaries that work with the TWIN32 Windows API emulator.

    +wxWindows 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 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 -programs with TWIN32, and finally produce an ix86 Windows executable using Cygwin/Mingw32, +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 is under consideration, though we need to get wxWindows Unicode-aware first. -There are other interesting issues, such as how to combine the menubar and toolbar APIs -as Windows CE requires. But there's no doubt that it will be possible, albeit -by mostly cutting down wxWindows 2 API functionality, and adding a few classes here -and there. Since wxWindows for 2 produces small binaries (less than 300K for -the statically-linked 'minimal' sample), shoehorning wxWindows 2 into a Windows CE device's limited -storage should not be a problem.

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

    What do I need to do for Windows XP?

    @@ -137,18 +131,17 @@ Please see the wxWindows 2 for Windows install.txt file for up-to-date informati currently the following are known to work:

    -There is a linking problem with Symantec C++ which I hope someone can help solve. -

    Which is the best compiler to use with wxWindows 2?

    @@ -178,24 +171,20 @@ wxWindows.

    Is Unicode supported?

    -Yes, Unicode is fully supported under Windows NT/2000 (Windows 9x don't -have Unicode support anyhow). +Yes, Unicode is fully supported under Windows NT/2000 and there is limited +support for it under Windows 9x using MSLU. +

    Does wxWindows support double byte fonts (Chinese/Japanese/Korean etc.)?

    -An answer from Klaus Goedde:

    - -"For Japanese under Win2000, it seems that wxWindows has no problems to work with double byte char sets -(I mean DBCS, that's not Unicode). First you have to install Japanese support on your Win2K system -and choose for ANSI translation -HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage=932 (default is 1252 for Western). -Then you can see all the funny Japanese letters under wxWindows too.

    - -In a wxTextCtrl control you have to set the window style "wxTE_RICH", otherwise this control shows the wrong -letters. - -I don't now whether it works on non W2K systems, because I'm just starting using wxWindows." -

    +For Japanese under Win2000, it seems that wxWindows has no problems to work +with double byte char sets (meaning DBCS, not Unicode). First you have to +install Japanese support on your Win2K system and choose for ANSI translation +HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage=932 +(default is 1252 for Western). Then you can see all the Japanese letters in +wxWindows applications. +

    Can you compile wxWindows 2 as a DLL?

    @@ -243,6 +232,21 @@ There is a sample which demonstrates MFC and wxWindows code co-existing in the s application. However, don't expect to be able to enable wxWindows windows with OLE-2 functionality using MFC.

    +

    Why do I get errors about setup.h not being found?

    + +When you build the wxWindows library, setup.h is copied +from include/wx/msw/setup.h to e.g. lib/mswd/wx/setup.h (the path +depends on the configuration you're building). So you need to add +this include path if building using the static Debug library:

    + +lib/mswd

    + +or if building the static Release library, lib/msw.

    + +See also the wxWiki Contents +for more information.

    + +

    Why do I get errors about FooBarA when I only use FooBar in my program?

    If you get errors like @@ -281,7 +285,8 @@ the VC++ CRT memory debugging features instead.

    How do I port MFC applications to wxWindows?

    -Set up your interface from scratch using wxWindows (especially wxDesigner -- +Set up your interface from scratch using wxWindows (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 modifications. This is the approach I have used, and I found @@ -329,7 +334,7 @@ example) and regenerate the makefile using tmake.

    tmake can be found at www.troll.no/freebies/tmake.html. -It's a Perl5 program and so it needs Perl (doh). There is a binary for +It's a Perl5 program and so it needs Perl (doh). There is a binary for Windows (available from the same page), but I haven't used it, so I don't know if it works as flawlessly as "perl tmake" does (note for people knowing Perl: don't try to run tmake with -w, it won't @@ -338,7 +343,7 @@ just go to distrib/msw/tmake and type

    tmake -t b32 wxwin.pro -o ../../src/msw/makefile.b32

    -The makefiles are untested - I don't have any of Borland, Watcom or +The makefiles are untested - I don't have any of Borland, Watcom or Symantec and I don't have enough diskspace to recompile even with VC6 using makefiles. The new makefiles are as close as possible to the old ones, but not closer: in fact, there has been many strange things @@ -445,7 +450,7 @@ First, you can use wxRegKey directly, for example: regKey.SetName(idName); { - wxLogNull dummy; + wxLogNull dummy; if (!regKey.Create()) { idName = wxT("HKEY_CURRENT_USER\\SOFTWARE\\My Company\\My Product\\Stuff\\"); @@ -490,6 +495,20 @@ 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 +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 +the files with the DOS line endings, so you must transform the files to this +format using any of the thousands ways to do it. +

    +Of course, another possibility is to always use only the Windows cvs client +and to avoid this problem completely. +

    +