X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/cd5082468fc4dd397d7eea951fa4e905ea3f9368..f24badde9a0efe4e2a18057045e044542f582158:/docs/html/faqmsw.htm?ds=sidebyside
diff --git a/docs/html/faqmsw.htm b/docs/html/faqmsw.htm
index 30970bb620..346e9de28d 100644
--- a/docs/html/faqmsw.htm
+++ b/docs/html/faqmsw.htm
@@ -35,6 +35,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 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?
Why do I sometimes get bizarre crash problems using VC++ 5/6?
@@ -201,7 +202,8 @@ Statically-linked wxWindows 2 programs are smaller than wxWindows 1.xx programs,
wxWindows 2 has been designed to reduce dependencies between classes, and other
techniques. The linker will not include code from the library that is not (directly or
indirectly) referenced
-by your application. So for example, the 'minimal' sample is less than 300KB using VC++ 6.
+by your application. So for example, the 'minimal' sample is less than 500KB using VC++ 6
+(note that this figure may be greater for the latest version of wxWindows).
If you want to distribute really small executables, you can
use Petite
@@ -210,12 +212,37 @@ will shrink to a mere 250KB. With this sort of size, there is reduced incentive
use DLLs. Another good compression tool is UPX.
+Please do not be surprised if MinGW produces a statically-linked minimal executable of 1 MB. Firstly, gcc
+produces larger executables than some compilers. Secondly, this figure will
+include most of the overhead of wxWindows, so as your application becomes more
+complex, the overhead becomes proportionaly less significant. And thirdly, trading executable compactness
+for the enormous increase in productivity you get with wxWindows is almost always well worth it.
+
There is a sample which demonstrates MFC and wxWindows code co-existing in the same
application. However, don't expect to be able to enable wxWindows windows with OLE-2
functionality using MFC.
+
+
+If you get errors like
+
+
+no matching function for call to 'wxDC::DrawTextA(const char[5], int,
+int)'
+
+
+or similar ones for the other functions, i.e. the compiler error messages
+mention the function with the 'A' suffix while you didn't
+use it in your code, the explanation is that you had included
+<windows.h> header which redefines many symbols to have such
+suffix (or 'W' in the Unicode builds).
+
+
+The fix is to either not include <windows.h> at all or include
+"wx/msw/winundef.h" immediately after it.
+
The most common cause of this problem is the memory debugging settings in
@@ -373,7 +400,11 @@ VZ
This can happen if you have a child window intercepting EVT_CHAR events and swallowing
all keyboard input. You should ensure that event.Skip() is called for all input that
-isn'used by the event handler.
+isn'used by the event handler.
+
+It can also happen if you append the submenu to the parent
+menu {\it before} you have added your menu items. Do the append {\it after} adding
+your items, or accelerators may not be registered properly.