Release 4.1.0
October 2013

Modifications/Improvements:

- EULA can now be accepted on the command line (for example, when the
    first run is in batch mode).
- Wire starts and ends can face either left or right now.
- Right-click wire start, "Create Matching End" option added.
- Components now all accept the "Enter" key as substitute for the
    "Okay" button when creating them, making creation a bit faster.
- Bundler/unbundler put sorting and grouping now allows you to be far
     more arbitrary with which wires get grouped with which and what order
     the groups are in, though the default behavior is just like the old.
- Display elements will now take their input from any of the four
     sides, you no longer need to specify - just like Stop elements do.
- JLS 4.1 is backwards compatible when loading JLS 4.0 files. However,
     4.1 will not attempt to KEEP files backwards compatible when saving, due
     to the addition of several features mentioned above.

Bug fixes:

- Many typo fixes, etc in help pages.
- Many minor fixes in the undo system, mostly in things being undone
     incorrectly.
- Bundlers handle tri-state wires more predictably now.
- The linux placement bug is fixed.

Installation and use:

        Make sure you have Java version 5.0 (at least) installed on your
        machine(s).  Warning - there have been unreproducable errors when
	using Java version 7.  Use at your own risk.

        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.