Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
350b2b95
Commit
350b2b95
authored
Nov 14, 1995
by
Jack Jansen
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Documented ProgressBar and idle()
parent
a5503284
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
42 additions
and
2 deletions
+42
-2
Doc/libmacui.tex
Doc/libmacui.tex
+21
-1
Doc/mac/libmacui.tex
Doc/mac/libmacui.tex
+21
-1
No files found.
Doc/libmacui.tex
View file @
350b2b95
...
...
@@ -31,9 +31,25 @@ hitting return is \code{0}. This can be changed with the optional
\var
{
default
}
argument.
\end{funcdesc}
\begin{funcdesc}
{
ProgressBar
}{
\optional
{
label
\,
maxval
}}
Display a modeless progress dialog with a thermometer bar.
\var
{
Label
}
is the textstring displayed (default ``Working...''),
\var
{
maxval
}
is
the value at which progress is complete (default 100). The returned
object has one method,
\code
{
set(value)
}
, which sets the value of the
progress bar. The bar remains visible until the object returned is
discarded.
The progress bar has a ``cancel'' button, but it is currently
non-functional.
\end{funcdesc}
Note that
\code
{
EasyDialogs
}
does not currently use the notification
manager. This means that displaying dialogs while the program is in
the background will need to unexpected results and possibly crashes.
the background will lead to unexpected results and possibly
crashes. Also, all dialogs are modeless and hence expect to be at the
top of the stacking order. This is true when the dialogs are created,
but windows that pop-up later (like a console window) may also result
in crashes.
\section
{
Standard module
\sectcode
{
FrameWork
}}
...
...
@@ -145,6 +161,10 @@ through the the \code{DialogWindow} object involved). Override if you
need special handling of dialog events (keyboard shortcuts, etc).
\end{funcdesc}
\begin{funcdesc}
{
idle
}{}
Called by the main event loop when no events are available.
\end{funcdesc}
\subsection
{
Window Objects
}
Window objects have the following methods, among others:
...
...
Doc/mac/libmacui.tex
View file @
350b2b95
...
...
@@ -31,9 +31,25 @@ hitting return is \code{0}. This can be changed with the optional
\var
{
default
}
argument.
\end{funcdesc}
\begin{funcdesc}
{
ProgressBar
}{
\optional
{
label
\,
maxval
}}
Display a modeless progress dialog with a thermometer bar.
\var
{
Label
}
is the textstring displayed (default ``Working...''),
\var
{
maxval
}
is
the value at which progress is complete (default 100). The returned
object has one method,
\code
{
set(value)
}
, which sets the value of the
progress bar. The bar remains visible until the object returned is
discarded.
The progress bar has a ``cancel'' button, but it is currently
non-functional.
\end{funcdesc}
Note that
\code
{
EasyDialogs
}
does not currently use the notification
manager. This means that displaying dialogs while the program is in
the background will need to unexpected results and possibly crashes.
the background will lead to unexpected results and possibly
crashes. Also, all dialogs are modeless and hence expect to be at the
top of the stacking order. This is true when the dialogs are created,
but windows that pop-up later (like a console window) may also result
in crashes.
\section
{
Standard module
\sectcode
{
FrameWork
}}
...
...
@@ -145,6 +161,10 @@ through the the \code{DialogWindow} object involved). Override if you
need special handling of dialog events (keyboard shortcuts, etc).
\end{funcdesc}
\begin{funcdesc}
{
idle
}{}
Called by the main event loop when no events are available.
\end{funcdesc}
\subsection
{
Window Objects
}
Window objects have the following methods, among others:
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment