V1.2--4

On the New Desktop, Style Manager contains a control that displays a dialog box used to select font size. Selecting a new font size affects only New Desktop applications and does not affect existing DECwindows Motif applications.

1.1.18 Default Workspace Limitations

V1.2--4

The New Desktop provides a default backdrop for the four default workspaces. You can change or even select Nobackdrop using the Backdrop control located in Style Manager.

When no backdrop is selected, you cannot drag icons and place them on the backdrop of the desktop. If you drag an icon and release it, it snaps back to File Manager or Application Manager.

Icons that were dropped on the background before Nobackdrop was selected remain and function correctly.

1.1.19 Alt + Space Key Does Not Post the Window Menu

V1.2--4

The New Desktop maps the key binding Alt+space key to the Compose Character function by default. This provides a method for character composition on keyboards which do not supply a specific Compose Character key. To use this feature, follow these steps:

1. Copy CDE$SYSTEM_DEFAULTS:[CONFIG.lang]SYS.DTWMRC to DISK$:[LOGIN.DT]DTWMRC.DAT.
2. In the Keys DtKeyBindings section, uncomment the following line:

   Alt<Key>space icon|window f.post_wmenu

3. Restart the Workspace Manager.

V1.2--5

DECwindows does not include the DECwrite program. However, DECwindows does include the DECwrite icon on the New Desktop. If the DECwrite product has not been installed, clicking on the DECwrite icon results in the following error messages:

> RCV'D (pid 000000CA): %DCL-W-IVVERB, unrecognized command verb - check validity and spelling -> RCV'D (pid 000000CA): \DECWRITE\ -> RCV'D (pid 000000CA): TESTER logged out at 29-JUL-1998 17:56:44.63

If the DECwrite product is installed and you still get this error, ensure that DECwrite is started in SYSTARTUP_VMS.COM.

1.2 DECwindows Support of OpenVMS Extended File Specifications (EFS)

V1.2--5

In general, DECwindows Motif supports the Extended File Specifications (EFS) option provided in OpenVMS Alpha Version 7.2. The interface either supports the new ODS-5 file names or provides an error message indicating that the particular component does not support the new names.

1.2.1 The File Selection Popup

V1.2--5

The standard file selection popup window used by most DECwindows Motif applications fully supports ODS-5 style file names. The window supports deep directories, case preservation, and extended-length file names. The window supports entry of file names using the extended file name character and displays files using the extended file name character set using the circumflex character (^). See the OpenVMS Guide to Extended File Specifications for more specific information about using deep directories and the extended file name character set.

1.2.2 The FileView Application in the Traditional DECwindows Desktop

V1.2--5

With an ODS-5 volume, the FileView application supports deep directories, case preservation, and extended-length file names. FileView supports entry of file names using the extended file name character and displays files using the extended file name character set using the circumflex character (^). See the OpenVMS Guide to Extended File Specifications for more specific information about using deep directories and the extended file name character set.

Any custom FileView command extensions must be modified to support EFS.

1.2.3 The File Manager Application in the New Desktop

V1.2--5

The FileManager application supports case preservation.

The FileManager application creates files with the extended file name character set, but does not support any operations on its files.

The FileManager application supports deep directories and extended-length file names with the following restriction. As indicated in the OpenVMS Guide to Extended File Specifications, ODS-5 volumes allow file names up to 236 8-bit characters in length and deep directory structures if the total file specification does not exceed 512 8-bit characters in length. The current version of the File Manager supports extended-length file names and deep directory structures with the additional restriction that a total file specification cannot exceed 235 8-bit characters in length. Exceeding this limit causes an error message for some menu items.

1.2.3.1 File Manager Problems with EFS (New Desktop Only)

