HP OpenVMS Systems Documentation

V1.2

The WRITE$FONTS logical name references an initialization file used to provide font definitions to the CDA Viewer.

The default location for the WRITE$FONTS.INI file is SYS$LIBRARY, but, if the logical name WRITE$FONTS is defined, the CDA Viewer 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:

This section describes features that pertain to the Clock application.

4.4.3.1 DECsound Alarm Capability

V1.2

The Clock application includes an alarm feature that can be used if your system 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).

4.4.4 DECterm

V1.2--3

The latest version of the Window Manager (MWM) supports overlays and utilizes additional planes of memory, which are available on some 3D graphics accelerators. The Window Manager places borders and banners for all the windows into these extra planes of memory and thereby reduces the number of expose events for your applications that use overlays.

You may need to modify your existing applications that use overlays to avoid potential problems with the colormap. Compaq recommends that you set up your system to share the overlay colormap with the Window Manager, as the hardware supports only one colormap for the overlay planes.

See the associated documentation for your 3D graphic accelerator to determine if overlays are supported.

Setting Up the Overlay Colormap

To modify your applications to share the overlay colormap with the Window Manager, query the server property name SERVER_OVERLAY_COLORMAPS. When you make the query, the server returns the 32-bit value for the overlay Colormap ID.

To set up your system to share the overlay colormap with the Window Manager, edit the files SYS$COMMON:[VUE$LIBRARY.SYSTEM]VUE$MWM.COM and SYS$COMMON:[SYSMGR]DECW$MWM.COM. Change the following line in each file:

 $ mwm -multiscreen

Edit this line by adding the -Overlay command-line option as follows:

 $ mwm -multiscreen "-Overlay"

Note that if you create and install your own colormap, the following problems can result:

• Colors flash on the screen when the colormap is changed.
• Border and banner colors also change when you change the colors of your colormap.

Restrictions

The following restrictions apply when you enable the Window Manager to use overlays:

• The Window Manager supports only single-screen systems and does not function correctly with multiple graphics devices (multihead).
• If you select a Matte Size value other than "None" from the Window Manager options list, the Matte color may not be correct; that is, the color does not match the selection and is occasionally transparent.
• If you select "Show feedback when moving or resizing windows" from the Workspace Options menu, the window with the feedback information causes expose events.

• When you move windows by showing the outline of the window, the outline appears to go below the window borders and banners.
• Window borders are occasionally and randomly displayed in clear or black. If this problem occurs, select the restart option from the Workspace menu to restart the Window Manager.

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 for OpenVMS Version 1.2--4, DECterm chooses its default fonts by pixel size. The following table shows the two behaviors.

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--3

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

4.4.4.4 ReGIS Input Cursors and Escape Sequences

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 6.5.3.1, ReGIS Input Cursors for additional information about escape sequences in DECwindows Motif software. See HP DECwindows Motif for HP OpenVMS Alpha Release Notes for details and restrictions on the use of these sequences.

4.4.4.5 Support for Local Echo Mode

V1.2

DECterm supports a local echo mode. In the Options/General dialog box, select Local Echo, which causes all character sequences generated locally to be echoed on the display and passed to the remote host. This feature is useful when connected to a host that does not echo typed characters.

4.4.4.6 Answerback Message Support

V1.2

A user interface is available to enter answerback messages. This answerback message field is for compatibility with Compaq terminals.

The answerback field is a buffer that contains up to thirty characters. The answerback field in earlier Compaq terminals contained a message used to identify itself to the host system. For DECterm windows, the answerback field can be used to store a sequence of characters that you can use for any repetitive purpose.

