[an error occurred while processing this directive]
HP OpenVMS Systems Documentation |
HP DECwindows Motif for OpenVMS
|
Previous | Contents | Index |
Although this extension is part of the X display server, it is not enabled by default.
To enable XINERAMA, modify the DECW$PRIVATE_SERVER_SETUP.COM file and redefine the parameter DECW$SERVER_EXTENSIONS so that it includes a value of "XINERAMA." For example:
$ DECW$SERVER_EXTENSIONS == "DEC-XTRAP,XINERAMA" |
Save the file and restart the server.
3.4.3.3 Arranging the Monitors
By default, the system uses the physical location of the video cards on the system bus to assign the device names (such as, GYA0, GYB0, etc.). The devices are subsequently assigned screen numbers and initialized in alphabetical order according to device name.
For example in a four-monitor multihead configuration, if you have connected the cables to the video cards in the proper order and placed the monitors side-by-side, the screens should be numbered in either ascending (0, 1, 2, 3) or descending (3, 2, 1, 0) order.
On OpenVMS systems, the order in which screens are initialized is key to proper edge and pointer attachment. Screen 0 should be initialized first (representing the top-left corner of the virtual display), followed by the remaining screens in sequential order, ending with the highest screen number (representing the bottom-right corner of the virtual display). If the screens are not in the proper order, you can do one of the following depending on your screen configuration:
Once the screens are in the appropriate order, you can further customize the virtual display using the following edge attachment parameters in DECW$PRIVATE_SERVER_SETUP.COM:
These parameters control where each edge of the virtual display is attached.
When the setup process is complete, all the monitors should be active
and organized in the proper arrangement. Once you restart
DECwindows Motif, the login dialog box for the session is displayed at the
center of the virtual display, and you should be able to open
application windows and drag them from screen to screen.
3.5 Changing the Default Keyboard Layout
There are two types of keyboard layouts available to DECwindows Motif: the DECwindows keymaps and the X Keyboard keymaps. The following sections describe how to change the default keyboard settings outside of a desktop session. Note that these settings can be overridden by the Session Manager during a desktop session, as described in the Using DECwindows Motif for OpenVMS and Getting Started With the New Desktop manuals.
See Appendix B for a listing of all languages, keyboard models, and
keymap names.
3.5.1 Using the DECwindows Keymap Files
To override the default keyboard layout and specify a DECwindows keymap file, determine the correct name from the model number of your keyboard, as follows:
$ DECW$DEFAULT_KEYBOARD_MAP == "DUTCH_LK201LH_TW" |
Example 3-2 shows a sample setup for two workstations with Dutch keyboards and 100-dpi monitors.
Example 3-2 Sample Setup for Dutch Keyboards and 100-dpi Monitors |
---|
$do_DUTCH: $do_DUTCH2: $ decw$server_density == 100 $ decw$default_keyboard_map == "DUTCH_LK201LH_DP" $ exit |
The X Keyboard keymap files are the standard X Window System alternative to the keymaps provided with DECwindows Motif. They are intended to supplement, rather than replace, the DECwindows Motif keymap files.
You can compile X Keyboard layout files to create loadable keymaps using the X Keyboard Compiler utility (xkbcomp), as described in the following section, or the server will compile the files as needed.
Also, since the X Keyboard keymap format (.XKM) is the accepted,
vendor-independent standard for loadable keyboards, you can choose to
load .XKM files from other X11R6-based systems and X Window System
software providers.
3.5.2.1 The X Keyboard Components Database
The X display server maintains a database of X keyboard components and common keyboard mappings. When combined, these components provide a complete description of a keyboard and its behavior.
The server loads the database from the compiled keymap file specified by the DECW$SERVER_XKEYBOARD_MAP parameter. This file is located in the directory defined by the DECW$SERVER_XKEYBOARD_COMPILED_DIR parameter. If the compiled keymap file does not exist, the server runs the xkbcomp utility to compile the file from its component sources.
The following keyboard component source files comprise the database and are used to produce the loadable keymap files:
To create an X Keyboard keymap file, do the following:
. . . 19 key <AE09> { [ 9, parenleft ] }; 20 key <AE10> { [ 0, parenright ] }; . . . |
$ xkbcomp -RDECW$SYSCOMMON:[SYS$KEYMAP.XKB] -xkm -m lk401 - _$ DECW$SYSCOMMON:[SYS$KEYMAP.XKB.KEYMAP.DIGITAL]us - _$ -o SYS$COMMON:[SYS$KEYMAP.XKB.COMPILED]digital_us_lk401.xkm |
You can then load the modified, compiled keymap file as described in
Section 3.5.2.3.
3.5.2.3 Loading a Compiled Keymap File
To load a compiled X Keyboard keymap file, do the following:
$ DECW$SERVER_EXTENSIONS == "XKB,XINERAMA" |
$ DECW$SERVER_XKEYBOARD_LOAD_MAP=="1" |
To enable AccessX key features, do the following:
$ DECW$SERVER_EXTENSIONS == "XKB,XINERAMA" |
You can then further configure the AccessX features using the accessx utility or use the slow and sticky key functions, as follows:
To... | Perform This Action... |
---|---|
Toggle slow keys | Hold Shift key by itself for eight seconds |
Toggle sticky keys | Press and release the left or right Shift key five times in a row, without any intervening key events and with less than 30 seconds delay between consecutive presses |
Turn off sticky keys | Simultaneously press two or more modifier keys. |
You can add support for new fonts by doing the following:
$ @SYS$UPDATE:DECW$MKFONTDIR |
If you want to use a third-party font, choose one of the following options:
$ FONT file-name |
SYS$COMMON:[SYSFONT.DECW.USER_75DPI] SYS$COMMON:[SYSFONT.DECW.USER_100DPI] SYS$COMMON:[SYSFONT.DECW.COMMON_USER] |
$ @SYS$UPDATE:DECW$MKFONTDIR |
End the current session and start a new session for the new font to become available.
To use other third-party fonts, create a DECW$FONT_ALIAS.DAT file in the appropriate font directory.
The format of the font alias file is:
alias-font-name actual-font-name
If the font names contain embedded spaces, enclose the names in double quotes (" ").
The alias-font-name value is the third-party font name, and the actual-font-name value is a DECwindows font name.
See the VMS DECwindows Guide to Xlib (Release 4) Programming: MIT C Binding and HP DECwindows Motif for OpenVMS New Features manuals for supported
DECwindows font names.
3.6.2 Enabling Support for Euro Currency Symbol
DECwindows Motif includes support for the euro currency symbol. The euro font sets are installed during the base OpenVMS operating system installation. Choosing the euro option during installation allows you to then enable and display the euro symbol on systems running DECwindows Motif Version 1.3 or higher.
To enable euro support, you need to load the font definitions. Do this by creating a set of euro setup command files, as follows:
$ COPY SYS$COMMON:[SYSMGR]DECW$EURO_APPS_SETUP.TEMPLATE - _$ SYS$COMMON:[SYSMGR]DECW$EURO_APPS_SETUP.COM $ COPY SYS$COMMON:[SYSMGR]DECW$EURO_SERVER_SETUP.TEMPLATE - _$ SYS$COMMON:[SYSMGR]DECW$EURO_SERVER_SETUP.COM |
Restart your DECwindows Motif system. The command files are run automatically as part of the DECwindows Motif startup procedure.
Support for the euro locale by the OpenVMS C Run-Time Library is not
required for base DECwindows Motif euro support. However, if you want to
run Motif applications in a euro locale, you must install euro locale
support, which is included in the OpenVMS Alpha and OpenVMS I64 media
kits.
3.6.2.1 Displaying the Euro Symbol in DECwindows Motif Applications
Once euro support is enabled on your system, you can display the euro sign with any ISO8859-1 bitmap font on your workstation, with no additional setup. DECwindows Motif applications that use standard ISO Latin-1 fonts to display text will display the euro sign for character 0xA4. The character set portion of the X Logical Font Description (XLFD) name for these fonts is ISO8859-1.
To display the euro sign in a DECterm window, be sure the following two items are selected in the DECterm General Options dialog box:
Once euro support is enabled, you can manually enter the symbol using one of the following key sequences, depending on the type of keyboard attached to your system:
Keyboard Type | Keymap | Key Sequence |
---|---|---|
LK-style | *LK201* keymap |
Use the same key sequence you use for the universal currency symbol.
For example:
Compose+Space o x or Compose+Space O X |
LK-style | *LK401* keymap 1 | LeftCompose + E |
PC-style 2 | *LK44* keymap | RightAlt + E |
You can add font servers to the font path by defining the symbol DECW$FONT_SERVERS in the site-specific server section of the file SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM. Depending on the transport type, use one of the following methods:
$ DECW$FONT_SERVERS == "TCP/node::port_number" |
$ DECW$FONT_SERVERS == "DECNET/node::network_object" |
Multiple font servers can be added by defining the symbol as a
comma-separated list. The symbol is not case sensitive.
3.7 Setting up an LBX Proxy Server
As illustrated in Figure 1-3, DECwindows supports LBX proxy server implementations. An LBX proxy server implementation can be configured as one of three types:
DECwindows Motif currently supports the managed and standalone configurations.
In order to use the proxy server and proxy manager components, the LBX option must have been chosen during DECwindows installation. See the HP DECwindows Motif for OpenVMS Installation Guide for information about installing LBX support.
The following sections describe how to enable the LBX extension and configure a proxy server implementation.
Because the communication between the client and the proxy server uses the unoptimized X protocol, the client and the proxy server should always be on the same node or on the same LAN. Although LBX reduces data flow between systems, it is not recommended for a LAN-only environment. While it does reduce overall traffic flow, this comes at a cost of increased processing requirements. This generally results in a slight decrease in performance in a LAN-only environment. |
Previous | Next | Contents | Index |