• In File Manager (New Desktop), the "Selected/Move to" menu item does not support case preservation. The files are moved correctly, but case is not preserved.
• The File Manager currently does not support case preservation when you create file names that contain special characters. For example, "Special^&Characters" will be converted to "SPECIAL^&CHARACTERS.;1".
• In File Manager (New Desktop), the "Selected/Copy to" menu item does not support case preservation. The files are copied correctly, but case is not preserved.
• In File Manager (New Desktop), the "Selected/Put in Trash" menu item does not work on ODS-5 volumes marked for EFS (Extended File Specifications). This applies only to folders with extended file names. An error message similar to the following is displayed:

  File Manipulation Error Cannot create "sys$sysroot:[sysmgr.dt.trash]qwertyuiopasdfghjklzxcvbnm- QWERTYUIOPASDFGHJKLZXCVBNM.LONG_NAME;1" The most common cause is that you do not have the correct permissions for the involved files or folders. To view permissions, select the object and then select "Change Permissions..." from the Selected or popup menu.

  
  These files can be deleted at the DCL level.

• In File Manager (New Desktop), dragging a file or folder with an extended file name to Trash causes an error message. On an ODS-2 volume you can drag a file or folder with a short file name to Trash and still be able to restore it. On an ODS-5 volume you can drag a file or folder with a short name to Trash, but you cannot restore even files with short names from an ODS-5 volume. These files can be deleted at the DCL level.
• In File Manager (New Desktop), the "File/New Folder" menu item can handle the creation of a folder when the path length exceeds 255 characters, but the folder cannot be displayed (it is hidden). These files can be viewed at the DCL level.
• In File Manager (New Desktop), the "File/Find/File" menu item cannot find a file with file name that exceeds 235 characters if the full file name has been entered in the dialog's form field. To avoid the problem, use wildcards to conduct the search.
• In File Manager (New Desktop), the "Selected/Change Permissions" menu item does not work on files with file names that exceed 235 characters. Permission cannot be changed on files with long file names.
• In File Manager (New Desktop), the "Selected/Copy to" menu item causes an error with file names that exceed 235 characters. The operation produces an error message instructing the user to change the permission on the file in order to copy it. However, it does not work because permissions cannot be changed on files with long file names.
• In File Manager (New Desktop), the "Selected/Purge" menu item does not work for long file names on ODS-5 volumes marked for EFS (Extended File Specifications). "Short" file names do not present this problem. An error similar to the following is displayed:

  File Manipulation Error Cannot create "sys$sysroot:[sysmgr.dt.trash]qwertyuiopasdfghjklzxcvbnm- QWERTYUIOPASDFGHJKLZXCVBNM.LONG_NAME;1" The most common cause is that you do not have the correct permissions for the involved files or folders. To view permissions, select the object and then select "Change Permissions..." from the Selected or popup menu.

  
  These files with long file names can still be purged at the DCL level.

• In File Manager (New Desktop) the updated protection settings are not displayed when invoking "Fileview/Command/Protection," although the settings have actually been updated. However, the new settings can be verified by either issuing a DCL command or invoking "Fileview/Command/Show File."

V1.2--5

The programming libraries fully support deep directories and extended-length file names. The libraries do not support case preservation or the extended file name character set.

1.2.5 The Translated Image Support (TIS) Library (Alpha Only)

V1.2--5

The translated image support (TIS) library has not been updated to support EFS.

1.3 Alt + Space Key Does Not Post the Window Menu (DECwindows Desktop Only)

V1.2--4

OpenVMS DECwindows Motif maps the key binding Alt+space key to the Compose Character function by default. This provides a method for character composition on keyboards which do not supply a specific Compose Character key. To use this feature, follow these steps:

1. Copy DECW$SYSTEM_DEFAULTS:DECW$MWM_RC.DAT to DECW$USER_DEFAULTS:DECW$MWM_RC.DAT.
2. In the Keys DtKeyBindings section, uncomment the line:

   Alt<Key>space icon|window f.post_wmenu

3. Restart the Window Manager.

V1.2

All DECwindows Motif for OpenVMS applications except Notepad support the drag-and-drop feature. DECwindows Mail supports the drag-and-drop feature in all windows except the main message area, where DECwindows Mail has its own drag-and-drop; you can use MB2 to move messages around with the SVN interface.

The drag-and-drop feature lets you move or copy screen objects; this feature is provided primarily for programmers who choose to incorporate drag-and-drop into their applications. For example, you can move text from a text entry area and paste it elsewhere.

To drag and drop text into a new location:

