Fixed some typos
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@43690 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
@@ -10,9 +10,9 @@ determine each pane's docking and floating behavior. wxAuiManager
|
|||||||
uses wxWidgets' sizer mechanism to plan the layout of each frame. It
|
uses wxWidgets' sizer mechanism to plan the layout of each frame. It
|
||||||
uses a replaceable dock art class to do all drawing, so all drawing is
|
uses a replaceable dock art class to do all drawing, so all drawing is
|
||||||
localized in one area, and may be customized depending on an
|
localized in one area, and may be customized depending on an
|
||||||
applications' specific needs.
|
application's specific needs.
|
||||||
|
|
||||||
wxAuiManager works as follows: The programmer adds panes to the class,
|
wxAuiManager works as follows: the programmer adds panes to the class,
|
||||||
or makes changes to existing pane properties (dock position, floating
|
or makes changes to existing pane properties (dock position, floating
|
||||||
state, show state, etc.). To apply these changes, wxAuiManager's
|
state, show state, etc.). To apply these changes, wxAuiManager's
|
||||||
Update() function is called. This batch processing can be used to avoid
|
Update() function is called. This batch processing can be used to avoid
|
||||||
@@ -48,19 +48,18 @@ Center. This is fairly self-explanatory. The pane will be placed in the
|
|||||||
location specified by this variable.
|
location specified by this variable.
|
||||||
|
|
||||||
{\bf Position:}
|
{\bf Position:}
|
||||||
More than one pane can be placed inside of a dock. Imagine to panes
|
More than one pane can be placed inside of a dock. Imagine two panes
|
||||||
being docked on the left side of a window. One pane can be placed over
|
being docked on the left side of a window. One pane can be placed over
|
||||||
another. In proportionally managed docks, the pane position indicates
|
another. In proportionally managed docks, the pane position indicates
|
||||||
it's sequential position, starting with zero. So, in our scenario with
|
its sequential position, starting with zero. So, in our scenario with
|
||||||
two panes docked on the left side, the top pane in the dock would have
|
two panes docked on the left side, the top pane in the dock would have
|
||||||
position 0, and the second one would occupy position 1.
|
position 0, and the second one would occupy position 1.
|
||||||
|
|
||||||
{\bf Row:}
|
{\bf Row:}
|
||||||
A row can allow for two docks to be placed next to each other. One of
|
A row can allow for two docks to be placed next to each other. One of
|
||||||
the most common places for this to happen is in the toolbar. Multiple
|
the most common places for this to happen is in the toolbar. Multiple
|
||||||
toolbar rows are allowed, the first row being in row 0, and the second
|
toolbar rows are allowed, the first row being row 0, and the second
|
||||||
in row 1. Rows can also be used on vertically docked panes.
|
row 1. Rows can also be used on vertically docked panes.
|
||||||
|
|
||||||
|
|
||||||
{\bf Layer:}
|
{\bf Layer:}
|
||||||
A layer is akin to an onion. Layer 0 is the very center of the
|
A layer is akin to an onion. Layer 0 is the very center of the
|
||||||
@@ -73,7 +72,7 @@ understand layers is by running the wxAUI sample.
|
|||||||
|
|
||||||
\wxheading{Derived from}
|
\wxheading{Derived from}
|
||||||
|
|
||||||
\helpref{wxEvent}{wxevent}
|
\helpref{wxEvtHandler}{wxevthandler}
|
||||||
|
|
||||||
\wxheading{Include files}
|
\wxheading{Include files}
|
||||||
|
|
||||||
|
@@ -24,7 +24,7 @@ require additional functionality, such as "spring-loaded" rebar support,
|
|||||||
"chevron" buttons and end-user customizability.
|
"chevron" buttons and end-user customizability.
|
||||||
|
|
||||||
{\bf Modeless Controls:}
|
{\bf Modeless Controls:}
|
||||||
Modeless controls expose a tool pallete or set of options that float
|
Modeless controls expose a tool palette or set of options that float
|
||||||
above the application content while allowing it to be accessed. Usually
|
above the application content while allowing it to be accessed. Usually
|
||||||
accessed by the toolbar, these controls disappear when an option is
|
accessed by the toolbar, these controls disappear when an option is
|
||||||
selected, but may also be "torn off" the toolbar into a floating frame
|
selected, but may also be "torn off" the toolbar into a floating frame
|
||||||
|
Reference in New Issue
Block a user