Release Notes for NeXT Mazewar 1/27/1990 release

This version is based on the 1988 comp.sources.sun code.  All
changes to the original source files are under conditionals.
I started with a shar distribution, so anything I didn't touch
has the date I exploded the archive, not when it was created.

I've fixed two bugs in the original code: a free() was misplaced,
causing the program to sometimes use an pointer to garbage, and
a bad multiprecision comparison caused players to randomly turn
into unkillable ghosts.

& characters in pw_gecos are handled properly, but in a NeXT-
dependent way, so it's under #ifdef NeXT.  You still get the old,
broken behavior on non-NeXTs.

The mouse buttons don't affect the game unless the cursor is
in the perspective view.

If NeXT supplied a 3-button mouse, I would be a lot happier.
The right mouse support is pretty lame as it is.

The initial modal panel disables the main menu and help scroller.
This can be somewhat annoying, but really isn't inconsistent with
the other versions, which engage in conventional terminal-based
dialog.  The "flashing" when you click the panel's Help button
comes from ordering the Help window front; trying to order it
below the panel fails with a DPS rangecheck error, presumably
because the panel didn't change tiers cleanly.

Command-w isn't implemented.

I apologize for the Times-Roman 10 font in the score area; I only
had 12 rows per line to work with and needed something that fit.

I also apologize for using the truly lousy C code written by
others that appears in some parts of winNeXT.m.  It's in no way
indicative of by own abilities.  If I was going to be a
perfectionist about it, this wouldn't be out now.

Running two copies of the program on the same workstation can
cause one to fail with an "Address in use" error after the other
exits.

If you want to start a new game even if there are other games on
the same network, type  localhost  to the "duke host" choice.

Why didn't I make the application more "NeXT-like?"  To some
extent I did: I took some liberties with the use of grayscale;
the original version was strictly blank-and-white.  I am not
at all interested in forcing it conform to NeXT interface
guidelines.

Why isn't there a GUI version of mazefind?  Because it's most
useful as a target of rsh.  I suppose it could be run out of
inetd too, but that's bordering on silliness.

Why didn't I use Interface Builder?  I wanted to have readable
source code.  .nib files aren't source code, and I didn't want
the overhead of a __NIB section.  There are a lot of Application
Kit calls relative to the other window systems because this is a
bona fide NeXT application; the others run from shells, and don't
need the panels, menus, built-in help, etc.

Note that the supplied makefile creates NeXT_mazewar.  Use
	cp -p NeXT_mazewar /LocalApps/MazeWar
to install it, and do a Find Applications in the Workspace.

mazefind belongs in /usr/local/bin, and its man page in
/usr/man/man6.  The man page for MazeWar iself is built into the
application.

					Eric P. Scott
					January 1990