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

typo fixes

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@15176 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Robin Dunn
2002-04-16 21:33:33 +00:00
parent 1757121732
commit 36d9119341
1 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
wxPython/CHANGES.txt
View File

@@ -40,7 +40,7 @@ UNICODE!
wxWindows/wxPython can be compiled with unicode support enabled or wxWindows/wxPython can be compiled with unicode support enabled or
disabled. Previous to wxPython 2.3.3 non-unicode mode was always disabled. Previous to wxPython 2.3.3 non-unicode mode was always
used. Starting with 2.3.3 either mode is supported, but only if used. Starting with 2.3.3 either mode is supported, but only if
it is also available in wxWindow on the platform. Currently it is also available in wxWindows on the platform. Currently
wxWindows only supports unicode on MS Windows platforms, but with wxWindows only supports unicode on MS Windows platforms, but with
the recent release of GTK+ 2.0 it is only a matter of time until the recent release of GTK+ 2.0 it is only a matter of time until
it can be done on wxGTK (Linux and other unixes) as well. it can be done on wxGTK (Linux and other unixes) as well.
@@ -48,14 +48,14 @@ UNICODE!
Unicode works best on platforms in the NT branch of the Windows Unicode works best on platforms in the NT branch of the Windows
family tree (NT, win2k, XP) but it is now also possible to use the family tree (NT, win2k, XP) but it is now also possible to use the
same unicode binaries on win95/98/ME platforms as well! This is same unicode binaries on win95/98/ME platforms as well! This is
done by using a special library and DLL in the application called done by using a special library and DLL with the application
MSLU, (Microsoft Layer for Unicode). It simply gets out of the called MSLU, (Microsoft Layer for Unicode). It simply gets out of
way if the app is run on an NT box, or if run on a win9x box it the way if the app is run on an NT box, otherwise if run on a
loads a special DLL that provides the unicode versions of the win9x box it loads a special DLL that provides the unicode
windows API. So far I have not been able to get this to work versions of the windows API. So far I have not been able to get
perfectly on win9x. Most things work fine but wxTaskBarIcon for this to work perfectly on win9x. Most things work fine but
example will cause a crash if used with the unicode build on wxTaskBarIcon for example will cause a crash if used with the
win95. unicode build on win95.
So how do you use it? It's very simple. When unicode is enabled, So how do you use it? It's very simple. When unicode is enabled,
then all functions and methods in wxPython that return a wxString then all functions and methods in wxPython that return a wxString