Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Misc fixes

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@12516 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Julian Smart
2001-11-20 14:55:10 +00:00
parent ecdba0d10f
commit 8b283bb88e
11 changed files with 300 additions and 182 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
distrib/msw/generic.rsp
View File

@@ -113,6 +113,19 @@ src/zlib/makefile*
src/zlib/*.com src/zlib/*.com
src/zlib/*.3 src/zlib/*.3
src/regex/COPYRIGHT
src/regex/makefile*
src/regex/README
src/regex/WHATSNEW
src/regex/mkh
src/regex/makefile*
src/regex/*.h
src/regex/*.ih
src/regex/*.c
src/regex/tests
src/regex/regex.3
src/regex/regex.7
include/wx/*.h include/wx/*.h
include/wx/*.inl include/wx/*.inl
include/wx/*.cpp include/wx/*.cpp

2
distrib/msw/makefile.rsp
View File

@@ -1,4 +1,5 @@
Makefile.in Makefile.in
src/regex/Makefile.in
locale/Makefile locale/Makefile
samples/Makefile.in samples/Makefile.in
samples/calendar/Makefile.in samples/calendar/Makefile.in
@@ -157,4 +158,5 @@ src/motif/descrip.mms
src/png/scripts/descrip.mms src/png/scripts/descrip.mms
src/unix/descrip.mms src/unix/descrip.mms
src/zlib/descrip.mms src/zlib/descrip.mms
src/regex/descrip.mms
utils/dialoged/src/descrip.mms utils/dialoged/src/descrip.mms

3
distrib/msw/vc.rsp
View File

@@ -22,6 +22,9 @@ src/zlib/zlib.dsw
src/png/png.dsp src/png/png.dsp
src/png/png.dsw src/png/png.dsw
src/regex/regex.dsp
src/regex/regex.dsw
samples/samples.dsw samples/samples.dsw
samples/calendar/Calendar.dsp samples/calendar/Calendar.dsp

8
distrib/msw/zipdistinno.bat
View File

@@ -3,6 +3,7 @@ rem Zip up an external, generic + Windows distribution of wxWindows 2
rem using Inno Setup + ScriptMaker rem using Inno Setup + ScriptMaker
set src=%wxwin set src=%wxwin
set dest=%src\deliver set dest=%src\deliver
set webfiles=c:\wx2dev\wxWebSite
set inno=0 set inno=0
Rem Set this to the required version Rem Set this to the required version
@@ -43,6 +44,13 @@ erase %dest\make*
if direxist %dest\wx erase /sxyz %dest\wx\ if direxist %dest\wx erase /sxyz %dest\wx\
if not direxist %dest mkdir %dest if not direxist %dest mkdir %dest
# Copy FAQ from wxWebSite CVS
if not direxist %webfiles% echo Error - %webfiles% does not exist
if not direxist %webfiles% goto end
echo Copying FAQ and other files from %webfiles
copy %webfiles%\site\faq*.htm %src\docs\html
copy %webfiles%\site\platform.htm %src\docs\html
cd %src cd %src
echo Zipping... echo Zipping...

1
docs/html/faq.htm
View File

@@ -1,3 +1,4 @@
<HTML> <HTML>
<HEAD> <HEAD>

149
docs/html/faqgen.htm
View File

@@ -1,3 +1,4 @@
<HTML> <HTML>
<HEAD> <HEAD>
@@ -22,22 +23,38 @@ wxWindows 2 FAQ: General
See also <a href="faq.htm">top-level FAQ page</a>. See also <a href="faq.htm">top-level FAQ page</a>.
<hr> <hr>
<h3>List of questions in this category</h3>
<ul>
<li><a href="#whatis">What is wxWindows?</a></li>
<li><a href="#users">Who uses wxWindows?</a></li>
<li><a href="#platforms">What platforms are supported by wxWindows 2?</a></li>
<li><a href="#specific">How does wxWindows 2 support platform-specific features?</a></li>
<li><a href="#stl">Does wxWindows use STL? or the standard string class?</a></li>
<li><a href="#richedit">Is there a rich edit/markup widget for wxWindows 2?</a></ li>
<li><a href="#dev">How is wxWindows 2 being developed?</a></li>
<li><a href="#distrib">How is wxWindows 2 distributed?</a></li>
<li><a href="#future">What are the plans for the future?</a></li>
<li><a href="#univ">What is wxUniversal?</a></li>
<li><a href="#jave">What about Java?</a></li>
<li><a href="#help">How can I help the project?</a></li>
</ul>
<hr>
<H3><a name="whatis">What is wxWindows?</a></H3> <H3><a name="whatis">What is wxWindows?</a></H3>
wxWindows is a class library that allows you to compile graphical C++ programs on a range of wxWindows is a class library that allows you to compile graphical C++ programs on a range of
different platforms. wxWindows defines a common API across platforms, but uses the native graphical user interface (GUI) on each platform, different platforms. wxWindows defines a common API across platforms, but uses the native graphical user interface (GUI) on each platform,
so your program will take on the native 'look and feel' that users are familiar with.<P> so your program will take on the native &#39;look and feel&#39; that users are familiar with.<P>
Although GUI applications are mostly built programmatically, there is a dialog editor to help Although GUI applications are mostly built programmatically, there is a dialog editor to help
build attractive dialogs and panels. Robert Roebling's <a href="http://www.roebling.com">wxDesigner</a> build attractive dialogs and panels. Robert Roebling&#39;s <a href="http://www.roebling.com">wxDesigner</a>
makes light work of resizable, portable dialogs.<P> makes light work of resizable, portable dialogs.<P>
You don't have to use C++ to use wxWindows: wxWindows 1 has been interfaced to several interpreted languages, You don&#39;t have to use C++ to use wxWindows: there is a <a href="http://wxpython.org">Python interface</a> for wxWindows 2,
such as CLIPS, Python, Scheme, XLisp and Perl, and there is a <a href="http://wxpython.org">Python interface</a> for wxWindows 2. and also a <a href="http://wxperl.sourceforge.net" target=_top>Perl interface</a>.
<P> <P>
<h3>Can I use wxWindows 2 for both proprietary (commercial) projects, and GPL'ed projects?</h3> <h3>Can I use wxWindows 2 for both proprietary (commercial) projects, and GPL&#39;ed projects?</h3>
Yes. Please see the <a href="newlicen.htm">licence</a> for details, but basically Yes. Please see the <a href="newlicen.htm">licence</a> for details, but basically
you can distribute proprietary binaries without distributing any source code, and neither will wxWindows you can distribute proprietary binaries without distributing any source code, and neither will wxWindows
@@ -57,7 +74,7 @@ keen to fix bugs as soon as possible, though obviously there are no guarantees.
<H3><a name="users">Who uses wxWindows?</a></H3> <H3><a name="users">Who uses wxWindows?</a></H3>
Many organisations - commercial, government, and academic - across the Many organisations - commercial, government, and academic - across the
world. It's impossible to estimate the true number of users, since world. It&#39;s impossible to estimate the true number of users, since
wxWindows is obtained by many different means, and we cannot monitor wxWindows is obtained by many different means, and we cannot monitor
distribution. The mailing list contains around 300-400 entries which is distribution. The mailing list contains around 300-400 entries which is
quite large for a list of this type.<P> quite large for a list of this type.<P>
@@ -65,62 +82,28 @@ quite large for a list of this type.<P>
See <a href="users.htm">Users</a> for a list of some users and their applications, and See <a href="users.htm">Users</a> for a list of some users and their applications, and
also <A href="feedback.htm">Feedback</a> for comments.<P> also <A href="feedback.htm">Feedback</a> for comments.<P>
<H3>How much has the API changed since 1.xx?</H3> <H3><a name="platforms">What platforms are supported by wxWindows 2?</a></H3>
It's difficult to summarize, but some aspects haven't changed very much. For example, if you have some
complex drawing code, you will mostly need to make sure it's parameterised with a device
context (instead of obtaining one from a window or storing it). You won't have
to completely rewrite the drawing code.<P>
The way that events are handled has changed, so for example, where you overrode
OnSize before, you now have a non-virtual OnSize with a single event class argument.
To make this function known to wxWindows, you add an entry in an 'event table' using macros. Addition of these macros
will eventually be made easier by a tool which will allow selection from a list
and copy-and-paste into your editor. This is extended to button presses, listbox selection
etc. so callbacks have gone (they may be added back for limited backward compatibility).<P>
The class hierarchy has changed to allow greater flexibility but it probably won't affect your
existing application. One exception to this is MDI applications which now use separate MDI classes instead of style
flags. As a result, it won't be possible to switch between MDI and SDI operation at run-time
without further coding, but a benefit is less interdependence between areas of code,
and therefore smaller executable size.<P>
Panel items (now called controls) no longer have labels associated with most of them,
and default panel layout has been removed. The idea is that you make greater use
of dialog resources, for better-looking dialogs.<P>
<H3>What classes have disappeared?</H3>
wxForm, wxTextWindow (subsumed into wxTextCtrl).
<H3>Does wxWindows 2 mean that wxWindows 1.xx is dead?</H3>
While wxWindows 2 is being developed, there will be further patches to wxWindows 1.xx.
Obviously we are investing most of our energy into the new code, but we're also trying
to fix bugs in the current version.<P>
<H3>What platforms are supported by wxWindows 2?</H3>
<ul> <ul>
<li>Windows 3.1, Windows 95/98, Windows NT; <li>Windows 3.1, Windows 95/98, Windows NT, Windows 2000, Windows ME.
<li>Linux and other Unix platforms with GTK+; <li>Linux and other Unix platforms with GTK+.
<li>Unix with Motif or the free Motif clone Lesstif; <li>Unix with Motif or the free Motif clone Lesstif.
<li>Mac; <li>Mac OS.
<li>A BeOS port is being investigated. <li>Embedded platforms are being investigated. See the <a href="wxuniv.htm">wxUniversal</a> project.
<li>A Windows CE port is being investigated.
<li>An OS/2 port is in progress, and you can also compile wxWindows for GTK+ or Motif <li>An OS/2 port is in progress, and you can also compile wxWindows for GTK+ or Motif
on OS/2. on OS/2.
</ul> </ul>
<P> <P>
<H3>How does wxWindows 2 support platform-specific features?</H3> <H3><a name="specific">How does wxWindows 2 support platform-specific
features?</a></H3>
This is a hotly-debated topic amongst the developers. My own philosophy This is a hotly-debated topic amongst the developers. My own philosophy
is to make wxWindows as platform-independent as possible, but allow in a is to make wxWindows as platform-independent as possible, but allow in a
few classes (functions, window styles) that are platform-specific. few classes (functions, window styles) that are platform-specific.
For example, Windows metafiles and Windows 95 taskbar icons have For example, Windows metafiles and Windows 95 taskbar icons have
their own classes on Windows, but nowhere else. Because these classes their own classes on Windows, but nowhere else. Because these classes
are provided and are wxWindows-compatible, it doesn't take much are provided and are wxWindows-compatible, it doesn&#39;t take much
coding effort for an application programmer to add support for coding effort for an application programmer to add support for
some functionality that the user on a particular platform might otherwise some functionality that the user on a particular platform might otherwise
miss. Also, some classes that started off as platform-specific, such miss. Also, some classes that started off as platform-specific, such
@@ -128,24 +111,24 @@ as the MDI classes, have been emulated on other platforms. I can imagine
that even wxTaskBarIcon may be implemented for Unix desktops one day. that even wxTaskBarIcon may be implemented for Unix desktops one day.
<P> <P>
In other words, wxWindows is not a 'lowest common denominator' approach, In other words, wxWindows is not a &#39;lowest common denominator&#39; approach,
but it will still be possible to write portable programs using the but it will still be possible to write portable programs using the
core API. Forbidding some platform-specific classes would be a stupid core API. Forbidding some platform-specific classes would be a stupid
approach that would alienate many potential users, and encourage approach that would alienate many potential users, and encourage
the perception that toolkits such as wxWindows are not up to the demands the perception that toolkits such as wxWindows are not up to the demands
of today's sophisticated applications.<P> of today&#39;s sophisticated applications.<P>
Currently resources such as bitmaps and icons are handled in a platform-specific Currently resources such as bitmaps and icons are handled in a platform-specific
way, but it is hoped to reduce this dependence in due course.<P> way, but it is hoped to reduce this dependence in due course.<P>
Another reason why wxWindows 2 is not a 'lowest common denominator' toolkit is that Another reason why wxWindows 2 is not a &#39;lowest common denominator&#39; toolkit is that
some functionality missing on some platform has been provided using generic, some functionality missing on some platform has been provided using generic,
platform-independent code, such as the wxTreeCtrl and wxListCtrl classes.<P> platform-independent code, such as the wxTreeCtrl and wxListCtrl classes.<P>
<H3>Does wxWindows use STL? or the standard string class?</H3> <H3><a name="stl">Does wxWindows use STL? or the standard string class?</a></H3>
No. This is a much-discussed topic that has (many times) ended with the conclusion that it is in No. This is a much-discussed topic that has (many times) ended with the conclusion that it is in
wxWindows' best interests to avoid use of templates. Not all compilers can handle wxWindows&#39; best interests to avoid use of templates. Not all compilers can handle
templates adequately so it would dramatically reduce the number of compilers templates adequately so it would dramatically reduce the number of compilers
and platforms that could be supported. It would also be undersirable to make and platforms that could be supported. It would also be undersirable to make
wxWindows dependent on another large library that may have to be downloaded and installed. wxWindows dependent on another large library that may have to be downloaded and installed.
@@ -158,9 +141,20 @@ by being able to modify our own string class. Some compatibility with the string
has been built into wxString.<P> has been built into wxString.<P>
There is nothing to stop an application using templates or the string class for its own There is nothing to stop an application using templates or the string class for its own
purposes.<P> purposes. With wxWindows debugging options on, you may find you get errors when including
STL headers. You can work around it either by switching off memory checking,
or by adding this to a header before you include any STL files:<P>
<H3>Is there a rich edit/markup widget for wxWindows 2?</H3> <PRE>
&#35;ifdef new
&#35;undef new
&#35;endif
</PRE>
<P>
<H3><a name="richedit">Is there a rich edit/markup widget for wxWindows 2?</a></H3>
These are the possibilities so far:<P> These are the possibilities so far:<P>
@@ -173,12 +167,12 @@ for this widget.
then wxHTML will suit your needs. wxHTML is built into wxWindows - please see the reference then wxHTML will suit your needs. wxHTML is built into wxWindows - please see the reference
manual for details, and samples/html. manual for details, and samples/html.
<li>There are rich edit widgets in both WIN32 and GTK+, but there is currently <li>There are rich edit widgets in both WIN32 and GTK+, but there is currently
no wxWindows wrapper for these. no wxWindows wrapper for these (but text attribute functions are being added in the wxWindows 2.3.x series).
</ul> </ul>
<P> <P>
<H3>How is wxWindows 2 being developed?</H3> <H3><a name="dev">How is wxWindows 2 being developed?</a></H3>
We are using the <a href="cvs.htm">CVS</a> system to develop and maintain wxWindows. This allows We are using the <a href="cvs.htm">CVS</a> system to develop and maintain wxWindows. This allows
us to make alterations and upload them instantly to the SourceForge server, from us to make alterations and upload them instantly to the SourceForge server, from
@@ -187,20 +181,24 @@ which others can update their source.<P>
To build source from CVS, see the file BuildCVS.txt in the top-level wxWindows distribution To build source from CVS, see the file BuildCVS.txt in the top-level wxWindows distribution
directory.<P> directory.<P>
<H3>How is wxWindows 2 distributed?</H3> <H3><a name="distrib">How is wxWindows 2 distributed?</a></H3>
By ftp, and via the <a href="cdrom2.htm">wxWindows CD-ROM</a>.<P> By ftp, and via the <a href="cdrom2.htm">wxWindows CD-ROM</a>.
<P>
If you are feeling adventurous, you may also check out the sources directly
from the <a href="cvs.htm">cvs</a>
<p>
<H3>What are the plans for the future?</H3> <H3><a name="future">What are the plans for the future?</a></H3>
Currently we're working too hard on getting wxWindows 2 finished (are GUI toolkits ever Currently we&#39;re working too hard on getting wxWindows 2 finished (are GUI toolkits ever
finished?) to think very far ahead. However, we know we want to make wxWindows as robust finished?) to think very far ahead. However, we know we want to make wxWindows as robust
and well-publicised as possible. We also want to aim for better platform-independence of and well-publicised as possible. We also want to aim for better platform-independence of
resources such as icons and bitmaps, standardising on the PNG for all platforms.<P> resources such as icons and bitmaps, standardising on the PNG for all platforms.<P>
Other possibilities include: DCOM/CORBA compatibility; a wxWindows book; Other possibilities include: DCOM/CORBA compatibility; a wxWindows book;
<a href="http://wxstudio.linuxbox.com/">wxStudio</a>, an IDE; <a href="http://wxworkshop.sourceforge.net/">wxWorkshop</a>, an IDE;
other platforms; other interface abilities such as speech output.<P> other platforms, especially embedded systems; other interface abilities such as speech output.<P>
We will investigate the possibility of compiler or operating system vendors bundling wxWindows with We will investigate the possibility of compiler or operating system vendors bundling wxWindows with
their product.<P> their product.<P>
@@ -208,17 +206,28 @@ their product.<P>
The high-level goal of wxWindows is to be thought of as the number one C++ framework, The high-level goal of wxWindows is to be thought of as the number one C++ framework,
for virtually any platform. Move over, MFC!<P> for virtually any platform. Move over, MFC!<P>
<H3>What about Java?</H3> <H3><a name="univ">What is wxUniversal?</a></H3>
wxUniversal is a new port of wxWindows being currently actively developed. The
main difference is that wxUniversal implements all controls (or widgets) in
wxWindows itself thus allowing to have much more flexibility (i.e. support for
themes even under MS Windows!). It also means that it is now much easier to
port wxWindows to a new platform as only the low-level classes must be ported
which make for a small part of the library.
<p>
You may find more about wxUniversal <a href=wxuniv.htm>here</a>.
<H3><a name="jave">What about Java?</a></H3>
The Java honeymoon period is over :-) and people are realising that it cannot The Java honeymoon period is over :-) and people are realising that it cannot
meet all their cross-platform development needs. We don't anticipate a major threat meet all their cross-platform development needs. We don&#39;t anticipate a major threat
from Java, and the level of interest in wxWindows is as high as ever.<P> from Java, and the level of interest in wxWindows is as high as ever.<P>
<H3>How can I help the project?</H3> <H3><a name="help">How can I help the project?</a></H3>
Please check out the <a href="http://www.wxwindows.org/develop.htm" target=main>Backroom</a> pages, Please check out the <a href="http://www.wxwindows.org/develop2.htm">Community</a> pages,
in particular the <a href="http://www.wxwindows.org/projects.htm">suggested projects</a>, and in particular the <a href="projects.htm">suggested projects</a>, and
mail <a href="mailto:julian.smart@ukonline.co.uk">Julian Smart</a> or the developers' mailing list with your own suggestions.<P> mail <a href="mailto:julian.smart@btopenworld.com">Julian Smart</a> or the developers&#39; mailing list with your own suggestions.<P>
</font> </font>

21
docs/html/faqgtk.htm
View File

@@ -22,23 +22,36 @@ wxWindows 2 for GTK FAQ
See also <a href="faq.htm">top-level FAQ page</a>. See also <a href="faq.htm">top-level FAQ page</a>.
<hr> <hr>
<h3>List of questions in this category</h3>
<h3>What is wxWindows 2 for GTK?</h3> <li><a href="#wxgtk">What is wxWindows 2 for GTK?</a></li>
<li><a href="#gnome">Does wxGTK have GNOME support?</a></li>
<li><a href="#redhat">Warning about GTK libraries supplied with RedHat</a></li>
<li><a href="#wxgtk">What is wxWindows 2 for GTK?</a></li>
<hr>
wxWindows 2 for GTK is a port of wxWindows to the <a href="http://www.gimp.org/gtk" target=_top>GTK+ toolkit</a>, wxWindows 2 for GTK is a port of wxWindows to the <a href="http://www.gimp.org/gtk" target=_top>GTK+ toolkit</a>,
which is freely available for most flavours of Unix with X. wxWindows 2 for GTK is which is freely available for most flavours of Unix with X. wxWindows 2 for GTK is
often abbreviated to wxGTK. wxGTK has a separate home page <a href="http://www.freiburg.linux.de/~wxxt" target=_top>here</a>. often abbreviated to wxGTK. wxGTK has a separate home page <a href="http://www.freiburg.linux.de/~wxxt" target=_top>here</a>.
<P> <P>
<h3>Does wxGTK have GNOME support?</h3> <h3><a name="gnome">Does wxGTK have GNOME support?</a></h3>
Currently wxGTK does not have any features that would involve dependence on any desktop Currently wxGTK does not have any features that would involve dependence on any desktop
environment's libraries, so it can work on GNOME, KDE and with other window managers environment&#39;s libraries, so it can work on GNOME, KDE and with other window managers
without installation hassles. Some GNOME and KDE integration features are file based, and without installation hassles. Some GNOME and KDE integration features are file based, and
so may be added without dependence on libraries. Other features may be supported in the so may be added without dependence on libraries. Other features may be supported in the
future, probably as a separate library. future, probably as a separate library.
<P> <P>
<h3><a name="redhat">Warning about GTK libraries supplied with RedHat</a></h3>
It seems that some versions of RedHat include a badly patched version of GTK (not wxGTK)
which causes some trouble with wxWindows&#39; socket code. Common symptoms are that when
a client tries to establish a connection to an existing server which refuses the request,
the client will get notified twice, first getting a LOST event and then a CONNECT event.
This problem can be solved by updating GTK with an official distribution of the library.
<P>
</font> </font>

10
docs/html/faqmac.htm
View File

@@ -32,15 +32,15 @@ See also <a href="faq.htm">top-level FAQ page</a>.
<li><a href="#filetypes">How does CVS handle file types/creators under Mac OS 8.x /9.x?</a></li> <li><a href="#filetypes">How does CVS handle file types/creators under Mac OS 8.x /9.x?</a></li>
<li><a href="#filetypesx">How does CVS handle file types/creators under Mac OS X? </a></li> <li><a href="#filetypesx">How does CVS handle file types/creators under Mac OS X? </a></li>
<li><a href="#cwpro53">What steps are required to build wxMac using CodeWarrior P ro 5.3?</a></li> <li><a href="#cwpro53">What steps are required to build wxMac using CodeWarrior P ro 5.3?</a></li>
<li><a href="#buildx">What steps are required to build wxMac under Mac OS X?</a>< /li> <li><a href="#buildx">What steps are required to build wxMac under Mac OS X?</a></li>
<li><a href="#settings">What important settings are required in the CodeWarrior P roject Preferences?</a></li> <li><a href="#settings">What important settings are required in the CodeWarrior P roject Preferences?</a></li>
<li><a href="#smarterrors">What are the smart preprocessing errors with the Apple Developer Tools?</a></li> <li><a href="#smarterrors">What are the smart preprocessing errors with the Apple Developer Tools?</a></li>
<li><a href="#aboutmenu">How does wxMac support the standard Apple About menu ite m and Help menu?</a></li> <li><a href="#aboutmenu">How does wxMac support the standard Apple About menu item and Help menu?</a></li>
</ul> </ul>
<hr> <hr>
<h3><a name="release">When is wxMac 2.x due to be released?</a></h3> <h3><a name="release">When is wxMac 2.x due to be released?</a></h3>
There is a <a href="http://www.wxwindows.org/dl_mac2.htm">preview</a> available. There is a <a href="dl_mac2.htm">preview</a> available.
The author of this port is <a href="mailto:csomor@advancedconcepts.ch">Stefan Csomor</a>. The author of this port is <a href="mailto:csomor@advancedconcepts.ch">Stefan Csomor</a>.
<P> <P>
@@ -50,9 +50,9 @@ The author of this port is <a href="mailto:csomor@advancedconcepts.ch">Stefan Cs
<FONT FACE="Arial, Lucida Sans, Helvetica"> <FONT FACE="Arial, Lucida Sans, Helvetica">
<font size=2> <font size=2>
Please note that the version of wxMac in CVS is more robust and nearly feature-complete compared with the packaged 2.0 release. Please note that the version of wxMac in CVS is more robust and nearly feature-complete compared with the packaged 2.0 release.
Until a new release is made, it is recommended that you download the wxMac 2.3.1 <a href="http://www.wxwindows.org/dl_mac2.htm#dev">development snapshot</a> or the sources from the <a href="http://www.wxwindows.org/cvs.htm">CVS trunk</a>. Until a new release is made, it is recommended that you download the wxMac 2.3.1 <a href="dl_mac2.htm#dev">development snapshot</a> or the sources from the <a href="cvs.htm">CVS trunk</a>.
</font> </font>
</td> </font></td>
</tr> </tr>
</table> </table>

171
docs/html/faqmsw.htm
View File

@@ -22,8 +22,26 @@ wxWindows 2 for Windows FAQ
See also <a href="faq.htm">top-level FAQ page</a>. See also <a href="faq.htm">top-level FAQ page</a>.
<hr> <hr>
<h3>List of questions in this category</h3>
<ul>
<li><a href="#platforms">Which Windows platforms are supported?</a></li>
<li><a href="#wince">What about Windows CE?</a></li>
<li><a href="#compilers">What compilers are supported?</a></li>
<li><a href="#bestcompiler">Which is the best compiler to use with wxWindows 2?</a></li>
<li><a href="#unicode">Is Unicode supported?</a></li>
<li><a href="#dll">Can you compile wxWindows 2 as a DLL?</a></li>
<li><a href="#exesize">How can I reduce executable size?</a></li>
<li><a href="#mfc">Is wxWindows compatible with MFC?</a></li>
<li><a href="#newerrors">Why my code fails to compile with strange errors about new operator?</a></li>
<li><a href="#mfcport">How do I port MFC applications to wxWindows?</a></li>
<li><a href="#crash">Why do I sometimes get bizarre crash problems using VC++ 5/6?</a></li>
<li><a href="#makefiles">How are the wxWindows makefiles edited under Windows?</a></li>
<li><a href="#vcdebug">How do you use VC++&#39;s memory leak checking instead of that in wxWindows?</a></li>
<li><a href="#shortcutproblem">Why are menu hotkeys or shortcuts not working in my application?</a></li>
</ul>
<hr>
<h3>Which Windows platforms are supported?</h3> <h3><a name="platforms">Which Windows platforms are supported?</a></h3>
wxWindows 2 can be used to develop and deliver applications on Windows 3.1, Win32s, wxWindows 2 can be used to develop and deliver applications on Windows 3.1, Win32s,
Windows 95, Windows 98, and Windows NT. A Windows CE version is being looked into (see below).<P> Windows 95, Windows 98, and Windows NT. A Windows CE version is being looked into (see below).<P>
@@ -31,8 +49,8 @@ Windows 95, Windows 98, and Windows NT. A Windows CE version is being looked int
wxWindows 2 is designed to make use of WIN32 features and controls. However, unlike Microsoft, wxWindows 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 we have not forgotten users of 16-bit Windows. Most features
work under Windows 3.1, including wxTreeCtrl and wxListCtrl using the generic implementation. 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 However, don&#39;t expect very Windows-95-specific classes to work, such as wxTaskBarIcon. The wxRegConfig
class doesn't work either because the Windows 3.1 registry is very simplistic. Check out the 16-bit class doesn&#39;t work either because the Windows 3.1 registry is very simplistic. Check out the 16-bit
makefiles to see what other files have been left out. makefiles to see what other files have been left out.
<P> <P>
16-bit compilation is supported under Visual C++ 1.5, and Borland BC++ 4 to 5. 16-bit compilation is supported under Visual C++ 1.5, and Borland BC++ 4 to 5.
@@ -48,17 +66,17 @@ 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 TWIN32, 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.<P> without ever needing a copy of Microsoft Windows. See the Technical Note on the Web site detailing cross-compilation.<P>
<h3>What about Windows CE?</h3> <h3><a name="wince">What about Windows CE?</a></h3>
This is under consideration, though we need to get wxWindows Unicode-aware first. 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 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 as Windows CE requires. But there&#39;s no doubt that it will be possible, albeit
by mostly cutting down wxWindows 2 API functionality, and adding a few classes here 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 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 the statically-linked &#39;minimal&#39; sample), shoehorning wxWindows 2 into a Windows CE device&#39;s limited
storage should not be a problem.<P> storage should not be a problem.<P>
<h3>What compilers are supported?</h3> <h3><a name="compilers">What compilers are supported?</a></h3>
Please see the wxWindows 2 for Windows install.txt file for up-to-date information, but Please see the wxWindows 2 for Windows install.txt file for up-to-date information, but
currently the following are known to work:<P> currently the following are known to work:<P>
@@ -77,43 +95,42 @@ currently the following are known to work:<P>
There is a linking problem with Symantec C++ which I hope someone can help solve. There is a linking problem with Symantec C++ which I hope someone can help solve.
<P> <P>
<h3>Which is the best compiler to use with wxWindows 2?</h3> <h3><a name="bestcompiler">Which is the best compiler to use with wxWindows 2?</a></h3>
It's partly a matter of taste, but I (JACS) prefer Visual C++ since the debugger is very It&#39;s partly a matter of taste, but I (JACS) prefer Visual C++ since the debugger is very
good, it's very stable, the documentation is extensive, and it generates small executables. good, it&#39;s very stable, the documentation is extensive, and it generates small executables.
Since project files are plain text, it's easy for me to generate appropriate project files Since project files are plain text, it&#39;s easy for me to generate appropriate project files
for wxWindows samples.<P> for wxWindows samples.<P>
Borland C++ is fine - and very fast - but it's hard (impossible?) to use the debugger without using project files, and Borland C++ is fine - and very fast - but it&#39;s hard (impossible?) to use the debugger without using project files, and
the debugger is nowhere near up to VC++'s quality. The IDE isn't great.<P> the debugger is nowhere near up to VC++&#39;s quality. The IDE isn&#39;t great.<P>
C++Builder's power isn't really used with wxWindows since it needs integration with its C++Builder&#39;s power isn&#39;t really used with wxWindows since it needs integration with its
own class library (VCL). For wxWindows, I've only used it with makefiles, in which case own class library (VCL). For wxWindows, I&#39;ve only used it with makefiles, in which case
it's almost identical to BC++ 5.0 (the same makefiles can be used).<P> it&#39;s almost identical to BC++ 5.0 (the same makefiles can be used).<P>
You can't beat Cygwin's price (free), and you can debug adequately using gdb. However, it's You can&#39;t beat Cygwin&#39;s price (free), and you can debug adequately using gdb. However, it&#39;s
quite slow to compile since it does not use precompiled headers.<P> quite slow to compile since it does not use precompiled headers.<P>
CodeWarrior is cross-platform - you can debug and generate Windows executables from a Mac, but not CodeWarrior is cross-platform - you can debug and generate Windows executables from a Mac, but not
the other way around I think - but the IDE is, to my mind, a bit primitive.<P> the other way around I think - but the IDE is, to my mind, a bit primitive.<P>
Watcom C++ is a little slow and the debugger is not really up to today's standards.<P> Watcom C++ is a little slow and the debugger is not really up to today&#39;s standards.<P>
<h3>Is Unicode supported?</h3> Among the free compilers the best choice seem to be Borland C++ command line
tools and mingw32 (port of gcc to Win32). Both of them are supported by
wxWindows.
Not yet, although there are other internationalisation features.<P> <h3><a name="unicode">Is Unicode supported?</a></h3>
However, the issues surrounding Unicode support have been looked into so we know Yes, Unicode is fully supported under Windows NT/2000 (Windows 9x don&#39;t
what we need to do, and have some header files ready to use containing appropriate have Unicode support anyhow).
type definitions. Just about every file in wxWindows will need changes, due to the
pervasive nature of characters and character arrays. Unicode support is needed
for the port to Windows CE (see above), and will probably be added in time for version 2.1.<P>
<h3>Can you compile wxWindows 2 as a DLL?</h3> <h3><a name="dll">Can you compile wxWindows 2 as a DLL?</a></h3>
Yes (using the Visual C++ or Borland C++ makefile), but be aware that distributing DLLs is a thorny issue Yes (using the Visual C++ or Borland C++ makefile), but be aware that distributing DLLs is a thorny issue
and you may be better off compiling statically-linked applications, unless you're and you may be better off compiling statically-linked applications, unless you&#39;re
delivering a suite of separate programs, or you're compiling a lot of wxWindows applications delivering a suite of separate programs, or you&#39;re compiling a lot of wxWindows applications
and have limited hard disk space.<P> and have limited hard disk space.<P>
With a DLL approach, and with different versions and configurations of wxWindows With a DLL approach, and with different versions and configurations of wxWindows
@@ -122,7 +139,7 @@ negating the point of using DLLs. Of course, this is not a problem just associat
wxWindows! wxWindows!
<P> <P>
<H3>How can I reduce executable size?</H3> <h3><a name="exesize">How can I reduce executable size?</a></h3>
You can compile wxWindows as a DLL (see above, VC++/BC++ only at present). You should also You can compile wxWindows as a DLL (see above, VC++/BC++ only at present). You should also
compile your programs for release using non-debugging and space-optimisation options, but compile your programs for release using non-debugging and space-optimisation options, but
@@ -132,7 +149,7 @@ Statically-linked wxWindows 2 programs are smaller than wxWindows 1.xx programs,
wxWindows 2 has been designed to reduce dependencies between classes, and other 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 techniques. The linker will not include code from the library that is not (directly or
indirectly) referenced indirectly) referenced
by your application. So for example, the 'minimal' sample is less than 300KB using VC++ 6.<P> by your application. So for example, the &#39;minimal&#39; sample is less than 300KB using VC++ 6.<P>
If you want to distribute really small executables, you can If you want to distribute really small executables, you can
use <a href="http://www.icl.ndirect.co.uk/petite/" target=_top>Petite</a> use <a href="http://www.icl.ndirect.co.uk/petite/" target=_top>Petite</a>
@@ -140,60 +157,90 @@ by Ian Luck. This nifty utility compresses Windows executables by around 50%, so
will shrink to a mere 250KB. With this sort of size, there is reduced incentive to will shrink to a mere 250KB. With this sort of size, there is reduced incentive to
use DLLs.<P> use DLLs.<P>
<H3>Is wxWindows compatible with MFC?</H3> <H3><a name="mfc">Is wxWindows compatible with MFC?</a></H3>
There is a sample which demonstrates MFC and wxWindows code co-existing in the same 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 application. However, don&#39;t expect to be able to enable wxWindows windows with OLE-2
functionality using MFC.<P> functionality using MFC.<P>
<H3>Why do I sometimes get bizarre crash problems using VC++ 5/6?</H3> <H3><a name="newerrors">Why my code fails to compile with strange errors about new operator?</a></H3>
The most common cause of this problem is the memory debugging settings in
<tt>wx/msw/setup.h</tt>. You have several choices:
<ul>
<li> Either disable overloading the global operator new completely by
setting <tt>wxUSE_GLOBAL_MEMORY_OPERATORS</tt> and
<tt>wxUSE_DEBUG_NEW_ALWAYS</tt> to 0 in this file
<li> Or leave them on but do <tt>#undef new</tt> after including any
wxWindows headers, like this the memory debugging will be still on
for wxWindows sources but off for your own code
</ul>
Notice that IMHO the first solution is preferable for VC++ users who can use
the <a href="#vcdebug">VC++ CRT memory debugging features</a> instead.
<H3><a name="mfcport">How do I port MFC applications to wxWindows?</a></H3>
Set up your interface from scratch using wxWindows (especially wxDesigner --
it&#39;ll save you a <i>lot</i> of time) and when you have a shell prepared, you can start
&#39;pouring in&#39; code from the MFC app, with appropriate
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&#39;t try to think MFC
and wxWindows simultaneously from the beginning - it is easier to
reproduce the initial UI by looking at the behaviour of the MFC
app, not its code.
<H3><a name="crash">Why do I sometimes get bizarre crash problems using VC++ 5/6?</a></H3>
Some crash problems can be due to inconsistent compiler 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&#39;t limited to wxWindows).
If strange/weird/impossible things start to happen please If strange/weird/impossible things start to happen please
check (dumping IDE project file as makefile and doing text comparison check (dumping IDE project file as makefile and doing text comparison
if necessary) that the project settings, especially the list of defined if necessary) that the project settings, especially the list of defined
symbols, struct packing, etc. are exactly the same for all items in symbols, struct packing, etc. are exactly the same for all items in
the project. After this, delete everything (including PCH) and recompile.<P> the project. After this, delete everything (including PCH) and recompile.<P>
VC++ 5's optimization code seems to be broken and can VC++ 5&#39;s optimization code seems to be broken and can
cause problems: this can be seen when deleting an object Dialog cause problems: this can be seen when deleting an object Dialog
Editor, in Release mode with optimizations on. If in doubt, Editor, in Release mode with optimizations on. If in doubt,
switch off optimisations, although this will result in much switch off optimisations, although this will result in much
larger executables. It seems possible that the library can be created with larger executables. It seems possible that the library can be created with
strong optimization, so long as the application is not strongly strong optimization, so long as the application is not strongly
optimized. For example, in wxWindows project, set to 'Minimum optimized. For example, in wxWindows project, set to &#39;Minimum
Size'. In Dialog Editor project, set to 'Customize: Favor Small Size&#39;. In Dialog Editor project, set to &#39;Customize: Favor Small
Code' (and no others). This will then work.<P> Code&#39; (and no others). This will then work.<P>
<H3>How are the wxWindows makefiles edited under Windows?</H3> <H3><a name="makefiles">How are the wxWindows makefiles edited under Windows?</a></H3>
As of wxWindows 2.1, there is a new system written by Vadim Zeitlin, that As of wxWindows 2.1, there is a new system written by Vadim Zeitlin, that
generates the makefiles from templates using tmake.<P> generates the makefiles from templates using tmake.<P>
Here are Vadim's notes:<P> Here are Vadim&#39;s notes:<P>
<blockquote> <blockquote>
To use these new makefiles, you don't need anything (but see below). To use these new makefiles, you don&#39;t need anything (but see below).
However, you should NOT modify them because these files will be However, you should NOT modify them because these files will be
rewritten when I regenerate them using tmake the next time. So, if rewritten when I regenerate them using tmake the next time. So, if
you find a problem with any of these makefiles (say, makefile.b32) you find a problem with any of these makefiles (say, makefile.b32)
you'll need to modify the corresponding template (b32.t in this you&#39;ll need to modify the corresponding template (b32.t in this
example) and regenerate the makefile using tmake.<P> example) and regenerate the makefile using tmake.<P>
tmake can be found at tmake can be found at
<a href="http://www.troll.no/freebies/tmake.html" target=_new>www.troll.no/freebies/tmake.html</a>. <a href="http://www.troll.no/freebies/tmake.html" target=_new>www.troll.no/freebies/tmake.html</a>.
It's a Perl5 program and so it needs Perl (doh). There is a binary for It&#39;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 Windows (available from the same page), but I haven&#39;t used it, so
I don't know if it works as flawlessly as "perl tmake" does (note I don&#39;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 for people knowing Perl: don&#39;t try to run tmake with -w, it won&#39;t
do you any good). Using it extremely simple: to regenerate makefile.b32 do you any good). Using it extremely simple: to regenerate makefile.b32
just go to distrib/msw/tmake and type<P> just go to distrib/msw/tmake and type<P>
<pre>tmake -t b32 wxwin.pro -o ../../src/msw/makefile.b32</pre><P> <pre>tmake -t b32 wxwin.pro -o ../../src/msw/makefile.b32</pre><P>
The makefiles are untested - I don't have any of Borland, Watcom or The makefiles are untested - I don&#39;t have any of Borland, Watcom or
Symantec and I don't have enough diskspace to recompile even with Symantec and I don&#39;t have enough diskspace to recompile even with
VC6 using makefiles. The new makefiles are as close as possible to the 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 old ones, but not closer: in fact, there has been many strange things
(should I say bugs?) in some of makefiles, some files were not compiled (should I say bugs?) in some of makefiles, some files were not compiled
@@ -205,13 +252,13 @@ 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 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 primitive (very C like) so it should be possible for anybody to make
trivial modifications to it (I hope that only trivial modifications trivial modifications to it (I hope that only trivial modifications
will be needed). I've tagged the ol makefiles as MAKEFILES_WITHOUT_TMAKE will be needed). I&#39;ve tagged the ol makefiles as MAKEFILES_WITHOUT_TMAKE
in the cvs, so you can always retrieve them and compare the new ones, 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.<P> this will make it easier to solve the problems you might have.<P>
Another important file is filelist.txt: it contains the list of all Another important file is filelist.txt: it contains the list of all
files to be compiled. Some of them are only compiled in 16/32 bit mode. 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 Some other are only compiled with some compilers (others can&#39;t compile
them) - all this info is contained in this file.<P> them) - all this info is contained in this file.<P>
So now adding a new file to wxWindows is as easy as modifying filelist.txt So now adding a new file to wxWindows is as easy as modifying filelist.txt
@@ -219,10 +266,10 @@ So now adding a new file to wxWindows is as easy as modifying filelist.txt
need to modify all files manually any more.<P> need to modify all files manually any more.<P>
Finally, there is also a file vc6.t which I use myself: this one Finally, there is also a file vc6.t which I use myself: this one
generates a project file for VC++ 6.0 (I didn't create vc5.t because generates a project file for VC++ 6.0 (I didn&#39;t create vc5.t because
I don't need it and can't test it, but it should be trivial to create I don&#39;t need it and can&#39;t test it, but it should be trivial to create
one from vc6.t - probably the only things to change would be the 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 version number in the very beginning and the /Z option - VC5 doesn&#39;t
support edit-and=continue). This is not an officially supported way support edit-and=continue). This is not an officially supported way
of building wxWindows (that is, nobody guarantees that it will work), of building wxWindows (that is, nobody guarantees that it will work),
but it has been very useful to me and I hope it will be also for but it has been very useful to me and I hope it will be also for
@@ -233,7 +280,7 @@ others. To generate wxWindows.dsp run<P>
Then just include this project in any workspace or open it from VC IDE Then just include this project in any workspace or open it from VC IDE
and it will create a new workspace for you.<P> and it will create a new workspace for you.<P>
If all goes well, I'm planning to create a template file for Makefile.ams If all goes well, I&#39;m planning to create a template file for Makefile.ams
under src/gtk and src/motif and also replace all makefiles in the samples under src/gtk and src/motif and also replace all makefiles in the samples
subdirectories with the project files from which all the others will be subdirectories with the project files from which all the others will be
generated. At least it will divide the number of files in samples generated. At least it will divide the number of files in samples
@@ -242,21 +289,21 @@ directory by 10 (and the number of files to be maintained too).
<P> <P>
<H3>How do you use VC++'s memory leak checking instead of that in wxWindows?</H3> <H3><a name="vcdebug">How do you use VC++&#39;s memory leak checking instead of that in wxWindows?</a></H3>
Vadim Zeitlin: Vadim Zeitlin:
<pre> <pre>
On the VC++ level, it's just the matter of calling _CrtSetDbgFlag() in the very On the VC++ level, it&#39;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 wxWindows, this is done automatically when
compiling with VC++ in debug mode unless wxUSE_GLOBAL_MEMORY_OPERATORS or 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 __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 is included from app.cpp which then calls wxCrtSetDbgFlag() without any
#ifdefs. ifdefs.
This works quite well: at the end of the program, all leaked blocks with their This works quite well: at the end of the program, all leaked blocks with their
malloc count are shown. This number (malloc count) can be used to determine malloc count are shown. This number (malloc count) can be used to determine
where exactly the object was allocated: for this it's enough to set the variable where exactly the object was allocated: for this it&#39;s enough to set the variable
_crtBreakAlloc (look in VC98\crt\srs\dbgheap.c line 326) to this number and _crtBreakAlloc (look in VC98\crt\srs\dbgheap.c line 326) to this number and
a breakpoint will be triggered when the block with this number is allocated. a breakpoint will be triggered when the block with this number is allocated.
@@ -267,6 +314,14 @@ Regards,
VZ VZ
</pre> </pre>
<P>
<H3><a name="shortcutproblem">Why are menu hotkeys or shortcuts not working in my application?</a></H3>
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&#39;used by the event handler.
</font> </font>

94
docs/html/platform.htm
View File

@@ -1,3 +1,4 @@
<html> <html>
<head> <head>
<title>Platforms supported by wxWindows 2.x</title> <title>Platforms supported by wxWindows 2.x</title>
@@ -21,7 +22,7 @@ Supported Platforms
</p> </p>
You will find below the list of all supported platforms for different ports of wxWindows 2.x (wxMSW/wxGTK/wxMotif ports You will find below the list of all supported platforms for different ports of wxWindows 2.x (wxMSW/wxGTK/wxMotif ports
only). The cross icon in the third column doesn't mean that the platform is not supported, but just that wxWindows hasn't only). The cross icon in the third column doesn&#39;t mean that the platform is not supported, but just that wxWindows hasn&#39;t
been tested on it recently (the table is being updated for wxWindows 2.1.14 been tested on it recently (the table is being updated for wxWindows 2.1.14
beta currently). beta currently).
<p> <p>
@@ -31,7 +32,7 @@ If you have tested wxWindows on a platform not mentioned here, please tell us ab
We would especially like to have information about compiling wxGTK on other Unix variants, such as IRIX, DG-UX, We would especially like to have information about compiling wxGTK on other Unix variants, such as IRIX, DG-UX,
other flavours of BSD, ... Please note that you will generally need GNU make other flavours of BSD, ... Please note that you will generally need GNU make
(also known as <tt>gmake</tt>) to compile wxWindows, native make programs (also known as <tt>gmake</tt>) to compile wxWindows, native make programs
often don't work. often don&#39;t work.
<p> <p>
<table width=100% border=4 cellpadding=5 cellspacing=0> <table width=100% border=4 cellpadding=5 cellspacing=0>
@@ -49,87 +50,100 @@ often don't work.
</tr> </tr>
<tr> <tr>
<td bgcolor="#FFFFFF" align=center valign=center rowspan=7>Win32 (Windows 9x/NT)</td> <td bgcolor="#FFFFFF" align=center valign=center rowspan=7>Win32<br>(Win 9x/NT/2K)</td>
<td>Visual C++ 4.2/5.x/6.0</td><td align=center><IMG SRC="icons/yes.gif" ALT=Ok></td><td>VZ, JS</td><td>Project files are provided for all versions except 4.2</td> <td>Visual C++ 4.2/5.x/6.0</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>VZ, JS</td><td>Project files are provided for all versions except 4.2</td>
<tr> <td>Borland C++ 5.0</td><td align=center><IMG SRC="icons/yes.gif" ALT=Ok></td><td><br></td><td>Also works with free command line Borland C++ 5.5</td> <tr> <td>Borland C++ 5.0</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td><br></td><td>Also works with free command line Borland C++ 5.5</td>
<tr> <td>Mingw32</td><td align=center><IMG SRC="icons/yes.gif" ALT=Ok></td><td>GRG, VZ</td><td>Cross compilation from Linux works as well<br> <tr> <td>Mingw32</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>GRG, VZ</td><td>Cross compilation from Linux works as well<br>
Version 2.95.2 recommended, otherwise some (included) patches must be applied<br> Version 2.95.2 recommended, otherwise some (included) patches must be applied<br>
Memory debugging code doesn't seem to work well</td> Memory debugging code doesn&#39;t seem to work well</td>
<tr> <td>Cygwin</td><td align=center><IMG SRC="icons/yes.gif" ALT=Ok></td><td>Stephane Junique<br>Andrea Venturoli</td><td>tested under NT 4, cross-compiling for mingw also works</td> <tr> <td>Cygwin</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>Stephane Junique<br>Andrea Venturoli</td><td>tested under NT 4, cross-compiling for mingw also works</td>
<tr> <td>Watcom C++ 10</td><td align=center><IMG SRC="icons/somewhat.gif" ALT=Almost></td><td>JS</td><td>Tested with 10.6: works, but wxImage seems to be broken<br>no support for JPEG, TIFF or OpenGL</td> <tr> <td>Watcom C++ 10</td><td align=center><IMG SRC="images/somewhat.gif" ALT=Almost></td><td>JS</td><td>Tested with 10.6: works, but wxImage seems to be broken<br>no support for JPEG, TIFF or OpenGL</td>
<tr> <td>Watcom C++ 11</td><td align=center><IMG SRC="icons/yes.gif" ALT=Ok></td><td>Markus Neifer</td><td>Tested with 11.0b under win95</td> <tr> <td>Watcom C++ 11</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>Markus Neifer</td><td>Tested with 11.0b under win95</td>
<tr> <td>Symantec C++</td><td align=center><IMG SRC="icons/no.gif" ALT=Unknown></td><td><br></td><td><br></td> <tr> <td>Symantec C++</td><td align=center><IMG SRC="images/no.gif" ALT=Unknown></td><td><br></td><td><br></td>
</tr> </tr>
<tr> <tr>
<td bgcolor="#F0F0F0" align=center valign=center rowspan=2>Win16 (Windows 3.1)</td> <td bgcolor="#F0F0F0" align=center valign=center rowspan=2>Win16<br>(Windows 3.1)</td>
<td>Visual C++ 1.52</td><td align=center><IMG SRC="icons/somewhat.gif" ALT=Ok></td><td><br></td> <td>Visual C++ 1.52</td><td align=center><IMG SRC="images/somewhat.gif" ALT=Ok></td><td><br></td>
<td rowspan=2 valign=center>Some features are missing (OLE related classes, threads, ...)<br> <td rowspan=2 valign=center>Some features are missing (OLE related classes, threads, ...)<br>
Borland C++ can't cope with ODBC, resources and new wxGrid class</td> Borland C++ can&#39;t cope with ODBC, resources and new wxGrid class</td>
<tr> <td>Borland C++ 4.0/5.0</td><td align=center><IMG SRC="icons/somewhat.gif" ALT=Ok></td><td>JS</td> <tr> <td>Borland C++ 4.0/5.0</td><td align=center><IMG SRC="images/somewhat.gif" ALT=Ok></td><td>JS</td>
</tr> </tr>
<tr> <tr>
<td bgcolor="#FFFFFF" align=center valign=center rowspan=4>Linux</td> <td bgcolor="#FFFFFF" align=center valign=center rowspan=5>Linux x86</td>
<td>wxGTK with gcc 2.7.2</td><td align=center><IMG SRC="icons/no.gif" ALT=Unknown></td><td><br></td><td>Should work, but nobody uses it any more</td> <td>wxGTK with gcc 2.7.2</td><td align=center><IMG SRC="images/no.gif" ALT=Unknown></td><td><br></td><td>Should work, but nobody uses it any more</td>
<tr> <td>wxGTK with egcs 1.1.1</td><td align=center><IMG SRC="icons/yes.gif" ALT=Ok></td><td>VZ, RR</td><td><br></td> <tr> <td>wxGTK with egcs 1.1.1</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>VZ, RR</td><td><br></td>
<tr> <td>wxGTK with gcc 2.95</td><td align=center><IMG SRC="icons/yes.gif" ALT=Ok></td><td><br></td><td><br></td> <tr> <td>wxGTK with gcc 2.95</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td><br></td><td><br></td>
<tr> <td>wxMotif with egcs 1.1.1</td><td align=center><IMG SRC="icons/yes.gif" ALT=Ok></td><td><br></td><td>with <a href=http://www.lesstif.org>LessTif</a> 0.87</td> <tr> <td>wxMotif with egcs 1.1.1</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td><br></td><td>with <a href="http://www.lesstif.org">LessTif</a> 0.87</td>
<tr> <td>wxMotif with gcc 2.95</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td><br></td><td>with <a href="http://www.openmotif.org">OpenMotif</a></td>
</tr> </tr>
<tr> <tr>
<td bgcolor="#F0F0F0" align=center valign=center rowspan=1>FreeBSD</td> <td bgcolor="#F0F0F0" align=center valign=center rowspan=1>FreeBSD</td>
<td>wxGTK with gcc</td><td align=center><IMG SRC="icons/yes.gif" ALT=Ok></td><td>VZ</td><td>Limited thread support on older systems</td> <td>wxGTK with gcc</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>VZ</td><td>Limited thread support on older systems</td>
</tr> </tr>
<tr> <tr>
<td bgcolor="#FFFFFF" align=center valign=center rowspan=4>Solaris</td> <td bgcolor="#FFFFFF" align=center valign=center rowspan=5>Solaris</td>
<td>wxMotif with Sun CC 4.2</td><td align=center><IMG SRC="icons/yes.gif" ALT=Ok></td><td>VZ</td><td>Thread support must be disabled on system with not MT-safe X11</td> <td>wxMotif with Sun CC 4.2</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>VZ</td><td>Thread support must be disabled on system with not MT-safe X11</td>
<tr> <td>wxMotif with gcc</td><td align=center><IMG SRC="icons/yes.gif" ALT=Ok></td><td><br></td><td><br></td> <tr> <td>wxMotif with gcc</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td><br></td><td><br></td>
<tr> <td>wxGTK with Sun CC 4.2</td><td align=center><IMG SRC="icons/yes.gif" ALT=Ok></td><td>Shiv Shankar Ramakrishnan</td><td><br></td> <tr> <td>wxGTK with Sun CC 4.2</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>Shiv Shankar Ramakrishnan</td><td><br></td>
<tr> <td>wxGTK with gcc</td><td align=center><IMG SRC="icons/yes.gif" ALT=Ok></td><td><br></td><td><br></td> <tr> <td>wxGTK with gcc</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td><br></td><td><br></td>
<tr> <td>wxGTK with Sun CC 5.0 and 6.1 (Solaris 7 and 8)</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>Jiri Mracek</td><td>You have to edit line 2079 in glib.h to fix GTK+ error</td>
</tr> </tr>
<tr> <tr>
<td bgcolor="#F0F0F0" align=center valign=center rowspan=2>AIX</td> <td bgcolor="#F0F0F0" align=center valign=center rowspan=2>AIX</td>
<td>wxGTK with AIX CC</td><td align=center><IMG SRC="icons/no.gif" ALT=Unknown></td><td><br></td><td><br></td> <td>wxGTK with AIX CC</td><td align=center><IMG SRC="images/no.gif" ALT=Unknown></td><td><br></td><td><br></td>
<tr> <td>wxMotif with xlC (AIX 4.2)</td><td align=center><IMG SRC="icons/yes.gif" ALT=Ok></td> <tr> <td>wxMotif with xlC 3.1.4.0 (AIX 4.2)</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td>
<td>Bernhard Eck</td> <td>Bernhard Eck</td>
<td>Some problems with OpenGL and native X server</td> <td>Some problems with OpenGL and native X server</td>
</tr> </tr>
<tr> <tr>
<td bgcolor="#FFFFFF" align=center valign=center rowspan=2>HP-UX</td> <td bgcolor="#FFFFFF" align=center valign=center rowspan=2>HP-UX 10.20</td>
<td>wxGTK with HP CC A.10.22<br>or HP aCC B3910B A.01.18 <td>wxGTK with HP CC A.10.22<br>or HP aCC B3910B A.01.18
</td><td align=center><IMG SRC="icons/yes.gif" ALT=Ok></td><td>Staf Verhaegen</td> </td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>Staf Verhaegen</td>
<td>you need to add <tt>-Aa -D_HPUX_SOURCE</tt> to <tt>CFLAGS</tt></td> <td>you need to add <tt>-Aa -D_HPUX_SOURCE</tt> to <tt>CFLAGS</tt></td>
<tr> <td>wxGTK with gcc</td><td align=center><IMG SRC="icons/no.gif" ALT=Unknown></td><td><br></td><td><br></td> <tr> <td>wxGTK with gcc</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>Julian Albo Garcia</td><td><br></td>
</tr> </tr>
<tr> <tr>
<td bgcolor="#F0F0F0" align=center valign=center rowspan=2>IRIX</td> <td bgcolor="#F0F0F0" align=center valign=center rowspan=3>IRIX</td>
<td>wxGTK</td><td align=center><IMG SRC="icons/yes.gif" ALT=Ok></td><td><br></td><td>You may need to use <tt>--disable-catch_segvs</tt> if you get compiler<br>error in utilsunx.cpp</td> <td>wxGTK</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td><br></td><td>You may need to use <tt>--disable-catch_segvs</tt> if you get compiler error in utilsunx.cpp</td>
<tr> <td>wxMotif with MIPSPro 7.30</td><td align=center><IMG SRC="icons/yes.gif" ALT=Ok></td><td>David Marshall</td><td>On IRIX 6.5.6 (Indigo2, 64bit), with SGI Motif 1.2</td> <tr> <td>wxMotif with MIPSPro 7.30</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>David Marshall</td><td>On IRIX 6.5.6 (Indigo2, 64bit), with SGI Motif 1.2</td>
<tr> <td>wxMotif with "CC -mips3 -n32"</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>Ian</td><td>You need to set LD_LIBRARYN32_PATH</td>
</tr> </tr>
<tr> <tr>
<td bgcolor="#FFFFFF" align=center valign=center rowspan=1>SCO UnixWare</td> <td bgcolor="#FFFFFF" align=center valign=center rowspan=1>SCO UnixWare</td>
<td>wxGTK with gcc</td><td align=center><IMG SRC="icons/yes.gif" ALT=Ok></td><td>William Suetholz</td><td>UnixWare 2.1.3 with UnixWare 7 compatibility PTF</td> <td>wxGTK with gcc</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>William Suetholz</td><td>UnixWare 2.1.3 with UnixWare 7 compatibility PTF</td>
</tr> </tr>
<tr> <tr>
<td bgcolor="#F0F0F0" align=center valign=center rowspan=1>DEC OSF/1</td> <td bgcolor="#F0F0F0" align=center valign=center rowspan=1>DEC OSF/1</td>
<td>wxGTK with gcc</td><td align=center><IMG SRC="icons/yes.gif" ALT=Ok></td><td>Fabrice Didierjean</td><td>OSF1 4.0 on Dec Alpha<br> <td>wxGTK with gcc</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>Fabrice Didierjean</td><td>OSF1 4.0 on Dec Alpha<br>
you may need to run configure with <tt>--host=alpha-dec-osf switch</tt></td> you may need to run configure with <tt>--host=alpha-dec-osf switch</tt></td>
</tr> </tr>
<tr> <tr>
<td bgcolor="#FFFFFF" align=center valign=center rowspan=4>OS/2</td> <td bgcolor="#FFFFFF" align=center valign=center rowspan=4>OS/2</td>
<td>VisualAge 3.0/4.0</td><td align=center><IMG SRC="icons/no.gif" ALT="Not yet"></td><td>DW</td> <td>VisualAge 3.0/4.0</td><td align=center><IMG SRC="images/no.gif" ALT="Not yet"></td><td>DW</td>
<td rowspan=2 valign=center>OS/2 port is work in progress...</td> <td rowspan=2 valign=center>OS/2 port is work in progress...</td>
<tr> <td>EMX</td><td align=center><IMG SRC="icons/no.gif" ALT="Not yet"></td><td>SN</td> <tr> <td>EMX</td><td align=center><IMG SRC="images/no.gif" ALT="Not yet"></td><td>SN</td>
<tr> <td>wxGTK with EMX</td><td align=center><IMG SRC="icons/yes.gif" ALT=Ok></td><td>SN</td><td>configure scripts need to be regenerated with OS/2 port of autoconf</td> <tr> <td>wxGTK with EMX</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>SN</td><td>configure scripts need to be regenerated with OS/2 port of autoconf</td>
<tr> <td>wxMotif with EMX</td><td align=center><IMG SRC="icons/yes.gif" ALT=Ok></td><td>SN</td><td>with <a href=http://www.lesstif.org>LessTif</a> 0.89; configure scripts need to be regenerated with OS/2 port of autoconf</td> <tr> <td>wxMotif with EMX</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>SN</td><td>with <a href="http://www.lesstif.org">LessTif</a> 0.89; configure scripts need to be regenerated with OS/2 port of autoconf</td>
</tr>
<tr>
<td bgcolor="#F0F0F0" align=center valign=center rowspan=1>OpenVMS</td>
<td>wxGTK with Compaq-C++ V6.2 (OpenVMS Alpha 7.3)</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>Jouk Jansen</td><td><br></td>
</tr>
<tr>
<td bgcolor="#FFFFFF" align=center valign=center rowspan=1>Linux S/390</td>
<td>wxGTK with gcc 2.95.2</td><td align=center><IMG SRC="images/yes.gif" ALT=Ok></td><td>VZ</td><td>2.3.1+ only</td>
</tr> </tr>
</table> </table>

10
docs/latex/wx/tglbtn.tex
View File

@@ -11,14 +11,14 @@
\section{\class{wxToggleButton}}\label{wxtogglebutton} \section{\class{wxToggleButton}}\label{wxtogglebutton}
wxToggleButton is a button which stays pressed when clicked by the user. In wxToggleButton is a button that stays pressed when clicked by the user. In
other words, it is more similar to \helpref{wxCheckBox}{wxcheckbox} in other words, it is similar to \helpref{wxCheckBox}{wxcheckbox} in
functionality but looks like a \helpref{wxButton}{wxbutton}. functionality but looks like a \helpref{wxButton}{wxbutton}.
You can see wxToggleButton in action in the sixth page of the You can see wxToggleButton in action in the sixth page of the
\helpref{controls}{samplecontrols} sample. \helpref{controls}{samplecontrols} sample.
{\bf NB: } This class is only available under wxMSW and wxGTK currently. {\bf NB:} This class is only available under wxMSW and wxGTK currently.
\wxheading{Derived from} \wxheading{Derived from}
@@ -115,8 +115,8 @@ Returns {\tt TRUE} if it is pressed, {\tt FALSE} otherwise.
\func{void}{SetValue}{\param{const bool}{ state}} \func{void}{SetValue}{\param{const bool}{ state}}
Sets the toggle button to the given state. This does not cause a Sets the toggle button to the given state. This does not cause a
{\tt EVT\_TOGGLEBUTTON} event to get emitted. {\tt EVT\_TOGGLEBUTTON} event to be emitted.
\wxheading{Parameters} \wxheading{Parameters}