V1.2

The default value of the automatic shadowing toggle button is set using the Custom.autoShadow resource in the CUSTOM.DAT file as follows:

Custom.autoShadowing: False

The default value is True.

1.7.10 Using the Customizer on Multihead Systems

V1.2

The color customizer affects only applications started on the same screen as the customizer. On multihead systems, you can start a different color customizer for each screen and have a different palette in effect on each screen.

The color customizer can be configured so that it is invoked once and affects all applications regardless of where they are started. This mode is invoked by modifying the Custom.multiScreen resource in the CUSTOM.DAT file as follows:

Custom.multiScreen: True

The default value is False.

1.7.11 Using the XSETROOT_CUST.EXE Demonstration Program

V1.2

The XSETROOT_CUST.EXE demonstration program, created during the customizer build, is a modified version of the MIT utility program xsetroot that is used to set a bitmap on the root window. The XSETROOT_CUST.EXE program uses DXmDynamicScreenBackground and DXmDynamicScreenForeground as the background and foreground colors of the specified bitmap. If your DXMDEFAULTS.DAT file contains entries for these two dynamic colors, then use the customizer to dynamically modify the colors of your bitmap.

For example:

$ XSETROOT_CUST :== "$SYS$LOGIN:XSETROOT_CUST.EXE" $ XSETROOT_CUST -BITMAP your_xbm_file.XBM

1.8 Display PostScript No Longer Supported

V1.2--5

Starting August 1, 1998, Compaq will no longer support Adobe Display PostScript software. Compaq is taking this action because Adobe Systems Incorporated is discontinuing support for Display PostScript. This action only affects the Adobe Display PostScript software, not the applications that make use of the software. For example, Bookreader will continue to be supported for all other types of source files, except Adobe Display PostScript.

However, for customer convenience, Adobe Display PostScript software will be supplied on an "as is" unsupported basis. Compaq disclaims all warranties made with regard to Adobe Display PostScript software, including all implied warranties of merchantability and fitness.

1.9 DECwindows Motif Application Notes

This section contains information about DECwindows Motif applications.

1.9.1 Bookreader

This section includes problems, restrictions, and enhancements in the Bookreader application.

1.9.1.1 Bookreader Printing Improved

V1.2--4

The Bookreader application allows only draft-quality printing for books or topics. However, for this release the Bookreader print function has been improved to eliminate such problems as missing lines and words, figures being overwritten by text, and poor leading of lines.

1.9.1.2 Multiple-Byte Character Limitation

V1.2--4

In order to print documents that contain multi-byte characters (Japanese, Chinese, Korean or Thai), you should use the version of Bookreader that was provided in the DECwindows Motif Version 1.2-3 for OpenVMS language variant products.

1.9.1.3 Including Comment Characters in the DECW$BOOKSHELF File

V1.2--3