1. Select the text to be copied or moved with MB1.
2. To move the text, press and hold MB2; to copy the text, press and hold
   Ctrl/MB2.
   A move or copy icon is displayed.
3. Drag the icon to the location where you want to drop the text and release Ctrl/MB2.
   If the object is highlighted as you drag the icon across it, you can drop the text into that location.

V1.2--3

The following applications do not support tear-off menus:

• CDA Viewer
• Notepad
• Print Screen

Refer to Section 4.2.3.2 for instructions on tearing off a menu and closing a tear-off menu.

1.6 Access Control Not Explicitly Enabled by Default

V1.0

DECwindows Motif does not enable access control by default. Instead, the product uses access control set by the server. The DECwindows X11 display server enables access control at startup time.

To force the DECwindows Session Manager to enable or disable access control explicitly at login time, you can define one of the following logical names:

$ DEFINE/SYSTEM/EXECUTIVE DECW$LOGIN_ACCESS_CONTROL ENABLE $ DEFINE/SYSTEM/EXECUTIVE DECW$LOGIN_ACCESS_CONTROL DISABLE

If the logical name is not defined or if it is defined to some other value, such as "SERVER", DECwindows login neither enables nor disables access control.

In most cases, it should not be necessary to define the logical name.

1.7 Color Customizer Example Program

V1.2

The color customizer example program allows you to dynamically control the colors of your workstation environment. Window, icon, and window manager colors can be changed individually or as part of a palette switch. You can control mapping between resources and color cells, as well as the size and contents of the palette set. Also, automatic shadowing with the standard Motif shadowing algorithms is supported.

1.7.1 Supported Displays

V1.2

The color customizer supports any display using pseudocolor or grayscale visuals. This includes most 4- and 8-plane workstation displays.

1.7.2 Supported Applications

V1.2

The color customizer can affect the colors of any applications that use the current release of the DIGITAL X Toolkit Library. Applications from other vendors and previous versions of the DIGITAL X Toolkit Library are unaffected.

V1.2

To build the color customizer on OpenVMS systems, perform the following steps:

1. Copy the files to a private directory. For example:

   $ SET DEFAULT SYS$LOGIN $ CREATE/DIRECTORY [.CUSTOMIZER] $ SET DEFAULT [.CUSTOMIZER] $ COPY DECW$EXAMPLES:CUSTOM.C [] $ COPY DECW$EXAMPLES:CUSTOM.UIL [] $ COPY DECW$EXAMPLES:CUSTOMIMAGE.DAT [] $ COPY DECW$EXAMPLES:XSETROOT_CUST.C [] $ COPY DECW$EXAMPLES:BUILD_CUSTOMIZER.COM []

2. Build the customizer using the following command:

   $ @BUILD_CUSTOMIZER.COM

This command procedure creates the following output files:

• CUSTOM.UID
• CUSTOM.EXE
• XSETROOT_CUST.EXE

V1.2

To run the color customizer, perform the following steps:

1. Copy the files CUSTOM.UID and CUSTOM.EXE, which were created during the customizer build, to the directory where the customizer will be run. A typical location is the directory SYS$LOGIN or the directory DECW$USER_DEFAULTS.
2. Copy the files CUSTOM.DAT and DXMDEFAULTS.DAT from the directory DECW$EXAMPLES to the same location as you copied the files in step 1. The same typical locations apply.
3. Run the executable file CUSTOM.EXE as follows:

   $ RUN CUSTOM

V1.2

As noted in Section 1.7.4, the color customizer should be the first X application started during the login process. Do this by starting it as a subprocess from within the DECW$LOGIN.COM file. Add a command to wait approximately 10 seconds between customizer startup and the startup of other applications.

For example, add the following lines to the DECW$LOGIN.COM file:

$! Starting the color customizer $ DISPLAY = F$LOGICAL("DECW$DISPLAY") $ SPAWN/NOWAIT/OUTPUT='DISPLAY' RUN SYS$LOGIN:CUSTOM.EXE $ WAIT 0:0:10

See Using DECwindows Motif for OpenVMS and Managing DECwindows Motif for OpenVMS Systems for more information on the file DECW$LOGIN.COM.

