HP OpenVMS Systems Documentation

4.3.6.4 Bitstream Speedo Scalable Fonts

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

Table 4-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 4-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]

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 toolkit (Xt).

4.4.1 New Functions Available with X11R6.6 Upgrade

V1.3

The following new functions from X11R6.6 have been added to the version of Xt available with DECwindows Motif for OpenVMS Alpha Version 1.3.

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.

4.4.2 Support for Easy Resource Configuration

V1.3

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 DECwindows Motif for 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.

4.4.3 New Option for CompositeClassExtensionRec

V1.3

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 OpenVMS Alpha Release Notes.

4.4.4 New Default Format for XtResolvePathname

V1.2--6

In XtResolvePathname, the default pathname is required to have certain properties when either no other path information is present in the call, or when it is referenced by the environment variable XFILESEARCHPATH. The former default OpenVMS format of the pathname consisted of a type-name-suffix substitution. The modified pathname now reflects the 6-part fallback, as specified by X11 Release 6.

The new pathname behavior is enabled by setting the DECW$VSW_COMPLIANT variable, as follows:

$ DEFINE DECW$VSW_COMPLIANT 1

V1.2--5

Previously, if a program entered its event loop, (for example, by calling XtAppMainLoop) without having opened a display or specified a timer or event flag for the program to wait for (by calling XtAppAddTimeout or XtAppAddInput), Xlib terminated the program with the following error message:

        X Toolkit Error: Error in XMultiplexInput

Starting with DECwindows Motif for OpenVMS Version 1.2--5, if there is nothing to wait for, Xlib stalls waiting for input instead of terminating with an error status.

To allow Xlib to process events at a later time, applications should provide some means of regaining control, such as specifying an event flag (on DECwindows Motif for OpenVMS Version 1.2--6 and previous systems) or a logical connection number (on DECwindows Motif for OpenVMS Alpha Version 1.3 and higher systems) by calling XtAppAddInput.

4.5 X Window System Extensions and Protocols

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 Section 3.7.3 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.3.2.

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.

4.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 3.7.3. 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.