
Thank you for purchasing SpeedEdit.  We beleive that you will
find SpeedEdit a valuable tool in your daily work which will serve
to save time and energy. We have taken every care to assure that
this product is well tested and free from bugs, but as any
software professional can attest bugs always slip through even the
most rigorous testing.	If you encounter problems, please let us
know and we will do our best to correct them in a timely fashion.
We suggest that you read this readme file now and also after you have
had a chance to use SpeedEdit for a couple of days since it will be
more meaningful then.

Release notes: SpeedEdit Version A.05

The following is a list of known problems and differences:

...................................................................

When a BACKUPDIR is defined, SpeedEdit will no longer change the
extension on the backup copy of your file to BAK.  The file name
in the backup directory will be the same as that of the original
file.  The BACKUPDIR can be set via the command SET BACKUPDIR.

...................................................................

A new feature has been added to the Remote Program
Development facility which is not in the manual.  When the
REMOTE (SET REMOTE) option is on, SpeedEdit will attempt to
execute a procedure named rclose.xeq each time a file is
closed for editing. This procedure allows you to impliment
your own wrap up procedure to possibly delete a downloaded
file or add it to a source code control facility.

...................................................................

An additional SpeedEdit replacement field has been added
since the documentation went to press.	The variable EXISTS
test for the existence of a file, returning either TRUE or
FALSE.	The variable is used as follows:

    IF [EXISTS(myfile)]=TRUE
    purge myfile
    ENDIF

...................................................................

The SpeedEdit manual does not clearly point out that in order to
change the SpeedEdit/Windows menus by altering MENU02.WIN you
must include a "UMENU MENU02.WIN" command in your EDIT.INI file.
Additionally, if you have set SAA mode on, SpeedEdit uses the file
MENU03.WIN and you do not have to include the UMENU MENU03.WIN
file while the SAA mode is ON.

...................................................................

A change has been made to the use of the f5 & f6 keys (SET START
& SET STOP) while using the SAA - GUI mode of operation.  When
either of these keys are pressed, you will be taken out of what
SpeedEdit refers to as partial mode and placed in line mode.
This was done since the f5 and f6 keys require that the cursor be
positioned at the point to start or stop a range and this is in
direct conflict with the SAA mode of operation.  Line mode
essentially turns off a portion of the SAA mode and thus is no
longer a problem.  Under SAA operation the range is selected
using the SHIFT key and the ARROW keys.  To this end, if you wish
to have SpeedEdit behave exactly like other windows application,
where there is no such thing as line mode, you may wish to
permanently redefine the f5 and f6 keys to some other purpose by
including and entry in your EDIT.INI file (see page 222 of the
SpeedEdit reference).

As an aside to this.  There is a known problem of not being able
to select a single character in column 1 at the end of a range.
This will be corrected in the next release.

...................................................................

The slide command while operating in SAA mode requires that the user
position the cursor to indicate where the slide is supposed to open
or close space.  Since the cursor and the range are one, this becomes
difficult while in "partial mode" and thus it is recommended that
you disable partial mode while using the slide command.  This can
be done by using the right mouse button to select the range or by
clicking on the Edit Menu Item PARTIAL to ensure that it is not checked.

...................................................................

Some confusion has arisen concerning the use of SAA mode.  When SAA mode
is turned on, settings for WINKEYS, MOUSE KEY SWAP, CURSOR SAME AS RANGE,
INSERT MODE, PARTIAL MODE, and the USER MENU are automatically set
each time SpeedEdit is started, even if you had changed them while
editing in the previous session.  If you wish to override any one of these
settings and still have SAA mode ON, you must add one or more of the following
commands to your EDIT.INI file.

    SET WINKEYS ON/OFF
    SET MOUSESWAP OFF
    CINSERT OFF
    SET PARTIAL OFF
    SET OPTIONS COFF
    UMENU menuname

...................................................................

In order to avoid confusion when dealing with data files which
contain numbers as opposed to numbered source files, we have added
the options SET OPTIONS NON and SET OPTIONS NOFF.  When OPTIONS
NON is in effect, SpeedEdit examines the first few lines of text
in each file to try to determine if line numbers are present, and
if so turn NUMBERING on.  When OPTIONS NOFF is in effect, this
checking is not done and numbered files will not be detected.  On
all but the MPE versions of SpeedEdit, this flag is OFF by default
since numbered files are the exception rather than the rule in
most cases.

