Terminology
The following terms, which represent key animation concepts, are used throughout this overview and the descriptions of Anim package KPs. The definitions build upon each other and are best read in sequence.
request
An animation request is an atomic unit of an animation, for example, “drawing a line.” Generally, each Anim package KP issues a single request, but some KPs issue several requests.
graphical primitive
A graphical primitive is a icon or geometric figure such as a circle or rectangle. Primitives serve as building blocks for more complex graphical figures. Some animation requests perform operations, such as drawing and erasing, on graphical primitives.
model element
A model element is synonymous with the conventional term “model object.” Examples of model elements are nodes, modules, and states. Some animation requests perform model element operations, such as updating element graphical attributes and determining element positions.
flow
An animation flow is the sequence of animation requests issued during a simulation. Animation flows start at the beginning of the simulation, and end at one of three events:
- the termination of the simulation
- the occurrence of a fatal animation error
- a special “flow end” request
The settings of certain simulation environment attributes determine whether an animation flow is directed to a running instance of the animation viewer program or to a history file for viewing later.
history
An animation history is a complete record of an animation flow that has been stored in a file for post-simulation viewing by the animation viewer program. History files are stored in the model directories, and have the suffix .ah.
viewer
A viewer is rectangular area for displaying sequences of related animation requests. Within the viewer program, each open viewer is assigned a graphical window in which the viewer’s requests are displayed. Some animation requests are directed to specific viewers.
drawing
A drawing is a retained instance of a graphical primitive, such as a particular circle or line. A drawing is created when a graphical primitive is drawn with the retain property enabled. Drawings are associated with viewers, and are visible until specifically erased. When a viewer is redrawn, all of its drawings are redrawn.
immediate-mode
Immediate-mode requests address graphical output directly to an animation viewer. This is in contrast to macro-oriented requests, which define an operation for later execution within a macro.
macro
An animation macro is a combination of several animation requests that together represent a graphical figure. For example, a macro’s graphical figure might consist of a rectangle with two diagonal lines. Invoking a macro is more efficient than issuing a sequence of individual animation requests, if the macro is invoked at least several times. This is due to the fact that when invoked, macros simply reference the previously issued requests that define the graphical figure, and thus only the minimal number of animation requests needed to convey the new parameters of the figure.
register
Registers are used to pass parameter values to macros and as variables for storing intermediate values. Registers are memory cells that can hold general parameters, including integer, double, and character string values. Each time a macro is invoked, a separate drawing is allocated. Macro drawings include a set of 26 registers, named A-Z, thus supporting up to 26 parameters.