X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/c6900c006b669c92ba6b0c5df9fd12b7da437a6f..4d7ec9f1e74d5925aae73e66602bfbd16468b04d:/docs/html/faqmsw.htm diff --git a/docs/html/faqmsw.htm b/docs/html/faqmsw.htm index ff37bf0d35..6d7a5452bf 100644 --- a/docs/html/faqmsw.htm +++ b/docs/html/faqmsw.htm @@ -1,3 +1,4 @@ + @@ -44,9 +45,9 @@ 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{/a>
  • Visual C++ gives errors about multiply defined symbols, what can I do?
    • -
  • Why do I get compilation errors when using wxWidgets with DirectShow?
    • +
  • Why do I get compilation erros when using wxWidgets with DirectShow?
  • How do I handle Windows messages in my wxWidgets program?
    • @@ -322,6 +323,10 @@ Code' (and no others). This will then work.

    How are the wxWidgets makefiles edited under Windows?

    +wxWidgets 2.5.x and above uses Bakefile to generate makefiles, which +is described in technical note 16 under docs/tech in your distribution. +For 2.4.x, the following explanation applies.

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

    @@ -359,7 +364,7 @@ The templates are described in tmake ref manual (1-2 pages of text) and are quite simple. They do contain some Perl code, but my Perl is primitive (very C like) so it should be possible for anybody to make trivial modifications to it (I hope that only trivial modifications -will be needed). I've tagged the old makefiles as MAKEFILES_WITHOUT_TMAKE +will be needed). I've tagged the ol makefiles as MAKEFILES_WITHOUT_TMAKE in the cvs, so you can always retrieve them and compare the new ones, this will make it easier to solve the problems you might have.

    @@ -437,7 +442,7 @@ your items, or accelerators may not be registered properly.

    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 writable by a user with Administrator privileges. In theory, +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 wxWidgets developers. There are at least two ways to work around it if you really need to write to HKLM.

    @@ -453,7 +458,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\\"); @@ -499,7 +504,7 @@ for the current status.

    -

    Why does Visual C++ complain about corrupted project files??

    +

    Why does Visual C++ complain about corrupted project files{/a>

    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 @@ -525,7 +530,7 @@ when linking your project, this means that you used different versions of CRT 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 properties dialog in VC6/7. +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 @@ -542,7 +547,7 @@ all components of your project. If you get errors when including Microsoft DirectShow or DirectDraw headers, the following message from Peter Whaite could help: -

    +
     > This causes compilation errors within DirectShow:
 >
 > wxutil.h(125) : error C2065: 'EXECUTE_ASSERT' : undeclared identifier
@@ -554,7 +559,7 @@ DXSDK/Samples/C++/DirectShow/BaseClasses/wxdebug.h.  So if __WXDEBUG__
 is defined, then wxdebug.h doesn't get included, and the assert macros
 don't get defined.  You have to #undef __WXDEBUG__ before including the
 directshow baseclass's <streams.h>.
-
    +

    How do I handle Windows messages in my wxWidgets program?