wxWidgets/samples/dll
Vadim Zeitlin 49b8d79c87 Remove (Open)Watcom support.
This compiler is not being developed since several years and almost certainly
can't be used to build the current wxWidgets sources anyhow, so remove all
support for it, including a lot of extremely ugly workarounds for its bugs
with template functions.

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@76546 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
2014-05-16 13:01:06 +00:00
..
dll_vc7_my_dll.vcproj Remove support for Win9x from wxMSW. 2014-05-16 02:33:40 +00:00
dll_vc7_sdk_exe.vcproj Don't include wxUniversal configurations in MSVC project files. 2013-01-21 16:37:01 +00:00
dll_vc7_wx_exe.vcproj Remove support for Win9x from wxMSW. 2014-05-16 02:33:40 +00:00
dll_vc8_my_dll.vcproj Remove support for Win9x from wxMSW. 2014-05-16 02:33:40 +00:00
dll_vc8_sdk_exe.vcproj Don't include wxUniversal configurations in MSVC project files. 2013-01-21 16:37:01 +00:00
dll_vc8_wx_exe.vcproj Remove support for Win9x from wxMSW. 2014-05-16 02:33:40 +00:00
dll_vc9_my_dll.vcproj Remove support for Win9x from wxMSW. 2014-05-16 02:33:40 +00:00
dll_vc9_sdk_exe.vcproj Don't include wxUniversal configurations in MSVC project files. 2013-01-21 16:37:01 +00:00
dll_vc9_wx_exe.vcproj Remove support for Win9x from wxMSW. 2014-05-16 02:33:40 +00:00
dll.bkl Remove all lines containing cvs/svn "$Id$" keyword. 2013-07-26 16:02:46 +00:00
makefile.bcc Remove support for Win9x from wxMSW. 2014-05-16 02:33:40 +00:00
makefile.gcc Remove support for Win9x from wxMSW. 2014-05-16 02:33:40 +00:00
Makefile.in Remove support for Win9x from wxMSW. 2014-05-16 02:33:40 +00:00
makefile.unx
makefile.vc Remove support for Win9x from wxMSW. 2014-05-16 02:33:40 +00:00
my_dll.cpp use "new" wx-prefixed macros in samples 2014-03-30 07:07:55 +00:00
my_dll.h Remove all lines containing cvs/svn "$Id$" keyword. 2013-07-26 16:02:46 +00:00
README.txt
sdk_exe.cpp Remove all lines containing cvs/svn "$Id$" keyword. 2013-07-26 16:02:46 +00:00
wx_exe.cpp use "new" wx-prefixed macros in samples 2014-03-30 07:07:55 +00:00

This Windows-specific sample demonstrates how to use wxWidgets-based UI from
within a foreign host application that may be written in any toolkit
(including wxWidgets).

For this to work, you have to overcome two obstacles:


(1) wx's event loop in the DLL must not conflict with the host app's loop
(2) if the host app is written in wx, its copy of wx must not conflict
    with the DLL's one


Number (1) is dealt with by running DLL's event loop in a thread of its own.
DLL's wx library will consider this thread to be the "main thread".

The simplest way to solve number (2) is to share the wxWidgets library between
the DLL and the host, in the form of wxWidgets DLLs build. But this requires
both the host and the DLL to be compiled against exactly same wx version,
which is often impractical.

So we do something else here: the DLL is compiled against *static* build of
wx. This way none of its symbols or variables will leak into the host app.
Win32 runtime conflicts are eliminated by using DLL's HINSTANCE instead of
host app's one and by using unique window class names (automatically done
since wx-2.9).