KEDIT for Windows - Changes in Service Level 2

Changes in KEDIT for Windows 1.5 Service Level 2

Here is a list of the changes made to KEDIT for Windows 1.5 in Service Level 2, which was released in January 1997. All of the changes in Service Level 2 are also included in KEDIT for Windows 1.5 Service Level 3. KEDIT for Windows 1.5 was originally released, as KEDIT for Windows 1.5 Service Level 1, in June, 1996.

Enhancements in Service Level 2

KEDIT for Windows 1.5 Service Level 2 was released in January, 1997. Most of the changes since Service Level 1 (the version released in June, 1996) involve bug fixes. There are, however, a few minor enhancements. These enhancements will primarily be of interest to advanced users of KEDIT who are developing their own macros or KEDIT Language Definition files.

The DIALOG and ALERT commands now accept a PASSWORD operand, which causes data entered into the resulting dialog box to be masked, so that potentially sensitive data is not visible on the screen. An example:
```
'DIALOG /Enter your password/ EDITFIELD PASSWORD'
```
The PASSWORD operand is only valid when the EDITFIELD operand is also used, and it must come after the EDITFIELD operand.
.KLD files can now use multi-token keywords in the :MATCH section, with a plus sign joining the components of a multi-token keyword. For example:
```
:MATCH
 do end+do
 if end+if
```
EXTRACT /MACROSEARCH fileid [defaultextension]/
Searches for a file in the same directories KEDIT searches when looking for a macro. Returns the fully qualified name of the resulting file, or the null string if an error is encountered or the file can't be found. If 'fileid' has no extension then 'defaultextension', if specified, is assumed.
EXTRACT /PRINTSIZE/
Returns the number of lines per page, and the number of columns per page, used for print operations, based on the currently selected printer, font, and margins. If KEDIT cannot determine the result, -1 will be returned for the lines and/or columns. -1 will always be returned if PRINTER WINDOWS is not in effect, and can also be returned if, for example, no printers are installed.
EXTRACT /WINDIR/
Returns the fully-qualified name of your Windows directory, and of your Windows system directory.
EXTRACT /TIME/
TIME.5 is new. It returns the date using a 4-digit year, in the format yyyy-mm-dd.
DATECONV() function
When DATECONV() is used to convert a date that is specified using a 2-digit year, it previously assumed that the date fell in the current century. Beginning with KEDIT for Windows 1.5 Service Level 2, it now assumes that the date falls within a 100 year sliding window starting at
```
(current year - 50)
```
and ending at
```
(current year + 49)
```
For example, in 1997, Service Level 2 converts 2-digit years to 4-digit years in the range 1947-2046. So, in 1997, with
```
DATECONV('12/17/02','U', 'N')
```
Service Level 1 yields '16 Dec 1902', but Service Level 2 yields '16 Dec 2002'. As another example, in the year 2000, 2-digit years will be converted by Service Level 2 to 4-digit years in the range 1950-2049.
```
DATECONV('12/17/96','U', 'N')
```
will yield '17 Dec 2096' if earlier versions of KEDIT are used in the year 2000, but with KEDIT for Windows 1.5 Service Level 2 or later will yield '17 Dec 1996'.
DOSDIR() function
Dates returned by the KEXX DOSDIR() function now use 4-digit years in the format mm/dd/yyyy. (This is a change from earlier versions of KEDIT for Windows, in which DOSDIR() returned dates in the format mm/dd/yy.)
Two new KEXX functions, SHORTNAME() and LONGNAME() have been added.
SHORTNAME(fileid) takes the name of an existing file, and returns the short, MS-DOS style, form of the fileid. That is, all components of the fileid are uppercased and are converted to their corresponding short 8.3 format alias.
LONGNAME(fileid) takes the name of an existing file, and returns the long, Windows 95/98/NT/2000/Me/XP style, form of the fileid. That is, all components of the fileid that are 8.3 short format aliases are converted to the correct case and to the long Windows 95/98/NT/2000/Me equivalent.
For example:
```
SHORTNAME('c:\program files\keditw\readme.txt')
```
might yield
```
C:\PROGRA~1\KEDITW\README.TXT
```
while
```
LONGNAME('c:\progra~1\keditw\alongn~1')
```
might yield
```
C:\Program Files\keditw\a long name
```
In the 16-bit version of KEDIT for Windows, for both SHORTNAME() and LONGNAME(), the fileid of an existing file is returned unchanged.
In both the 16- and 32-bit versions, if the fileid involved does not exist, both SHORTNAME() and LONGNAME() return the null string.

