fixed a few typos
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@27011 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
parent
c567d635a2
commit
653d2f0cb3
@ -620,7 +620,7 @@ DocStr(wxActiveXEvent,
|
||||
ActiveX events. Any event parameters from the ActiveX cntrol are
|
||||
turned into attributes of the Python proxy for this event object.
|
||||
Additionally, there is a property called eventName that will
|
||||
return (suprizingly <wink>) the name of the ActiveX event.");
|
||||
return (surprisingly <wink>) the name of the ActiveX event.");
|
||||
|
||||
class wxActiveXEvent : public wxCommandEvent
|
||||
{
|
||||
|
@ -88,7 +88,7 @@ ActiveX control in a very intuitive way.
|
||||
the win32all extensions, and is more "wx\'ish", meaning that it uses
|
||||
events and etc. as would be expected from any other wx window.
|
||||
|
||||
<p> This demo embeds the Shackwave Flash control, and lets you play a game.
|
||||
<p> This demo embeds the Shockwave Flash control, and lets you play a game.
|
||||
|
||||
</body></html>
|
||||
"""
|
||||
|
@ -60,7 +60,7 @@ come with the class itself.
|
||||
|
||||
<li>Print
|
||||
|
||||
<p>Suprise! It prints the current plot to your printer! :-)
|
||||
<p>Surprise! It prints the current plot to your printer! :-)
|
||||
|
||||
<li>Save Plot
|
||||
|
||||
|
@ -147,7 +147,7 @@ place, then do the same for wxPython.
|
||||
these commands, so it won't impact your already installed version
|
||||
of the latest release. You'll be able test with this version when
|
||||
you want to, and use the installed release version the rest of the
|
||||
time. If do want to install the development verison please read
|
||||
time. If you want to install the development version please read
|
||||
INSTALL.txt.
|
||||
|
||||
If you have more than one version of Python on your system then be
|
||||
@ -190,7 +190,7 @@ place, then do the same for wxPython.
|
||||
located in the wx package.
|
||||
|
||||
|
||||
4. To run code with the development verison of wxPython, just set the
|
||||
4. To run code with the development version of wxPython, just set the
|
||||
PYTHONPATH to the wxPython dir located in the source tree. For
|
||||
example::
|
||||
|
||||
@ -236,7 +236,7 @@ wxPython extensions that I distribute are built with MSVC 6 with all
|
||||
the Service Packs applied. This policy will change with Python 2.4
|
||||
and MSVC 7.1 will be used starting with that version.
|
||||
|
||||
If you want to build a debugable version of wxWidgets and wxPython you
|
||||
If you want to build a debuggable version of wxWidgets and wxPython you
|
||||
will need to have also built a debug version of Python and any other
|
||||
extension modules you need to use. You can tell if you have them
|
||||
already if there is a _d in the file names, for example python_d.exe
|
||||
@ -326,7 +326,7 @@ below assume that you are using my scripts.
|
||||
installed version of the latest release. You'll be able to test
|
||||
with this version when you want to, and use the installed release
|
||||
version the rest of the time. If you ever do want to install the
|
||||
development verison please refer to INSTALL.txt.
|
||||
development version please refer to INSTALL.txt.
|
||||
|
||||
Change to the %WXDIR%\\wxPython dir and run the this command,
|
||||
makeing sure that you use the version of python that you want to
|
||||
@ -358,7 +358,7 @@ below assume that you are using my scripts.
|
||||
files) located in the wx package.
|
||||
|
||||
|
||||
9. To run code with the development verison of wxPython, just set the
|
||||
9. To run code with the development version of wxPython, just set the
|
||||
PYTHONPATH to the wxPython dir in the CVS tree. For example::
|
||||
|
||||
set PYTHONPATH=%WXDIR%\wxPython
|
||||
|
@ -78,7 +78,7 @@ installing them also on my main Mandrake 9.2 box.
|
||||
|
||||
There are some big changes in the OS X disk image. The actual
|
||||
Installer package now *only* installs the wxMac dynlibs, wxPython
|
||||
extension modules and Python pacakges, and also the command-line tool
|
||||
extension modules and Python packages, and also the command-line tool
|
||||
scripts. The remaining items (demo, samples, and application bundles
|
||||
for the Demo, PyCrust and XRCed) are now top-level items in the disk
|
||||
image (.dmg file) that users can just drag and drop to wherever they
|
||||
|
Loading…
Reference in New Issue
Block a user