X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/c6f4913a7636367c7f3b677e3a30bbb4e50604e9..146ba0feacf1222ec8a45dfd69dae77b063bf2cf:/docs/latex/wx/treectrl.tex diff --git a/docs/latex/wx/treectrl.tex b/docs/latex/wx/treectrl.tex index 3af18623f5..2792ac55df 100644 --- a/docs/latex/wx/treectrl.tex +++ b/docs/latex/wx/treectrl.tex @@ -35,14 +35,14 @@ to hide vertical level connectors.} \twocolitem{\windowstyle{wxTR\_FULL\_ROW\_HIGHLIGHT}}{Use this style to have the background colour and the selection highlight extend over the entire horizontal row of the tree control window. (This flag is ignored under Windows unless you -specified wxTR\_NO\_LINES as well.) } +specify wxTR\_NO\_LINES as well.) } \twocolitem{\windowstyle{wxTR\_LINES\_AT\_ROOT}}{Use this style to show lines between root nodes. Only applicable if wxTR\_HIDE\_ROOT is set and wxTR\_NO\_LINES is not set.} \twocolitem{\windowstyle{wxTR\_HIDE\_ROOT}}{Use this style to suppress the display of the root node, effectively causing the first-level nodes -to appear as a series of root nodes. Generic only.} +to appear as a series of root nodes.} \twocolitem{\windowstyle{wxTR\_ROW\_LINES}}{Use this style to draw a contrasting border between displayed rows.} \twocolitem{\windowstyle{wxTR\_HAS\_VARIABLE\_ROW\_HEIGHT}}{Use this style @@ -350,7 +350,7 @@ Returns an invalid tree item if there are no further children. value are both returned as a tuple containing the two values.} \perlnote{In wxPerl this method only takes the {\tt item} parameter, and - returns a 2-element list ( item, cookie ).} + returns a 2-element list {\tt ( item, cookie )}.} \membersection{wxTreeCtrl::GetFirstVisibleItem}\label{wxtreectrlgetfirstvisibleitem} @@ -454,7 +454,7 @@ Returns an invalid tree item if there are no further children. value are both returned as a tuple containing the two values.} \perlnote{In wxPerl this method returns a 2-element list - ( item, cookie ), instead of modifying its parameters.} + {\tt ( item, cookie )}, instead of modifying its parameters.} \membersection{wxTreeCtrl::GetNextSibling}\label{wxtreectrlgetnextsibling} @@ -570,7 +570,7 @@ id at this point plus extra information {\it flags}. {\it flags} is a bitlist of returned as a tuple.} \perlnote{In wxPerl this method only takes the {\tt point} parameter - and returns a 2-element list ( item, flags ).} + and returns a 2-element list {\tt ( item, flags )}.} \membersection{wxTreeCtrl::InsertItem}\label{wxtreectrlinsertitem} @@ -589,7 +589,7 @@ If {\it image} > -1 and {\it selImage} is -1, the same image is used for both selected and unselected items. \pythonnote{The second form of this method is called -\tt{InsertItemBefore} in wxPython.} +{\tt InsertItemBefore} in wxPython.} \membersection{wxTreeCtrl::IsBold}\label{wxtreectrlisbold} @@ -826,75 +826,3 @@ This function either behaves the same as \helpref{Unselect}{wxtreectrlunselect} if the control doesn't have wxTR\_MULTIPLE style, or removes the selection from all items if it does have this style. -\section{\class{wxTreeItemData}}\label{wxtreeitemdata} - -wxTreeItemData is some (arbitrary) user class associated with some item. The -main advantage of having this class (compared to the old untyped interface) is -that wxTreeItemData's are destroyed automatically by the tree and, as this -class has virtual dtor, it means that the memory will be automatically -freed. We don't just use wxObject instead of wxTreeItemData because -the size of this class is critical: in any real application, each tree leaf -will have wxTreeItemData associated with it and number of leaves may be -quite big. - -Because the objects of this class are deleted by the tree, they should -always be allocated on the heap. - -\wxheading{Derived from} - -wxTreeItemId - -\wxheading{Include files} - - - -\wxheading{See also} - -\helpref{wxTreeCtrl}{wxtreectrl} - -\latexignore{\rtfignore{\wxheading{Members}}} - -\membersection{wxTreeItemData::wxTreeItemData}\label{wxtreeitemdataconstr} - -\func{}{wxTreeItemData}{\void} - -Default constructor. - -\pythonnote{The wxPython version of this constructor optionally -accepts any Python object as a parameter. This object is then -associated with the tree item using the wxTreeItemData as a -container. - -In addition, the following methods are added in wxPython for accessing -the object: - -\indented{2cm}{\begin{twocollist}\itemsep=0pt -\twocolitem{{\bf GetData()}}{Returns a reference to the Python Object} -\twocolitem{{\bf SetData(obj)}}{Associates a new Python Object with the -wxTreeItemData} -\end{twocollist}} -} - -\perlnote{In wxPerl the constructor accepts as parameter an optional scalar, - and stores it as client data. You may retrieve this data by calling - {\bf GetData()}, and set it by callling {\bf SetData( data ).} -} - -\membersection{wxTreeItemData::\destruct{wxTreeItemData}} - -\func{void}{\destruct{wxTreeItemData}}{\void} - -Virtual destructor. - -\membersection{wxTreeItemData::GetId}\label{wxtreeitemdatagetid} - -\func{const wxTreeItem\&}{GetId}{\void} - -Returns the item associated with this node. - -\membersection{wxTreeItemData::SetId}\label{wxtreeitemdatasetid} - -\func{void}{SetId}{\param{const wxTreeItemId\&}{ id}} - -Sets the item associated with this node. -