Two new options have been added to SpeedEdit to allow you to control if
and when SpeedEdit attempts to detect a Unix file and also, when to
attempt to save a file as a Unix file (as opposed to a DOS file).

  SET OPTIONS UON      Tells speededit to check for Unix files.  Unless
		       you are often dealing with Unix files, you should
		       should leave SET OPTIONS UOFF.

  SET OPTIONS UOFF     Tells SpeedEdit not to check for unix files and when
		       this is set you will loose the last character of each
		       line when a unix file is encountered.  This is the
		       default.

  SET OPTIONS USAVE    Tells SpeedEdit to always save files flagged as Unix
		       files as Unix files.  If this flag is not set,
		       SpeedEdit will save all files (Unix or DOS) as DOS
		       files.  (The difference between a DOS and a Unix
		       file is that DOS fileshave lines which end in
		       carriage return line feed, where Unix files have
		       lines which end in just a line feed.  SET OPTIONS
		       USAVE OFF diables this feature.  Files that start out
		       as DOS files will always be saved as DOS files.

...................................................................

We have modified the keyboard macro record mode so that it auto-
matically shuts off if you perform a search (FIND) and no string is
found and a warning message similar to "string not found" is
displayed. We did this since the macro would be unpredictable depending
on if the striong was found or not, and the find is usually the last
step in a macro anyway.

...................................................................

An addition has been made to the BOX command that is not in the manual.  If
you enter the command

    BOX ~

SpeedEdit will draw a box using the PC line drawing character set.  If you attempt
to print this box, make sure your printer is set to use a font which support
the PC line drawing characters.  If the box on your screen looks like a bunch
of gibberish (special characters) this means you need to select a display font which
supports the PC line drawing characters (TERMINAL).

...................................................................

The manual does not state that there is a way to remap the Previous Word
and Next Word key actions. An extension to the DISPLAY command allows you to
perform prev & next word operations and thus this may be bound to alternate
keystrokes as needed.  To make the control X sequence a next word
operation, the command would be:

    SET MAP CTL X "DISPLAY NEXTWORD"

Notice the use of quotes, since this command requires two words.

........................................................................

It has come to our attention that the documentation does not point out how to
run a Windows application from SpeedEdit.  Where typing any DOS command causes
SpeedEdit to pass the command on to the DOS shell, this won't work for a Windows
application since the shell can't launch a Windows application.  Use the RUN
command which can launch a Windows application.

    run notepad.exe


................................................................................

A.05.000:000

................................................................................

There are several new features and functions in release A.05 which are documented
in the release notes which came with your update from A.04 or with a new purchase
of A.05.  Please review this document.

................................................................................

In this version and future versions, the use of the /R option indicating
remote files names will be replaced with ,R.  The /R will still work on DOS
based SpeedEdit as documented but users should start using ,R for
consistency.  We found that /R under UNIX is unusable since the Unix file
names include the / as part of the path.  MPE uses the slash to indicate a
password.

........................................................................

Running SpeedEdit with Reflection 3.7 and later:

Add the following to your EDIT.INI file:

   EMULATOR=R1WIN
   R1DIR=C:\R1WIN

Use the Options/Setup SpeedEdit menu item to select the Reflection entry in the one line
list box at the bottom of the dialog box on the left.  Make sure the item "Reflection"
is selected.  Tab to the box to the right of this and enter "r1win".  Select
the OK pushbutton at the bottom of the dialog.

You should now be configured for remote development with Reflection 3.7 or better.

........................................................................

A problem existed in A.05.000:000 which caused pages to not be ejected on
some printers, causing overprinting of one page on top of another.  This has
been corrected as of A.05.001:000.

Another note.  Even though SpeedEdit checks the printer page length as known
by windows, this is not always accurate due to settings that may be made on
the printer itself or clipping regions on laser printers.  When first printing
using SpeedEdit, check to make sure that all the end of page one and the top
of page two are consecutive lines.  If this is not true, reduce the page length
by setting the PAGELEN setting in SpeedEdit

  SET PAGELEN 60

........................................................................

Editing COBOL code:

There are three basic flavors of COBOL source files.  Those with sequence numbers
in columns 1-6, those with blanks in 1-6, and those that assume that
the first column in the file is really column 6 (in other words the
blanks have been removed).

SpeedEdit can handle all three conditions.

If you want SpeedEdit to detect and manage line numbers in your
COBOL code, SET OPTIONS NON, otherwise SET OPTIONS NOFF and SpeedEdit
will leave the sequence numbers alone, treating them as ordinary
text.

If you are dealing with files that have blanks in columns 1-6 and
wish to have SpeedEdit detect and maintain these blanks for you,
set the variable COBOLBLANKS as a command:

	cobolblanks=on

If you do not want SpeedEdit to tamper with the blanks, either
do not set a cobolblanks variable or set it to off
(cobolblanks=off).  To see how your variable(s) is/are set, enter
the command:

	DISPLAY VARS

When cobolblanks=on, SpeedEdit will strip off the first 6 leading
blanks and make column 1 on the screen column 7 in your file.
When you save the file, SpeedEdit will insert the blanks
appropriately. With cobolblanks=off, it is your responsibility to
maintain the blanks.  For cobolblanks=on to work, you must also have
SET OPTIONS NON.

Files that do not have numbers or blanks in columns 1-6 will be editable
as cobol source files and will not insert blanks or line numbers
in columns 1-6 unless you open the file and:

	SET NUMBERS ON

or

	SET ALL
	type Control-B (or press the Home key)
	SLIDE 6

SET NUMBERS ON will number your file, where the second example
will just insert spaces.

........................................................................

A change has been made how SpeedEdit deals with user created compiler
entries.  In the past (prior to A.05:008:014) SpeedEdit used the
compiler on which the new compiler was based to "know" how to
deal with comments, ignoring any comment information provided
in the "compilers" file.  Now SpeedEdit will require that the compiler
file define how comments are to be handled.  This allows one to get
the indentation and personality of C while using a different style
for comments.

........................................................................
Win32
When running under the WindowsNT July beta, starting SpeedEdit (or
I imagine any other application) will pass SpeedEdit the name "wowexec.exe"
as the first parameter which indicates to SpeedEdit to edit "wowexec.exe".
SpeedEdit will inform you that you can't edit that kind of file and
terminate.  You can work around that problem by including the name
of a file like "untitled" on the command line, which eliminates this
behavior.

        c:\speedit\speedit untitled

........................................................................
Win32
Also when using the July NT beta attempting to set colors by using
the color boxes doesn't work, always yeilding black instead of the
desired color.	Use the red, green, blue scroll bars to mix your
colors instead.

........................................................................
Win32
Running programs from SpeedEdit using the July beta also does not
work.  Of course the Win32 version of SpeedEdit will resolve this
and the other issues and that is anticipated shortly.

........................................................................
Win32
We have enhanced the file RWORD010, which is the file used to define
reserved words for a language, so that it will cause most of the procedure
names and messages flagged by Microsoft as needing adjustment for
WIN32.	These words will show up in the same color as that defined
for CHANGED text, normally magenta by default.

........................................................................
Win
By popular demand we have added an item to the GUI preferences dialog
which allows you to select if you wish to see text scrolled when the slider
is moved or not.  The default condition is OFF.  The command to set
this is:

        SET SCROLLING SHOW ON
        SET SCROLLING SHOW OFF

........................................................................
Win
A problem was detected with unreleased memory usage where after having
selected numerous items from menus the menus would eventually stop working.
This has been corrected.

........................................................................
All
The compiler comments for languages such as Fortran were being handled
incorrectly.  This has been corrected.

........................................................................
Win31 / Workstation for Windows
SpeedEdit has been tested with Microsofts Workstation for Windows
product and appears to have no problems in this environment.

........................................................................
Win
An annoying "feature" of release A.05 was the attempt by SpeedEdit
to reformat comments as word wrapped text.  While this is fine for
actual comments, it is quite undesireable for commented out code.
This being the case, this function has been removed.

........................................................................
Win/32

In the beta version of SpeedEdit/NT (as well as the released version when it
ships) the use of the "compiler" file has been eliminated and replaced with
individual files which are associated with each compile type.  The files are
named compdef.XXX, where XXX is the extension of the file being edited.  The
compdef file for the C language is:

Name: C                                       COMPDEF.C
Number: 10
StartComment: /*
StopComment: */
CommentCol: 0
AltComment: 
CheckFile: ccmds.cmp
BasedOn: 0
Extensions: .c .h .dlg .rc

The words on the left are key words which SpeedEdit uses to identify each item
in the compdef file.  The file works as follows:

Name:    The name of the compiler as it is shown in the banner line.  Far to
         the right is the name of the compdef file.

Number:  This must be a unique number not used in any other compdef file, normally
         between 1 and 100 byt can be any positive integer.

StartComment:  The special symbol(s) used to identify the start of a comment
               for the language being defined.


StopComment:   If the language being defined requires some sort of closing characters
               to signify the end of a comment they are specified here.

CommentCol:    If the language being defined requires that a given column be
               used to indicate a comment (Fortran uses column 1, COBOL uses
               column 7) the column number goes here, otherwise this field should
               be 0 or omitted altogether.


AltComment:    If a language has a second method of indicating a comment by
               using special symbols to start the comment, the symbol(s) are
               indicated here.  No closing symbols are allowed and no column
               number is taken into account.  A language such as C++ use // to
               start a free form comment.

CheckFile:     The name of the file which contains the SpeedEdit compile error
               checking macro.  No drive or directory need be specified.


BasedOn:       If this compiler entry is syntactically similar to some other
               language (like C++ is similar to C), follow BasedOn with the
               number of that compiler.

Extensions:    List the valid extensions for this compiler to allow SpeedEdit
               to recognise a file by its extension.  The extensions should
               be separated by spaces and should include the leading period
               (.).

........................................................................
Win/32

There are now user definable "buttons" available in a "toolbar" which will appear
at the top of each SpeedEdit Window.  You can define as many buttons as you
would like, however no attempt will be made to make them fit on the screen so
for all practical purposes, you are limited by the screen width.  Buttons are
defined by including a list of SpeedEdit variable definitions in the EDIT.INI
file.  The definitions require two variables per button, one that describes
the label for the button, the other the command to be executed.  Commands can
be anything you like, SpeedEdit commands or operating system commands.  The
definitions must be of the form:

  _label_f1=Copy
  _button_f1=copy
  _label_f2=Move
  _button_f2=move
  _label_f3=Diff
  _button_f3=run windif.exe

The labels should be kept short since they allow for only four or five characters.
The button commands can be any reasonable length.

........................................................................
Win/32

SpeedEdit/NT has a status bar across the top of each window.  The information
in the various status windows are row and column, file length, current compiler,
and source file name.  The last window (source file name) can be changed to
include other information known to SpeedEdit by setting a variable as follows:

  _source_field=[source] -- [dir]

This examples changes the contents of the window from the source file name to
the source file name followed by the default directory.
........................................................................
Win/32

A popular method of dealing with the mouse under unix's X-Window system is
to define the left mouse button to automatically copy the selected range to
the clipboard as the left mouse button is raised following the range selection.
The middle or right mouse button is define to paste the range and thus clipboard operations
can be invoked without having to use menus, tool bars or the keyboard.  SpeedEdit
A.06 has a method of defining what happens as each mouse button is depressed,
released, and double clicked.  Under the Options/GUI perferences, there are
two push buttons that will allow you to define press/release actions and double
click actions.  There corresponding commands to make such settings are:

  SET BUTTONUP L CLIPCOPY
  SET BUTTONUP R PASTE !
  SET DBLCLICKL UPSHIFT
  SET DBLCLICKR DOWNSHIFT

In the SET BUTTONUP and SET BUTTONDOWN commands, you follow with the letter
of the mouse button to define L=Left, M=Middle, R=Right followed by the command
with spaces between the parts.  Since the DBLCLICKL commands were originally
defined not to follow this rule they were left as is, with DBLCLICKL and DBLCLICKR
being sepearate commands.

Under Window 3.1, you may not use both a double click action and a press/release
action at the same time, since SpeedEdit will perform both the press/release
and the double click which is seldom the desired action.  Under the Windows/NT
version you can define both actions since one of the facilities of the Win32 API
allows us to detect a double click when in order to avoid executing the press/release
action.

The SET BUTTON (press/release) settings are not saved in your default (seconfig)
file and thus should be added to the EDIT.INI file if you want them to be in
effect for every edit session.
