Remaining BUGS (highest priority first)
---------------------------------------

4 January 1998
==============
Q: The source code could be condensed:
   1. Split off the object window stuff (it seems to be generally useful)
   2. Split off the netlist parsing
   3. Code cries out for structures (get rid of the magic offsets)
   4. Node number -> array address mapping in initialization phase (higher speed)
A: When there's time, or need...


Careful! ( Jan. 11)
There could be a bug in the ISO-FWR code somewhere. If I run a circuit using this
component followed by a different circuit using it also, the second circuit behaves
erratically. FIX: reload nspicetr before loading the second cicuit. The effect is
(probably) caused by a global variable that is not being reset.

Q: Is there backtracking to the correct event time when a diode current crosses zero?
A: Implemented for DIODE. The results are not devastatingly different, so for the time 
   being I won't bother for other components.

Q: The "immediate" screen output under Linux is screwed up.
A: Will be fixed (Linux bitmap copying doesn't work anymore).
   The new EKEY for Linux seems to have a lot of side-effects.

Q: NSPICETR should use both V(0) and I(0) to initialize L and C.
A: Will be changed, but it doesn't seem to make much of a difference.

Q: Should be able to set graph options (RASTER, linetype etc.)
A: I'm lazy. Use SPICE's INTUSCOPE.

Q: When doing many SHOWs, resizing etc, sometimes the colors disappear and the
   font is set to a default fixed width. The only remedy is a restart.
A: I suspect a resource leak when destroying the DC after SHOW CLIP or PRINT.

Q: iForth starts up with random characters all over the screen.
A: The default terminal window is 2500 lines. This seems to interfere with
   the startup messages & clear screen. It doesn't happen when I start from
   a desktop icon that sets a smaller screen size (100x40, no extra buffer).

Q: Not all of the .CIR's in ./oldcircuits work.
A: That's why they're not in ./circuits.

Q: Printing to the clipboard produces pictures too large / complex for 
   MS-Word to handle (can't edit them).
A: It seems there are [still] some 16-bit limitations in that wonderful program.
   Or maybe it can't handle real EMF yet (only WMF)?

