From 8b283bb88e49a83785c7fbe94fdb0203052022ce Mon Sep 17 00:00:00 2001 From: Julian Smart Date: Tue, 20 Nov 2001 14:55:10 +0000 Subject: [PATCH] Misc fixes git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@12516 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775 --- distrib/msw/generic.rsp | 13 +++ distrib/msw/makefile.rsp | 2 + distrib/msw/vc.rsp | 3 + distrib/msw/zipdistinno.bat | 8 ++ docs/html/faq.htm | 1 + docs/html/faqgen.htm | 149 ++++++++++++++++--------------- docs/html/faqgtk.htm | 21 ++++- docs/html/faqmac.htm | 10 +-- docs/html/faqmsw.htm | 171 ++++++++++++++++++++++++------------ docs/html/platform.htm | 94 +++++++++++--------- docs/latex/wx/tglbtn.tex | 10 +-- 11 files changed, 300 insertions(+), 182 deletions(-) diff --git a/distrib/msw/generic.rsp b/distrib/msw/generic.rsp index c6a50e457a..35e63017a1 100644 --- a/distrib/msw/generic.rsp +++ b/distrib/msw/generic.rsp @@ -113,6 +113,19 @@ src/zlib/makefile* src/zlib/*.com 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/*.inl include/wx/*.cpp diff --git a/distrib/msw/makefile.rsp b/distrib/msw/makefile.rsp index 454b31aee1..bd1c46f628 100644 --- a/distrib/msw/makefile.rsp +++ b/distrib/msw/makefile.rsp @@ -1,4 +1,5 @@ Makefile.in +src/regex/Makefile.in locale/Makefile samples/Makefile.in samples/calendar/Makefile.in @@ -157,4 +158,5 @@ src/motif/descrip.mms src/png/scripts/descrip.mms src/unix/descrip.mms src/zlib/descrip.mms +src/regex/descrip.mms utils/dialoged/src/descrip.mms diff --git a/distrib/msw/vc.rsp b/distrib/msw/vc.rsp index 52e693f751..ab8dadc35e 100644 --- a/distrib/msw/vc.rsp +++ b/distrib/msw/vc.rsp @@ -22,6 +22,9 @@ src/zlib/zlib.dsw src/png/png.dsp src/png/png.dsw +src/regex/regex.dsp +src/regex/regex.dsw + samples/samples.dsw samples/calendar/Calendar.dsp diff --git a/distrib/msw/zipdistinno.bat b/distrib/msw/zipdistinno.bat index fee10dbb01..d5f4db1b88 100755 --- a/distrib/msw/zipdistinno.bat +++ b/distrib/msw/zipdistinno.bat @@ -3,6 +3,7 @@ rem Zip up an external, generic + Windows distribution of wxWindows 2 rem using Inno Setup + ScriptMaker set src=%wxwin set dest=%src\deliver +set webfiles=c:\wx2dev\wxWebSite set inno=0 Rem Set this to the required version @@ -43,6 +44,13 @@ erase %dest\make* if direxist %dest\wx erase /sxyz %dest\wx\ 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 echo Zipping... diff --git a/docs/html/faq.htm b/docs/html/faq.htm index 582397d58d..8dca0fa260 100644 --- a/docs/html/faq.htm +++ b/docs/html/faq.htm @@ -1,3 +1,4 @@ + diff --git a/docs/html/faqgen.htm b/docs/html/faqgen.htm index 4bcbaf21df..0c14ce0fe1 100644 --- a/docs/html/faqgen.htm +++ b/docs/html/faqgen.htm @@ -1,3 +1,4 @@ + @@ -22,22 +23,38 @@ wxWindows 2 FAQ: General See also top-level FAQ page.
+

List of questions in this category

+ +

What is wxWindows?

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, -so your program will take on the native 'look and feel' that users are familiar with.

+so your program will take on the native 'look and feel' that users are familiar with.

Although GUI applications are mostly built programmatically, there is a dialog editor to help -build attractive dialogs and panels. Robert Roebling's wxDesigner +build attractive dialogs and panels. Robert Roebling's wxDesigner makes light work of resizable, portable dialogs.

-You don't have to use C++ to use wxWindows: wxWindows 1 has been interfaced to several interpreted languages, -such as CLIPS, Python, Scheme, XLisp and Perl, and there is a Python interface for wxWindows 2. +You don't have to use C++ to use wxWindows: there is a Python interface for wxWindows 2, +and also a Perl interface.

-

Can I use wxWindows 2 for both proprietary (commercial) projects, and GPL'ed projects?

+

Can I use wxWindows 2 for both proprietary (commercial) projects, and GPL'ed projects?

Yes. Please see the licence for details, but basically 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.

Who uses wxWindows?

Many organisations - commercial, government, and academic - across the -world. It's impossible to estimate the true number of users, since +world. It's impossible to estimate the true number of users, since wxWindows is obtained by many different means, and we cannot monitor distribution. The mailing list contains around 300-400 entries which is quite large for a list of this type.

@@ -65,62 +82,28 @@ quite large for a list of this type.

See Users for a list of some users and their applications, and also Feedback for comments.

-

How much has the API changed since 1.xx?

- -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.

- -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).

- -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.

- -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.

- -

What classes have disappeared?

- -wxForm, wxTextWindow (subsumed into wxTextCtrl). - -

Does wxWindows 2 mean that wxWindows 1.xx is dead?

- -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.

- -

What platforms are supported by wxWindows 2?

+

What platforms are supported by wxWindows 2?

-

How does wxWindows 2 support platform-specific features?

+

How does wxWindows 2 support platform-specific +features?

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 few classes (functions, window styles) that are platform-specific. For example, Windows metafiles and Windows 95 taskbar icons have 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't take much coding effort for an application programmer to add support for some functionality that the user on a particular platform might otherwise 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.

-In other words, wxWindows is not a 'lowest common denominator' approach, +In other words, wxWindows is not a 'lowest common denominator' approach, but it will still be possible to write portable programs using the core API. Forbidding some platform-specific classes would be a stupid approach that would alienate many potential users, and encourage the perception that toolkits such as wxWindows are not up to the demands -of today's sophisticated applications.

+of today's sophisticated applications.

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.

-Another reason why wxWindows 2 is not a 'lowest common denominator' toolkit is that +Another reason why wxWindows 2 is not a 'lowest common denominator' toolkit is that some functionality missing on some platform has been provided using generic, platform-independent code, such as the wxTreeCtrl and wxListCtrl classes.

-

Does wxWindows use STL? or the standard string class?

+

Does wxWindows use STL? or the standard string class?

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' best interests to avoid use of templates. Not all compilers can handle templates adequately so it would dramatically reduce the number of compilers 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. @@ -158,9 +141,20 @@ by being able to modify our own string class. Some compatibility with the string has been built into wxString.

There is nothing to stop an application using templates or the string class for its own -purposes.

+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:

+ +

+#ifdef new
+#undef new
+#endif
+
+ +

+ -

Is there a rich edit/markup widget for wxWindows 2?

+

Is there a rich edit/markup widget for wxWindows 2?

These are the possibilities so far:

@@ -173,12 +167,12 @@ for this widget. then wxHTML will suit your needs. wxHTML is built into wxWindows - please see the reference manual for details, and samples/html.

  • 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).

    -

    How is wxWindows 2 being developed?

    +

    How is wxWindows 2 being developed?

    We are using the CVS system to develop and maintain wxWindows. This allows us to make alterations and upload them instantly to the SourceForge server, from @@ -187,20 +181,24 @@ which others can update their source.

    To build source from CVS, see the file BuildCVS.txt in the top-level wxWindows distribution directory.

    -

    How is wxWindows 2 distributed?

    +

    How is wxWindows 2 distributed?

    -By ftp, and via the wxWindows CD-ROM.

    +By ftp, and via the wxWindows CD-ROM. +

    +If you are feeling adventurous, you may also check out the sources directly +from the cvs +

    -

    What are the plans for the future?

    +

    What are the plans for the future?

    -Currently we're working too hard on getting wxWindows 2 finished (are GUI toolkits ever +Currently we'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 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.

    Other possibilities include: DCOM/CORBA compatibility; a wxWindows book; -wxStudio, an IDE; -other platforms; other interface abilities such as speech output.

    +wxWorkshop, an IDE; +other platforms, especially embedded systems; other interface abilities such as speech output.

    We will investigate the possibility of compiler or operating system vendors bundling wxWindows with their product.

    @@ -208,17 +206,28 @@ their product.

    The high-level goal of wxWindows is to be thought of as the number one C++ framework, for virtually any platform. Move over, MFC!

    -

    What about Java?

    +

    What is wxUniversal?

    + +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. +

    +You may find more about wxUniversal here. + +

    What about Java?

    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't anticipate a major threat from Java, and the level of interest in wxWindows is as high as ever.

    -

    How can I help the project?

    +

    How can I help the project?

    -Please check out the Backroom pages, -in particular the suggested projects, and -mail Julian Smart or the developers' mailing list with your own suggestions.

    +Please check out the Community pages, +in particular the suggested projects, and +mail Julian Smart or the developers' mailing list with your own suggestions.

    diff --git a/docs/html/faqgtk.htm b/docs/html/faqgtk.htm index ba070ce196..bd6386cbe2 100644 --- a/docs/html/faqgtk.htm +++ b/docs/html/faqgtk.htm @@ -22,23 +22,36 @@ wxWindows 2 for GTK FAQ See also top-level FAQ page.

    - -

    What is wxWindows 2 for GTK?

    +

    List of questions in this category

    +
  • What is wxWindows 2 for GTK?
    • +
  • Does wxGTK have GNOME support?
    • +
  • Warning about GTK libraries supplied with RedHat
    • +
  • What is wxWindows 2 for GTK?
    • +
    wxWindows 2 for GTK is a port of wxWindows to the GTK+ toolkit, 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 here.

    -

    Does wxGTK have GNOME support?

    +

    Does wxGTK have GNOME support?

    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'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 so may be added without dependence on libraries. Other features may be supported in the future, probably as a separate library.

    +

    Warning about GTK libraries supplied with RedHat

    + +It seems that some versions of RedHat include a badly patched version of GTK (not wxGTK) +which causes some trouble with wxWindows' 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. +

    + diff --git a/docs/html/faqmac.htm b/docs/html/faqmac.htm index 2fb703eaa8..1357289d66 100644 --- a/docs/html/faqmac.htm +++ b/docs/html/faqmac.htm @@ -32,15 +32,15 @@ See also top-level FAQ page.

  • How does CVS handle file types/creators under Mac OS 8.x /9.x?
  • How does CVS handle file types/creators under Mac OS X?
  • What steps are required to build wxMac using CodeWarrior P ro 5.3?
    • -
  • What steps are required to build wxMac under Mac OS X?< /li> +
  • What steps are required to build wxMac under Mac OS X?
  • What important settings are required in the CodeWarrior P roject Preferences?
  • What are the smart preprocessing errors with the Apple Developer Tools?
    • -
  • How does wxMac support the standard Apple About menu ite m and Help menu?
    • +
  • How does wxMac support the standard Apple About menu item and Help menu?

    • When is wxMac 2.x due to be released?

    -There is a preview available. +There is a preview available. The author of this port is Stefan Csomor.

    @@ -50,9 +50,9 @@ The author of this port is Stefan Cs 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 development snapshot or the sources from the CVS trunk. +Until a new release is made, it is recommended that you download the wxMac 2.3.1 development snapshot or the sources from the CVS trunk. - + diff --git a/docs/html/faqmsw.htm b/docs/html/faqmsw.htm index be0f8d9091..58dca23c94 100644 --- a/docs/html/faqmsw.htm +++ b/docs/html/faqmsw.htm @@ -22,8 +22,26 @@ wxWindows 2 for Windows FAQ See also top-level FAQ page.

    +

    List of questions in this category

    + +
    -

    Which Windows platforms are supported?

    +

    Which Windows platforms are supported?

    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).

    @@ -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, we have not forgotten users of 16-bit Windows. Most features 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 -class doesn't work either because the Windows 3.1 registry is very simplistic. Check out the 16-bit +However, don'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 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. @@ -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, without ever needing a copy of Microsoft Windows. See the Technical Note on the Web site detailing cross-compilation.

    -

    What about Windows CE?

    +

    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 +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 +the statically-linked 'minimal' sample), shoehorning wxWindows 2 into a Windows CE device's limited storage should not be a problem.

    -

    What compilers are supported?

    +

    What compilers are supported?

    Please see the wxWindows 2 for Windows install.txt file for up-to-date information, but currently the following are known to work:

    @@ -77,43 +95,42 @@ 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?

    +

    Which is the best compiler to use with wxWindows 2?

    -It'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. -Since project files are plain text, it's easy for me to generate appropriate project files +It'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. +Since project files are plain text, it's easy for me to generate appropriate project files for wxWindows samples.

    -Borland C++ is fine - and very fast - but it'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.

    +Borland C++ is fine - and very fast - but it'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.

    -C++Builder's power isn'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 -it's almost identical to BC++ 5.0 (the same makefiles can be used).

    +C++Builder's power isn'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 +it's almost identical to BC++ 5.0 (the same makefiles can be used).

    -You can't beat Cygwin's price (free), and you can debug adequately using gdb. However, it's +You can't beat Cygwin's price (free), and you can debug adequately using gdb. However, it's quite slow to compile since it does not use precompiled headers.

    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.

    -Watcom C++ is a little slow and the debugger is not really up to today's standards.

    +Watcom C++ is a little slow and the debugger is not really up to today's standards.

    -

    Is Unicode supported?

    +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.

    +

    Is Unicode supported?

    -However, the issues surrounding Unicode support have been looked into so we know -what we need to do, and have some header files ready to use containing appropriate -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.

    +Yes, Unicode is fully supported under Windows NT/2000 (Windows 9x don't +have Unicode support anyhow). -

    Can you compile wxWindows 2 as a DLL?

    +

    Can you compile wxWindows 2 as a DLL?

    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 -delivering a suite of separate programs, or you're compiling a lot of wxWindows applications +and you may be better off compiling statically-linked applications, unless you're +delivering a suite of separate programs, or you're compiling a lot of wxWindows applications and have limited hard disk space.

    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!

    -

    How can I reduce executable size?

    +

    How can I reduce executable size?

    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 @@ -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 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 300KB using VC++ 6.

    If you want to distribute really small executables, you can use Petite @@ -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 use DLLs.

    -

    Is wxWindows compatible with MFC?

    +

    Is wxWindows compatible with MFC?

    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't expect to be able to enable wxWindows windows with OLE-2 functionality using MFC.

    -

    Why do I sometimes get bizarre crash problems using VC++ 5/6?

    +

    Why my code fails to compile with strange errors about new operator?

    + +The most common cause of this problem is the memory debugging settings in +wx/msw/setup.h. You have several choices: + + + +Notice that IMHO the first solution is preferable for VC++ users who can use +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 -- +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 +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'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. + +

    Why do I sometimes get bizarre crash problems using VC++ 5/6?

    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't limited to wxWindows). If strange/weird/impossible things start to happen please check (dumping IDE project file as makefile and doing text comparison if necessary) that the project settings, especially the list of defined symbols, struct packing, etc. are exactly the same for all items in the project. After this, delete everything (including PCH) and recompile.

    -VC++ 5's optimization code seems to be broken and can +VC++ 5's optimization code seems to be broken and can cause problems: this can be seen when deleting an object Dialog Editor, in Release mode with optimizations on. If in doubt, switch off optimisations, although this will result in much larger executables. It seems possible that the library can be created with strong optimization, so long as the application is not strongly -optimized. For example, in wxWindows project, set to 'Minimum -Size'. In Dialog Editor project, set to 'Customize: Favor Small -Code' (and no others). This will then work.

    +optimized. For example, in wxWindows project, set to 'Minimum +Size'. In Dialog Editor project, set to 'Customize: Favor Small +Code' (and no others). This will then work.

    -

    How are the wxWindows makefiles edited under Windows?

    +

    How are the wxWindows makefiles edited under Windows?

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

    -Here are Vadim's notes:

    +Here are Vadim's notes:

    -To use these new makefiles, you don't need anything (but see below). +To use these new makefiles, you don't need anything (but see below). However, you should NOT modify them because these files will be 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'll need to modify the corresponding template (b32.t in this +you'll need to modify the corresponding template (b32.t in this 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 -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 +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 do you any good). Using it extremely simple: to regenerate makefile.b32 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 -Symantec and I don't have enough diskspace to recompile even with +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 (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 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 ol 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.

    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. -Some other are only compiled with some compilers (others can't compile +Some other are only compiled with some compilers (others can't compile them) - all this info is contained in this file.

    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.

    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 -I don't need it and can't test it, but it should be trivial to create +generates a project file for VC++ 6.0 (I didn't create vc5.t because +I don't need it and can't test it, but it should be trivial to create 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't support edit-and=continue). This is not an officially supported way 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 @@ -233,7 +280,7 @@ others. To generate wxWindows.dsp run

    Then just include this project in any workspace or open it from VC IDE and it will create a new workspace for you.

    -If all goes well, I'm planning to create a template file for Makefile.ams +If all goes well, I'm planning to create a template file for Makefile.ams 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 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).

    -

    How do you use VC++'s memory leak checking instead of that in wxWindows?

    +

    How do you use VC++'s memory leak checking instead of that in wxWindows?

    Vadim Zeitlin: 
    -On the VC++ level, it's just the matter of calling _CrtSetDbgFlag() in the very
+On the VC++ level, it's just the matter of calling _CrtSetDbgFlag() in the very
 beginning of the program. In wxWindows, this is done automatically when
 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
 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
 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's enough to set the variable
 _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.
 
@@ -267,6 +314,14 @@ Regards,
 VZ
    +

    + +

    Why are menu hotkeys or shortcuts not working in my application?

    + +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. + diff --git a/docs/html/platform.htm b/docs/html/platform.htm index 72442a67b5..3fce58d0d9 100644 --- a/docs/html/platform.htm +++ b/docs/html/platform.htm @@ -1,3 +1,4 @@ + Platforms supported by wxWindows 2.x @@ -21,7 +22,7 @@ Supported Platforms

    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't mean that the platform is not supported, but just that wxWindows hasn't been tested on it recently (the table is being updated for wxWindows 2.1.14 beta currently).

    @@ -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, other flavours of BSD, ... Please note that you will generally need GNU make (also known as gmake) to compile wxWindows, native make programs -often don't work. +often don't work.

    @@ -49,87 +50,100 @@ often don't work. - - - - + + + - - - - + Memory debugging code doesn't seem to work well + + + + - - + + - + Borland C++ can't cope with ODBC, resources and new wxGrid class + - - - - - + + + + + + - + - - - - - + + + + + + - - + + - + + - + - - - + + + + - + - - + - - - + + + + + + + + + + + + +
    Win32 (Windows 9x/NT)Visual C++ 4.2/5.x/6.0OkVZ, JSProject files are provided for all versions except 4.2
    Borland C++ 5.0Ok
    		Also works with free command line Borland C++ 5.5
    Mingw32OkGRG, VZCross compilation from Linux works as well
    +    		Win32
    (Win 9x/NT/2K)    		Visual C++ 4.2/5.x/6.0OkVZ, JSProject files are provided for all versions except 4.2
    Borland C++ 5.0Ok
    		Also works with free command line Borland C++ 5.5
    Mingw32OkGRG, VZCross compilation from Linux works as well
    Version 2.95.2 recommended, otherwise some (included) patches must be applied
    - Memory debugging code doesn't seem to work well
    CygwinOkStephane Junique
    Andrea Venturoli    		tested under NT 4, cross-compiling for mingw also works
    Watcom C++ 10AlmostJSTested with 10.6: works, but wxImage seems to be broken
    no support for JPEG, TIFF or OpenGL
    Watcom C++ 11OkMarkus NeiferTested with 11.0b under win95
    Symantec C++Unknown

    CygwinOkStephane Junique
    Andrea Venturoli    		tested under NT 4, cross-compiling for mingw also works
    Watcom C++ 10AlmostJSTested with 10.6: works, but wxImage seems to be broken
    no support for JPEG, TIFF or OpenGL
    Watcom C++ 11OkMarkus NeiferTested with 11.0b under win95
    Symantec C++Unknown
    Win16 (Windows 3.1)Visual C++ 1.52Ok
    		Win16
    (Windows 3.1)    		Visual C++ 1.52Ok
    		 Some features are missing (OLE related classes, threads, ...)
    - Borland C++ can't cope with ODBC, resources and new wxGrid class
    Borland C++ 4.0/5.0OkJS
    Borland C++ 4.0/5.0OkJS
    LinuxwxGTK with gcc 2.7.2Unknown
    		Should work, but nobody uses it any more
    wxGTK with egcs 1.1.1OkVZ, RR
    wxGTK with gcc 2.95Ok

    wxMotif with egcs 1.1.1Ok
    		with LessTif 0.87Linux x86wxGTK with gcc 2.7.2Unknown
    		Should work, but nobody uses it any more
    wxGTK with egcs 1.1.1OkVZ, RR
    wxGTK with gcc 2.95Ok

    wxMotif with egcs 1.1.1Ok
    		with LessTif 0.87
    wxMotif with gcc 2.95Ok
    		with OpenMotif
    FreeBSDwxGTK with gccOkVZLimited thread support on older systemswxGTK with gccOkVZLimited thread support on older systems
    SolariswxMotif with Sun CC 4.2OkVZThread support must be disabled on system with not MT-safe X11
    wxMotif with gccOk

    wxGTK with Sun CC 4.2OkShiv Shankar Ramakrishnan
    wxGTK with gccOk

    		SolariswxMotif with Sun CC 4.2OkVZThread support must be disabled on system with not MT-safe X11
    wxMotif with gccOk

    wxGTK with Sun CC 4.2OkShiv Shankar Ramakrishnan
    wxGTK with gccOk

    wxGTK with Sun CC 5.0 and 6.1 (Solaris 7 and 8)OkJiri MracekYou have to edit line 2079 in glib.h to fix GTK+ error
    AIXwxGTK with AIX CCUnknown

    wxMotif with xlC (AIX 4.2)OkwxGTK with AIX CCUnknown

    wxMotif with xlC 3.1.4.0 (AIX 4.2)Ok Bernhard Eck Some problems with OpenGL and native X server
    HP-UXHP-UX 10.20 wxGTK with HP CC A.10.22
    or HP aCC B3910B A.01.18 -     		OkStaf VerhaegenOkStaf Verhaegen you need to add -Aa -D_HPUX_SOURCE to CFLAGS
    wxGTK with gccUnknown

    wxGTK with gccOkJulian Albo Garcia
    IRIXwxGTKOk
    		You may need to use --disable-catch_segvs if you get compiler
    error in utilsunx.cpp
    wxMotif with MIPSPro 7.30OkDavid MarshallOn IRIX 6.5.6 (Indigo2, 64bit), with SGI Motif 1.2IRIXwxGTKOk
    		You may need to use --disable-catch_segvs if you get compiler error in utilsunx.cpp
    wxMotif with MIPSPro 7.30OkDavid MarshallOn IRIX 6.5.6 (Indigo2, 64bit), with SGI Motif 1.2
    wxMotif with "CC -mips3 -n32"OkIanYou need to set LD_LIBRARYN32_PATH
    SCO UnixWarewxGTK with gccOkWilliam SuetholzUnixWare 2.1.3 with UnixWare 7 compatibility PTFwxGTK with gccOkWilliam SuetholzUnixWare 2.1.3 with UnixWare 7 compatibility PTF
    DEC OSF/1wxGTK with gccOkFabrice DidierjeanOSF1 4.0 on Dec Alpha
    +     		wxGTK with gccOkFabrice DidierjeanOSF1 4.0 on Dec Alpha
    you may need to run configure with --host=alpha-dec-osf switch
    OS/2VisualAge 3.0/4.0Not yetDWVisualAge 3.0/4.0Not yetDW OS/2 port is work in progress...
    EMXNot yetSN
    wxGTK with EMXOkSNconfigure scripts need to be regenerated with OS/2 port of autoconf
    wxMotif with EMXOkSNwith LessTif 0.89; configure scripts need to be regenerated with OS/2 port of autoconf
    EMXNot yetSN
    wxGTK with EMXOkSNconfigure scripts need to be regenerated with OS/2 port of autoconf
    wxMotif with EMXOkSNwith LessTif 0.89; configure scripts need to be regenerated with OS/2 port of autoconf
    OpenVMSwxGTK with Compaq-C++ V6.2 (OpenVMS Alpha 7.3)OkJouk Jansen
    Linux S/390wxGTK with gcc 2.95.2OkVZ2.3.1+ only
    diff --git a/docs/latex/wx/tglbtn.tex b/docs/latex/wx/tglbtn.tex index 78e059361b..75184f5541 100644 --- a/docs/latex/wx/tglbtn.tex +++ b/docs/latex/wx/tglbtn.tex @@ -11,14 +11,14 @@ \section{\class{wxToggleButton}}\label{wxtogglebutton} -wxToggleButton is a button which stays pressed when clicked by the user. In -other words, it is more similar to \helpref{wxCheckBox}{wxcheckbox} in +wxToggleButton is a button that stays pressed when clicked by the user. In +other words, it is similar to \helpref{wxCheckBox}{wxcheckbox} in functionality but looks like a \helpref{wxButton}{wxbutton}. You can see wxToggleButton in action in the sixth page of the \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} @@ -115,8 +115,8 @@ Returns {\tt TRUE} if it is pressed, {\tt FALSE} otherwise. \func{void}{SetValue}{\param{const bool}{ state}} -Sets the toggle button to the given state. This does not cause a -{\tt EVT\_TOGGLEBUTTON} event to get emitted. +Sets the toggle button to the given state. This does not cause a +{\tt EVT\_TOGGLEBUTTON} event to be emitted. \wxheading{Parameters} -- 2.47.2