HP OpenVMS Systems Documentation

HP DECwindows Motif for OpenVMS
New Features

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

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.

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

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

This section describes features that pertain to the DECterm application.

2.4.2.1 New 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 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.

2.4.2.3 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 4.2.2.1, ReGIS Input Cursors for additional information about escape sequences in DECwindows Motif software.

2.4.2.4 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

This section describes features that pertain to the Motif Window Manager application.

2.4.3.1 Overlay Support

V1.2--3

The latest version of the Motif 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. HP 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.

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

2.5.1 AccessX Keyboard Utility (accessx)

V1.3

The AccessX Keyboard utility (accessx) is a client application that enables you to set one or more AccessX keyboard enhancements available with the X Keyboard extension (XKB). These enhancements make it easier for users with disabilities to interact with workstation input devices (keyboard and mouse).

Specifically, AccessX enhancements for XKB offer the following capabilities:

• Sticky Keys -- Allows you to perform multikey operations with one hand, one finger, or a mouth stick. You can use this feature to enter certain uppercase letters and punctuation characters without having to hold down the Shift key. This feature also makes it easier to enter control sequences, such as Ctrl/C.
• Mouse Keys (also known as Dead Mouse) -- Lets you map actions that you would perform with a mouse to keys on the numeric keyboard or other keys that you specify. With this feature, you can use one finger or a mouth stick to move the cursor to different areas of the screen, manipulate menus, and select, cut, and paste text.
• Toggle Keys -- Provides audio feedback when the Shift Lock (Caps Lock) key is pressed. This feature helps users who might have difficulty seeing the keyboard light indicator for the Shift Lock key or users who are using a keyboard that does not provide light indicators for any keyboard settings.
• Repeat Keys -- Allows you to adjust the auto-repeat keyboard mechanism speed or to turn it off entirely. With this feature turned on, you can set your keyboard so that holding down a key for a longer than average time does not cause a repeat entry of that character.
• Slow Keys -- Makes the keys less likely to respond when brushed accidentally. With this feature turned on, the computer accepts only keystrokes that are held for a certain length of time. The computer ignores light keystrokes that are held only for a moment.
• Bounce Keys -- Eliminates the problem of pressing a key and then accidentally pressing it again before moving to another key. You can set this feature to tell the computer not to process a second pressing of a key unless a certain length of time elapses between each pressing.
• Time Out -- Shuts off the AccessX features (except for Repeat Keys) on a workstation after a specified period of time. If you are sharing a workstation and have set AccessX features, the settings are turned off automatically before the next use. To retain the AccessX settings at all times, you can turn off the Time Out feature.

The settings for these capabilities are stored as X resource specifications available from an AccessX configuration file. This utility reads the appropriate file (either for the client or server) and adjusts the resource settings depending upon the changes you make.

See Section 2.5.1.1 and Section 2.5.1.2 to learn more about the configuration file and its default values. For information about enabling and using XKB and X Keyboard keymaps, see the HP DECwindows Motif for OpenVMS Management Guide.

To run this utility, define accessx as a foreign command, and copy the UID file to DECW$USER_DEFAULTS:

$ accessx :== "$DECW$EXAMPLES:ACCESSX.EXE"
$ COPY DECW$EXAMPLES:ACCESSX.UID DECW$USER_DEFAULTS:ACCESSX.UID

The command format for accessx is as follows:

$ accessx [-options...]

You can run accessx by entering the command at the DCL prompt, with or without options. The options, described in Table 2-4, allow you to specify which configuration file to load and choose whether to display the status of the editing session. If no options are specified, the client configuration file is loaded by default.

Once invoked, the accessx dialog box is displayed, which lets you select the AccessX features that you want to enable. It also provides a test area that allows you to preview your settings before applying them to a DECwindows Motif session.

For detailed information on the controls and menu options in the dialog box, see the online help available from the Help menu option.

2.5.1.1 The AccessX Configuration File

The AccessX configuration file is an X resource file used to store and load specific AccessX settings for the client. The default client configuration file is located in DECW$USER_DEFAULTS:ACCESSX.DAT and is created the first time you choose Save Settings.

You can choose to edit the file directly or use the accessx utility (with the -client or -server option) to modify the settings. Note that any comments inserted in this file are deleted when you perform a save settings action.

The format for entries in this file follow the standard X resource specification format, which is:

*resource:value

For example:

*BounceKeysToggle.set:False

Since an application can consist of a combination of input widgets (such as, push buttons and a scroll bar), you can use the widget class and name identifiers to create additional resource specifications.

2.5.1.2 Default Resource Settings

Table 2-5 lists the AccessX resources and their default values. These are default settings maintained by the server and also represent the initial settings in the client configuration file, prior to modification.