Changes in KEDIT for Windows 1.5 Service Level 3

Changes affecting both 16- and 32-bit KEDIT for Windows 1.5

• In rare circumstances, KEDIT could crash when an instance of KEDIT was already active, INSTANCE SINGLE was in effect, and a fresh copy of KEDIT was started.
• Invalid data entered into the Edit Goto dialog box could sometimes crash KEDIT.
• KEDIT could sometimes crash when printing files with very long names.
• When two lines were joined together by the JOIN command, trailing blanks in the second line were sometimes being deleted.
• When the current line was overlaid by a KEDIT message, the box normally drawn around the current line was being drawn around the message line.
• Invalid options used with the KEXX DOSDIR() function could sometimes crash KEDIT.
• KEXX I/O functions (LINEIN(), LINEOUT(), etc.) were sometimes improperly handling I/O to LPT1, etc.
• When the command line scrolled to accommodate long command lines, the cursor wasn't being displayed, or was being displayed in the wrong column.
• The cursor could sometimes disappear if KEDIT was used with a mouse that has a mouse wheel and the shareware program FlyWheel was in use.
• Minor updates were made to the list of keywords highlighted by the syntax coloring facility for C/C++, Pascal, xBase, and Java programs.
• Pascal syntax coloring is now also applied by default to .DPK files, which are used with Delphi.
• TAG BLOCK and TAG ALL were previously invalid, but are now allowed.
• EXTRACT /RING/ was previously invalid with no files in the ring, but is now allowed.
• When invoked with a fileid beginning with DIR (for example, the command line KEDITW32 DIR.C) KEDIT was incorrectly executing KEDIT's DIR command, instead of editing the specified file.
• The KEXX debugger was not properly displaying lines of a macro that used variables whose names ended with THEN.
• KEDIT could crash in rare situations when using the JOIN command (Alt+J) in column 1 of syntax-colored files.
• If a KLD file specified paired comment delimiters, but the starting and ending delimiters had different lengths, syntax coloring was incorrect for files that used those comment delimiters.
• SET STATUSLINE OFF, saved in .INI file via Options Save Settings, was not taking effect in future KEDIT sessions.
• Allow selection of simulated fonts, such as Lucida Console Bold, from Options Screen Font dialog.
• EXTRACT /QUICKFIND/ was returning QUICKFIND.4 in uppercase, but should return it in mixed case.
• QUERY STARTUP now includes additional identifying information in its output.
• A macro that used the PURGE command to remove itself from memory could crash KEDIT.
• The command DEFINE =.=, issued with a .KML file as the current file, was being treated as equivalent to DEFINE =.KEX, instead of DEFINE =.KML.
• Character code 255 was not being handled properly by KEDIT's syntax coloring code, and when entered from Cyrillic keyboard.
• PM indicator was incorrectly displayed in time field of status line in countries with 24-hour clock.
• EXTRACT /DIRECTORY/ now returns DIRECTORY.2, with the current directory in mixed case.
• Comma (',') specified alone in a .KLD file :MATCH section was crashing KEDIT.
• KEDIT was checking printer status at startup, but if a networked printer responded very slowly, KEDIT took too long to initialize. KEDIT now waits until the first use of the PRINT command or related dialog boxes to check printer status.
• In rare situations, KEDIT could cause a GPF during regular expression processing.
• Syntax coloring was incorrect for quoted strings within HTML tags if the quoted strings began in column 1.

Changes affecting only the 32-bit version of KEDIT for Windows 1.5

• SET COLOR TOOLTIP no longer has any effect. Instead, tooltips are displayed using the color and font determined through the Windows Control Panel or Display Properties.
• You can now use the wheel on the Microsoft IntelliMouse to scroll forward and backward in your files.
• KEDIT could crash if File Save or File Save As was used, a very long fileid was involved, and an error (such as an unexpected change to the file's timestamp) is encountered.
• KEDIT could crash in rare situations when editing a file with a very long filename, one of whose components ends in a period or contains two periods in a row.
• Workaround for Win 95 bug returning incorrect information about root directory of SUBSTed drive.
• After KEDIT detected an internal error and produced a KEDIT.RPT file, it would sometimes attempt to continue running, but should instead terminate execution.
• DIR command for a fileid with no extension, such as DIR .EXT, was being handled as equivalent to DIR *.EXT, but since .EXT is a valid Win32 fileid, should simply search for the file .EXT.
• KEDIT could crash if FILESEARCH.n() Implied EXTRACT function was used within a macro assigned to a key.
• The module is slightly smaller and faster than the Service Level 1 and 2 modules.
• '=' specified as a fileid component at KEDITW32 startup, or when KEDIT or DIR commands are issued with no files in the ring, should yield an error message but was instead incorrectly treating '=' as '+'.
• The FRAMESIZE option was being ignored under NT 4.0 if KEDITW32 was started from the MS-DOS command prompt.
• The maximum number of ARBCHAR characters that can be used in a target has been increased from 8 to 16.
• When the new name specified for a file via the RENAME command names a file that already exists, KEDIT now gives a better error message.
• When a macro issued a DOSQ command and the user clicked on an inactive KEDIT document window while the DOSQ command was running, KEDIT was incorrectly activating the file in the inactive window.