source: vendor/python/2.5/Doc/lib/libcursespanel.tex

Last change on this file was 3225, checked in by bird, 18 years ago

Python 2.5

File size: 2.9 KB
Line 
1\section{\module{curses.panel} ---
2 A panel stack extension for curses.}
3
4\declaremodule{standard}{curses.panel}
5\sectionauthor{A.M. Kuchling}{amk@amk.ca}
6\modulesynopsis{A panel stack extension that adds depth to
7 curses windows.}
8
9Panels are windows with the added feature of depth, so they can be
10stacked on top of each other, and only the visible portions of
11each window will be displayed. Panels can be added, moved up
12or down in the stack, and removed.
13
14\subsection{Functions \label{cursespanel-functions}}
15
16The module \module{curses.panel} defines the following functions:
17
18
19\begin{funcdesc}{bottom_panel}{}
20Returns the bottom panel in the panel stack.
21\end{funcdesc}
22
23\begin{funcdesc}{new_panel}{win}
24Returns a panel object, associating it with the given window \var{win}.
25Be aware that you need to keep the returned panel object referenced
26explicitly. If you don't, the panel object is garbage collected and
27removed from the panel stack.
28\end{funcdesc}
29
30\begin{funcdesc}{top_panel}{}
31Returns the top panel in the panel stack.
32\end{funcdesc}
33
34\begin{funcdesc}{update_panels}{}
35Updates the virtual screen after changes in the panel stack. This does
36not call \function{curses.doupdate()}, so you'll have to do this yourself.
37\end{funcdesc}
38
39\subsection{Panel Objects \label{curses-panel-objects}}
40
41Panel objects, as returned by \function{new_panel()} above, are windows
42with a stacking order. There's always a window associated with a
43panel which determines the content, while the panel methods are
44responsible for the window's depth in the panel stack.
45
46Panel objects have the following methods:
47
48\begin{methoddesc}{above}{}
49Returns the panel above the current panel.
50\end{methoddesc}
51
52\begin{methoddesc}{below}{}
53Returns the panel below the current panel.
54\end{methoddesc}
55
56\begin{methoddesc}{bottom}{}
57Push the panel to the bottom of the stack.
58\end{methoddesc}
59
60\begin{methoddesc}{hidden}{}
61Returns true if the panel is hidden (not visible), false otherwise.
62\end{methoddesc}
63
64\begin{methoddesc}{hide}{}
65Hide the panel. This does not delete the object, it just makes the
66window on screen invisible.
67\end{methoddesc}
68
69\begin{methoddesc}{move}{y, x}
70Move the panel to the screen coordinates \code{(\var{y}, \var{x})}.
71\end{methoddesc}
72
73\begin{methoddesc}{replace}{win}
74Change the window associated with the panel to the window \var{win}.
75\end{methoddesc}
76
77\begin{methoddesc}{set_userptr}{obj}
78Set the panel's user pointer to \var{obj}. This is used to associate an
79arbitrary piece of data with the panel, and can be any Python object.
80\end{methoddesc}
81
82\begin{methoddesc}{show}{}
83Display the panel (which might have been hidden).
84\end{methoddesc}
85
86\begin{methoddesc}{top}{}
87Push panel to the top of the stack.
88\end{methoddesc}
89
90\begin{methoddesc}{userptr}{}
91Returns the user pointer for the panel. This might be any Python object.
92\end{methoddesc}
93
94\begin{methoddesc}{window}{}
95Returns the window object associated with the panel.
96\end{methoddesc}
Note: See TracBrowser for help on using the repository browser.