HP OpenVMS Systems Documentation

HP DECwindows Motif for OpenVMS
New Features

Table 4-11 lists previously undocumented Common fonts and their file names. The files for these fonts are located in the following directory:

• DECW$SYSCOMMON:[SYSFONT.DECW.COMMON]

Table 4-12 lists the previously undocumented Bitstream Speedo scalable fonts and their file names. The files for these fonts are located in the following directory:

• DECW$SYSCOMMON:[SYSFONT.DECW.SPEEDO]

Table 4-13 lists the new Agfa Monotype TrueType scalable fonts and their file names. The files for these fonts are located in the following directory:

• DECW$SYSCOMMON:[SYSFONT.DECW.TRUETYPE]

Table 4-14 lists previously undocumented Adobe Type1 fonts and their file names. The files for these fonts are located in the following directory:

• DECW$SYSCOMMON:[SYSFONT.DECW.TYPE1]

V1.2--6

When opening a hierarchy, DECwindows Motif searches the DECW$USER_DEFAULTS and DECW$SYSTEM_DEFAULTS areas for the User Interface Definition (UID) file. On UNIX systems, the search path is defined using the UIDPATH variable and its fallbacks.

Now DECwindows Motif also checks for the UIDPATH variable if the UID file is not found using either of the OpenVMS symbols listed above. This variable references a UNIX-style pathname (for example, /foo/bar) and allows the substitutions strings as specified by X11 standards. For more information on the UIDPATH variable, see the OSF/Motif Programmer's Reference.

V1.1

Starting with DECwindows Motif for OpenVMS Version 1.1, Xlib added a client side library, DECW$XEXTLIBSHR.EXE, that allows OpenVMS clients to issue Shape, XInput, Multibuffer, and Shared Memory extension requests to servers that provide these features.

You must modify the linking file options for client applications that issue these extension requests to link to the Xlib extensions shareable image in SYS$LIBRARY:DECW$XEXTLIBSHR.EXE. Add the following line to your linker options file:

SYS$LIBRARY:DECW$XEXTLIBSHR/SHARE

For more information on Shape, XInput, and Multibuffer extensions, see the following text files in SYS$HELP:

• DECW$SHAPE.TXT
• DECW$XINPUT.TXT
• DECW$MULTIBUFFER.TXT

The following sections describe features related to X Window System extensions, protocols, and their libraries.

4.7.1 Additional X Display Server Extensions Supported with X11R6.6

V1.3

The following X11R6.6 protocol X Window System extensions have been integrated into the DECwindows X11 Display Server and are now supported by DECwindows Motif:

• Application Group (XC-APPGROUP)
• Big Requests (BIG-REQUESTS)
• Colormap Utilization Policy (TOG-CUP)
• Extended Visual Information (EVI)
• Low-Bandwidth X (LBX)
• Security (SECURITY)
• Synchronization (SYNC)
• XC-MISC
• X Double Buffer (DBE)
• XINERAMA (formerly PanoramiX)
• X Keyboard (XKB)

BIG-REQUESTS, EVI, SYNC, TOG-CUP, and XC-MISC are a permanent part of the DECwindows X11 Display Server and are always enabled. DBE, LBX, SECURITY, XC-APPGROUP, XINERAMA, and XKB are dynamically loadable using the DECW$SERVER_EXTENSIONS parameter defined in the DECW$PRIVATE_SERVER_SETUP.COM file. With this symbol, each extension is converted to a shareable image, which is run at server startup. Note that some combinations of extensions can result in conflict; see HP DECwindows Motif for OpenVMS Management Guide for instructions on enabling these extensions.

To access these these extensions, link applications against one or more of the following libraries:

For more information about the updates made to the client-side extension library in support of X11R6.6, see Section 4.6.3.

The following sections briefly describe each extension, its function, and any variances from the standard X11R6.6 implementation provided by the X.Org Foundation. For a detailed description of each extension protocol and the available server requests, see the X Window System (Scheifler and Gettys) series of manuals described in the HP DECwindows Motif for OpenVMS Documentation Overview, or visit the X.Org Foundation web site (http://www.x.org) for protocol and library specifications.

4.7.1.1 Application Group Extension (XC-APPGROUP)

XC-APPGROUP enables multiple programs to manage X Window applications on the desktop. This extension allows X applications to be embedded into the window of another program, such as a web browser.

Sets of one or more applications, known as an Application Group, are managed by a controlling application, known as the Application Group Leader. The group shares the Substructure-Redirect attribute of the window with the Application Manager and one or more Application Group Leaders.

Code that uses XC-APPGROUP must include the following header files:

# include "DECW$INCLUDE:Xlib.h"
# include "DECW$INCLUDE:Xag.h"

This extension is dynamically loadable (along with the SECURITY extension) at server startup; see the HP DECwindows Motif for OpenVMS Management Guide. Call the following routine to check if XC-APPGROUP is available on the server system:

Bool XagQueryVersion (
       Display *dpy,
       int     *major_version_return,
       int     *minor_version_return
);

The following table lists each argument and its description.

BIG-REQUESTS enables a client application to extend the length field of a protocol request from 2 ¹⁸ bytes to a 32-bit value. This is useful for clients and other extensions that frequently transmit complex information to the display server.

The only callable function associated with this extension is XExtendedMaxRequestSize, which has been incorporated into Xlib. As such, it is always available when connected to an X Window system that offers this extension.

4.7.1.3 Colormap Utilization Policy Extension (TOG-CUP)

TOG-CUP provides the following colormap management capabilities to the display server:

• A mechanism for a special application (such as a colormap manager) to recognize special colormap requirements. For example, this extension enables an application to locate and initialize a default colormap.
• A policy that encourages colormap sharing and reduces colormap flashing on low-end 8-bit frame buffers.
• A behavior in the color allocation scheme that reduces colormap flashing when colormaps are not shared.

Specifically, the TOG-CUP protocol provides methods that query the server for a list of reserved colormap entries and initialize shareable colormap entries at specific locations. If the core protocol does not contain information about the returned pixel values, the AllocColor and AllocNamedColor requests look in the default colormap for a matching color. If a match is found and the corresponding cell in the private colormap is empty, the color is allocated to that cell in the private colormap rather than the first available location. This minimizes colormap flashing when the main window's default visual class is using a private colormap and is set to GrayScale, PseudoColor, or DirectColor.

Code that uses the TOG-CUP extension must include the following header files:

# include "DECW$INCLUDE:Xlib.h"
# include "DECW$INCLUDE:Xcup.h"

This extension is a fixed part of the display server and is always enabled. Call the following routine to check if the TOG-CUP extension is available on the server system:

Bool XcupQueryVersion (display, &major, &minor)
       Display *display,
       int     major,minor;

Note that client applications must call XcupQueryVersion before calling any other TOG-CUP function.

The following table lists each argument and its description.