Release 4.0.13
January 2009
Modifications/Improvements:
    Can rotate almost all elements, either when placed or afterwards if not
	connected.
    Anotated tic marks added to signal trace.
    Order of signal traces saved in .jls file (but not probes).
    Can change the color of the edit window background and grid.
    Simulator occupies 1/2 of window when shown.
    JLSerror file contains build date/time.
    Can reset all propagation delays from startup file.
    JLS can open a .jls~ file on both the command line (batch or
	interractive) and with file open dialog.


Bug fixes:
    Open file dialog will start in the same directory as the last time an
	open or saveAs was done.
    Can now change the propagation delay of the truth table element and state
	machine elements.
    Invalid file name error message clearer.
    Subcircuit close bug fixed.
    Name of deleted truth table element can now be re-used.
    Register create/modify dialog manages initial value changes properly.
    Simulator Window size is correct for switching between run/show/hide.
    Truth tables simulation should work ok.
    Reset all propagation delays no longer resets the delay of a delay gate.
    Watched elements now all show up correctly in signal traces, even after
	changing which elements are watched/unwatched.
    Statemachine will no longer detach if no input/output changes were
	made.
    Statemachine edit dialog box size better matches state machine visible
	parts.
    Checks that an input signal in a new state has the same number of bits
	as an existing input signal with the same name in different state(s).
    
Installation and use:

        Make sure you have Java version 5.0 (at least) installed on your
        machine(s).

        Put JLS.jar in any folder/directory you like.

        Linux (or any other UNIX variant):
                Execute by typing "java -jar JLS.jar [params]",
                or better yet, make a script.

        Windows:
                Simply click on the JLS.jar icon to start it up.
                Run it non-interractively from a DOS or CYGWIN prompt just
                    like Linux.

        Read the on-line documentation (Help menu) for everything else.

If a bug in JLS causes a Java exception, JLS will usually catch it and give you
a chance to save your circuit.  JLS will also spit out a file called "JLSerror"
in the current directory/folder.  It contains the exception info, a stack
trace, platform specfics and the current circuit.  Please send this file to me
when reporting the problem so I have the information I'll need to track down
and fix it.