BUGS AND WORKAROUNDS
	AVS will crash if the Keyframe Animator is saved into a network
	then loaded back in.  Don't save the Keyframe Animator as part
	of a network.  Always drag the module down and connect it by
	hand.

	Because matrix calculations within AVS are done as floats
	instead of doubles, rounding errors occur causing the SCALE
	button to light sometimes when you're only rotating an object.
	Currently there is no workaround.

	Due to a bug in AVS concerning sliders in immediate mode, the
	"animation frame" slider occasionally shows a different value
	than the slider is actually producing.  Clicking one of the
	arrow buttons will update the animation so that it matches the
	slider value.

	Because certain operations aren't allowed in a module's
	destroy routine, any popup windows created by the Keyframe
	Animator that are open when you kill the module will remain
	behind.  Also, the trace object will remain behind if left on
	when the module is killed and any object under the control of
	the Keyframe Animator will retain its parents and its transform
	and notify status.  Always use the "exit" button to kill the
	Keyframe Animator module.

	Animating cameras and lights doesn't work properly (AVS doesn't
	seem to notify transformations of lights and cameras).  There is
	no workaround except to animate the "%top" object instead of the
	camera.

FUTURE ENHANCEMENTS
	Loading objects in through the Keyframe Animator instead of
	having to load them in via the Geometry Viewer subsystem.

	Picking an object's parent using the mouse instead of by typing
	in the name of the parent object.

	Support for interpolation of other object attributes like
	color, as well as interpolation of parameters from other
	modules in the network.
	
	Having separate keyframe lists for each object.
