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

Name change replacements

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/branches/WX_2_4_BRANCH@27091 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Julian Smart
2004-05-04 08:52:33 +00:00
parent 03d21d9053
commit 74ca941903
229 changed files with 1170 additions and 1138 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
docs/latex/wx/app.tex
View File

@@ -12,7 +12,7 @@ objects in the application.
\end{itemize}
You should use the macro IMPLEMENT\_APP(appClass) in your application implementation
file to tell wxWindows how to create an instance of your application class.
file to tell wxWidgets how to create an instance of your application class.
Use DECLARE\_APP(appClass) in a header file if you want the wxGetApp function (which returns
a reference to your application object) to be visible to other files.
@@ -104,7 +104,7 @@ Returns the application name.
\wxheading{Remarks}
wxWindows sets this to a reasonable default before
wxWidgets sets this to a reasonable default before
calling \helpref{wxApp::OnInit}{wxapponinit}, but the application can reset it at will.
\membersection{wxApp::GetAuto3D}\label{wxappgetauto3d}
@@ -194,7 +194,7 @@ dialogs to pop up before the main loop has been entered).
\func{int}{MainLoop}{\void}
Called by wxWindows on creation of the application. Override this if you wish
Called by wxWidgets on creation of the application. Override this if you wish
to provide your own (environment-dependent) main loop.
\wxheading{Return value}
@@ -269,7 +269,7 @@ was used}
Provide this member function for any processing which needs to be
done as the application is about to exit. OnExit is called after
destroying all application windows and controls, but before
wxWindows cleanup.
wxWidgets cleanup.
\membersection{wxApp::OnCmdLineError}\label{wxapponcmdlineerror}
@@ -346,11 +346,11 @@ work and, in fact, probably won't.
%%since this forwards OnIdle events to windows and also performs garbage collection for
%%windows whose destruction has been delayed.
%%
%%wxWindows' strategy for OnIdle processing is as follows. After pending user interface events for an
%%application have all been processed, wxWindows sends an OnIdle event to the application object. wxApp::OnIdle itself
%%wxWidgets' strategy for OnIdle processing is as follows. After pending user interface events for an
%%application have all been processed, wxWidgets sends an OnIdle event to the application object. wxApp::OnIdle itself
%%sends an OnIdle event to each application window, allowing windows to do idle processing such as updating
%%their appearance. If either wxApp::OnIdle or a window OnIdle function requested more time, by
%%calling \helpref{wxIdleEvent::RequestMore}{wxidleeventrequestmore}, wxWindows will send another OnIdle
%%calling \helpref{wxIdleEvent::RequestMore}{wxidleeventrequestmore}, wxWidgets will send another OnIdle
%%event to the application object. This will occur in a loop until either a user event is found to be
%%pending, or OnIdle requests no more time. Then all pending user events are processed until the system
%%goes idle again, when OnIdle is called, and so on.
@@ -395,7 +395,7 @@ application's main window, optionally calling
\helpref{wxApp::SetTopWindow}{wxappsettopwindow}.
Notice that if you want to to use the command line processing provided by
wxWindows you have to call the base class version in the derived class
wxWidgets you have to call the base class version in the derived class
OnInit().
Return TRUE to continue processing, FALSE to exit the application.
@@ -451,14 +451,14 @@ Under Windows, OnQueryEndSession is called in response to the WM\_QUERYENDSESSIO
Windows-only function for processing a message. This function
is called from the main message loop, checking for windows that
may wish to process it. The function returns TRUE if the message
was processed, FALSE otherwise. If you use wxWindows with another class
was processed, FALSE otherwise. If you use wxWidgets with another class
library with its own message loop, you should make sure that this
function is called to allow wxWindows to receive messages. For example,
function is called to allow wxWidgets to receive messages. For example,
to allow co-existence with the Microsoft Foundation Classes, override
the PreTranslateMessage function:
\begin{verbatim}
// Provide wxWindows message loop compatibility
// Provide wxWidgets message loop compatibility
BOOL CTheApp::PreTranslateMessage(MSG *msg)
{
if (wxTheApp && wxTheApp->ProcessMessage((WXMSW *)msg))
@@ -505,7 +505,7 @@ If TRUE is returned, more OnIdle processing is requested by one or more window.
Sets the name of the application. The name may be used in dialogs
(for example by the document/view framework). A default name is set by
wxWindows.
wxWidgets.
\wxheading{See also}
@@ -563,10 +563,10 @@ deleted. If FALSE, the application will continue to run.}
\func{void}{SetTopWindow}{\param{wxWindow* }{window}}
Sets the `top' window. You can call this from within \helpref{wxApp::OnInit}{wxapponinit} to
let wxWindows know which is the main window. You don't have to set the top window;
let wxWidgets know which is the main window. You don't have to set the top window;
it is only a convenience so that (for example) certain dialogs without parents can use a
specific window as the top window. If no top window is specified by the application,
wxWindows just uses the first frame or dialog in its top-level window list, when it
wxWidgets just uses the first frame or dialog in its top-level window list, when it
needs to use the top window.
\wxheading{Parameters}
@@ -584,7 +584,7 @@ needs to use the top window.
Sets the name of application's vendor. The name will be used
in registry access. A default name is set by
wxWindows.
wxWidgets.
\wxheading{See also}