Bug fixes in KEDIT for Windows 1.5 Service Level 2

Here is a list of problems encountered in KEDIT for Windows 1.5 Service Level 1 (released in June 1996) that are fixed in Service Level 2. Most of the problems are fairly obscure and have affected only a small number of KEDIT users.

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

Syntax coloring for HTML files treated '<!' as the start of a comment, but should use '<!--'. This caused incorrect coloring of files that use !DOCTYPE specifications.
'KEDIT *.* SOME.FIL' (KEDIT command using wildcard specification and then additional files), with enough files matched by the wildcard specification to hit the limit of files allowed in the ring, could crash KEDIT.
With CMDLINE OFF, built-in macros handling button clicks and double-clicks got an error. To adjust for this CMDLINE.2 now returns 0 as it did in earlier versions of KEDIT, when there are no files in the ring.
Fix incorrect error handling for input to macro debugger beginning with invalid token.
KEDIT could crash if a very small font size, yielding a window more than 200 characters wide or containing more than 32000 characters, was selected.
The NOINI option was allowed (and ignored) if issued from the KEDIT command line; it now yields an error message.
KEDIT could crash if a user-defined KLD file used the CLASS line within a :POSTCOMPARE section and the CMATCH command was then issued.
Operands to SET PATH and SET MACROPATH were improperly limited to approximately 80 characters in the 16-bit version and 260 characters in the 32-bit version.
A 'KEDIT' command that specified a file already in the ring and that used the LINE option to specify an excluded line could crash KEDIT.
If a 'WIN CLOSE FRAME' command is issued from a PROFILE macro, a KEDIT.RPT file could be created when KEDIT exited.
CHDIR, CHDRIVE, ERASE, and RENAME were unnecessarily disallowed when there were no files in the ring.
The meter displayed on the status line when reading in large files gave incorrect results (saying 'Writing' and always indicating 0% complete) when reading in a file that is open for write access by some other application.
If the status line was off and was then turned on, it could incorrectly display help information for the last menu item selected, rather than information about your location within the current file.
KEDIT was using Helvetica font to display some text; this font is obsolete and is normally mapped by Windows to the MS Sans Serif font. KEDIT now uses MS Sans Serif directly.
The box around the current line was sometimes not properly updated after a READV CMDLINE command.
The KEXX ITERATE instruction improperly caused an 'unexpected END encountered' if used within a loop with a DO WHILE or DO UNTIL condition involving a function call.
The UNDO command, if issued from Input Mode with INPUTMODE FULL in effect, could sometimes crash KEDIT.
With 'DIRFORMAT n 0' in effect, the case sensitivity of sorting of filenames in DIR.DIR files was incorrectly controlled by the third operand of SET CASE, but should be controlled by the second operand.
Regular expression searches involving a minimal closure operator that must be matched at the end of a line could improperly miss matching occurrences.

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

The KEXX DOSDIR() function was ignoring files with the read-only attribute bit set.
KEDIT command with wildcard characters (for example, 'KEDIT *.C') was ignoring files with the read-only attribute bit set.
KEXX DOSDIR() function with no arguments, issued when no directory search was active, could crash KEDIT.
Marking a stream block extending to the beginning of a line, and then attempting to move the stream block to the beginning of the same line, could crash KEDIT.
A macro that was assigned to a key and that called an undefined function could crash KEDIT.
An invalid 4 or 5 character prefix area command could crash KEDIT.
KEDIT could crash if a PARSE instruction uses a very large number of tokens in its template.
KEDIT could crash if the Options Status dialog box is used and its List Non-Default Settings Only box is checked, but all settings have their default values.
KEDIT could crash if LINEND ON is in effect and a LINEND character separates multiple commands on the command line, one of which removes the last file from the ring.
KEDIT command specifying complete fileid of a file already in the ring was doing unnecessary disk I/O.
DIR command such as 'DIR =.KEX', using '=' as a file component, could crash KEDIT.
KEDIT should accept the START and STOP operands of the DEBUG command in mixed case, but was incorrectly requiring them to be in lowercase.
In rare circumstances under Windows 95, usually when scrolling rapidly a line at a time via the scroll bar, a second cursor could temporarily appear on the screen.