Known bugs in and problems with Polyview 3.0:

o Polyview supports multiple graphics windows but only one action list.
  Thus, if you are in the middle of an action sequence (a 'move camera'
  flight, or a series of commands loaded from a script) in one window and
  make another window active, the newly active window will start executing
  the actions.

  There should be separate action lists on a per-window basis.  This is a 
  deficiency inherited from Polyview 2.0 and is on my long-range to-do list.

o Having separate windows for animation control ('time') and for palette
  control ('palette') and having those windows reconfigure themselves when
  the user makes a new polyview window active is bad; those controls should
  be built into each polyview window.

  Again, this is a deficiency inherited from 2.0 and is also on my long-
  range to-do list.

o When running with multiple windows, one palette is shared among all the
  windows.  Which palette is used at any given time is determined by the
  current active window, but when the active window changes, all windows
  on the screen change palettes to accommodate the new active window.

  Again, inherited from 2.0 and to be changed.

