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

Fixed wxScrolledWindow references to properly link (and appropriately changed others to wxScrolled).

Browse Source 
Initial reviews of a few d* interface headers in this commit as well.


git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@53241 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Bryan Petty
2008-04-17 07:06:20 +00:00
parent 7e38638c34
commit f09b568121
18 changed files with 902 additions and 783 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/doxygen/overviews/dialog.h
View File

@@ -67,7 +67,7 @@ within wxDialog::Show or wxDialog::ShowModal:
@li If that search failed too, wxWidgets finds 'loose' standard buttons (in any kind of sizer)
and adds them to a wxStdDialogButtonSizer.
If no standard buttons were found, the whole dialog content will scroll.
@li All the children apart from standard buttons are reparented onto a new wxScrolledWindow
@li All the children apart from standard buttons are reparented onto a new ::wxScrolledWindow
object, using the old top-level sizer for the scrolled window and creating a new top-level
sizer to lay out the scrolled window and standard button sizer.

4
docs/doxygen/overviews/html.h
View File

@@ -45,7 +45,7 @@ There is a generic wxHtmlParser class, independent of wxHtmlWindow.
First of all, you must include @c wx/wxhtml.h.
Class wxHtmlWindow (derived from wxScrolledWindow) is used to display HTML documents.
Class wxHtmlWindow (derived from ::wxScrolledWindow) is used to display HTML documents.
It has two important methods: wxHtmlWindow::LoadPage and wxHtmlWindow::SetPage.
LoadPage loads and displays HTML file while SetPage displays directly the
@@ -65,7 +65,7 @@ See wxHtmlHelpController.
@subsection overview_html_quickstart_settingup Setting up wxHtmlWindow
Because wxHtmlWindow is derived from wxScrolledWindow and not from
Because wxHtmlWindow is derived from ::wxScrolledWindow and not from
wxFrame, it doesn't have visible frame. But the user usually wants to see
the title of HTML page displayed somewhere and the frame's titlebar is
the ideal place for it.

2
docs/doxygen/overviews/python.h
View File

@@ -415,7 +415,7 @@ spec over time.
@li wxScreenDC
@li wxScrollBar
@li wxScrollEvent
@li wxScrolledWindow
@li ::wxScrolledWindow
@li wxScrollWinEvent
@li wxShowEvent
@li wxSingleChoiceDialog

4
docs/doxygen/overviews/scrolling.h
View File

@@ -12,7 +12,7 @@
Classes:
@li wxWindow
@li wxScrolledWindow
@li ::wxScrolledWindow
@li wxScrollBar
@li @ref overview_scrolling_model
@@ -35,7 +35,7 @@ events. If you created a wxWindow object with scrollbars, and then clicked on
the scrollbars, nothing at all would happen. This is deliberate, because the
@e interpretation of scroll events varies from one window class to another.
wxScrolledWindow (formerly wxCanvas) is an example of a window that adds
::wxScrolledWindow (formerly wxCanvas) is an example of a window that adds
functionality to make scrolling really work. It assumes that scrolling happens
in consistent units, not different-sized jumps, and that page size is
represented by the visible portion of the window. It is suited to drawing