home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Professional
/
OS2PRO194.ISO
/
os2
/
editor
/
boxer
/
history.60a
< prev
Wrap
Text File
|
1994-02-04
|
2KB
|
71 lines
Several small bugs were found in the initial release of BOXER/OS2, and
have been cured in version 6.0a. While most of the bugs are somewhat
obscure, a few do involve program crashes, so it is recommended that you
upgrade from 6.0 to this new version. Here are the corrections made:
The "-" and "&" characters had been accidentally disallowed in FAT
and HPFS filenames, and are now allowed.
If bright backgrounds have been selected by another program (such as
4OS2), BOXER/OS2 will now recognize and permit these as screen colors.
The Block Total command reported an incorrect result when summing a
column of values.
The -M# option was being improperly processed and resulted in the
activation of Macintosh style (CR-only) line enders.
B2.EXE could not be run from a full screen session on systems with
XGA adapters.
An accidental attempt to compile a program which had no file extension
would cause a crash.
Loading files (on HPFS systems) with long file extensions could cause
a crash.
Printing with the typewriter command, or the Print Registration option
could cause a crash if performed before other operations.
The sort by file size mode of the File Menu was malfunctioning.
The Locate command did not fetch the full file path from the File Menu.
The Locate command could crash on jobs which resulted in the location
of long file paths.
The install program had reversed the sense of the BOXER5 and BOXERCUA
keyboard files.
Searches for asterisks with patterns such as "\*" were mishandled.
Boxer will now complain when invalid option flags are encountered, but
won't abort.
The options.* directive could mis-process option flags when 3-character
extensions were involved.
When closing the second of two windows into the same file, the file
position from the closed window was being used in the remaining window.
Macros which ended with a pop-up window open, or on the message line,
weren't running properly.
Extended keys which were typed-ahead during program startup were often
improperly executed upon entry.
Screen repaint is less "jumpy" after certain undo operations.
Multi-line block comments could be improperly syntax-highlighted, in
some cases.
Page Up on the first screen did not move to start of file.
when -T was used as an extension specific option, the cursor size was
not adjusted
An EPM.KEY file has been added to the release file set.