|[ Home | What's New | Contents | Overview | Contributors | Distribution | Examples | Documentation | Manual | Publications | Mailing List Archive | Problems ]||This page was last updated by Axel Belinfante on 2006-06-30|
|TorX Test Tool Information|
Actually, aniwait is a shell-level command that uses a running aniwaitsrv to create or reuse a progressbar window, and animate it using animation commands on standard input of aniwait. The connection between aniwait and a running aniwaitsrv will not be closed until the complete standard input of the aniwait command has been processed by aniwaitsrv. If aniwait cannot find a running aniwaitsrv, it will start a new one. In general, it should not be necessary to start aniwaitsrv by hand. However, if startup time of aniwait is an issue, it may be advantageous to start aniwaitsrv (by hand) in advance, because a starting aniwaitsrv may spend some time to check if another aniwaitsrv is already running.
To display a new progressbar, aniwaitsrv will reuse windows that contain a completed animation and have the Reuse toggle activated. If more windows are needed, they are created.
The -r command line option of aniwait will activate the Reuse toggle button for the aniwait window.
The animation commands are expected to be generated using log2aniwait(1), e.g. using a unix command as
log2aniwait < logfile | aniwaitor
tail -f logfile | log2aniwait | aniwait
Each animation command consists of a single line of text, of the following form:
wait countwhere count and remains are floating point numbers. The wait command starts a countdown of the given count number of seconds. The freeze and stop commands stop the countdown, and add a `step' to the trace of progress times. freeze and stop interpret the optional remains as the time remaining from the count from the countdown command; if no remains is given, the real-time system clock is used. An additional freeze or stop command without preceding wait command has no effect and is ignored. The difference between freeze and stop is in the color of the progressbar: freeze does not change the color, but only `freezes' the animation, whereas stop changes the color of the progressbar to blue.
freeze [ remains ]
stop [ remains ]
The animation in the window will follow the animation commands read from standard input. The animation can be be done manually using the left and middle mouse button, and/or with the Step up and down arrow buttons (as discussed below).
In addition, the animation can be remotely controlled. If the -m mcastid command line option is given, or environment variable TORXMCASTID was set, aniwait will attempt to make a remote control connection to the tcp address in mcastid. If it succeeds, it will then interpret lines of text read from the remote control connection consisting of a single number as commands to show the corresponding step in the animation. Additionally, whenever the user uses mouse button and/or navigation commands to show a different step, its step number is written to the remote control connection. The remote control connection allows multiple viewers to show the same test step.
The left mouse button and the right mouse button can be used to ``navigate'' in the animation: the left mouse button will show the ``next'' step in the animation, and the right mouse button will show the ``previous'' step in the animation.
To stop a running aniwaitsrv, invoke aniwait with the -exit command line option.
Table of Contents
|Prev||Table of Contents||Next|
|Appendix D: TorX Manual Pages: aniwait(1) - animate progressbar||Appendix D: TorX Manual Pages: aut2fsmview(1) - translate Aldebaran (.aut) to FSMView input|