Re: Conventions for ;u4; files

[Robert Holmgren holmgren@xxxxxxxx]

** Reply to note from Stephen Shaw  02/12/96 12:13pm -0500

Stephen:

Herewith, information which emanates from someone (Jim Jefferson?) in
Billerica, about two years ago, in response to my query, and which was
posted publicly to the XyQuest BBS. The background was that I had written
an XPL program designed to identify all existing VAriables recognized by
EDITOR.EXE. That program uncovered U5-U9 -- but Help files labeled U5-U9
wouldn't LOAD properly. So I asked what was going on, and this was
XyQuest's response. (I should note parenthetically that I'm incensed by
the implication, mooted here recently, that Tech Support isn't responsive;
in my experience, they're meticulous and willing to go the extra time &
distance to find detailed, even obscure, answers -- this is a clear example
of that liberality.)

Note that, notwithstanding the statement below that U1 "is designed for the
incorporation of user's routines", and despite a general willingness to
accept the conventions that XyQuest dictates (we have no choice, in fact),
there was hesitancy among outsiders (like myself) to adopt this particular
standard because 1) XyQuest had never previously enunciated it, 2) "You
Too" had been informally embraced and a lot of programming done
specifically for it by public and private programmers, 3) conversion from
U2 to U1 would yield no performance gain, and 4) the reserved purpose of U2
(Command Override) is Not Recommended in public programming, which frees U2
for other uses.  FYI...

*********************************

Here is some additional information with regard to the use of the loadable
"U" files:

Under XyWrite 4.0 for DOS, "U" files 1 - 4 are accessible by the user of
the program. There has been some confusion regarding the use of such
files, basically because documentation is insufficient. Each of the "U"
files was designed, although not exclusively, for a purpose. The U1 file is
designed for the incorporation of user's routines.

The U2 file was designed for Command Override, although it can also be used
in a manner such as the U1 file. The Command Override feature, however, can
only be configured in the U2 file. This feature is outlined on pages 1-3 of
the Customization Guide.

The U3 file was designed with the forethought of the XyWrite for Windows
product; specifically, the buttons and Format Bar. It can also be used for
user's routines as well. U5 through U9 files were added to the Windows
product as reserved for use by developers for other products being
developed.

The U4 file was designed to contain the help system for Ibib for XyWrite.
It can be used for user's routine's as well. If Ibid is present, it is
recommended to use U4 only for Ibid.

*********************************



-----------
Robert Holmgren
holmgren@xxxxxxxx
-----------