1.7.6 Command Interface Summary

V1.2

A box containing a list of available palettes is in the leftmost section of the Color Customizer window. Click on the desired palette to see the colors take affect.

Below the palettes are two arrays of colored buttons, representing the dynamically allocated color cells for normal and shadow colors. To find out what resources are affected by a color cell, click and hold the arrow button next to the color cell.

To modify a single color cell, click on the corresponding color button. A colormix widget pops up; as you modify the color, these modifications are reflected in your workstation environment. Use the colormix widget reset button to return to the starting color at any time. You can also change the color cell you are modifying by clicking on a different color button while the colormix widget is displayed.

The automatic shadowing option causes shadow and select colors to be automatically updated when their corresponding background colors are changed. The standard Motif shadowing algorithms are used for these calculations.

Use the File menu to modify, add, and delete color palettes as follows:

• To modify an existing palette, select the palette, change the colors, and choose Save Palette from the File menu.
• To add a new palette, select an existing palette, modify the colors as necessary, and choose Save Palette As... from the File menu. A message box prompts you for the name of the new palette.
• To delete a palette, select the palette and choose Delete Palette from the File menu.

Changes made through the File menu automatically update the CUSTOM.DAT file, which contains the resource defaults.

The File menu Exit button causes the customizer application to exit. A warning dialog is displayed first. Note that the color cells allocated by the customizer (and used by the currently running applications) will be deallocated. After the customizer exits, if the colors of the currently running applications are not correct, the applications should be restarted to restore normal colors. Usually, there is no need to exit the color customizer; it is typically kept running at all times, like the Session Manager.

1.7.7 Changing the Mapping Between Color Resources and Color Cells

V1.2

The file DXMDEFAULTS.DAT allows you to control how many dynamic color cells are allocated and what resources are affected. This file contains resource specifications like the following:

*background: DXmDynamicWindowBackground *foreground: DXmDynamicWindowForeground *topShadowColor: DXmDynamicWindowTopShadow

When the customizer is started, the file DXMDEFAULTS.DAT is written to a property on the root window. Any application that is subsequently run and that uses the correct X Toolkit Library merges these resources with its normal resource database. Resource specifications in this file take precedence over specifications with equivalent resource names in other resource default files.

The resource values within the file DXMDEFAULTS.DAT have a special format. For each unique color value in this file that begins with the string "DXmDynamic", a color button is created in the color customizer. If the string "Shadow" is encountered in a name, the color button is placed in the shadow button box rather than the normal color button box. If a color value string ends with the suffix "Background", it is linked to any color buttons with identical prefixes and suffixes of "TopShadow", "BottomShadow", or "SelectColor" for purposes of automatic shadowing. If a color value named "DXmDynamicScreenBackground" is encountered, the color cell allocated is used by the customizer to set the root window background color.

You can edit the file DXMDEFAULTS.DAT and define resources to use the same color cells. You can have separate dynamic color cells, for scrollbar widgets or for your DECwindows Mail application, for example, by adding the following lines to the file DXMDEFAULTS.DAT:

Mail*background: DXmDynamicMyMailBackground Mail*foreground: DXmDynamicMyMailForeground Mail*topShadowColor: DXmDynamicMyMailTopShadow Mail*bottomShadowColor: DXmDynamicMyMailBottomShadow

Adding the previous lines to the file DXMDEFAULTS.DAT and restarting the customizer causes four new color cells to be allocated and four new color buttons to be added to the customizer interface. These buttons are assigned default color values (usually black or white) for each palette. These defaults can then be modified for each palette through the customizer interface.

V1.2

The color customizer does not affect the colors of DECterm windows. To change the colors of DECterm windows, copy the DECterm resource specifications from the file DXMDEFAULTS.DAT and add them to the DECterm resource defaults file DECW$USER_DEFAULTS:DECW$TERMINAL_DEFAULT.DAT. For example, add the following lines to the DECterm resource defaults file:

. . . DECW$TERMINAL.main.terminal.background: DXmDynamicTerminalBackground DECW$TERMINAL.main.terminal.foreground: DXmDynamicTerminalForeground

This allows the DECterm window colors to be customized with the color customizer.