A list of the known bugs in ani v1.10 as of May 7, 1986. 

Of course I plan to fix all of these as soon as I can.  Now that
I'm working with the Aztec development system, this should not be
too long.  Frankly I don't even know what the Aegis update policy is.
However they are charging 10 bucks for Images updates.  Anyway by
hook or by crook come a month or so these bugs should be replaced
by newer better and probably more cryptic bugs.

1.	Rubberbanding an object fully off-screen (partially ok) causes 
	massive list scrambling and introduces you quickly to the guru.
	Workaround: The path type of movement doesn't involve rubberbanding.
	Use this if you are moving things off-screen.

2.  The visible representation of centers for movement and hilighted
	outlines and points for multiple-selections get clobbered by
	the new EA-style (visible over complex background) rubberbanding.
	Incedentally it was this upgrade that caused bug #1.  (See what
	I mean about newer better bugs...?)  The work-around is to
	remember what you've done yourself.

3.  Exiting the Animator from the Project-menu pull-down causes
    slow death if you run it from the work-bench.
	Work-around:  Exit from the fast menu, or run ani from the CLI.

4.  Sometimes the select routines get confused when objects are not
    all on the initial Z plane if you are in "points", "segment" or "point"
	select modes.
	Work-around:  try selecting things with ghost-mode enabled.
	Sometimes this helps.  Real workaround is to get me to fix it.

5.  When I load FireEater.script, and then load anything else 
	I get "outta memory gotta go" panics.
	Work-around:  this is caused by two things.  FireEater was
	made with another version of ani that had more memory and less
	code.  Ani keeps the old script after a load for the "undo"
	option.  Hitting "new script" from the project menu before
	loading a new script will eliminate the panic.

6.  When I respond YES to save script during a "outta memory"
	situation sometimes the system hangs and sometimes even
	eats my disk!
	Work-around: Sorry about that disk!  Well yes actually I
	made this up but it could happen.  In about 5% or the
	outta memory situations Ani is so confused that nasty things
	happen.  The work-around is to watch your gas gauge (or
	do frequent status's), back up disks frequently, save to
	disk frequently, and never say YES when you can't afford to
	lose that disk.  As I say 95% of the time you'll be ok, but
	please don't send me a letter bomb when it does happen.

7.  I sometimes get outta-memory situations even when status
	says I have 10000 bytes left.
	Explanation:  Memory fragmentation.  You may have some memory left
	but it may all be in little pieces too small for what is needed.
	Work-around: Don't let gas gauge get that low.  By some expansion
	memory and type "ani -m 400000" from the CLI.