| Previous | Contents | Index |
The release notes in this chapter are cumulative from DECwindows Motif Version 1.0 and still apply to Version 1.2--5. This chapter describes the following information:
V1.2--5
This chapter contains updates to DECwindows Motif documentation. Note that some of the documents have not been reissued for this release of DECwindows Motif.
| Title | Software Version |
|---|---|
| DECwindows Motif Version 1.2--5 for OpenVMS Release Notes | Version 1.2--5 |
| DECwindows Motif Version 1.2--5 for OpenVMS Installation Guide | Version 1.2--5 |
| Getting Started With the New Desktop | Version 1.2--4 |
| DECwindows Motif for OpenVMS Applications Guide | Version 1.2 1 |
| DECwindows Motif for OpenVMS Guide to Non-C Bindings | Version 1.2 1 |
| Using DECwindows Motif for OpenVMS (Digital Press) | Version 1.1 1 |
| DECwindows Motif for OpenVMS Quick Reference Card | Version 1.2 1 |
| Managing DECwindows Motif for OpenVMS Systems | Version 1.2 1 |
| Overview of DECwindows Motif for OpenVMS Documentation | Version 1.2 1 |
| DECwindows Extensions to Motif | Version 1.2 |
| DECwindows Companion to the OSF/Motif Style Guide | Version 1.2 |
| DECwindows Motif Guide to Application Programming | Version 1.2 |
| VMS DECwindows Device Driver Manual | Version 1.0 1 |
| VMS DECwindows Transport Manual | Version 1.0 1 |
| Porting XUI Applications to Motif | Version 1.0 1 |
| VMS DECwindows Guide to Xlib (Release 4) Programming: MIT C Binding | Version 1.0 1 |
| VMS DECwindows Guide to Xlib (Release 4) Programming: VAX Binding | Version 1.0 1 |
| VMS DECwindows Display PostScript System Programming Supplement | Version 1.0 1 |
| X Window System (Digital Press) |
Release 5
Third Edition |
| X Window System Toolkit (Digital Press) | Release 4 |
| X and Motif Quick Reference Guide (Digital Press) | Release 5 |
| OSF/Motif Style Guide (Prentice--Hall) | Release 1.2 |
| OSF/Motif Programmer's Guide (Prentice--Hall) | Release 1.2 |
| OSF/Motif Programmer's Reference (Prentice--Hall) | Release 1.2 |
DECwindows Motif also provides the following Common Desktop Environment (CDE) manuals in support of the New Desktop:
This section contains corrections and enhancements to existing
DECwindows Motif documentation.
4.2.1 Getting Started With the New Desktop
This section contains documentation corrections to the Getting Started With the New Desktop
manual.
4.2.1.1 File Specification Incorrect
V1.2--5
A file specification for a command procedure in Getting Started With the New Desktop (part number AA-QUW1A-TE) is incorrect. The file specification appears in Section 3.4.9, paragraph 5, as follows:
"Optional DECwindows applications, such as DECwindows Notes, may not provide any information and therefore are not restarted. For such cases, there is a command procedure called disk$:[user.DT]SESSIONETC.COM that you can use to start any applications that cannot be restarted automatically. This procedure is analogous to the DECW$LOGIN.COM procedure in the traditional DECwindows environment."
The correct file specification is:
disk$:[user.DT.SESSIONS]SESSIONETC.COM
4.2.2 DECwindows Motif for OpenVMS Applications Guide
This section contains documentation corrections to the DECwindows Motif for OpenVMS Applications Guide
manual.
4.2.2.1 Enhancing Information About the Finish Printing Option
V1.2--3
The section called "Printing Information" in the chapter on DECterm provides information about the Print menu. To further clarify the information in the Finish Printing section, note the following:
Selecting the Finish Printing option on the Print menu closes the print
job and toggles Auto Print mode back to Normal Print mode.
4.2.3 Using DECwindows Motif for OpenVMS
This section contains documentation corrections and enhancements to the
Using DECwindows Motif for OpenVMS manual.
4.2.3.1 Using the Drag-and-Drop Feature
V1.2
The drag-and-drop feature lets you move or copy screen objects. For example, you can move text from buttons and paste it elsewhere.
To drag and drop text into a new location:
Drag-and-drop is provided primarily for programmers to incorporate the feature into their applications.
The DECwindows Motif Version 1.2 for OpenVMS applications support the drag-and-drop feature, with
the exception of Notepad. DECwindows Mail supports drag-and-drop in all
windows except the main message area, where DECwindows Mail has its own
drag-and-drop feature; you can use MB2 to move messages around with the
SVN interface.
4.2.3.2 Tear-Off Menus
V1.2--3
The DECwindows Mail application supports tear-off menus.
V1.2
The DECwindows Motif applications allow you to tear off pull-down and popup menus. Tear-off menus let you keep frequently used menus displayed without repeatedly pulling them down or popping them up.
To tear off a menu:
To close a tear-off menu:
The following applications do not support tear-off menus:
V1.2
The example "Adding Target Screen Options to Application Menu Items" in Using DECwindows Motif for OpenVMS is incorrect. To correct the problem, remove the first occurrence of the following line:
$ select_qualifiers:
4.2.3.4 Changing the Startup Environment
V1.2
The example "Changing Your Logo" is incorrect. To correct the problem, change the following code example in step one:
$ COPY SYS$COMMON:[SYSMGR]DECW$PRIVATE_APPS_SETUP.TEMPLATE - _$ SYS$SPECIFIC:[SYSMANAGER]DECW$PRIVATE_APPS_SETUP.COM/LOG |
The code example should read as follows:
$ COPY SYS$COMMON:[SYSMGR]DECW$PRIVATE_APPS_SETUP.TEMPLATE - _$ SYS$SPECIFIC:[SYSMGR]DECW$PRIVATE_APPS_SETUP.COM/LOG |
V1.1
Extensive SYLOGIN.COM or LOGIN.COM command procedures slow down application startup. Many of the operations performed in a SYLOGIN.COM or LOGIN.COM are meaningless for DECwindows application startup. Therefore, the SYLOGIN.COM and LOGIN.COM files should be conditionalized for DECwindows application startup performance. When starting a DECwindows application, a minimum of SYLOGIN.COM and LOGIN.COM commands should be executed.
Typically, the commands that should be executed are the redefinition of DECW$USER_DEFAULTS (if present), and other logical name definitions if the user will be referencing them from within the context of a DECwindows application. The following code segment can be inserted into SYLOGIN.COM and LOGIN.COM immediately following the commands necessary for DECwindows:
$ mode = f$mode()
$ tt_devname = f$trnlnm("TT")
$ session_mgr_login = (mode .eqs. "INTERACTIVE") .and. -
(f$locate("WSA",tt_devname) .ne. f$len(tt_devname))
$ session_detached_process = (mode .eqs. "INTERACTIVE") .and. -
(f$locate("MBA",tt_devname) .ne. f$len(tt_devname))
$ if session_mgr_login .or. session_detached_process then exit
|
Applications continue to run even if these lines are not added to the
SYLOGIN.COM and LOGIN.COM files.
4.2.3.6 Enhancing Hold-Screen Response Time
V1.1
If the Hold Screen key response time is too slow, add the following lines to your DECW$TERMINAL_DEFAULT.DAT file:
DECW$TERMINAL.main.terminal.syncFrequency: 1 DECW$TERMINAL.main.terminal.batchScrollCount: 1 |
Using this resource can affect the performance of the DECterm window.
The actual impact on performance varies from site to site. You can
trade off scrolling speed to hold-screen response time. A faster
hold-screen response results in a slower scrolling speed. The default
values for these resources are 10 and 0, respectively.
4.2.4 Managing DECwindows Motif for OpenVMS Systems
This section contains documentation enhancements and corrections to the
Managing DECwindows Motif for OpenVMS Systems manual.
4.2.4.1 Global Symbols
V1.2--3
The following additional global symbols are available in the DECwindows Motif for OpenVMS product:
For information about using these symbols, refer to Section 2.18 in
these Release Notes. Refer to the chapter "Using DECwindows"
in Managing DECwindows Motif for OpenVMS Systems for the complete list of global symbols.
4.2.4.2 Security Options
V1.2
In the Session Manager Security Options dialog box, place the node name within quotation marks if the name contains any of the following:
Session Manager automatically adds quotation marks to the node name if they are needed, unless the node name begins with a double quotation mark. If the node name begins with a double quotation mark, Session Manager assumes that the user has already quoted the node name and does not change it.
Within a quoted string, a double quotation mark should be replaced by two double quotation marks (" "). For example, the quoted string "DEC:.zko."my node"" should be changed to the following:
("DEC:.zko.""my node""").
|
V1.1
By default, if there is no DECwindows Motif license registered for the SYSTEM account, DECwindows does not display customized login logos. This is a problem on systems with DECwindows Motif personal-use licenses that do not include SYSTEM on the list of authorized DECwindows users.
To display a customized logo without a DECwindows Motif license for SYSTEM, add the following definition to the SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM file:
$ DECW$LOGINLOGOSUB == "TRUE" |
If the SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM file does not exist, copy it from the file SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.TEMPLATE. |
After editing the setup file, restart DECwindows Motif using the following command:
$ @SYS$MANAGER:DECW$STARTUP RESTART |
DECwindows Motif login starts the logo process as a subprocess instead
of as a detached process. The license check sees that the logo process
is a child of the login process and that the X connection is opened.
4.2.4.4 Enabling and Disabling Access Control
V1.0
DECwindows Motif does not enable access control by default. Instead, it uses the 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.
4.2.5 DECwindows Motif for OpenVMS Guide to Non-C Bindings
This section contains documentation enhancements and corrections to the
DECwindows Motif for OpenVMS Guide to Non-C Bindings.
4.2.5.1 GET_CHAR_STRUCT Function
V1.2--3
The access related to the char_struct argument for the XLIB
GET_CHAR_STRUCT function is incorrectly documented. The correct access
is write.
4.2.6 VMS DECwindows Guide to Xlib (Release 4) Programming: VAX Binding
V1.2
Example 1-1 in the VMS DECwindows Guide to Xlib (Release 4) Programming: VAX Binding is incorrect. To correct the problem, change the following two lines in the section "Create the WINDOW_1 window":
WINDOW_1X = (X$WIDTH_OF_SCREEN(DPY) - WINDOW_1W) / 2 WINDOW_1Y = (X$HEIGHT_OF_SCREEN(DPY) - WINDOW_1H) / 2 |
The example should read as follows:
WINDOW_1X = (X$WIDTH_OF_SCREEN(SCREEN) - WINDOW_1W) / 2 WINDOW_1Y = (X$HEIGHT_OF_SCREEN(SCREEN) - WINDOW_1H) / 2 |
Example 3-1 in the VMS DECwindows Guide to Xlib (Release 4) Programming: VAX Binding is incorrect. To correct the problem, change the following two lines:
WINDOW_1X = (X$DISPLAY_WIDTH_OF_SCREEN(SCREEN) - WINDOW_1W) / 2 WINDOW_1Y = (X$DISPLAY_HEIGHT_OF_SCREEN(SCREEN) - WINDOW_1H) / 2 |
The example should read as follows:
WINDOW_1X = (X$DISPLAY_WIDTH_OF_SCREEN(DPY) - WINDOW_1W) / 2 WINDOW_1Y = (X$DISPLAY_HEIGHT_OF_SCREEN(DPY) - WINDOW_1H) / 2 |
This section lists documentation corrections and enhancements for the
DECwindows Extensions to Motif document.
4.2.7.1 DXmNlayoutDirection Resource Constants
V1.2--3
The section on DXmNlayoutDirection Resource in Chapter 2 lists the following constants:
Note that the following constants are not currently available for the DXmNlayoutDirection resource:
The introduction to Table 2--1 is incorrect. Table 2--1 describes the effect of the constants DXmLAYOUT_LEFT_DOWN and DXmLAYOUT_RIGHT_DOWN on the functions.
V1.2
In Section 2.2 of the DECwindows Extensions to Motif manual, the description of DXmChildren indicates that the routine can be used to learn the length of widget_list.
The documentation is incorrect. The sentence should read, "You can
use the DXmNumChildren routine to learn the length of the widget list
returned by DXmChildren."
4.2.8 DECwindows Motif Guide to Application Programming
This section lists documentation corrections and enhancements for the
DECwindows Motif Guide to Application Programming manual.
4.2.8.1 UIL Source Code for the OpenVMS DECburger Application
V1.2--3
The introduction to the section in Chapter 4 called "Creating the
Help Widget with UIL", which introduces Example 4--6, "UIL
Help Widget Implementation," does not clearly state that the
complete UIL source code for the OpenVMS DECburger application is
included in DECW$EXAMPLES on OpenVMS systems.
4.2.8.2 Help Widget Implementation Code
V1.2--3
In the title of Example 4--7, "Help Widget Implementation---C Language Module", DECBURGER.C should be added to the title as follows:
"Help Widget Implementation---C Language Module (DECburger.C)"
4.2.8.3 Help Widget Implementation---Callbacks
V1.2--3
The title of Example 4-8 should read as follows:
"Help Widget Implementation---Callbacks (DECburger.C
continued)"
4.2.8.4 Using UIL to Create the Help Widget
V1.2--3
The title of Section 4.10, "Using the Toolkit Help Widget Creation Routine," does not accurately reflect the contents of this section. The title should read, "Using UIL to Create the Help Widget".
The introductory paragraph to Example 4--9 in the section called "Using the Toolkit Help Widget Creation Routine" is incomplete. The information should state the following:
"The code in Example 4--9 is included in DECburger.C but is commented and will not be compiled when the example program is built."
The implementation in this example is not complete; it requires some sections from Examples 4-7 and 4-8.
To summarize, the documentation should state the following information:
V1.2
Table 2-2 in the Overview of DECwindows Motif for OpenVMS Documentation Version 1.2 indicates that the
DECwindows Motif Version 1.2 for OpenVMS Installation Guide is included in the User Kit. This is incorrect. The
installation guide is included with the media kit.
4.3 OSF/Motif List of Known Problems
Included in the DECwindows Motif for OpenVMS software is an OSF file that contains the OSF/Motif known problems. During the installation this file is copied from the kit to SYS$HELP:DECW$MOTIF_OSF_BUGLIST_V12.TXT.
| Previous | Next | Contents | Index |