A field is provided in the Options/General dialog box to enter answerback text. Click on the answerback field and enter your text. To enter control characters, encode the control character as a two-digit hex ASCII code, preceded by a number sign (#).

For example, when you enter #0D in the answerback field, DECterm responds with a carriage return.

If two consecutive number sign characters are entered (##), a single number sign is transmitted.

If anything other than a valid two-digit hex code or another number sign is detected after an initial number sign, the number sign is treated as a normal text character. Refer to any ASCII table for a complete list of characters.

The answerback text can also be concealed. When the Conceal Answerback button is enabled, the answerback message is concealed. To deselect the Conceal Answerback button, click on the answerback text field, which erases the previous answerback message.

4.4.4.7 Seven-Bit Printer Support

V1.2

When the 7-Bit Printer button is selected in the Options/Printer dialog box, DECterm modifies printed text to be compatible with printers that do not support 8-bit characters. This includes modifying control sequence introducer (CSI) strings to use the format Escape-Left Bracket rather than the single 8-bit CSI character.

When the 8-Bit Printer button is selected, DECterm allows the use of 8-bit characters when printing. This mode can cause problems for older printers if they can not interpret 8-bit characters.

The default is 8-Bit.

4.4.4.8 Automatic Window Positioning

V1.1

A resource has been defined to manage repositioning a DECterm window when a resize operation forces part of the window off the screen. If a DECterm window is enlarged by using the Options/Window dialog box or by entering a SET TERMINAL/PAGE=nn or SET TERMINAL/WIDTH=nn command, the controller moves the newly resized DECterm window so that it can be viewed in its entirety. If you prefer DECterm not to move, add the following line to your DECW$TERMINAL_DEFAULT.DAT file:

DECW$TERMINAL.main.terminal.autoAdjustPosition: off

The following sections describe new features related to specific X Window System utilities ported to DECwindows Motif.

4.5.1 Window Dump to Print File (xpr) Utility

V1.2

The Window Dump to Print File utility prints an X Window dump using the xpr program.

The xpr program receives as input a window dump file produced by the Window Dump utility (xwd) and formats it for output on the following printers:

• PostScript
• DIGITAL LN03 or LA100
• IBM PP3812 page printer
• HP LaserJet (or other PCL printers)
• HP PaintJet

To use the xpr program, define xpr as a user-defined command:

$ xpr == "$DECW$UTILS:XPR"

You must specify an input file. The xpr program prints the largest possible representation of the window on the output page. Options allow the user to add headers and trailers, specify margins, adjust the scale and orientation, and append multiple window dumps to a single output file.

Use the following command format:

$ xpr input_file [options...]

Options include:

    -append filename  -noff  -output filename
    -compact
    -device {ln03 | la100 | ps | lw | pp | ljet | pjet | pjetxl}
    -dump
    -gamma correction
    -gray {2 | 3 | 4}
    -height inches  -width inches
    -header string  -trailer string
    -landscape  -portrait
    -left inches  -top inches
    -noposition
    -nosixopt
    -plane n
    -psfig
    -render type
    -report
    -rv
    -scale scale
    -slide
    -split n-pages

Table 4-4 defines the available options.

The program contains the following limitations:

• Support for PostScript output currently cannot use the -append, -noff, or -split options.
• The -compact option is only supported for PostScript output. It compresses white space but not black space, so it is not useful for reverse-video windows.
• For color images, map directly to PostScript image support.

Program limitations with an LN03 printer:

• The current version of xpr can print most X Windows that are not larger than two-thirds of the screen.
  For example, the LN03 prints a large Emacs window, but fails when trying to print the entire screen.
• The LN03 has memory limitations that cause it to incorrectly print large or complex windows. The two most common errors encountered are "band too complex" and "page memory exceeded" and are described as follows:
  • "band too complex"
    A window may have a particular six pixel row that contains too many changes (from black to white to black). This causes the printer to drop part of the line and possibly drop parts of the page. The printer flashes the number "1" on its front panel when this problem occurs. A possible solution to this problem is to increase the scale of the picture or to split the picture onto two or more pages.
  • "page memory exceeded"
    This occurs if the picture contains too much black space, or if the picture contains complex half-tones, such as the background color of a display. When this problem occurs, the printer automatically splits the picture onto two or more pages. The number "5" may flash on its front panel. As a possible solution to the problem, it might be necessary to either cut and paste or to rework the application to produce a less complex picture.

Program limitations with a LA100 printer:

• The picture is always printed in portrait mode.
• The scale is ignored.
• The scale factor will be different in the horizontal and vertical directions.

Program limitations with an HP printer:

• If the -density option is not specified, 300 dots-per-inch (dpi) is assumed for the ljet device and 90-dpi for the pjet device. The LaserJet printer supports 300-, 150-, 100-, and 75-dpi. Consult the operator's manual to determine the densities supported by other printers.
• If the -scale option is not specified, the image is expanded to fit the printable page area.
• The default printable page area is 8x10.5 inches. Other paper sizes can be accommodated using the -height and -width options.
• Note that a 1024x768 image fits the default printable area when processed at 100-dpi with scale=1; the same image can also be printed using 300-dpi with scale=3, but it requires more data to be transferred to the printer.
• The xpr program may be tailored for use with monochrome PCL printers other than the LaserJet. To print on a ThinkJet (HP 2225A) printer, invoke xpr as follows:

  xpr -density 96 -width 6.667 filename

  To print black-and-white output on a PaintJet printer, invoke xpr as follows:

  xpr -density 180 filename

• The monochrome intensity of a pixel is computed as 0.30*R + 0.59*G + 0.11*B. If the computed intensity of a pixel is less than the -cutoff level, it prints white. This maps light-on-dark display images to black-on-white hard copy. The default cutoff intensity is 50% of full brightness. For example, specifying -cutoff 87.5 means that a pixel will be displayed as black if the computed intensity is less than 85% of full brightness.
• A LaserJet printer must be configured with sufficient memory to print the image. To print a full page at 300-dpi, approximately 2 MB of printer memory is required.
• Color images are produced on the PaintJet printer at 90-dpi. The PaintJet is limited to 16 colors from its 330 color palette on each horizontal print line. The xpr program issues a warning message if more than 16 colors are encountered on a line. Xpr programs the PaintJet for the first 16 colors encountered on each line and uses the nearest matching programmed value for other colors on the line.
• Specifying the -rv option on the PaintJet printer causes black and white to be interchanged on the output image. No other colors are changed.
• Multiplane images must be recorded by xwd in ZPixmap format. Single-plane (monochrome) images may be in either XYPixmap or ZPixmap format.
• Some PCL printers do not recognize image positioning commands. Output for these printers is not centered on the page, and header and trailer strings may not appear where expected.
• The -gamma and -render options are supported only on the PaintJet XL printers.
• The -slide option is not supported on LaserJet printers.
• The -split option is not supported on HP printers.
• The -gray option is not supported on HP or IBM printers.