HP OpenVMS Systems Documentation

3.3.5.4 Bitstream Speedo Scalable Fonts

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

Table 3-8 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 3-9 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]

3.4 X Window System Toolkit (Xt) Enhancements

In addition, two new variables are provided in support of the new session shell widget:

• sessionShellClassRec
• sessionShellWidgetClass

See the X Toolkit Intrinsics - C Language Interface, X Window System, X Version 11 Release 6.4 specification available from X.Org for detailed information about each of these functions and variables.

3.4.1 Support for Easy Resource Configuration

Setting and changing resources in X Window System applications can be difficult for both the application developer and the end user. Resource Configuration Management (RCM) addresses this problem by changing the X Intrinsics to immediately modify a resource for the specified widget and each child widget in the hierarchy. As a result:

• No sourcing of resource files is required.
• The application does not need to be restarted for the new resource values to take effect.
• The change occurs immediately.

RCM was made available as part of the X11R6.4 release and is now available with HP DECwindows Motif for HP OpenVMS Alpha Version 1.3. However, note that RCM is not a standard part of the X Toolkit Intrinsics. It is neither an X Consortium standard nor part of the X Window System specifications. As a result, there are currently no public customization tools that take advantage of this feature.

If you are interested in learning more about RCM, see the X Toolkit Intrinsics - C Language Interface, X Window System, X Version 11 Release 6.4 Release Notes available from X.Org.

3.4.2 New Option for CompositeClassExtensionRec

With X11R6, some modifications were made to the widget internals, as described in the X Window System Toolkit manual.

In particular, a new option in the Composite Class extension record enables you to make bundled changes to the managed set of a Composite widget. Widgets that define a change-managed procedure that performs additions and deletions to the managed set of children in a single invocation should set allows_change_managed_set option to TRUE in the extension record.

For more information about the impact this new option may have on existing applications, see the HP DECwindows Motif for HP OpenVMS Alpha Release Notes.

3.5 X Window System Extension and Protocol Enhancements

The following sections describe the new and updated server extensions and protocols available with HP DECwindows Motif for HP OpenVMS Alpha Version 1.3. With the exception of AccessX, all existing extensions continue to be supported.

3.5.1 New X Display Server Extensions

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

• 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 Section 2.2 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 3.3.1.

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

3.5.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 Section 2.2. 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.

3.5.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.