If you include a comment character (! or #) in the last line of the DECW$BOOKSHELF file, Bookreader fails with a reserved operand fault. As a workaround, ensure that you do not add comment characters to the last line of the file.

This restriction will be removed in a future version of the product.

1.9.2 Calendar---Year 2000 Support

V1.2--5

Previous versions of DECW$CALENDAR accepted two-digit years in the interchange format and interpreted the year as being in the range 1900--1999. This problem has been corrected by interpreting two-digit years as being in the range 1970--2069.

DECW$CALENDAR always uses a four-digit year when writing in the interchange format. Two-digit years can only arise if interfacing Calendar with other programs.

1.9.3 CDA Run-Time Services

V1.2

This section describes features in the CDA Run-time Services component:

• Pack and Unpack applications are provided. See Section 1.9.4.1
• Performance enhancements for viewing CDA and PostScript documents.
• Dynamic font support is implemented. Future upgrades to installed fonts are usable by the CDA Viewer and the PostScript back end.
• The DECwindows CDA Viewer supports DECfonts Version 1.2.
• CDA support is improved for documents created by DECwrite that contain links to other documents.

You can find additional information about CDA in the following manuals:

• DIGITAL CDA Base Services Reference Manual
  Provides reference material for using the CDA data structures and access routines to create compound document applications, converters, and viewers.
• Technical Overview of the DIGITAL CDA Base Services
  Provides an introduction to CDA, compound document processing concepts, and using the DIGITAL CDA Base Services.

V1.2

As well as supporting a static-table for the fonts supported by the DECfonts Typeface Collection Version 1.2, this version of CDA Run-Time Services includes support for dynamic font lookup. This enables the CDA Viewer and the PostScript back-end converter to use new fonts as they are installed on the system.

Dynamic font support is implemented using the WRITE$FONTS.INI file, which you can maintain using the Font utility provided with either DECwrite or DECpresent. If a document contains a font not found in the static tables, the CDA Viewer or the PostScript back-end converter tries to open the WRITE$FONTS.INI file and search for the font. If the font is not found or if the system does not contain a WRITE$FONTS.INI file, the viewer uses a fallback font.

For further information on the Font utility, see the following documents:

• DECwrite Installation Guide for VMS Systems
• DECpresent Installation Guide for VMS Systems
• DECfonts Typeface Collection and User's Guide for OpenVMS

V1.2

The default location for the WRITE$FONTS.INI file is SYS$LIBRARY, but, if the logical name WRITE$FONTS is defined, the CDA Viewer or the PostScript back end uses the logical name definition to search for the WRITE$FONTS.INI file.

Full path support is included, so any of the following definitions are valid:

WRITE$FONTS Logical Name	Resulting File
Undefined	SYS$LIBRARY:WRITE$FONTS.INI
DISK:[DIRECTORY]	DISK:[DIRECTORY]WRITE$FONTS.INI
SYS$LOGIN:	SYS$LOGIN:WRITE$FONTS.INI
.TMP	SYS$LIBRARY:WRITE$FONTS.TMP
DISK:[DIRECTORY]FILE	DISK:[DIRECTORY]FILE.INI

1.9.3.3 CDA Documents

V1.2

The current version of CDA Run-Time Services includes a performance enhancement that decreases the time it takes to display the first page of a CDA document. Other applications that use the CDA Viewer to view documents (for example, DECwindows Mail) also benefit from this enhancement.

The CDA Viewer enables this performance enhancement feature by default. You can disable the feature as follows:

$ DEFINE CDA_QUICK_FIRST_PAGE FALSE

The CDA Viewer might not display some documents correctly when this feature is enabled. If you encounter such a problem, disable the feature and invoke the CDA Viewer again. If the problem persists, please submit a Software Performance Report along with a copy of the document (and any associated documents). The CDA Pack application (see Section 1.9.4.1) allows you to create a single file that includes a .DDIF or .DTIF document and its associated files.

1.9.4 CDA---Additional Applications

V1.2

This section contains information about additional CDA applications.

1.9.4.1 Pack and Unpack Applications

V1.2

CDA Run-Time Services includes two standalone applications that can be used for transferring CDA documents across a network. The CDA Pack application packages a CDA document along with all of its externally referenced files into a single file that can be copied between systems or mailed to other users. The CDA Unpack application reads a file that is packaged by the CDA Pack application and creates a copy of the original document file and all its externally referenced files.

These applications allow you to copy CDA documents between systems without copying externally referenced files separately or correcting external file reference information after copying documents.

To use these applications, add the following lines to your LOGIN.COM file (or add the lines to the SYS$MANAGER:SYLOGIN.COM file):

$ PACK == "$SYS$SYSTEM:CDA$PACK.EXE" $ UNPACK == "$SYS$SYSTEM:CDA$UNPACK.EXE"

These lines enable you to use the symbols PACK and UNPACK to invoke the Pack and Unpack applications, respectively.

1.9.4.2 Pack Application

V1.2

The CDA Pack application creates a single output file that contains the contents of a .DDIF or .DTIF input file. The single output file also includes the files that are referenced by the .DDIF or .DTIF input file.

The format of the PACK command is as follows:

$ PACK input-file-spec output-file-spec

The following sections explain the format of the PACK command.

input-file-spec

Specifies the name of the primary .DDIF or .DTIF input file.

output-file-spec

Specifies the name of the output file that is created by the PACK application. If you do not specify a device or directory, the output file is created in the current default directory.

Qualifiers:

/[NO]SKIP_MISSING

Controls whether the Pack application continues processing if it cannot find one or more of the files that are listed as external references in the input file. The names of any missing files are sent to SYS$ERROR when the Pack application is completed. If you specify /NOSKIP_MISSING, the Pack application does not create an output file if any of the externally referenced files are missing. The default is /SKIP_MISSING.

/[NO]CONTROLLED_COPY

Controls whether the output file includes only those external references that specify COPY_REFERENCE as the value of the ERF_CONTROL item in the input file. If you specify /NOCONTROLLED_COPY, the Pack application includes all referenced files, regardless of the value of the ERF_CONTROL item. The default is /NOCONTROLLED_COPY.

/ALWAYS_ENCODE

Controls whether an output file is created when there are no external references in the input file, or if none of the externally referenced files are found. The default is not to create an output file in these cases. If an output file is not created for these reasons, the Pack application returns the CDA_W_NOOUTFIL status code.

For example:

$ PACK MYFILE.DDIF TEST.PACK

1.9.4.3 Unpack Application

V1.2

The CDA Unpack application unpacks an input file created by the Pack application. The output files are the .DDIF or .DTIF file that is packed by the Pack application, as well as a file for each external reference in the .DDIF or .DTIF file. The Unpack application sends a list of created files to SYS$ERROR.

The format of the UNPACK command is as follows:

$ UNPACK input-file-spec

The following sections explain the format of the UNPACK command.

input-file-spec

Specifies the name of the input file that is created by the Pack application.

Qualifier:

/OUTPUT=output-file-spec

Specifies the file name and location of the files created by the Unpack application.

If you specify an output file name without a directory name, the Unpack application creates the main .DDIF or .DTIF file with the file name you specify in the current default directory. It also creates all externally referenced files in the current default directory.

If you specify a directory name without a file name, the Unpack application creates the main .DDIF or .DTIF file and all externally referenced files in the specified directory. The main .DDIF or .DTIF file has the same name as the file packed by the Pack application.

If you specify a directory name and a file name, the Unpack application creates the main .DDIF or .DTIF file and all the externally referenced files, in the specified directory. The main .DDIF or .DTIF file has the file name you specify.

For example:

$ UNPACK TEST.PACK Output file DISK$:[SMITH]MYFILE.DDIF created. Output file DISK$:[SMITH]FIGURE_1.DDIF created. $ UNPACK TEST.PACK/OUTPUT=[SMITH.UNPACK] Output file DISK$:[SMITH.UNPACK]MYFILE.DDIF created. Output file DISK$:[SMITH.UNPACK]FIGURE_1.DDIF created. $ UNPACK TEST.PACK/OUTPUT=[SMITH.UNPACK]NEW_FILE.DDIF Output file DISK$:[SMITH.UNPACK]MYFILE.DDIF renamed NEW_FILE.DDIF Output file DISK$:[SMITH.UNPACK]FIGURE_1.DDIF created.

1.9.4.4 Pack and Unpack Error Messages

V1.2

This section describes messages associated with the CDA Pack and Unpack applications.

FILESPEC, Missing filespec: file-name

NOOUTFIL, No output file was created.

OUTFILE, Output file created: file-name

This section contains helpful hints, known restrictions, and known problems with the CDA Viewer.

1.9.5.1 Message for CDA Viewer

V1.2

The CDA Viewer issues the following message if it is unable to create the application context:

DRMCTXFAIL, DVR could not create application context, aborting

V1.2

In the CDA Viewer, the name of the Paper Size button in the Open dialog box is changed to Display Options. However, the function invoked by the button is not changed.

1.9.6 Clock---DECsound Capability

V1.2

The Clock application includes an alarm feature that can be used if your system is a TURBOchanel system that supports DECsound. On systems without sound capabilities, you can select only the keyboard bell. When you choose Alarm from the Options menu, a pop-up window appears. This pop-up window allows you to set the alarm time, choose the sound to be played, and indicate an alarm message. To see if your system supports this feature, invoke one of the sounds located in the DECW$EXAMPLES directory (for example, BELLS.AUD).

1.9.7 DECsound Application

This section contains information about DECsound.

1.9.7.1 DECsound Prerequisites

V1.2--3

DECsound is supported only on TURBOchannel systems. TURBOchannel systems that support DECsound include the following:

• DEC 3000 Model 400 series
• DEC 3000 Model 500 series
• DEC 3000 Model 700 series
• DEC 3000 Model 900 series
• VAXstation 4000 Model VLC, 60 and 90

V1.1

The following is a known problem with DECsound:

• The Record operation does not work when you select part of the waveform.
  To correct this problem, do not select any part of the waveform before you click on the Record button.

This section contains information about the DECterm application.

1.9.8.1 New DECterm Default Font Sizes

V1.2--4

In previous releases, the default DECterm font size for the "big" and "little" fonts were chosen by point size. This depended on whether 75 or 100 dpi fonts were installed first in the font path. Starting with DECwindows Motif Version 1.2-4 for OpenVMS, DECterm chooses its default fonts by pixel size. The following table shows the two behaviors.

	Prior Releases			Since Version 1.2--4
Default Font Size (in pixels)	100	751		100	75
Big font	25	18		18	18
Little font	18	14		14	14

In addition, on 100-dpi displays DECterm now uses the big font by default. This results in DECterm using the same font size (18 pixels) on 100-dpi displays as it did in prior releases. On displays that are less than 325 mm wide, DECterm also now uses a bigger default font.

Follow these steps to use the same font as in previous releases (14 pixels):

1. From the Options menu, select the Window... item.
2. Choose Little Font. Click on Apply.
3. If the new default font is too small, click on the Big Font button and change the pixel size in the Other text entry field from 18 to 25.

V1.2--4

In this release, the locale of the display is used to create the file name of the DECterm resource file. For example, if the locale is set to "ja_JP", then the default resource file name becomes DECW$TERMINAL_DEFAULT_JA_JP.DAT.

However, DECterm continues to use the old resource file name until the user selects Save Options at least once in the particular locale. The default resource file name for DECterm continues to be DECW$TERMINAL_DEFAULT.DAT if the locale:

• Is "C"
• Starts with "en_US"
• Contains "8859-1"

V1.2--3

The DECterm application supports all ReGIS input cursors:

• Crosshair
• Diamond
• Rubber-band line
• Rubber-band rectangle

For a shape other than the diamond cursor when n is equal to 1, define the logical name DECW$TERM_REGIS_CURSOR as one of the numbers defined in the SYS$LIBRARY:DECW$CURSOR file.

V1.2

The following escape sequences are supported by DECterm:

• All page movement sequences (NP, PP, PPA, PPB, and PPR).
• One rectangular area operation sequence (DECCRA).
• The DECLFKC sequence.
• The ReGIS command S(C(In)) supports the rubber-band rectangle cursor and the diamond cursor.

See Section 3.15.4, ReGIS Input Cursors for additional information about escape sequences in DECwindows Motif software. See Chapter 3 for details and restrictions on the use of these sequences.

1.9.8.4 Scrolling Through the Keyboard

V1.2--3

You can scroll through the keyboard by pressing the Ctrl key and arrow keys or by pressing the Prev or Next key on the editing keypad.

1.9.8.5 Reporting the DECterm Window Size

V1.2--3

When you enable the Show Feedback option in the Workspace Options dialog box of the Window Manager and you resize a DECterm window, the size of the window is reported in characters instead of pixels.

1.9.8.6 Resizing the Terminal

V1.2--3

If you maximize the DECterm window when you enable the Auto Resize Terminal window option, the window is expanded to its nearest cell boundary; the window does not necessarily occupy the entire screen. The Restore options continue to function appropriately.

1.9.8.7 Timeout for Displaying the Copyright Notice

V1.2--3

If keyboard or mouse activity does not take place for 10 seconds after the copyright notice is displayed on the terminal, the notice disappears from the DECterm screen.