home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Current Shareware 1994 January
/
SHAR194.ISO
/
drawing
/
air20.zip
/
CHANGES.DOC
< prev
next >
Wrap
Text File
|
1993-11-02
|
5KB
|
95 lines
Changes to AIR since 1.0
Changes are listed as I did them, and are basically notes. If you are
already familiar with AIR, reading this is probably all you need to do.
Who reads DOC's anyway ?????
Version: 2.0
------------------
0. Added a couple more screens, total in program now 9.
1. The screen file name and the RIP file name can now be up to
40 characters in length. This applies to command line modes,
and interactive mode.
2. You can now specify a directory to change to when starting AIR
just type AIR <directory>, AIR will change to the specified directory
and put you in interactive mode.
If an invalid directory is given, you will be taken into interactive
mode in the current directory, unless other errors were made.
3. Pressing F1 while in the Name field, presents a file list that allows
you to move through the directories, to find the file you wish.
As you change directories, the new directory will display just below
the pick list.
Upon selecting the file of choice, you will be returned to the working
directory before editing is continued.
In other words, the new RIP file is always created in the directory
you are "working" in. If you start in \BBS\SCREENS\, but specifiy
another directory, as in AIR \ansi, the file will be created in \ansi.
Else the file will be created in the current directory, if you started
AIR with 'AIR' alone. - See the manual!
4. When in the Sysop Message field, pressing F1 will display a list
of pre-defined messages that you create. It looks for a file named
MESSAGES.AIR, and if found will read in up to 20 lines. You select the
line you wish and press ENTER or click with left mouse button.
MESSAGES.AIR is a simple ascii text file you create. See the included
copy for instructions. It should be stored in a PATH directory, so it
can be found from anywhere.
If you wish to include BBS variables in these lines, you may do so,
they will be properly displayed in the Frame's message area. Keep in
mind that the variable will expand, so be sure there is enough room.
Currently the data entry code used in AIR does not accept the Ctl
characters, this will possibly be modified soon. For the time being,
codes must be placed in the MESSAGES.AIR file.
If you leave the Message field blank, the program's default message will
be placed in the RIP frame.
5. Same list has been created for the RIP name field. The file is called
RIPNAMES.AIR, and follows the same format, but entries are limited to
40 characters in length. There is no default for this field, if you
don't choose from the list, you need to type in a name, you cannot
leave until a name has been entered.
You can store up to 20 RIP file names in this list.
The list must be in a path directory, or the current, for AIR to find
it.
If you select a name from the list that contains no directory path, or
enter a name only, no directory, in the field, AIR will add the name of
the "Work" directory (changed to via AIR <dirname> or the current
directory (AIR no parameters). - See Manual!
6. Upon Exit, whether normal or due to an error, AIR returns to the
directory that was active when the program was invoked.
7. AIR now displays a message, F1: List, just above the Help line, when you
are in any field that has a lookup list.
8. AIR now prompts, in interactive mode, if you would like to do another
screen. (Y)es will return to the editing fields, (N)o, or any other key
will exit the program. Pressing ENTER will select (Y)es....
9. Adjusted the template number field to accept two digits, allowing for
future two digit template numbers. (Thinking Big!!)
10. Stretched the message length to 65 characters. This may be tight for
a couple of screens, you will just have to test...
Also now allows up to 20 message lines to be picked from.
11. Corrected Host Command for Exit Button in template #6 for RemoteAccess.
12. Jon Kent has supplied a new version of FlatView, this one supports
Ansi, so you can view a more representative version of what your
callers will see, it's not perfect, but damn close! The character files
are inluded in the EXE, so extended fonts will show properly without
having the individual CHR files laying around.
Read WHATSUP.DOC for upcomming attractions!