           H                     HP DECwindows Motif for OpenVMS_____________________!                     Release Notes                          July 2006   F                     This manual describes corrections, known problems,I                     and restrictions that pertain to the DECwindows Motif )                     Version 1.6 software.               H                     Revision/Update Information:  This manual supersedesC                                                   the HP DECwindows C                                                   Motif for OpenVMS E                                                   Alpha Release Notes B                                                   for Version 1.5.  I                     Operating Systems:            OpenVMS I64 Version 8.3   G                                                   OpenVMS Alpha Version 5                                                   8.3   F                     Software Versions:            DECwindows Motif forI                                                   OpenVMS I64 Version 1.6   F                                                   DECwindows Motif forG                                                   OpenVMS Alpha Version 5                                                   1.6                       +                     Hewlett-Packard Company )                     Palo Alto, California                  J           ________________________________________________________________  D            Copyright 2006 Hewlett-Packard Development Company, L.P.  ?           Confidential computer software. Valid license from HP B           required for possession, use or copying. Consistent with>           FAR 12.211 and 12.212, Commercial Computer Software,A           Computer Software Documentation, and Technical Data for D           Commercial Items are licensed to the U.S. Government under/           vendor's standard commercial license.   ?           The information contained herein is subject to change A           without notice. The only warranties for HP products and C           services are set forth in the express warranty statements A           accompanying such products and services. Nothing herein E           should be construed as constituting an additional warranty. E           HP shall not be liable for technical or editorial errors or %           omissions contained herein.   C           Intel and Itanium are trademarks or registered trademarks @           of Intel Corporation or its subsidiaries in the United%           States and other countries.   :           Java is a US trademark of Sun Microsystems, Inc.  ;           UNIX is a registered trademark of The Open Group.   C           The X device is a trademark of X/Open Company Ltd. in the !           UK and other countries.              Printed in the US   E                                                                ZK6470                                  C   _________________________________________________________________   C                                                            Contents       C   Preface...................................................     xi      1  Introduction        2  General User Release Notes   8         2.1   OpenVMS Display Device and Layered ProductC               Interfaces....................................    2-1 C         2.1.1     OpenVMS Display Device (SET DISPLAY)......    2-1 7         2.1.1.1     SET DISPLAY/REVOKE Error Message is C                     Misleading..............................    2-1 6         2.1.1.2     I/O Error Displayed When Using SETC                     DISPLAY/REVOKE..........................    2-1 C         2.1.1.3     Display Devices Not Deleted Upon Exit...    2-2 C         2.1.2     DECTPU....................................    2-2 C         2.1.2.1     Small Display Monitors and DECTPU.......    2-2 C         2.2   General DECwindows Motif Environment..........    2-3 :         2.2.1     DECwindows Logicals Created in the WrongC                   Logical Name Table........................    2-3 C         2.2.2     DECW$GREET.TXT Timer Added................    2-4 C         2.2.3     Login Box Does Not Appear.................    2-4 6         2.2.4     XGetExtensionVersion Does Not Unlock3                   Display When the Extension is Not C                   Present...................................    2-4 <         2.2.5     Problem with Node Name Not Being DisplayedC                   in the Absence of DECnet..................    2-5 ;         2.2.6     DECW$SERVER Process Hangs When Displaying C                   a Java Applet Inside CSWB.................    2-5 C         2.2.7     Web Browser Support.......................    2-5 3         2.2.8     Scaled Bitonal Images Now Display C                   Correctly (Alpha Only)....................    2-6     C                                                                 iii                    :           2.2.9     Applications That Issue Lengthy Server9                     Requests Now Respond Correctly (Alpha E                     Only).....................................    2-6 7           2.2.10    Applications Running Over the LOCAL E                     Transport No Longer Cause System Lag......    2-6 6           2.2.11    Applications That Use GKS May FailE                     Unexpectedly..............................    2-7 <           2.2.12    Request-Intensive Applications May PauseE                     Before Closing............................    2-7 4           2.2.13    Support Discontinued for DisplayE                     PostScript................................    2-7 E           2.2.14    Limited Support for Tear-Off Menus........    2-8 =           2.2.15    Implications of the Message, "System Menu E                     Bar: Pseudo Mouse Not Available"..........    2-8 =           2.2.16    Printing from Applications Linked Against E                     OSF/Motif Release 1.1.3...................    2-8 E           2.3   New Desktop Environment.......................    2-9 E           2.3.1     Worksapce Customization...................    2-9 E           2.3.2     Workspace Background Color Problem........    2-9 E           2.3.3     Login Text Fields Display the Password....   2-10 3           2.3.4     Default Width of the Calculator E                     Increased.................................   2-10 =           2.3.5     File Manager No Longer Hangs During Large E                     Copy or Move Operations...................   2-10 ;           2.3.6     File Manager Cancels Restore Operations E                     Properly (Alpha Only).....................   2-10 =           2.3.7     Style Manager Displays Incorrect Security E                     Options on Multihead Systems..............   2-11 7           2.3.8     Screen Saver and Screen Lock Set by E                     Default...................................   2-11 E           2.3.9     Session Manager Logging Problem...........   2-11 <           2.3.10    File Manager Problems with Extended FileE                     Specifications............................   2-12 8           2.3.11    DECwrite Icon Does Not Open DECwriteE                     Program...................................   2-12 >           2.3.12    Delay When Exiting a Session with Open TPUE                     Windows...................................   2-12 E           2.3.13    Viewing TIF Files with dximageview........   2-12 E           2.3.14    Text Editor Restrictions..................   2-13 9           2.3.15    Some File Names are Displayed in UNIX E                     Format....................................   2-13 E           2.3.16    Front Panel Clock is an Icon Only.........   2-14 E           2.3.17    ToolTalk Actions Not Supported............   2-14          iv                   8               2.3.18    Session Manager Save and RestoreI                         Limitations...............................   2-14 I               2.3.19    File Manager Search List Limitations......   2-15 9               2.3.20    Login and Pause Screen Text Field I                         Restrictions..............................   2-16 @               2.3.20.1    Control Characters Not Recognized WhenI                           Entering Username.......................   2-16 >               2.3.20.2    Use Return Key to Move Between LoginI                           Text Fields.............................   2-16 A               2.3.20.3    First Character Discarded When Entering I                           Pause Screen Password...................   2-16 ;               2.3.20.4    Text on the Welcome Screen is Not I                           Displayed...............................   2-17 I               2.3.21    Font Selection Limitations................   2-17 I               2.3.22    Default Workspace Limitations.............   2-17 I               2.4   Applications..................................   2-17 I               2.4.1     Bookreader................................   2-18 8               2.4.1.1     Support for Display PostScriptI                           Removed.................................   2-18 I               2.4.2     CDA.......................................   2-18 ?               2.4.2.1     Viewing Large, Color DDIF Files using I                           eXcursion Version 7.1...................   2-18 8               2.4.2.2     Support for Display PostScriptI                           Removed.................................   2-19 I               2.4.3     Clock.....................................   2-19 B               2.4.3.1     Clock Updates Correctly after the SystemI                           Time is Reset (Alpha Only)..............   2-19 I               2.4.4     DECterm...................................   2-19 >               2.4.4.1     Graphics Applications Using ReGIS No>                           Longer Cause DECterm to Crash (AlphaI                           Only)...................................   2-19 >               2.4.4.2     DECterm Windows Positioned CorrectlyI                           (Alpha Only)............................   2-20 ?               2.4.4.3     Use CREATE/TERMINAL/DETACH to Display I                           Broadcast Messages......................   2-20 A               2.4.4.4     Using CREATE/TERMINAL with IPv6 Support I                           Enabled.................................   2-20 <               2.4.4.5     Use ignoreVisibility Resource When9                           Displaying DECterm Windows with             I                                                                         v                    8                       eXcursion or on XINERAMA MultiheadE                       Systems.................................   2-21 >           2.4.4.6     Invoking DECterm May Fail while KerberosE                       is Enabled..............................   2-21 :           2.4.4.7     Euro Currency Symbol May Not DisplayE                       Correctly When Using eXcursion..........   2-21 7           2.4.4.8     Text Does Not Display Properly on 6                       XINERAMA Multihead Systems using;                       Powerstorm 4d20 Graphics Cards (Alpha E                       Only)...................................   2-22 E           2.4.4.9     Shrinking Window Problem................   2-22 E           2.4.4.10    DECterm Resource File Name..............   2-22 E           2.4.4.11    Maximum Number of DECterm Windows.......   2-23 E           2.4.4.12    Resizing the Terminal...................   2-23 E           2.4.4.13    Reporting the DECterm Window Size.......   2-23 E           2.4.4.14    Changing the Auto Repeat Setting........   2-24 :           2.4.4.15    Timeout for Displaying the CopyrightE                       Notice..................................   2-24 E           2.4.4.16    Selecting Fonts.........................   2-24 E           2.4.4.17    Supported DECterm Logical Names.........   2-25 E           2.4.4.18    Printing to an Attached Printer.........   2-25 E           2.4.4.19    Improving Hold Screen Response Time.....   2-26 E           2.4.4.20    DECterm Graphics........................   2-26 E           2.4.4.21    DECterm Resource Usage..................   2-27 E           2.4.4.22    Diagnostic Crash File and Messages......   2-27 E           2.4.4.23    Using the Debugger......................   2-28 E           2.4.4.24    Virtual Terminal Support................   2-28 8           2.4.4.25    VT330 and VT340 Terminal EmulationE                       Restrictions............................   2-28            2.4.4.26    Using E                       CREATE/TERMINAL/DETACHED/PROCESS........   2-29 E           2.4.4.27    ReGIS Locator Report....................   2-30 E           2.4.5     DECwindows CD Player......................   2-30 E           2.4.5.1     Required Privileges.....................   2-30 E           2.4.6     DECwindows Mail...........................   2-30 1           2.4.6.1     Support Removed for Display E                       PostScript..............................   2-30 9           2.4.6.2     Pasting Messages from the Directory E                       Window..................................   2-31 E           2.4.6.3     Responses to Keyboard Actions...........   2-31 5           2.4.6.4     Using the Color Customizer with E                       DECwindows Mail.........................   2-31            vi                   I               2.4.7     Notepad...................................   2-32 >               2.4.7.1     Notepad Is Linked with the OSF/MotifI                           Release 1.1.3 Toolkit...................   2-32 I               2.4.8     Paint.....................................   2-32 I               2.4.8.1     Private Colormaps.......................   2-32 8               2.4.8.2     Slow Performance of Some PaintI                           Operations..............................   2-32 I               2.4.9     Session Manager...........................   2-33 ?               2.4.9.1     Specifying Authorized User Node Names I                           That Contain Reserved Characters........   2-33 A               2.4.9.2     Using the Color Customizer with Session I                           Manager.................................   2-34 ?               2.4.9.3     Detached Processes Created by Default =                           May Prevent Other Applications from I                           Opening.................................   2-34 <               2.4.9.4     Change in Input Focus When Using aI                           Private Logo............................   2-34 I               2.4.9.5     Stopping a Session Manager Process......   2-34 I               2.4.10    Window Manager............................   2-35 B               2.4.10.1    The Motif Window Manager Does Not HonourI                           ACLs....................................   2-35 ;               2.4.10.2    Help Text Does Not Display on All I                           Screens in a Multihead System...........   2-35 B               2.4.10.3    Alt + Space Key Does Not Post the WindowI                           Menu....................................   2-36 9               2.4.10.4    Using the Color Customizer with I                           DECwindows Motif Window Manager.........   2-36 B               2.4.10.5    Changing Function Key Bindings Using theI                           Window Manager Configuration File.......   2-37 I               2.4.10.6    Restarting the Window Manager...........   2-37 A               2.4.10.7    Customizing Color-Related Resources for I                           Monochrome Monitors.....................   2-38 9               2.4.10.8    Customizing Colors on Multihead I                           Systems.................................   2-38 I               2.4.10.9    Moving the Icon Box Off Screen..........   2-38 I               2.4.10.10   Multiline Icon Title Not Centered ......   2-38 I               2.5   Tools and Utilities...........................   2-39 I               2.5.1     X Authority Utility (xauth)...............   2-39 A               2.5.1.1     File Locking Not Supported with Logical I                           Names...................................   2-39 B               2.5.1.2     Specifying File Names without File TypesI                           Can Result in Failure...................   2-39       I                                                                       vii                    3           2.5.2     Font Server Information Utility E                     (fsinfo)..................................   2-40 ;           2.5.2.1     Font Server Information Utility Fails E                       After Invoking..........................   2-40 E           2.5.3     Print Screen..............................   2-40 7           2.5.3.1     Print Screen Truncates PostScript E                       Output..................................   2-40   &     3  System Management Release Notes  E           3.1   Installation and Upgrade Information..........    3-1 8           3.1.1     DECwindows Motif Version Support andE                     Compatibility.............................    3-1 :           3.1.2     Limited Support for Third-Party TCP/IPE                     Products (Alpha Only).....................    3-2 E           3.1.3     DECW$STARTUP Requires SHARED Privilege....    3-3 7           3.1.4     Using Shareable Linkages to Install E                     Images....................................    3-3 6           3.1.5     DECW$COMPARE_VERSIONS Command FileE                     Limitation................................    3-4 8           3.1.6     Restarting DECwindows Motif from theE                     Operator Console (OPA0:)..................    3-4 E           3.2   System Tuning and Performance.................    3-5 9           3.2.1     Changes in Recommended UAF and System E                     Parameter Values..........................    3-5 E           3.3   Security and Authorization....................    3-5 ;           3.3.1     Buffer Overflow Reported on Xpm Library E                     (CERT Vulnerability VU#882750)............    3-5 ;           3.3.2     A Deprecated Kerberos API Replaced with E                     New API...................................    3-6 E           3.3.3     PWDMIX Flag Now Handled Properly..........    3-6 ;           3.3.4     GENPWD Flag Now Handled Properly (Alpha E                     Only).....................................    3-6 <           3.3.5     BadAuthorizationProtocol Error Displayed;                     When Generating Authorization Keys with E                     Kerberos Enabled..........................    3-7 E           3.3.6     Setting the hostList Resource Manually....    3-7 >           3.3.7     Unknown Code Error Displayed When EnablingE                     Kerberos..................................    3-8 9           3.3.8     Bad Atom Error Displayed When Running 2                     Applications Over an UntrustedE                     Connection................................    3-8            viii                   >               3.3.9     Applications Running Over an UntrustedA                         Connection May Not Work with XINERAMA and I                         SEC_XAG Extensions........................    3-9 >               3.3.10    Kerberos and TCP/IP Do Not Recognize aI                         Node Name of 0............................    3-9 >               3.3.11    Do Not Use DECwindows Motif Login When<                         Initializing Kerberos Setup from theI                         Server X Authority File...................   3-10 I               3.3.12    Help on Kerberos Login Box is Incorrect...   3-10 @               3.3.13    Do Not Insert Generated Cookies into theI                         Default X Authority File..................   3-10 I               3.4   Desktop Management............................   3-11 I               3.4.1     Trusted Unpause Operations Allowed........   3-11 9               3.4.2     Color Problem in DECwindows Login I                         Screen....................................   3-11 I               3.5   Font and Keymap Management....................   3-12 >               3.5.1     Queries on TrueType Font Properties No>                         Longer Reset the Display Server (AlphaI                         Only).....................................   3-12 I               3.5.2     Euro Currency Symbol Restrictions.........   3-12 ?               3.5.3     Adjusting Resource Settings for Keymaps I                         that Implement the Mode_switch Modifier...   3-12 I               3.6   Proxy Server Management.......................   3-13 =               3.6.1     LBX Proxy Servers Does Not Accept the I                         Client Connection Request.................   3-13 ;               3.6.2     Proxy Servers Do Not Support Use of I                         XC-QUERY-SECURITY-1 Protocol..............   3-14 >               3.6.3     Proxy Manager Process Does Not RestartI                         Automatically.............................   3-14 8               3.6.4     Proxy Manager Configuration FileI                         Restriction...............................   3-15 I               3.7   X Display Server Management...................   3-15 <               3.7.1     Support for Choosing the Location ofI                         Dialogs in a Xinerama Configuration.......   3-15 A               3.7.2     Adjusting Pixel Depth on Systems with ATI I                         RADEON Graphics Cards.....................   3-17 <               3.7.3     Performance Degradation May Occur onI                         XINERAMA Multihead Systems................   3-17 I               3.7.4     Using XINERAMA on New Desktop Systems.....   3-19 B               3.7.5     Some Combinations of Server Extensions NotI                         Supported.................................   3-20         I                                                                        ix                    8           3.7.6     Extraneous Characters Displayed When8                     Running XMAG in a Vertical MultiheadE                     Configuration Using XINERAMA..............   3-20 ;           3.7.7     Incorrect Placement of Cascade Menus in E                     Multihead Configurations Using XINERAMA...   3-20 E           3.7.8     XINERAMA Supported in 2D Mode Only........   3-20         4  Programming Release Notes  E           4.1   General Programming...........................    4-1 ;           4.1.1     Applications Are Not Displayed Properly E                     with Version 1.3-1 or higher..............    4-1 E           4.1.2     Xpoll.h Changes...........................    4-2 E           4.1.3     XLIBINT.H Changes.........................    4-3 2           4.1.4     Problem with Error Handling inE                     _XDefaultIOError..........................    4-3 2           4.1.5     Problem with Error Handling inE                     _XDefaultError............................    4-4 =           4.1.6     Motif Toolkit and X Window System Support E                     and Compatibility.........................    4-4 8           4.1.7     Run-Time and Programming EnvironmentE                     Support...................................    4-5 ;           4.1.8     Multithreaded Applications with Upcalls >                     Enabled No Longer Cause Address CorruptionE                     (Alpha Only)..............................    4-6 :           4.1.9     DECwindows Display Server Blocks Write=                     Operations When All Transport Buffers are E                     in Use....................................    4-6 5           4.1.10    Functions Calling getaddrinfo and >                     getnameinfo are not Threadsafe Over TCP/IPE                     Connections...............................    4-7 =           4.1.11    Increasing the Limit of Top-Level Widgets E                     Allowed by the UIL Compiler...............    4-7 E           4.1.12    Increased Stack Requirements..............    4-8 6           4.1.13    Privileges Required for ICE, ProxyE                     Manager, and LBX Server Processes.........    4-8 E           4.1.14    Support for Display PostScript Removed....    4-8 0           4.1.14.1    Impact on DECwindows MotifE                       Applications............................    4-9 E           4.1.14.2    Impact on Java Applications.............   4-10 &           4.1.15    Problems Using theE                     DECW$INCLUDE:INTRINSIC.H File.............   4-10            x                    ?               4.1.16    DECW$WML.EXE Looks in Current Directory I                         For DECW$WML_TOKENS.DAT...................   4-11 <               4.1.17    Running Translated Images on OpenVMSI                         Systems (Alpha Only)......................   4-11 <               4.1.18    UIL Compilation Problems with LoopedI                         Object References.........................   4-13 9               4.1.19    Compiling Applications Written in I                         Fortran...................................   4-13 I               4.1.20    Compiling Applications Written in C.......   4-14 I               4.2   Application Programming.......................   4-14 I               4.2.1     CDA Viewer Programming....................   4-14 3               4.2.1.1     Corrected Image Ident for 6                           SYS$LIBRARY:DDIF$VIEWSHR.EXEI                           (Alpha Only)............................   4-14 I               4.2.1.2     Message for Style Guide Fallback........   4-15 :               4.2.1.3     Using Logical Names with CONVERTI                           Commands................................   4-15 I               4.2.2     DEClinks Programming......................   4-16 :               4.2.2.1     DEClinks Shareable Libraries NotI                           Available (I64 only)....................   4-16 I               4.2.3     DECterm Programming.......................   4-16 I               4.2.3.1     DECCRA Sequence.........................   4-16 I               4.2.3.2     DECLFKC Sequence........................   4-16 I               4.3   OSF/Motif Toolkit (Xm)........................   4-16 A               4.3.1     OSF/Motif Release 1.2.2 and X11 Release 5 I                         and Greater Shareable Libraries...........   4-17 <               4.3.2     OSF/Motif Release 1.2.2 Callable UILI                         Compiler..................................   4-20 ;               4.3.3     OSF/Motif Release 1.1.3 Programming I                         Support and XUI...........................   4-20 @               4.3.3.1     Building Release 1.1.3 Applications in>                           the OpenVMS Alpha Environment (AlphaI                           Only)...................................   4-20 =               4.3.3.2     Building Release 1.1.3 Applications =                           in the OpenVMS I64 Environment (I64 I                           Only)...................................   4-23 8               4.3.3.3     Additional Motif Release 1.1.3I                           Compilation and Run-time Restrictions...   4-24 B               4.3.4     Memory Leaks in Cascade and Toggle ButtonsI                         Corrected (Alpha Only)....................   4-25 A               4.3.5     Memory Leaks in Bulletin Boards Corrected I                         (Alpha Only)..............................   4-26       I                                                                        xi                    ;           4.3.6     Compile-Time Incompatibilities in Motif E                     Header Files..............................   4-26 E           4.3.7     Use of _Xm Routines.......................   4-27 E           4.3.8     UID Files for Example Programs............   4-27 E           4.3.9     Motif Text Widget Translations............   4-28 8           4.3.10    Restrictions on Mixing Motif and XUIE                     Widgets...................................   4-28 E           4.4   DECwindows Extensions to Motif (DXm)..........   4-29 E           4.4.1     DXmFormSpaceButtonsEqually Restriction....   4-29 :           4.4.2     SVN Widget Does Not Support HorizontalE                     Live Scrolling............................   4-29 E           4.5   X Window System Toolkit (Xt)..................   4-29 6           4.5.1     Problem with the Implementation ofE                     XtAppAddTimeOut( ) in DECwindows..........   4-29 =           4.5.2     NULL Argument Passed to XtRemoveTimeOut() E                     Causes an Access Violation................   4-30 :           4.5.3     XtGetValues Function and Null ArgumentE                     Values....................................   4-30 =           4.5.4     Composite Class Extension Record Run-Time E                     Warning...................................   4-30 2           4.5.5     XtOpenDisplay Routine and CaseE                     Sensitivity...............................   4-31 E           4.6   X Window System Library (Xlib)................   4-31 >           4.6.1     Motif Error - Xlib: Unexpected Async ReplyE                     Fixed.....................................   4-31 >           4.6.2     XPutImage Now Displays Wide Graphic ImagesE                     Correctly.................................   4-31 E           4.6.3     Xlib Routines Now Use Recursive Locks.....   4-32 4           4.6.4     Memory Leaks in XOpenDisplay andE                     XCloseDisplay Corrected (Alpha Only)......   4-32 8           4.6.5     XOpenDisplay Calls No Longer Leave aE                     Pending Wake (Alpha Only).................   4-32 >           4.6.6     State of Event Flag Number 63 Changed OnlyE                     After Reserved (Alpha Only)...............   4-32 <           4.6.7     Xpoll.h Header File and ConnectionNumberE                     Macro Restriction.........................   4-33 8           4.6.8     Changed Record Format for ConnectionE                     Failure Error Message.....................   4-33 E           4.6.9     Retired and Changed Entry Points..........   4-33 4           4.6.10    Meaning of XConnectionNumber andE                     ConnectionNumber Changed..................   4-34 E           4.6.11    Locale Support in OpenVMS Systems.........   4-35            xii                    ?               4.6.12    XSelectAsyncEvent and XSelectAsyncInput I                         Routines .................................   4-35 I               4.6.13    Command Procedure Builds .PEN Files.......   4-36 I               4.6.14    Parameter/Protocol Datasize Mismatches....   4-36 I               4.7   X Window System Extensions and Protocols......   4-38 I               4.7.1     Using XCopyArea with XINERAMA.............   4-38 :               4.7.2     XINERAMA Does Not Correctly ReportI                         VisibilityNotify..........................   4-38 I               4.7.3     EVI Extension and Colormap Conflicts......   4-38 I               4.7.4     Dead Mouse Support........................   4-39 I               4.7.5     AccessX Extension No Longer Supported.....   4-39 B               4.7.6     Group Validation Not Performed by SecurityI                         and Application Group Extensions..........   4-39 @               4.7.7     Do Not Remove Watch Procedures from OpenI                         ICE Connections...........................   4-39 I               4.7.8     BAD_LOCAL_NODE Error When Using ICE.......   4-40 @               4.7.9     SmsGenerateClientId Does Not Generate anI                         ID........................................   4-40 I               4.7.10    Specifying Extension Include Files........   4-40 @               4.8   X Window System Internationalization LibraryI                     (Xnl).........................................   4-40 I               4.8.1     The I18N library Now Supports GB18030.....   4-40 I               4.8.2     xnl_parsedatetime.........................   4-41 I               4.8.3     xnl_langinfo..............................   4-41 I               4.9   Transport Programming.........................   4-41 I               4.9.1     User-Written Transports Not Supported.....   4-41   &         5  Documentation Release Notes  I               5.1   Getting Started With the New Desktop..........    5-1 I               5.1.1     Corrected File Specification..............    5-1 I               5.2   Using DECwindows Motif for OpenVMS............    5-2 A               5.2.1     Corrections to the Example for Changing a I                         Logo......................................    5-2 =               5.3   DECwindows Motif for OpenVMS Applications I                     Guide.........................................    5-2 =               5.3.1     Clarifications to the Finish Printing I                         Option....................................    5-2 B               5.3.2     Correction to Adding Target Screen OptionsI                         to Application Menu Items Example.........    5-3 ?               5.4   DECwindows Motif for OpenVMS Guide to Non-C I                     Bindings......................................    5-3       I                                                                      xiii                    6           5.4.1     Access to GET_CHAR_STRUCT FunctionE                     Correction................................    5-3 5           5.5   DECwindows Motif Guide to Application E                 Programming...................................    5-3 7           5.5.1     Location of UIL Source Code for the E                     OpenVMS DECburger Sample Application......    5-3 2           5.5.2     Corrections to the Help WidgetE                     Documentation.............................    5-4 E           5.6   DECwindows Extensions to Motif................    5-4 9           5.6.1     Corrected List of DXmNlayoutDirection E                     Resource Constants........................    5-4   *     A  OSF/Motif Release 1.2 Release Notes  E           A.1   Performance Improvements......................    A-1 E           A.2   Backward Compatibility........................    A-2 E           A.2.1     Visual and Behavioral Compatibility.......    A-2 >           A.3   Changes and New Features for OSF/Motif ReleaseE                 1.2...........................................    A-3 E           A.3.1     General Toolkit Changes...................    A-3 E           A.3.1.1     Include File Changes....................    A-3 E           A.3.2     Change in XT Translations.................    A-3 E           A.3.3     ANSI C Compliance.........................    A-4 E           A.3.4     Display and Screen Specific Data..........    A-4 E           A.3.5     Drag and Drop.............................    A-4 E           A.3.6     Tear-Off Menus............................    A-5 E           A.3.7     Insensitive Visuals.......................    A-5 E           A.3.8     Other Visual Changes......................    A-6 E           A.3.9     Titles for Frames.........................    A-6 E           A.3.10    Audible Warning...........................    A-6 E           A.3.11    Color Enhancements........................    A-7 E           A.3.12    Baseline Alignment........................    A-7 E           A.3.13    Expanded Traversal Set....................    A-7 E           A.3.14    Two-Dimensional Menu Traversal............    A-7 E           A.3.15    Input Focus...............................    A-7 E           A.3.16    Traversal Access Functions................    A-8 E           A.3.17    Virtual Keys..............................    A-8 E           A.3.18    Resource Management.......................    A-9 E           A.3.19    Changes for CUA and Windows Compliance....   A-10 4           A.4   Changes and Enhancements to SpecificE                 Widgets.......................................   A-10 E           A.4.1     XmClipboard...............................   A-10 E           A.4.2     XmCommand.................................   A-11          xiv                    I               A.4.3     XmList....................................   A-11 I               A.4.4     XmMessageBox..............................   A-12 I               A.4.5     XmRowColumn and Menus.....................   A-12 I               A.4.6     XmScrollBar...............................   A-12 I               A.4.7     XmScrolledWindow..........................   A-13 I               A.4.8     XmSelectionBox, XmFileSelectionBox........   A-13 I               A.4.9     XmText....................................   A-13 I               A.4.10    XmTextField...............................   A-14 I               A.4.11    XmToggleButton, XmToggleButtonGadget......   A-15 I               A.5   Motif Window Manager Enhancements.............   A-15 I               A.5.1     Changes to MWM............................   A-15 I               A.5.2     New and Enhanced MWM Resources............   A-15 I               A.5.3     New and Enhanced MWM Functions............   A-16 I               A.5.4     New MWM Action............................   A-17 I               A.6   Changes to the User Interface Language........   A-18 I               A.7   OSF/Motif List of Known Problems..............   A-19   %         B  OSF/Motif Example Programs   I               B.1   Cut and Paste Example Program.................    B-1 I               B.2   DNDDemo Example Program.......................    B-1 I               B.3   Dogs Example Program..........................    B-3 I               B.3.1     Dog Widget................................    B-3 I               B.3.2     Square Widget.............................    B-4 I               B.4   Helloint Example Program......................    B-5 I               B.5   Hellomotif Example Program....................    B-6 I               B.6   Motifanim Example Program.....................    B-6 I               B.7   Motifgif and Pict Viewing Programs............    B-7 I               B.8   Motifshell Example Program....................    B-7 I               B.9   Periodic Example Program......................    B-8 I               B.10  Textedit Example Program......................    B-8 I               B.10.1    Additional Translations...................   B-10 I               B.11  View Example Program..........................   B-11 I               B.12  Xmpiano Example Program.......................   B-13 I               B.13  Xmtravel Example Program......................   B-15 I               B.14  Additional Sample Programs....................   B-15 I               B.15  Resource Files for Example Programs...........   B-17                 I                                                                        xv                    	     Index     
     Tables  ;           1-1       Directory of Notes for DECwindows Motif E                     Version 1.6...............................    1-1   E           2-1       Logical Names Supported by DECterm........   2-25   E           3-1       Supported Versions of DECwindows Motif....    3-1   9           4-1       Names of Shareable Libraries Based on E                     X11R5 or Greater..........................   4-18   9           4-2       Names of Shareable Libraries Based on E                     OSF/Motif Release 1.2.2...................   4-18   9           4-3       Directories for Previous XUI or Motif E                     Programming Environment...................   4-21   >           4-4       Routine Names and Arguments Sent as 16-BitE                     Values....................................   4-37   E           B-1       View Menu Options.........................    B-8   E           B-2       Textedit Source Files.....................    B-9   E           B-3       Motif Sample Programs.....................   B-15                                      xvi                              I         _________________________________________________________________   I                                                                   Preface       G               These release notes describe corrections, known problems, F               and restrictions that pertain to the HP DECwindows MotifH               for OpenVMS Version 1.6 (DECwindows Motif) software on the6               OpenVMS I64 and OpenVMS Alpha platforms.  E               The notes in this manual are cumulative from DECwindows I               Motif for OpenVMS Version 1.0 and indicate any undocumented F               items that still pertain to the software. A label withinD               each note specifies when the correction or problem was               introduced.            Intended Audience   E               This manual is intended for users, system managers, and 9               programmers who work with DECwindows Motif.            Document Structure  3               This manual is structured as follows:   G               o  Chapter 1 provides an overview of the current release.   F               o  Chapter 2 contains general user release notes for all                  users.   E               o  Chapter 3 contains release notes intended for system                   managers.  >               o  Chapter 4 contains release notes intended for4                  application and system programmers.  C               o  Chapter 5 describes changes and corrections to the 4                  DECwindows Motif documentation set.  @               o  Appendix A contains excerpted material from the-                  OSF/Motif Release 1.2 Notes.   I                                                                        xi                    ?           o  Appendix B describes the OSF/Motif sample programs ,              included with DECwindows Motif.       Related Documents   @           For additional information about OpenVMS or DECwindowsD           Motif products and services, visit the following web site:  &           http://www.hp.com/go/openvms       Reader's Comments   ?           HP welcomes your comments on this manual. Please send 8           comments to either of the following addresses:  '           Internet    openvmsdoc@hp.com   -           Postal      Hewlett-Packard Company :           Mail        OSSG Documentation Group, ZKO3-4/U08(                       110 Spit Brook Rd.+                       Nashua, NH 03062-2698   )     How To Order Additional Documentation   7           For information about how to order additional D           documentation, visit the following World Wide Web address:  0           http://www.hp.com/go/openvms/doc/order       Conventions   @           The following product names may appear in this manual:  B           o  HP OpenVMS Industry Standard 64 for Integrity servers             o  OpenVMS I64             o  I64  A           All three names-the longer form and the two abbreviated D           forms-refer to the version of the OpenVMS operating system6           that runs on the Intel Itanium architecture.  B           All uses of DECwindows and DECwindows Motif refer to theE           HP DECwindows Motif for OpenVMS software; and all uses of X E           server and the X display server refer to the DECwindows X11 B           Display Server. Additionally, all uses of DECwindows XUIE           (X User Interface) refer to the DECwindows product prior to '           DECwindows Motif Version 1.0.        xii                    G               The following typographic conventions may be used in this                manual:   G               Ctrl/x           A sequence such as Ctrl/x indicates that F                                you must hold down the key labeled CtrlH                                while you press another key or a pointing-                                device button.   F               PF1 x            A sequence such as PF1 x indicates thatG                                you must first press and release the key E                                labeled PF1 and then press and release G                                another key or a pointing device button.   D               <Return>         In examples, a key name enclosed in aD                                box indicates that you press a key onH                                the keyboard. (In text, a key name is not2                                enclosed in a box.)  I                                In the HTML version of this document, this E                                convention appears as brackets, rather *                                than a box.  <                . . .           Horizontal ellipsis points inE                                examples indicate one of the following -                                possibilities:   D                                o  Additional optional arguments in a>                                   statement have been omitted.  D                                o  The preceding item or items can be=                                   repeated one or more times.   I                                o  Additional parameters, values, or other =                                   information can be entered.   D               .                Vertical ellipsis points indicate theD               .                omission of items from a code exampleG               .                or command format; the items are omitted D                                because they are not important to the5                                topic being discussed.   >               ( )              In command format descriptions,I                                parentheses indicate that you must enclose G                                the choices in parentheses if you choose -                                more than one.   I                                                                      xiii                      C           [ ]              In command format descriptions, brackets >                            indicate optional elements. You canC                            choose one, none, or all of the options. B                            (Brackets are not optional, however, in?                            the syntax of a directory name in an ?                            OpenVMS file specification or in the A                            syntax of a substring specification in 4                            an assignment statement.)  C           [|]              In command format descriptions, vertical @                            bars separating items inside bracketsA                            indicate that you choose one, none, or 8                            more than one of the options.  A           { }              In command format descriptions, braces ?                            indicate required elements; you must <                            choose one of the options listed.  9           text style       This text style represents the A                            introduction of a new term or the name E                            of an argument, an attribute, or a reason.   E                            In the HTML version of this document, this =                            convention appears as italic text.   ;           italic text      Italic text emphasizes important D                            information and indicates complete titles>                            of manuals and variables. VariablesD                            include information that varies in system?                            messages (Internal error number), in A                            command lines (/PRODUCER=name), and in ?                            command parameters in text (where dd A                            represents the predefined code for the (                            device type).  B           UPPERCASE TEXT   Uppercase text indicates a command, theD                            name of a routine, the name of a file, orC                            the abbreviation for a system privilege.                  xiv                      I                                Monospace type indicates code examples and ;               Monospace type   interactive screen displays.   G                                In the C programming language, monospace D                                type in text identifies the following?                                elements: keywords, the names of H                                independently compiled external functions?                                and files, syntax summaries, and E                                references to variables or identifiers 8                                introduced in an example.  F               -                A hyphen at the end of a command formatF                                description, command line, or code lineF                                indicates that the command or statement?                                continues on the following line.   D               numbers          All numbers in text are assumed to beI                                decimal unless otherwise noted. Nondecimal H                                radixes-binary, octal, or hexadecimal-are4                                explicitly indicated.                                                I                                                                        xv                          I                                                                         1 I         _________________________________________________________________   I                                                              Introduction     D               This chapter summarizes the corrections, restrictions,E               and known problems identified during or associated with H               the DECwindows Motif Version 1.6 software. Table 1-1 listsD               all the notes added or revised during this release andH               cross-references the sections in which they are described.  I               For a detailed description of the features and enhancements G               introduced with this release, see the HP DECwindows Motif .               for OpenVMS New Features manual.  G               Table 1-1 Directory of Notes for DECwindows Motif Version I               __________1.6______________________________________________   I               Title___________________________________Section____________   2               General DECwindows Motif Environment               Notes   C               DECwindows Logicals Created in the      Section 2.2.1 &               Wrong Logical Name Table  C               DECW$GREET.TXT Timer Added              Section 2.2.2   C               Login Box Does Not Appear               Section 2.2.3   C               XGetExtensionVersion Does Not Unlock    Section 2.2.4 /               Display When the Extension is Not                Present   C               Problem with Node Name Not Being        Section 2.2.5 0               Displayed in the Absence of DECnet  C               DECW$SERVER Process Hangs When          Section 2.2.6 2               Displaying a Java Applet Inside CSWB  +               New Desktop Environment Notes   I                                                  (continued on next page)   I                                                          Introduction 1-1                 Introduction      C           Table 1-1 (Cont.) Directory of Notes for DECwindows Motif E           __________________Version_1.6______________________________   E           Title___________________________________Section____________   ?           Worksapce Customization                 Section 2.3.1   ?           Workspace Background Color Problem      Section 2.3.2   ?           Login Text Fields Display the Password  Section 2.3.3              Application Notes   B           The Motif Window Manager Does Not       Section 2.4.10.1           Honour ACLs   (           Installation and Upgrade Notes  ?           DECwindows Motif Version Support and    Section 3.1.1            Compatibility   *           Security and Authorization Notes  ?           Buffer Overflow Reported on Xpm         Section 3.3.1 0           Library (CERT Vulnerability VU#882750)  ?           A Deprecated Kerberos API Replaced      Section 3.3.2            with New API  ?           PWDMIX Flag Now Handled Properly        Section 3.3.3   "           Desktop Management Notes  ?           Trusted Unpause Operations Allowed      Section 3.4.1   '           Proxy Server Management Notes   ?           LBX Proxy Servers Does Not Accept the   Section 3.6.1 #           Client Connection Request   +           X Display Server Management Notes   ?           Support for Choosing the Location of    Section 3.7.1 -           Dialogs in a Xinerama Configuration   E                                              (continued on next page)        1-2 Introduction           I                                                              Introduction       G               Table 1-1 (Cont.) Directory of Notes for DECwindows Motif I               __________________Version_1.6______________________________   I               Title___________________________________Section____________   '               General Programming Notes   C               Applications Are Not Displayed          Section 4.1.1 3               Properly with Version 1.3-1 or higher   C               Xpoll.h Changes                         Section 4.1.2   C               XLIBINT.H Changes                       Section 4.1.3   C               Problem with Error Handling in _        Section 4.1.4                XDefaultIOError   C               Problem with Error Handling in _        Section 4.1.5                XDefaultError   0               X Window System Toolkit (Xt) Notes  C               Problem with the Implementation of      Section 4.5.1 .               XtAppAddTimeOut( ) in DECwindows  C               NULL Argument Passed to                 Section 4.5.2 0               XtRemoveTimeOut() Causes an Access               Violation   2               X Window System Library (Xlib) Notes  C               Motif Error - Xlib: Unexpected Async    Section 4.6.1                Reply Fixed   2               X Window System Internationalization               Library (Xnl)   I               The_I18N_library_Now_Supports_GB18030___Section_4.8.1______               I                                                          Introduction 1-3                          I                                                                         2 I         _________________________________________________________________   I                                                General User Release Notes     F               This chapter contains information about DECwindows Motif                for general users.  A         2.1 OpenVMS Display Device and Layered Product Interfaces   E               This section contains release notes that pertain to the G               OpenVMS display device (SET DISPLAY) and DECwindows Motif )               layered product interfaces.   2         2.1.1 OpenVMS Display Device (SET DISPLAY)  G               This section contains notes pertaining to OpenVMS display H               devices created and managed using the SET DISPLAY and SHOWG               DISPLAY commands. For more information on these commands, D               see the HP OpenVMS DCL Dictionary: N-Z or online help.  >         2.1.1.1 SET DISPLAY/REVOKE Error Message is Misleading                 V1.3  D               The error message for revoking a cookie that has timedE               out is misleading. The error message indicates there is F               a %SYSTEM-F-BADPARAM, bad parameter value. This does not/               indicate the nature of the error.   A         2.1.1.2 I/O Error Displayed When Using SET DISPLAY/REVOKE                  V1.3  I               Using the SET DISPLAY/REVOKE command to revoke a generated, B               trusted, cookie can sometimes result in an I/O error'               similar to the following:   P               XIO:  fatal IO error 65535 (connection aborted) on X server ":0.0"R                     after 10 requests (8 known processed) with 0 events remaining.  F               This error results from the cookie being used by the SETG               DISPLAY/REVOKE command to connect to the server. Revoking E               the cookie breaks the connection to the display server.   I                                            General User Release Notes 2-1                 General User Release Notes=     2.1 OpenVMS Display Device and Layered Product Interfaces     @           Although the error appears fatal, the revoke operation*           actually completes successfully.  1     2.1.1.3 Display Devices Not Deleted Upon Exit              V1.2-6  B           When creating user-mode display devices with the DCL SET?           DISPLAY command, note that any unused devices may not B           be deleted when you log out of DECwindows Motif. Display@           devices created with SET DISPLAY are seen as permanentC           devices until used by an X client application and are not            destroyed upon exit.  ?           To avoid this problem, create supervisor-mode display            devices.       2.1.2 DECTPU  <           This section contains release notes related to the/           DECwindows Motif interface to DECTPU.   -     2.1.2.1 Small Display Monitors and DECTPU              V1.0  C           When running DECTPU for DECwindows Motif on small display C           monitors, the main window can be less than fully visible.   8           To correct this condition, follow these steps:  A           1. Add the following resources to the DECTPU section of "              your X resource file:  @              Tpu.Tpu$MainWindow.X:                             0@              Tpu.Tpu$MainWindow.Y:                             0A              Tpu.Tpu$MainWindow.Rows:                          21 A              Tpu*condensedFont:                                on @              Tpu*fontSetSelection:                             1  D           2. Copy the resource file from SYS$LIBRARY:EVE.DAT and add               the previous lines.  B           3. Use the logical name TPU$DEFAULTS to point at the new              resource file.   A              The following example references the X resource file D              EVE_SMALL_WINDOW.DAT, which defines the appropriate TPUC              window properties. The DECwindows Motif user interface B              to DECTPU is then invoked to edit the file LOGIN.COM.  "     2-2 General User Release Notes           I                                                General User Release Notes I                 2.1 OpenVMS Display Device and Layered Product Interfaces     F                  $  DEFINE TPU$DEFAULTS SYS$LOGIN:EVE_SMALL_WINDOW.DAT7                  $  EDIT/TPU/INTER=DECWINDOWS LOGIN.COM   0         2.2 General DECwindows Motif Environment  E               This section contains release notes that pertain to the F               general DECwindows Motif user environment. This includes@               corrections, restrictions, and known problems thatD               are common to both the New Desktop and the Traditional.               DECwindows Desktop environments.  I         2.2.1 DECwindows Logicals Created in the Wrong Logical Name Table                  V1.6  C               In most cases DECwindows uses LNM$FILE_DEV logical to #               create logical names.   E               In general, the first table pointed by the LNM$FILE_DEV D               logical is the LNM$PROCESS table. If an user has tableD               other than LNM$PROCESS table as the first table in theG               search list, then all DECwindows logicals will be created                in this table.  D               Now DECwindows has been modified to create the logical8               names explicitly in the LNM$PROCESS table.                                      I                                            General User Release Notes 2-3                 General User Release Notes,     2.2 General DECwindows Motif Environment    $     2.2.2 DECW$GREET.TXT Timer Added             V1.6  >           The login process of the New Desktop facilitates the/           display of a custom greeting message.   ?           If an user does not complete the login process within ;           a specified timeout interval, the custom greeting 9           message pops-up and the login process is reset. =           This timeout interval value (in seconds) can be set :           by assigning the appropriate timeout interval to:           the "Dtgreet*timeout" resource in the "cde$user_;           defaults:[config.c]xresources.dat" resource file.   3           The default timeout value is 180 seconds.   #     2.2.3 Login Box Does Not Appear              V1.6  A           There are two circumstances under which this problem is            observed:   E           o  After three consecutive failed login attempts, the LOGIN C              box does not appear. The problem is seen only when the =              DECW$SERVER_AUDIT_LEVEL is set to one or higher.   C           o  If an user tries to login to DECwindows when the usage B              exceeds the active license limit, the following errorB              message is displayed with the pop-up acknowledge box:  ;              Attempted usage exceeds active license limits.   E              When the user acknowledges this box, grey screen appears /              but the login box does not appear.   A           This problem has been corrected in DECwindows Motif for            OpenVMS Version 1.6.  ?     2.2.4 XGetExtensionVersion Does Not Unlock Display When the "           Extension is Not Present             V1.6  >           XGetExtensionVersion does not unlock display when no           extension is present.   "     2-4 General User Release Notes           I                                                General User Release Notes I                                  2.2 General DECwindows Motif Environment     G         2.2.5 Problem with Node Name Not Being Displayed in the Absence                of DECnet                  V1.6  E               If the DECnet transport is not configured on a machine, I               some of the DECwindows applications do not display the node                name as expected.   E         2.2.6 DECW$SERVER Process Hangs When Displaying a Java Applet                Inside CSWB                  V1.6  B               The CSWB opens multiple threads with the DECW$SERVERG               process. This causes a rare race condition, which in turn D               causes a deadlock, giving an illusion of process hang.  !         2.2.7 Web Browser Support                  V1.5  I               The HP Secure Web Browser (SWB) is the officially supported A               web browser for the HP OpenVMS Alpha and HP OpenVMS D               I64 operating systems. SWB is a licensed part of theseH               operating systems and is based on the Mozilla Web Browser,F               which is designed for standards compliance, performance,               and portability.  H               The OpenVMS Alpha version of the browser is available from%               the following location:   K               http://h71000.www7.hp.com/openvms/products/ips/cswb/cswb.html   G               This page contains installation and running instructions, @               as well as information about hardware and softwareC               prerequisites, system parameters, account quotas, and                 problem reporting.  H               The OpenVMS I64 version of the browser is a part of one orI               more of the OpenVMS I64 Operating Environments (OEs) and is G               included on the OE distribution media. See the HP OpenVMS I               I64 Software Product Description (SPD) for more information G               on the specific OE bundles available with this release of                OpenVMS.  F                 ________________________ Note ________________________  F                 There may be instances where running Java applicationsE                 from the SWB will cause the system to freeze briefly.   I                                            General User Release Notes 2-5                 General User Release Notes,     2.2 General DECwindows Motif Environment    C              This is due to the way the DECwindows X display server A              currently handles non-blocking write operations to a A              requesting client application. See Section 4.1.9 for 2              more information on this restriction.  C              ______________________________________________________   B     2.2.8 Scaled Bitonal Images Now Display Correctly (Alpha Only)             V1.5  E           Previously, on systems running DECwindows Motif for OpenVMS A           Alpha Version 1.3 or higher, scaled bitonal images were B           displayed incorrectly. The top-right corner of the image:           would overlay the top-left quarter of the image.  A           This problem has been corrected in DECwindows Motif for            OpenVMS Version 1.5.  E     2.2.9 Applications That Issue Lengthy Server Requests Now Respond             Correctly (Alpha Only)             V1.5  B           DECwindows Motif client applications that issue multiple?           requests requiring lengthy replies from the server no A           longer become unresponsive. Examples of such operations A           include requests for the entire contents of a screen or E           requests to list fonts that require access to font servers.   C           This problem has been corrected with DECwindows Motif for            OpenVMS Version 1.5.  B     2.2.10 Applications Running Over the LOCAL Transport No Longer            Cause System Lag              V1.5  B           Client applications using the LOCAL transport on systems@           running DECwindows Motif for OpenVMS Alpha Version 1.3C           or higher no longer enter a compute-bound state when they -           should normally be in a wait state.   ?           This problem has been corrected with DECwindows Motif A           for OpenVMS Version 1.5. However, there remains a small @           risk of the problem occurring with client applicationsA           that use multiple kernel threads, regardless of whether 2           multithreading support has been enabled.  "     2-6 General User Release Notes           I                                                General User Release Notes I                                  2.2 General DECwindows Motif Environment     >         2.2.11 Applications That Use GKS May Fail Unexpectedly                 V1.3  F               In some instances, applications that use the HP GraphicsD               Kernel System for OpenVMS (GKS) may fail when run fromE               DECwindows Motif. The problem is caused by a contention E               at the AST level between read and reply events. In this E               situation, the application process hangs, and the error C               message "unexpected asynchronous reply" is displayed.   F         2.2.12 Request-Intensive Applications May Pause Before Closing                 V1.3  B               There may be a slight delay when a request-intensiveD               application running over a LOCAL network connection isE               forced to close via the Window Manager. For example, an E               attempt to close the DECW$EXAMPLES:ICO application from B               a LOCAL display results in a slight pause before the(               application window closes.  H               This is a result of resource contention between the WindowB               Manager (DTWM) and server processes. To prevent thisB               problem from occurring, decrease the priority of theF               server process using the DECW$SERVER_PRIORITY parameter,H               as described in HP DECwindows Motif for OpenVMS Management               Guide.  :         2.2.13 Support Discontinued for Display PostScript                 V1.2-6  I               Starting August 1, 1998, support was discontinued for Adobe F               Display PostScript software resulting from Adobe SystemsG               Incorporated discontinuing its former ongoing support for !               Display PostScript.   C               This action has had a varying degree of impact on the B               behavior of those DECwindows Motif applications thatF               used the Adobe Display PostScript software. For example,G               starting with DECwindows Motif for OpenVMS Version 1.2-6, E               Bookreader can no longer display graphics in PostScript                format.   I                                            General User Release Notes 2-7                 General User Release Notes,     2.2 General DECwindows Motif Environment    =           For information about the effects of this action on E           specific DECwindows applications, see the following release            notes:  (           o  Bookreader, Section 2.4.1.1  !           o  CDA, Section 2.4.2.2   -           o  DECwindows mail, Section 2.4.6.1   @           To learn about the possible impact to user-written andD           third-party applications designed for the DECwindows Motif*           environment, see Section 4.1.14.  -     2.2.14 Limited Support for Tear-Off Menus              V1.2-3  C           The following applications do not support tear-off menus:              o  CDA Viewer              o  Notepad             o  Print Screen   @     2.2.15 Implications of the Message, "System Menu Bar: Pseudo            Mouse Not Available"              V1.2-3  =           "System Menu Bar: Pseudo Mouse not available" is an >           informational message that is included in the user's?           SYS$LOGIN:DECW$SM.LOG file when you run a session. It @           is not an error message. The X display server providesA           pseudomouse mode automatically, which allows you to use .           arrow keys to move the mouse cursor.  >     2.2.16 Printing from Applications Linked Against OSF/Motif            Release 1.1.3             V1.2  @           Applications that are linked against OSF/Motif ReleaseE           1.1.3 may end abruptly when you attempt to print on systems B           that do not have print queues. Any layered products thatB           linked against the OSF/Motif Release 1.1.3 libraries andC           use the standard DECwindows print dialog ("print widget")            are also affected.  "     2-8 General User Release Notes           I                                                General User Release Notes I                                  2.2 General DECwindows Motif Environment     A               As a possible solution, either avoid displaying the F               DECwindows print dialog, or define a print queue on yourF               system. The print queue does not have to be connected toH               a printer to accept print jobs. Assign a name to the printH               queue that indicates the print queue is not connected to a1               printer, for example, NULL_PRINTER.   #         2.3 New Desktop Environment   I               This section contains release notes that pertain to the New "               Desktop environment.  %         2.3.1 Worksapce Customization                  V1.6  E               On the New Desktop, workspace can now be customized for &               following functionality:  D               o  Color of the workspace button on the Common DesktopE                  Environment (CDE) front panel can now be tied to the 3                  color of the background workspace.   H               o  Number of workspaces can be limited by a combination of                  resources.   E               o  Option to ADD or DELETE a workspace in the workspace G                  button's pop-up menu is not enabled when the workspace 2                  count reaches maximum or minimum.  D               o  Subpanel can now be automatically removed on buttonF                  release or equivalent after a specific time interval.  G               See HP DECwindows Motif for OpenVMS New Features for more <               information about the workspace customization.  0         2.3.2 Workspace Background Color Problem                 V1.6  G               The background color changes at the bottom of the screen, I               if the screen resolution is greater than 1024 pixels in the G               y direction. The SkyLight and SkyDark backdrops show this !               behavioral problem.   E               This has been corrected in DECwindows Motif for OpenVMS                V1.6.   I                                            General User Release Notes 2-9                 General User Release Notes     2.3 New Desktop Environment     0     2.3.3 Login Text Fields Display the Password             V1.6  :           If you press the Return key to type the passwordD           immediately after entering the Username, the password willB           be displayed in the Username text field for a noticeable           amount of time.   A           This has been corrected in DECwindows Motif for OpenVMS            V1.6.   3     2.3.4 Default Width of the Calculator Increased              V1.5  B           The default width of the New Desktop calculator (DtCalc)B           has been increased. It is now wide enough to accommodateA           and display all digits in a value when the fixed-length %           display format is selected.   @     2.3.5 File Manager No Longer Hangs During Large Copy or Move           Operations             V1.5  @           The File Manager (dtFile) no longer hangs in the RWMBXE           state when copying or moving a large number of files (30 to A           50 depending on the name length) in a single operation.   D           However, note that moving a large collection of files in aD           single operation can still result in slower performance as3           compared to moving smaller sets of files.   A     2.3.6 File Manager Cancels Restore Operations Properly (Alpha            Only)              V1.5  ?           When attempting to put back a file from the Trash Can B           that has the same name as an existing file, File ManagerD           displays a dialog box that prompts you whether to continueD           or cancel the restore operation. Choosing Cancel no longer+           causes the File Manager to crash.   #     2-10 General User Release Notes            I                                                General User Release Notes I                                               2.3 New Desktop Environment     B         2.3.7 Style Manager Displays Incorrect Security Options on               Multihead Systems                  V1.3  I               When using the Style Manager to access the Security Options H               dialog box from a screen other than screen 0, the settings7               shown in the dialog box may be incorrect.   I               To prevent this from occurring, always display the Security C               Options dialog box from screen 0. Use the Set Default I               Screen tool to select the screen on which the Style Manager                displays.   G               Note that this problem only occurs on multiheaded systems *               configured without XINERAMA.  9         2.3.8 Screen Saver and Screen Lock Set by Default                  V1.2-6  C               Note that at initial DECwindows Motif startup, Screen F               Saver (with a 10-minute timeout) and Screen Lock (with a8               30-minute timeout) are enabled by default.  B               You can modify these defaults by accessing the StyleG               Manager and changing (and subsequently saving) the Screen                Saver settings.   -         2.3.9 Session Manager Logging Problem                  V1.2-5  H               In some cases, the New Desktop Session Manager (DtSession)I               continues to log errors to its log file until all free disk H               space is filled. These errors could occur, for example, ifI               DECW$DISPLAY is set to an incorrect value or if CDE$SYSTEM_ C               DEFAULTS:[BIN]DTSCREEN.EXE is not properly installed.   E               If on the New Desktop, DtSession is unable to start the G               Screen Saver (DTSCREEN), it logs an error to the log file F               device:[user.DT]ERRORLOG. DtSession logs this error at aF               user-settable interval controlled by the Style Manager's.               "Time Per Background" parameter.  @               To workaround this problem, increase the "Time PerD               Background" parameter to the maximum (120 minutes), orI               exit the New Desktop when you are done with it, rather than !               locking the screen.   I                                           General User Release Notes 2-11                 General User Release Notes     2.3 New Desktop Environment     B     2.3.10 File Manager Problems with Extended File Specifications             V1.2-5  B           The following are known problems or restrictions related?           to the File Manager and its handling of extended file            specifications:   D           o  The "File/New Folder" menu item can handle the creationE              of a folder when the path length exceeds 255 characters, E              but the folder cannot be displayed (it is hidden). These 2              files can be viewed at the DCL level.  C           o  The "File/Find/File" menu item cannot find a file with C              file name that exceeds 235 characters if the full file A              name has been entered in the dialog's form field. To D              avoid the problem, use wildcards to conduct the search.  7     2.3.11 DECwrite Icon Does Not Open DECwrite Program              V1.2-5  ?           Although the DECwrite icon exists on the New Desktop, 3           clicking on the icon will have no effect.   =     2.3.12 Delay When Exiting a Session with Open TPU Windows              V1.2-4  ;           Users will experience a one-minute delay for each <           DECwindows Text Processing utility (DECTPU) windowB           displayed when exiting the session or when saving a home           session.  C           The DECwindows interface for DECTPU (EVE editor) requires B           notification if its state needs to be saved, but it doesC           not respond to that notification sent by Session Manager. D           The Session Manager waits one minute for a response before-           continuing, resulting in the delay.   -     2.3.13 Viewing TIF Files with dximageview              V1.2-4  E           When using dximageview to view TIF-formatted files from the D           CDE$SYSTEM_DEFAULTS:[APPCONFIG.HELP.C.GRAPHICS] directory,E           the following warning messages similar to the following are            displayed:  #     2-12 General User Release Notes            I                                                General User Release Notes I                                               2.3 New Desktop Environment     O               TIFFOpen: Warning, unknown field with tag 34209 (0x85a1) ignored. P               TIFFOpen: XResolution: Rational with zero denominator (num = 200).               .                .                .   ?               Note this error only occurs with the TIF files in D               CDE$SYSTEM_DEFAULTS:[APPCONFIG.HELP.C.GRAPHICS]; it isF               only a warning. The file is still displayed correctly by               the image viewer.   '         2.3.14 Text Editor Restrictions                  V1.2-4  C               The Text Editor application, which is part of the New G               Desktop, is described in Chapter 10 of the Common Desktop H               Environment: User's Guide. Currently, it has the following&               issues and restrictions:  ?               o  The reference page for Text Editor describes a F                  client/server implementation of the Text Editor. ThisF                  release of the Text Editor supports the -"standAlone"@                  option only and is not built as a client/server                  application.   E               o  The spell-checking function described in the section I                  "To Correct Misspelled Words" is not implemented in this ,                  version of the Text Editor.  G               o  The Text Widget upon which the New Desktop Text Editor G                  is based does not set the size of a tab to exactly the F                  width of eight (8) characters; it is usually slightlyC                  larger. When displaying text with a combination of I                  spaces and tabs, text may not appear vertically aligned.   ;         2.3.15 Some File Names are Displayed in UNIX Format                  V1.2-4  E               In the Application Manager Find dialog box and in error B               messages reported by the Help Viewer, file names areF               displayed in UNIX format rather than in standard OpenVMSH               format. For example, SYS$SYSROOT:[SYSMGR]LOGIN.COM appears/               as /sys$sysroot/sysmgr/login.com.   I                                           General User Release Notes 2-13                 General User Release Notes     2.3 New Desktop Environment     ,     2.3.16 Front Panel Clock is an Icon Only             V1.2-4  D           The New Desktop Front Panel Clock is an animated icon thatC           displays the current system time using an analog display. E           The icon has no other function and does not support single- +           click or double-click operations.   )     2.3.17 ToolTalk Actions Not Supported              V1.2-4  ?           Creation of ToolTalk Action definitions in the Action D           Definition files (*.dt) as described in the Common DesktopA           Environment: Advanced User's and System Administrator's @           Guide is not supported. Although some ToolTalk actionsB           exist in the Action Definition files installed with thisE           product, modification of these actions is not supported and 9           could cause some New Desktop functions to fail.   7     2.3.18 Session Manager Save and Restore Limitations              V1.2-4  D           The Session Manager supplied with the New Desktop supportsD           the WM_SAVE_YOURSELF protocol for Bookreader, DECterm, and           Calendar.   B           Applications that have been written to take advantage of           this protocol can:  <           o  Save their state when the user exits a session.  @           o  Restore a state when the user starts a new session.  D           The New Desktop applications support save and restore, butC           many existing DECwindows Motif applications have not been <           modified to support the WM_SAVE_YOURSELF protocol.  @           The impact of this difference between existing and newD           applications can be seen during a logout/login sequence as           follows:  ?           o  Applications supporting save/restore create a main B              window if they were running when the user logged out.  A           o  Applications that do not support save/restore do not #              automatically restart.   #     2-14 General User Release Notes            I                                                General User Release Notes I                                               2.3 New Desktop Environment     I               An example of an existing DECwindows Motif application that 7               supports save/restore is DECwindows Mail.   F                 ________________________ Note ________________________  >                 This Session Manager application should not beD                 confused with the X Session Management protocol that=                 is part of the DECwindows X11 Display Server.   F                 ______________________________________________________  3         2.3.19 File Manager Search List Limitations                  V1.2-4  H               The File Manager application has the following limitations?               with search lists in the New Desktop environment.   C               o  If you specify a folder (directory) name, which is I                  strictly a logical name, and the logical name translates G                  to a search list, only the first directory encountered 1                  in the search list is displayed.   B               o  When displaying a directory whose name includes aD                  search-listed device, all directories in the searchH                  path are displayed. If more than one directory with theE                  same name exists in the search path, an icon appears F                  for each instance of that directory. If more than oneG                  file with the same name exists in the search path, the F                  behavior depends on whether the Show Top Version OnlyG                  filter option has been selected. If selected, only one H                  icon of the file with the highest version is displayed.E                  If not selected, all versions from all locations are F                  displayed. However, if more than one of the files hasH                  the same version number, any action to any of the filesI                  with that version applies to the first occurrence of the )                  file in the search path.                     For example, C                  suppose the files SYS$SPECIFIC:[SYSMGR]TOOLS.DIR;1 A                  and SYS$COMMON:[SYSMGR]TOOLS.DIR;1 both exist in >                  a system. If a user switches to the directoryC                  SYS$SYSROOT:[SYSMGR], two icons represent the file E                  TOOLS.DIR. Operations performed on either of the two E                  icons work identically. New files are created in the F                  first directory in the search path. In addition, some?                  actions for these icons may not work properly.   I                                           General User Release Notes 2-15                 General User Release Notes     2.3 New Desktop Environment     :              To work around this problem, specify explicitA              directory names when a conflict occurs, for example, :              SYS$SPECIFIC:[SYSMGR] or SYS$COMMON:[SYSMGR].  9     2.3.20 Login and Pause Screen Text Field Restrictions              V1.2-4  D           The following sections provide information about the Login.           Screen and Pause Screen text fields.  E     2.3.20.1 Control Characters Not Recognized When Entering Username   ;           The New Desktop does not support entering control B           characters in the login Username text field. If entered,?           these characters are discarded. This differs from the B           DECwindows login Username text field which supports such           key sequences as:   @           o  Ctrl/U, Ctrl/J, or F13 (deletes to beginning of the              line)  C           o  Ctrl/H or F11 (positions to the beginning of the line)   6           o  Ctrl/E (positions at the end of the line)  E           The New Desktop does support Ctrl/U, which when typed while D           entering a password at login or when unpausing the screen,9           erases any characters entered up to that point.   =     2.3.20.2 Use Return Key to Move Between Login Text Fields   E           Because the Username text field and Password text field are E           different dialog boxes in the New Desktop, press the Return D           key to move the cursor from the Username text field to theC           Password text field. The Tab key does not move the cursor D           to the next text field; rather, this action highlights the           OK button.  A     2.3.20.3 First Character Discarded When Entering Pause Screen               Password   B           If the workstation is paused and the Password dialog boxA           is not displayed, the first character typed is ignored. E           This differs from the DECwindows pause screen, which always '           accepts any characters typed.   #     2-16 General User Release Notes            I                                                General User Release Notes I                                               2.3 New Desktop Environment     F               When using the New Desktop, use a nontyping key, such asH               Shift, or move the mouse to redisplay the Pause dialog boxF               before entering your password. If you are unsure of whatE               you have already typed, you can use Ctrl/U to erase the "               Password text field.  <         2.3.20.4 Text on the Welcome Screen is Not Displayed  E               If the 100-dpi fonts are not included in the X server's F               font path, the welcome text is not displayed on the blueG               welcome screen that appears immediately after logging in. I               This may also occur if you are displaying your session on a                remote X server.  )         2.3.21 Font Selection Limitations                  V1.2-4  G               On the New Desktop, Style Manager contains a control that G               displays a dialog box used to select font size. Selecting G               a new font size affects only New Desktop applications and E               does not affect existing DECwindows Motif applications.   ,         2.3.22 Default Workspace Limitations                 V1.2-4  A               The New Desktop provides a default backdrop for the D               four default workspaces. You can change or even selectD               Nobackdrop using the Backdrop control located in Style               Manager.  E               When no backdrop is selected, you cannot drag icons and D               place them on the backdrop of the desktop. If you dragF               an icon and release it, it snaps back to File Manager or"               Application Manager.  I               Icons that were dropped on the background before Nobackdrop 9               was selected remain and function correctly.            2.4 Applications  F               The following sections contain notes related to specific,               DECwindows Motif applications.  I                                           General User Release Notes 2-17                 General User Release Notes     2.4 Applications         2.4.1 Bookreader  ?           This section contains release notes pertaining to the !           Bookreader application.   2     2.4.1.1 Support for Display PostScript Removed             V1.2-6  E           With the removal of the support for Display PostScript from E           DECwindows Motif, Bookreader no longer supports the display B           of PostScript artwork in online manuals. When BookreaderD           detects PostScript artwork, it displays a full-size figureC           window with a large X overlayed with an error message box +           containing the following message:   2           Unable to display PostScript(R) graphic..           This feature is no longer available.  !           There is no workaround.   
     2.4.2 CDA   A           This section contains release notes that pertain to the D           Compound Document Architecture (CDA) Run-Time Services and4           CDA Viewer components of DECwindows Motif.  C     2.4.2.1 Viewing Large, Color DDIF Files using eXcursion Version              7.1              V1.3  D           If you are unable to display large, color DDIF files whileD           running the CDA Viewer from an eXcursion X Server session,9           HP recommends that you do one of the following:   A           o  Display the DDIF file from a CDA Viewer session that A              uses either the local or DECnet transport outside of               eXcursion.   4           o  Upgrade the HP PATHWORKS 32 software to;              Version 7.2 or later. See the OpenVMS web site >              (http://www.hp.com/go/openvms) for information on/              obtaining a copy of this software.   #     2-18 General User Release Notes            I                                                General User Release Notes I                                                          2.4 Applications     6         2.4.2.2 Support for Display PostScript Removed                 V1.2-6  I               With the removal of the support for Display PostScript from E               DECwindows Motif, CDA no longer supports the display of G               PostScript source. The PostScript option has been removed F               from the CDA Viewer. If you attempt to view a PostScriptD               file from the character cell interface CDA viewer, the4               viewer displays the following message:  ;               %CDA-E-UNSUPFMT, unsupported document format.   %               There is no workaround.            2.4.3 Clock   I               This section contains release notes pertaining to the Clock                application.  F         2.4.3.1 Clock Updates Correctly after the System Time is Reset                 (Alpha Only)                 V1.5  B               The Clock application now updates correctly when theE               system time is set back to an earlier date and/or time. G               Previously in this circumstance, the analog, digital, and F               date displays would post updates only when the mouse was*               moved over the Clock window.           2.4.4 DECterm   C               This section contains release notes pertaining to the "               DECterm application.  I         2.4.4.1 Graphics Applications Using ReGIS No Longer Cause DECterm %                 to Crash (Alpha Only)                  V1.5  E               Previously, on systems running DECwindows Motif Version I               1.3 or higher, client graphics applications that used ReGIS H               (graphics instruction set for video terminals) crashed the>               DECterm controller due to thread stack overflow.  G               This problem has been corrected with DECwindows Motif for "               OpenVMS Version 1.5.  I                                           General User Release Notes 2-19                 General User Release Notes     2.4 Applications    =     2.4.4.2 DECterm Windows Positioned Correctly (Alpha Only)              V1.5  E           DECterm windows are now displayed in the location specified B           by the DECW$TERMINAL.x and DECW$TERMINAL.y resources and5           WM_NORMAL_HINTS is now being set correctly.   B           Resetting the resources Mwm*clientAutoPlace (TraditionalC           DECwindows Desktop) or Dtwm*clientAutoPlace (New Desktop) E           to FALSE is no longer necessary for proper placement of the            window.   D     2.4.4.3 Use CREATE/TERMINAL/DETACH to Display Broadcast Messages             V1.5  B           By default, DECterm windows are created as subprocesses.B           Regardless of their process settings, these subprocessesC           cannot receive broadcast messages, since OpenVMS does not ;           recognize them as connected to a terminal device.   B           To enable the display of broadcast messages in a DECtermB           window, manually create the DECterm window as a detached?           process using the DCL command CREATE/TERMINAL/DETACH.   ;     2.4.4.4 Using CREATE/TERMINAL with IPv6 Support Enabled              V1.5  @           The CREATE/TERMINAL command may fail if the DECW$IPV6_>           SUPPORT logical name has been defined as TCP_IS_IPV6A           in the process (or job) table but not in the system (or E           group) table. The failure occurs when the specified display @           uses the TCPIP transport and the node name is an IPv6-?           formatted address (or is only accessible via an IPv6-            enabled transport).   B           In these cases, the terminal controller detached processA           does not see the value of the DECW$IPV6_SUPPORT logical B           name, and therefore, assigns the default TCPIP transport           value of INET.  ?           If a conflict occurs, change the value of the network @           transport for the display device to INET or INET6, andD           repeat the CREATE/TERMINAL command. For a complete list ofE           the available transport values, see the HP DECwindows Motif '           for OpenVMS Management Guide.   #     2-20 General User Release Notes            I                                                General User Release Notes I                                                          2.4 Applications     E         2.4.4.5 Use ignoreVisibility Resource When Displaying DECterm G                 Windows with eXcursion or on XINERAMA Multihead Systems                  V1.3-1  I               A new resource, ignoreVisibility, has been added to prevent E               scrolling problems that occur when displaying a DECterm G               window using eXcursion or on a XINERAMA multihead system. B               To prevent these problems from occurring, insert the;               following line into the DECterm options file:   &               *.ignoreVisibility: True  H               To save and activate the setting, choose Save Options, and9               then close and restart all DECterm windows.   C         2.4.4.6 Invoking DECterm May Fail while Kerberos is Enabled                  V1.3  H               When using Kerberos authentication, the DECterm controllerC               may fail to start. The workaround for this problem is C               to change SYLOGIN.COM so that Kerberos is initialized B               (@SYS$MANAGER:KRB$SYMBOLS.COM) within the MODE_OTHER%               section of SYLOGIN.COM.   I         2.4.4.7 Euro Currency Symbol May Not Display Correctly When Using                  eXcursion                  V1.3  D               Due to differences in how the euro symbol is supportedH               between eXcursion and DECwindows Motif, the symbol may notI               display correctly on DECterm windows invoked via eXcursion. G               DECterm substitutes Latin-9 fonts with equivalent Latin-1 E               fonts, causing problems with the display of the symbol.   E               To prevent font substitution from occurring, modify the G               eXcursion font alias files, as described in the eXcursion G               release notes. The release notes describe how to edit the G               alias files, and describe additional restrictions related 5               to support of the euro currency symbol.       I                                           General User Release Notes 2-21                 General User Release Notes     2.4 Applications    @     2.4.4.8 Text Does Not Display Properly on XINERAMA MultiheadE             Systems using Powerstorm 4d20 Graphics Cards (Alpha Only)              V1.3  =           In a multihead configuration that uses the XINERAMA ?           extension and Powerstorm 4d20 graphics cards, DECterm B           windows may not display text properly. However, keyboard#           input is still processed.   A           To correct this issue, refresh the text in the affected C           DECterm windows by running the xrefresh utility from each            window, as follows:   $           $  RUN DECW$UTILS:XREFRESH  $     2.4.4.9 Shrinking Window Problem             V1.2-5  E           If the XUI window manager is in use, "Auto Resize Terminal" E           is on, and you used the mouse to resize the DECterm window, A           the DECterm window shrinks. To workaround this problem, =           add the following line to the DECterm resource file $           DECW$TERMINAL_DEFAULT.DAT:  7           DECW$TERMINAL.main.terminal.useWMHints: false   C           If you make this change, be aware that the window manager E           will report the size of the DECterm window in pixels rather ?           than character cells. Also, if you maximize a DECterm E           window, it might not properly restore to its previous size. ,           However, it will no longer shrink.  '     2.4.4.10 DECterm Resource File Name              V1.2-4  B           The locale of the display is now used to create the file@           name of the DECterm resource file. For example, if theB           locale is set to "ja_JP", then the default resource file7           name becomes DECW$TERMINAL_DEFAULT_JA_JP.DAT.   A           However, DECterm continues to use the old resource file C           name until the user selects Save Options at least once in C           the particular locale. The default resource file name for B           DECterm continues to be DECW$TERMINAL_DEFAULT.DAT if the7           locale meets any of the following conditions:              o  Is "C"   #     2-22 General User Release Notes            I                                                General User Release Notes I                                                          2.4 Applications     $               o  Starts with "en_US"  "               o  Contains "8859-1"  2         2.4.4.11 Maximum Number of DECterm Windows                 V1.2-4  E               A DECterm controller can create a maximum of 23 DECterm F               windows. This occurs because DECterm needs an event flagG               for each terminal window in use. There are 23 event flags G               that DECterm can use. (Event flag 0 and event flags 24-32 4               are not available for DECterm to use.)  E               If you need more than 23 DECterm windows, then you must H               create a new controller. To create a new controller, enter$               the following command:  !               $ MCR DECW$TERMINAL   F               Note that the window from which this command is executedH               cannot be used for anything else because this command doesG               not return until the last DECterm window is closed. After D               starting the controller with this method, the user canD               create another 23 DECterm windows with the DCL command               CREATE/TERMINAL.  &         2.4.4.12 Resizing the Terminal                 V1.2-3  I               If you maximize the DECterm window when you enable the Auto F               Resize Terminal window option, the window is expanded toH               its nearest cell boundary; the window does not necessarilyG               occupy the entire screen. The Restore options continue to %               function appropriately.   2         2.4.4.13 Reporting the DECterm Window Size                 V1.2-3  G               When you enable the Show Feedback option in the Workspace F               Options dialog box of the Window Manager, and you resizeE               a DECterm window, the size of the window is reported in +               characters instead of pixels.   I                                           General User Release Notes 2-23                 General User Release Notes     2.4 Applications    -     2.4.4.14 Changing the Auto Repeat Setting              V1.2-3  B           You cannot change the Auto Repeat setting in the DECtermE           Keyboard Options dialog box. Instead, change the setting in E           the Keyboard dialog box in the Session Manager (Traditional =           DECwindows Desktop) or Style Manager (New Desktop).   8     2.4.4.15 Timeout for Displaying the Copyright Notice             V1.2-3  B           If keyboard or mouse activity does not take place for 10@           seconds after the copyright notice is displayed on theB           terminal, the notice disappears from the DECterm screen.       2.4.4.16 Selecting Fonts             V1.2  D           Not all fonts work properly with DECterm. DECterm emulates@           a character-cell terminal, and, therefore, expects the=           fonts to be monospaced, fixed-width fonts (such as, D           CharCell), where each glyph possesses the same pixel widthC           and the ascenders and descenders do not extend beyond the E           bounding box. Proportional fonts can be specified, but they (           produce unpredictable results.  @           Furthermore, DECterm fonts are supplied in families ofB           26 related fonts, including variations for bold, double-B           width, double-width/double-height, normal, and condensedE           characters. Also, DECterm fonts include special characters, <           such as the Line Drawing and the DIGITAL Technical@           character sets. A DECterm font family is identified by%           the font naming convention.   C           Use of fonts that do not have all the related font family ?           variations, fonts that do not have the needed special @           characters, or font families that do not adhere to theC           DECterm font family naming conventions, may not result in >           an optimal display or otherwise perform as expected.  ?           If DECterm cannot find a selected font, or if DECterm D           encounters a font not present in the selected font family,A           a warning message is displayed indicating that the font D           cannot be found. DECterm then proceeds to use the fallback-           replacement for the specified font.   #     2-24 General User Release Notes            I                                                General User Release Notes I                                                          2.4 Applications     0         2.4.4.17 Supported DECterm Logical Names                 V1.1  I               Table 2-1 describes the logical names that are supported by G               DECterm. If you do not define these logical names in your F               LOGIN.COM file, the terminal controller uses the default               values.   I         Table_2-1_Logical_Names_Supported_by_DECterm_____________________   I         Logical_Name______________________Description____________________   F         DECTERM_DIAG                      Enables diagnostic messages.  F         DECTERM_SHOW_PARSING              Shows characters as they are1                                           parsed.   I         DECW$DECTERM_OUTPUT               Name of diagnostic output file; @                                           default is SYS$OUTPUT.  G         DECW$DECTERM_REGIS_CURSOR         Specifies which cursor to use 4                                           for ReGIS.  I         DECW$TERMINAL_NODENAME            Node name used by controller if F                                           it cannot find another name.  G         DECW$DECTERM_CTRL_SSRWAIT         Sets the SSRWAIT flag for the :                                           controller to 1.  F         DECW$DECTERM_CTRL_PSWAPM          Sets the PSWAPM flag for the:                                           controller to 1.  I         DECW$DECTERM_CTRL_WSEXTENT        Sets the WSEXTENT quota for the 5                                           controller.   H         DECW$DECTERM_CTRL_WSQUOTA         Sets the WSQUOTA quota for the5                                           controller.   C         DECW$DECTERM_DISABLE_QUOTA_       Turns off quota checking.          CHECKING  @         DECW$DECTERM_MEM_DIAG             Shows controller quotaI         __________________________________calculations.__________________   0         2.4.4.18 Printing to an Attached Printer                 V1.1  A               Printing to a port device requires you to have read D               and write privileges on that port. You cannot print byI               allocating the device, since the controller requires access A               to the device. Instead, set the device to WORLD:RW.   I                                           General User Release Notes 2-25                 General User Release Notes     2.4 Applications    ?           For example, to use the printer port TTA3:, enter the @           following command from a privileged account or include1           the command in the system startup file:   0           $ SET PROTECTION=WORLD:RW TTA3:/DEVICE  0     2.4.4.19 Improving Hold Screen Response Time             V1.1  C           If the hold screen key response time is too slow, add the A           following lines to your DECW$TERMINAL_DEFAULT.DAT file:   6           DECW$TERMINAL.main.terminal.syncFrequency: 19           DECW$TERMINAL.main.terminal.batchScrollCount: 1   A           Using these resources can affect the performance of the A           DECterm window. The actual impact on performance varies A           from site to site. You can trade off scrolling speed to B           hold-screen response time. A faster hold-screen responseE           results in a slower scrolling speed. The default values for 5           these resources are 10 and 0, respectively.        2.4.4.20 DECterm Graphics              V1.1  D           The following information is specific to DECterm graphics:  E           o  In some cases, a private colormap is created in DECterm. A              This private colormap is created when ReGIS or sixel B              graphics are displayed in the window and a sufficientA              number of colors from the default colormap cannot be B              allocated. The result is that when the DECterm windowA              has input focus, the colormap changes for the entire B              workstation. The default colormap is four colors on aC              four-plane or monochrome system and 16 colors on color 0              systems with more than four planes.  A              To restore a DECterm window to the default colormap, A              select Clear Display from the Commands menu to clear E              the window. Then select Reset Terminal from the Commands (              menu to reset the terminal.  A           o  Only graphics, not text, are written to the graphics C              backing store. When part of a window has to be redrawn D              in DECterm, the graphics portion of the window is drawn?              first, then the text is overlaid. As a result, the C              redrawn window might not look the same as the original               picture.   #     2-26 General User Release Notes            I                                                General User Release Notes I                                                          2.4 Applications     D               o  ReGIS addresses the entire window, not just 24 rowsE                  and 80 columns, so the aspect ratio between text and I                  graphics might not always be the same as on the VT330 or                    VT340 terminal.  B               o  The following ReGIS features are not implemented:  (                     Command Display mode                     Scrolling "                     Output cursors  '         2.4.4.21 DECterm Resource Usage                  V1.1  F               You cannot create more terminal windows than your systemB               resources and quotas allow. If you have insufficientA               resources, a dialog box is displayed with a message B               indicating that no additional DECterm windows can be               created.  I               To reduce the memory requirement of each DECterm window and H               create additional terminal windows, decrease the number ofI               Record Lines Off Top in the Display dialog box and decrease <               the number of columns for each DECterm window.  H               Once the resource limit is reached, log out of all DECtermD               windows that are running on the host system before you6               increase the number of terminal windows.  3         2.4.4.22 Diagnostic Crash File and Messages                  V1.1  F               DECterm produces a diagnostic file when a status code ofG               fatal is returned. The DECTERM_ERROR.LOG file is produced A               in the login directory when the DECterm application F               exits abnormally. If you have a problem with the DECtermA               application, submit a copy of this log file to your ?               HP service representative. However, under certain I               circumstances, a log file is generated even when no problem H               is encountered. Therefore, the appearance of a log file asI               an isolated event should not be cause for a problem report.   H               You can enable additional levels of diagnostic messages byG               defining either a logical name or a symbol named DECTERM_ D               DIAG. When defined, enhanced diagnostics are displayedF               by the DECterm images. Use this mode only for diagnosingG               problems; it causes Session Manager message windows to be   I                                           General User Release Notes 2-27                 General User Release Notes     2.4 Applications    A           generated for each new DECterm created from the Session            Manager.  C           DECterm diagnostics can be captured in a file by defining B           the logical name DECW$DECTERM_OUTPUT to point to a file.       2.4.4.23 Using the Debugger              V1.0  ?           To redirect the output from the debugger to a DECterm .           window, enter the following command:  0           $ CREATE/TERMINAL/NOPROCESS/DEFINE=xxx  >           This command creates a DECterm without an associatedC           process but with a logical name of xxx that points to the D           terminal. This procedure enables you to direct output to aD           DECterm window other than the window where the applicationA           is currently running. To redirect the output, enter the            following commands:   '           $ DEFINE /USER DBG$INPUT xxx: (           $ DEFINE /USER DBG$OUTPUT xxx:&           $ RUN /DEBUG application.EXE  %     2.4.4.24 Virtual Terminal Support              V1.0  E           To create a process that uses a virtual terminal, enter the            following command:  %           $ CREATE/TERMINAL/NOPROCESS   B           Then establish focus to the newly created DECterm, pressD           Return, and log in. Note that the /DEFINE qualifier is not           required.   <     2.4.4.25 VT330 and VT340 Terminal Emulation Restrictions             V1.0  C           Although DECterm incorporates some of the features of the @           VT330- and VT340-series video terminals, such as ReGISD           and Sixel graphics; it does not provide complete VT330 and#           VT340 terminal emulation.   6           The following restrictions apply to DECterm:  E           o  User-loadable characters (DRCS), local mode, and control ;              representation mode (CRM) are not implemented.   #     2-28 General User Release Notes            I                                                General User Release Notes I                                                          2.4 Applications     H               o  The checkerboard character (character 97 in the DIGITALC                  Special Graphic character set) is used as an error A                  character in place of the reverse question mark.   C               o  DECterm uses replace mode as the default for Sixel I                  drawing on servers with eight planes or less. On servers H                  with more than eight planes, DECterm uses overlay mode;A                  replace mode is not functional on those servers.   7         2.4.4.26 Using CREATE/TERMINAL/DETACHED/PROCESS                  V1.0  G               The /PROCESS=procnam qualifier does not work when used in G               conjunction with the /DETACHED qualifier, unless there is G               already a process running on the system where its process -               name is equal to the user name.   D               To work around this problem, use the following command               procedure:  %               $! CREATE_TERM_PROC.COM                $!B               $! Invoke as SPAWN/NOWAIT @CREATE_TERM_PROC procname               $!               $ SET NOON               $!-               $! Set Process name to username                $!O               $ X = F$CONTEXT("PROCESS", PID, "PRCNAM", "''F$PROCESS()'","EQL") @               $ NAME = F$EDIT(F$GETJPI(X,"USERNAME"),"COLLAPSE")*               $ SET PROCESS/NAME="''NAME'"8               $ CREATE/TERMINAL/DETACHED/PROCESS="''P1'"               $!L               $! Allow new process to RUN LOGINOUT before exiting subprocess               $ WAIT 00:00:10   H               If the /PROCESS=procnam qualifier specifies a process nameI               that is already in use, the DECterm is created but creation H               of the process inside the DECterm fails. In this case, theE               DCL command CREATE/TERMINAL returns the following error                message:  /               %SYSTEM-F-DUPLNAM, duplicate name   I                                           General User Release Notes 2-29                 General User Release Notes     2.4 Applications    !     2.4.4.27 ReGIS Locator Report              V1.0  B           When DECterm sends a ReGIS locator report in response to@           the R(P(I)) command, or in multiple input mode and theC           locator position is outside the addressable area, DECterm B           sends a locator report with the coordinates omitted. For:           example, press the A key to generate the report:  C           A[]<CR>, where <CR> is a carriage return (ASCII code 13).        2.4.5 DECwindows CD Player  ?           This section contains release notes pertaining to the +           DECwindows CD Player application.        2.4.5.1 Required Privileges              V1.1  >           The DECwindows CD Player (DECW$CDPLAYER) application<           in the DECW$EXAMPLES directory requires PHY_IO and@           DIAGNOSE privileges to operate the compact-disc playerD           hardware. Either your process or the image must have these           privileges.        2.4.6 DECwindows Mail   ?           This section contains release notes pertaining to the &           DECwindows Mail application.  2     2.4.6.1 Support Removed for Display PostScript             V1.2-6  E           With the removal of the support for Display PostScript from B           DECwindows Motif, DECwindows Mail no longer supports theC           display of messages that are exclusively PostScript code. C           In previous versions, DECwindows Mail sensed the presence B           of a mail message containing PostScript and used Display,           PostScript to display the message.  A           Currently, when DECwindows Mail detects a messages that C           is exclusively PostScript code, it displays the following            error message:  C           [This PostScript message cannot currently be displayed.]   C           As a workaround, use the Extract option in the File menu, B           (deselect the "Include Header Information" button in the<           Extract dialog box), and print the extracted file.  #     2-30 General User Release Notes            I                                                General User Release Notes I                                                          2.4 Applications     :         2.4.6.2 Pasting Messages from the Directory Window                 V1.2-4  A               In DECwindows Mail, if the user selects one or more H               messages in the directory window using MB1 and then clicksF               on MB2 in another window (such as a DECterm window), theE               entire contents of the selected messages is pasted into H               the other window. The selected messages are highlighted inH               the directory window, however the text of the selected andC               pasted message is not highlighted in the Read window.   -         2.4.6.3 Responses to Keyboard Actions                  V1.2-3  G               Enhancements in the DECwindows Mail application to comply F               more closely with OSF/Motif style conventions cause someE               changes with application responses to keyboard actions.   )               Note the following changes:   E               o  If you use the Tab key to advance through text entry F                  boxes in the Create/Send window, the current field isE                  no longer highlighted. To select a field, use one of E                  the standard Motif actions, such as double or triple E                  clicking MB1, or use the Shift+Alt - > key sequence.   E               o  In several dialog boxes, press either the Select key F                  or the space bar to activate a pushbutton through theI                  keyboard. Note that the Return key and the Enter key are I                  bound to other widgets in the dialog box. Alternatively, H                  you can continue to click MB1 to activate a pushbutton.  ?         2.4.6.4 Using the Color Customizer with DECwindows Mail                  V1.2  E               If you use the color customizer sample program provided G               in the directory DECW$EXAMPLES to control DECwindows Mail D               colors, the DECwindows Mail color customization dialogC               boxes used to modify those colors may not reflect the D               correct current color values. This is normal behavior;E               use the color customizer instead of the DECwindows Mail F               color customization dialog boxes to change these values.G               Alternatively, exit from the color customizer and restart                DECwindows Mail.  I                                           General User Release Notes 2-31                 General User Release Notes     2.4 Applications         2.4.7 Notepad   ?           This section contains release notes pertaining to the            Notepad application.  >     2.4.7.1 Notepad Is Linked with the OSF/Motif Release 1.1.3             Toolkit              V1.2-3  >           The Notepad application is linked with the OSF/MotifA           Release 1.1.3 Toolkit; it has not been modified to link @           with the updated OSF/Motif Release 1.2.3 Toolkit. As a3           result, the following restrictions apply:   E           o  OSF/Motif Release 1.2 drag-and-drop functionality is not C              supported. As a workaround, use the standard clipboard D              operations (Cut, Copy, and Paste) to transfer text into              Notepad.   D           o  OSF/Motif Release 1.2 tear-off menus are not supported.       2.4.8 Paint   E           This section contains release notes pertaining to the Paint            application.       2.4.8.1 Private Colormaps              V1.1  ?           If your workstation does not have sufficient colormap >           entries to view or edit a color image, Paint creates@           a private colormap. When this happens, the Paint image?           retains its colors, but the colors on the rest of the B           workstation are modified. To restore the colors to their=           original values, give another window input focus by            clicking on it.   5     2.4.8.2 Slow Performance of Some Paint Operations              V1.0  ;           On GPX systems, Paint might appear slow even when E           performing basic operations such as drawing a brush stroke. E           This is because the pixmap is being swapped into the pixmap C           memory in order to paint the object. If Paint performance C           is slow, click on the Pencil tool and draw a point in the C           image area. This should improve performance following the            initial Pencil click.   #     2-32 General User Release Notes            I                                                General User Release Notes I                                                          2.4 Applications     D               When editing images (especially color images), you canC               resize the image area using the Picture Size... entry G               from the Options menu. Resize to the least possible image H               area to significantly reduce the amount of required pixmap               memory.            2.4.9 Session Manager   C               This section contains release notes pertaining to the *               Session Manager application.  B         2.4.9.1 Specifying Authorized User Node Names That Contain#                 Reserved Characters                  V1.2  I               When specifying a list of users who can access the X server E               in the Authorized Users dialog box, place the node name D               within quotation marks if the name contains any of the               following:  E               o  Reserved characters: space, tab, comma (,) or double #                  quotation mark (")   "               o  Double colon (::)  D               o  A colon (:) as the final character in the node name  G               Session Manager automatically adds quotation marks to the G               node name if they are needed, unless the node name begins H               with a double quotation mark. If the node name begins withG               a double quotation mark, Session Manager assumes that the G               user has already quoted the node name and does not change                it.   G               Within a quoted string, a double quotation mark should be G               replaced by two double quotation marks (""). For example, I               the quoted string "DEC:.zko."my node"" should be changed to                the following:  '               ("DEC:.zko.""my node""").         I                                           General User Release Notes 2-33                 General User Release Notes     2.4 Applications    ;     2.4.9.2 Using the Color Customizer with Session Manager              V1.2  ?           If you are using the color customizer example program D           provided in the directory DECW$EXAMPLES to control SessionA           Manager colors, the Session Manager color customization B           dialog boxes used to modify those colors may not reflectD           the correct current color values. This is normal behavior;A           use the color customizer instead of the Session Manager B           color customization dialog boxes to change these values.C           Alternatively, exit the color customizer and restart your            session.  C     2.4.9.3 Detached Processes Created by Default May Prevent Other %             Applications from Opening              V1.1  B           Applications created by FileView and Session Manager are           detached processes.   =           The implication is that during application startup, A           SYS$MANAGER:SYLOGIN.COM and SYS$LOGIN:LOGIN.COM command @           procedures are executed. Any command executed by theseB           command procedures which reads from SYS$INPUT reads data@           intended to be used by FileView or Session Manager for@           the application startup. This prevents the application?           from starting. Examples of such commands are INQUIRE, 0           READ/PROMPT, and SET TERMINAL/INQUIRE.  ;     2.4.9.4 Change in Input Focus When Using a Private Logo              V1.0  >           If you are logging into DECwindows Motif and using a=           private logo command file, input focus might revert B           unexpectedly to the Username field when the private logo           starts up.  .     2.4.9.5 Stopping a Session Manager Process             V1.0  @           Stopping the Session Manager process abruptly can have>           the following serious consequences for nonprivileged           workstation users:  @           o  Nonprivileged users will not be able to start a new7              Session Manager or create a new login box.   #     2-34 General User Release Notes            I                                                General User Release Notes I                                                          2.4 Applications     D               o  If the session is paused, the Pause cover window isD                  deleted and unauthorized users will be able to gain4                  access windows on that workstation.  E               o  The workstation could become unusable if the Session I                  Manager process is terminated by the job controller (for F                  example, when the user's access hours, which might beF                  from 8 a.m. to 5 p.m., are exceeded). In this case, aF                  possible solution would be to restart DECwindows in a6                  batch job that runs during off-hours.  E               To avoid these problems, use the STOP/NOEXIT command to C               stop the process. Otherwise, stop the Session Manager E               process, and restart DECwindows from the SYSTEM account =               (or an account with system manager privileges):   1               $ @SYS$MANAGER:DECW$STARTUP RESTART            2.4.10 Window Manager   C               This section contains release notes pertaining to the .               DECwindows Motif Window Manager.  >         2.4.10.1 The Motif Window Manager Does Not Honour ACLs                 V1.6  G               The Motif Window Manager in the past did not honour ACLS.   I         2.4.10.2 Help Text Does Not Display on All Screens in a Multihead                   System                  V1.3  F               On the Traditional DECwindows Desktop, invoking help (byG               right-clicking) on a screen other than screen 0, displays )               an empty Bookreader window.   F               If you want to display help on a multihead configurationE               using the right-click method, initiate the request from                screen 0.         I                                           General User Release Notes 2-35                 General User Release Notes     2.4 Applications    :     2.4.10.3 Alt + Space Key Does Not Post the Window Menu             V1.2-4  <           With most Motif implementations, the Alt+space key?           combination prompts the Window Manager to display the C           Window menu. However, DECwindows Motif maps the Alt+space =           key binding to the Compose Character function. This B           provides a method for character composition on keyboards?           which do not supply a specific Compose Character key.   A           To change the Alt+space key binding so that it displays C           the Window menu, follow the procedure appropriate to your            desktop environment.  "           For New Desktop systems:  @           1. Copy CDE$SYSTEM_DEFAULTS:[CONFIG.lang]SYS.DTWMRC to(              DISK$:[LOGIN.DT]DTWMRC.DAT.  =           2. In the Keys DtKeyBindings section, uncomment the               following line:  7              Alt<Key>space   icon|window   f.post_wmenu   +           3. Restart the Workspace Manager.   5           For Traditional DECwindows Desktop systems:   D           1. Copy DECW$SYSTEM_DEFAULTS:DECW$MWM_RC.DAT to DECW$USER_&              DEFAULTS:DECW$MWM_RC.DAT.  C           2. In the Keys DtKeyBindings section, uncomment the line:   7              Alt<Key>space   icon|window   f.post_wmenu   (           3. Restart the Window Manager.  D     2.4.10.4 Using the Color Customizer with DECwindows Motif Window              Manager             V1.2  ?           If you are using the color customizer provided in the A           DECW$EXAMPLES directory to control Motif Window Manager ?           colors, the Motif Window Manager customization dialog ?           boxes used to modify those colors may not reflect the @           correct current color values. This is normal behavior;>           use the color customizer instead of the Motif WindowB           Manager color customization dialog boxes to change theseC           values. Alternatively, exit the color customizer and then C           restart Motif Window Manager. See HP DECwindows Motif for   #     2-36 General User Release Notes            I                                                General User Release Notes I                                                          2.4 Applications     G               OpenVMS New Features for more information about the color                customizer.   H         2.4.10.5 Changing Function Key Bindings Using the Window Manager#                  Configuration File                  V1.0  D               The configuration file DECW$MWM_RC.DAT defines how the@               Window Manager uses the function keys. Most of theE               accelerators use the form Alt key (or Compose Character 8               key) and function key, for example Alt+F7.  I               If any application needs to use these keys, you must either E               comment them out by placing an exclamation point (!) at I               the beginning of the line, or create new keyboard bindings. G               Then change Mwm*keyBindings:DefaultKeyBindings in the MWM 9               resource file to point to the new bindings.   ?               With the Motif binding, you can no longer use the E               Alt+spacebar or the Compose Character+spacebar to bring C               up the Window menu because it interferes with Compose D               Character sequences in DECterm. Use Shift+F11 to bring!               up the Window menu.   E               To reenable Alt+space, select the appropriate option in D               the Workspace Options dialog box and apply the currentG               settings. You can also remove the comment for the default H               button bindings for Alt+space in the DECW$MWM_RC.DAT file.  .         2.4.10.6 Restarting the Window Manager                 V1.0  F               The file SYS$MANAGER:DECW$MWM.COM contains settings thatI               specify how the Window Manager is restarted. By default, it H               is always restarted on all the screens that are available.F               However, if you are not starting the Window Manager fromI               the Session Manager, then the Window Manager might not have F               been initially started on all the available screens. YouG               can modify this file to change the way the Window Manager +               is restarted for your system.       I                                           General User Release Notes 2-37                 General User Release Notes     2.4 Applications    ?     2.4.10.7 Customizing Color-Related Resources for Monochrome               Monitors              V1.0  8           The Motif Window Manager does not support fullA           customization of color-related resources for monochrome D           monitors in the Options dialog box. In order to change theB           colors, you might need to modify the pixmap resources byA           directly editing the DECW$MWM_BW.DAT resource file. For C           example, to change the color of the active window's title D           background, you must change the Mwm*activeBackgroundPixmapE           resource. Some values include 25_foreground, 50_foreground, 0           75_foreground, and unspecified pixmap.  C           In addition, by default, the title text is created with a D           white background. To use the same color as the rest of the9           title, set the Mwm*cleanText resource to FALSE.   4     2.4.10.8 Customizing Colors on Multihead Systems             V1.0  E           If you have a multihead system with different monitor types C           (color, monochrome, or gray-scale), you can customize the E           colors only by using the Options dialog box on the monitors A           that match the type of your main monitor (screen 0). To C           customize the other monitors, you must either log in to a E           system with that monitor type or directly edit the resource            files.  +     2.4.10.9 Moving the Icon Box Off Screen              V1.0  @           If you move the icon box to the edge of the screen and@           then resize it using the keyboard, you can move it offC           the screen. To retrieve the icon box, press Alt+Tab until D           you reach that window and then press Shift+Escape (F11) toE           bring up the Window menu for that window. You can then move *           the window back onto the screen.  /     2.4.10.10 Multiline Icon Title Not Centered              V1.0  ?           The Window Manager does not center all the lines of a            multiline icon title.   #     2-38 General User Release Notes            I                                                General User Release Notes I                                                   2.5 Tools and Utilities              2.5 Tools and Utilities   D               This section contains notes related to X Window SystemB               utilities that have been ported to DECwindows Motif.  )         2.5.1 X Authority Utility (xauth)   E               This section contains release notes pertaining to the X (               Authority utility (xauth).  =         2.5.1.1 File Locking Not Supported with Logical Names                  V1.3  C               The X Authority utility (xauth) does not support file D               locking when files are specified using a logical name.I               Since xauth does not translate OpenVMS logicals, it creates H               the lock files in the current default directory versus the1               directory specified by the logical.   G               For example, the following xauth command creates the lock D               files in the current default directory not in the USER<               directory specified by the logical XAUTH_FILE:  <               $ DEFINE XAUTH_FILE DISK:[USER]FILE.DECW$XAUTH#               $ XAUTH -f XAUTH_FILE   F               In order to use logical names with xauth, translate each9               logical before invoking xauth, for example:   4               $ XAUTH_FILE = F$TRNLNM ("XAUTH_FILE")%               $ XAUTH -f 'XAUTH_FILE'   G               Note that this restriction only pertains to using logical D               names with xauth and does not apply when using logicalA               names with the SET DISPLAY/XAUTHORITY_FILE command.   F         2.5.1.2 Specifying File Names without File Types Can Result in                 Failure                  V1.3  B               The X Authority utility (xauth) cannot differentiateC               between files and directories of the same name if the D               file does not yet exist and the type is not specified.G               For example, the following xauth command creates a set of B               lock files but does not create the X authority file:  (               $ CREATE/DIRECTORY [.TEST]               $ XAUTH -f TEST   I                                           General User Release Notes 2-39                 General User Release Notes     2.5 Tools and Utilities     ?           In this case, xauth fails without reporting an error.   B           To prevent this problem from occurring, always specify aD           file type when entering an X authority file specification.  2     2.5.2 Font Server Information Utility (fsinfo)  D           This section contains release notes pertaining to the Font.           Server Information utility (fsinfo).  @     2.5.2.1 Font Server Information Utility Fails After Invoking             V1.3  E           In some cases, the Font Server Information utility (fsinfo) ?           terminates with an access violation after it is first E           invoked. If this situation occurs, rerun fsinfo. Subsequent /           fsinfo sessions should be successful.        2.5.3 Print Screen  E           This section contains release notes pertaining to the Print            Screen utility.   4     2.5.3.1 Print Screen Truncates PostScript Output             V1.2-3  <           When using the Print Screen application to produce@           PostScript output on some printers, part of the output=           may be lost. Usually, the upper and left portion is C           missing when printing in landscape mode and the lower and A           left portion is missing when printing in portrait mode. B           This problem is caused by differences between PostScript           printers.   ?           To correct this problem, DECwindows Motif for OpenVMS A           Version 1.2-5 added support for four resources that can /           be specified in DECW$PRINTSCREEN.DAT:   "           PrintScreen.plxtranslate"           PrintScreen.plytranslate           PrintScreen.plxscale           PrintScreen.plyscale  >           These resources control the size and position of the<           PostScript image on the page. The plxtranslate and?           plytranslate resources control the x and y offsets of ?           the image in inches from the origin. The plxscale and A           plyscale resources are an x and y scale factor to allow   #     2-40 General User Release Notes            I                                                General User Release Notes I                                                   2.5 Tools and Utilities     D               the entire image to be displayed on the page after the               origin is moved.                                                                                      I                                           General User Release Notes 2-41                          I                                                                         3 I         _________________________________________________________________   I                                           System Management Release Notes     H               This chapter describes changes, corrections, restrictions,F               and known problems that pertain to managing a DECwindows               Motif system.   0         3.1 Installation and Upgrade Information  @               This section contains release notes related to theC               DECwindows Motif installation and upgrade procedures.   @         3.1.1 DECwindows Motif Version Support and Compatibility                 V1.6  D               The following table lists which versions of DECwindowsF               Motif are supported on various platforms and versions ofD               the HP OpenVMS operating system. Support is defined toG               mean all features and functionality are available, except G               for Display PostScript, which has been withdrawn from all E               DECwindows X display servers since OpenVMS Version 7.3.   I               Table_3-1_Supported_Versions_of_DECwindows_Motif___________                  DECwindows               Motif I               Version_______OpenVMS_Version______________________________   3               Version 1.6   OpenVMS I64 Version 8.3 5                             OpenVMS Alpha Version 8.3   3               Version 1.5   OpenVMS I64 Version 8.2 5                             OpenVMS Alpha Version 8.2   7               Version       OpenVMS Alpha Version 7.3-2                1.3-1   I                                                  (continued on next page)   I                                       System Management Release Notes 3-1            #     System Management Release Notes ,     3.1 Installation and Upgrade Information    E           Table_3-1_(Cont.)_Supported_Versions_of_DECwindows_Motif___              DECwindows           Motif E           Version_______OpenVMS_Version______________________________   3           Version 1.3   OpenVMS Alpha Version 7.3-1   >           Version       OpenVMS Alpha Versions 7.3, 7.3-1, 6.25           1.2-6         OpenVMS VAX Versions 7.3, 6.2   >           Version       OpenVMS Alpha Versions 7.3, 7.3-1, 6.2E           1.2-5_________OpenVMS_VAX_Versions_7.3,_6.2________________   E           Note that since the DECwindows Motif Version 1.3 and higher D           releases are based upon specific OpenVMS server and deviceB           driver images, only install these releases of DECwindows>           Motif on the operating system versions listed above.  E           Mixed version clusters are supported as long as each system E           in the cluster is running one of the supported combinations >           of DECwindows Motif and OpenVMS listed in Table 3-1.;           Each version of OpenVMS must also support cluster >           configurations. See the Software Product DescriptionD           (SPD) associated with each version of OpenVMS to determine=           whether mixed-version cluster support is available.   @     3.1.2 Limited Support for Third-Party TCP/IP Products (Alpha           Only)              V1.5  ?           Significant changes were made to the DECwindows Motif ?           TCP/IP transport interface in support of newer socket D           interfaces (getaddrinfo and getnameinfo) and their addressD           formats. As a result, some third-party TCP/IP products mayE           not be compatible with the updated interface. Specifically, ?           older versions of MultiNet (prior to Version 5.1) and A           TCPware (prior to Version 5.7) from Process Software do A           not support the capabilities available with the updated <           DECwindows transport and prevent successful server           connections.  E           Contact the TCP/IP product vendor to check for availability B           of software patches or releases that support these newer           interfaces.   '     3-2 System Management Release Notes            I                                           System Management Release Notes I                                  3.1 Installation and Upgrade Information     4         3.1.3 DECW$STARTUP Requires SHARED Privilege                 V1.5  G               The DECW$STARTUP.COM command file now requires the SHARED G               privilege in addition to those system privileges required D               previously. This enables a user whose account does notH               have all system privileges enabled to run the DECW$STARTUPC               RESTART command successfully from the serial console.   H               Note that to prevent any difficulties with system startup,F               HP recommends that you start or restart DECwindows Motif&               from the SYSTEM account.  8         3.1.4 Using Shareable Linkages to Install Images                 V1.2-4  F               Using shareable linkages to install images on DECwindows?               Motif systems can offer the following advantages:   B               o  Enhanced startup performance by decreasing image-                   activation time  I               o  Conserved memory usage by decreasing the total of memory (                  pages used by the image                 V1.3  B               By default, the following images are installed using!               shareable linkages:   -                  DECW$XLIBSHR.EXE (X Library) ;                  DECW$XTLIBSHRR5.EXE (X Toolkit Intrinsics) 4                  DECW$XMLIBSHR12.EXE (Motif Toolkit)>                  DECW$MRMLIBSHR12.EXE (Motif Resource Manager)I                  DECW$DXMLIBSHR12.EXE (DECwindows Extensions to the Motif                   Toolkit) @                  CDE$UNIX_ROUTINES.EXE (UNIX emulation routines)6                  DECW$TRANSPORT_COMMON.EXE (Transport)4                  DECW$XPORT_SERVICES.EXE (Transport)?                  DECW$LCNLIBSHR.EXE (Logical Connection Number) ?                  DECW$SETSHODISSHR.EXE (OpenVMS Display Device)                    DECW$XAUSHR.EXE&                  DECW$ICELIB.EXE (ICE).                  DECW$ICELIB_PTHREAD.EXE (ICE)<                  DECW$SMSHR.EXE (X Session Manager Protocol)  I                                       System Management Release Notes 3-3            #     System Management Release Notes ,     3.1 Installation and Upgrade Information    B           These images are installed using the /SHARE=ADDRESS_DATAD           and /RESIDENT options. Note that if you accept the default?           values, these images are installed as memory resident C           and cannot be replaced during a restart. As a result, the D           following message is displayed when you restart DECwindows           Motif:  Q           Shared linkage sections are in use on this system and no images will be T           reinstalled. If you are restarting DECwindows to reinstall images then you!           must reboot the system.   B           To replace new images installed with this option, reboot>           the system. Note that you can disable shared-linkageB           sections by defining the logical name DECW$IGNORE_SHARE_=           ADDRESS in the SYSTARTUP_VMS.COM command procedure.   7     3.1.5 DECW$COMPARE_VERSIONS Command File Limitation              V1.2-4  A           The DECW$COMPARE_VERSIONS command file compares version >           identifications using two-digit years. Therefore, it<           will not compare version identifiers correctly forB           images generated in the year 2000 and later with version@           identifiers for images generated before the year 2000.  ?     3.1.6 Restarting DECwindows Motif from the Operator Console            (OPA0:)              V1.0  <           Starting or restarting DECwindows Motif by runningB           DECW$STARTUP.COM from a serial console attached to OPA0:=           can change the characteristics of the terminal. For ?           example, starting DECwindows Motif in this manner can @           change the current device type setting and prevent the&           subsequent use of an editor.  :           To prevent this from occurring, set the terminal9           characteristics permanently before invoking the 1           DECW$STARTUP.COM procedure, as follows:   +           $  SET TERMINAL/INQUIRE/PERMANENT .           $  @SYS$MANAGER:DECW$STARTUP RESTART  '     3-4 System Management Release Notes            I                                           System Management Release Notes I                                         3.2 System Tuning and Performance     )         3.2 System Tuning and Performance   H               This section describes important issues and considerations8               related to the tuning of DECwindows Motif.  D         3.2.1 Changes in Recommended UAF and System Parameter Values                 V1.5  @               With this release of DECwindows Motif, many of theD               recommended minimum values for user authorization fileG               (UAF) and system parameters on the OpenVMS Alpha platform H               have been significantly increased. In addition, a separateG               set of system parameter values has been generated for the #               OpenVMS I64 platform.   C               To optimize the performance of the DECwindows display F               server and client applications, scan the current UAF andI               system parameter values on systems running DECwindows Motif F               for OpenVMS Version 1.5 and make sure that they meet theE               suggested minimum values listed in Appendix A of the HP <               DECwindows Motif for OpenVMS Management Guide.  &         3.3 Security and Authorization  H               This section describes important issues and considerations)               related to system security.   I         3.3.1 Buffer Overflow Reported on Xpm Library (CERT Vulnerability                VU#882750)                 V1.6  >               A potential remotely exploitable buffer overflowI               vulnerability was reported in the X PixMap routines used in G               the Motif library, and in the Image Viewer (dximageview). E               The potential vulnerability could result in a denial of F               service condition or in the execution of arbitrary code.G               This problem was reported in CERT Vulnerability VU#882750 $               and has been resolved.          I                                       System Management Release Notes 3-5            #     System Management Release Notes "     3.3 Security and Authorization    9     3.3.2 A Deprecated Kerberos API Replaced with New API              V1.6  C           A new version of Kerberos V3.0 has been introduced in the 2           OpenVMS Alpha V8.3 and OpenVMS I64 V8.3.  ;           The krb5_get_in_tkt_with_password API was used by >           DECW$WSCUST and DTSTYLE and has been deprecated fromC           Kerberos Version 2.1. Now this API has been replaced with /           new API krb5_get_init_creds_password.   E           For more information about the Kerberos, see the HP OpenVMS #           Guide to System Security.   *     3.3.3 PWDMIX Flag Now Handled Properly             V1.6  B           On the Traditional DECwindows Desktop, when the UAF flagE           PWDMIX is set, Set Password dialog box converts the entered             password to uppercase.  7     3.3.4 GENPWD Flag Now Handled Properly (Alpha Only)              V1.5  >           When a system manager sets the GENPWD flag on a user?           account, that user is restricted to using a generated <           password versus setting their own. Once the user'sE           generated password expires, they must choose a new password "           from the generated list.  B           Previously when this flag was set on a user account, the&           following problems occurred:  D           o  On the Traditional DECwindows Desktop, the system would?              hang if the user entered a password other than one @              included on the generated password list. To recoverC              from the hang, the system manager had to terminate the A              existing DECW$LOGINOUT image and restart DECwindows.   =           o  On the New Desktop, users were not restricted to +              choosing a generated password.   B           These problems have been fixed with DECwindows Motif for           OpenVMS Version 1.5.  '     3-6 System Management Release Notes            I                                           System Management Release Notes I                                            3.3 Security and Authorization     F         3.3.5 BadAuthorizationProtocol Error Displayed When Generating6               Authorization Keys with Kerberos Enabled                 V1.3-1  E               The SECURITY extension to the X display server does not D               support on-demand generation of authorization keys forF               the Kerberos authentication protocol. Non-support of keyG               generation is consistent with the standard implementation =               of the server extension, as published by X.Org.   @               Consequently, the following DCL commands produce aE               BadAuthorizationProtocol error or unwanted results when G               used to generate an authorization key on an X server that #               has Kerberos enabled:   ?               o  SET DISPLAY/GENERATE=(PROTOCOL=MIT-KERBEROS-5)                  o  XAUTH GENERATE   E               This is expected behavior; do not use these commands to D               generate authorization keys for X servers that use theH               Kerberos protocol. See the HP DECwindows Motif for OpenVMSC               New Features manual to learn when and how to manually B               create X authority file entries for Kerberos-enabled               servers.  4         3.3.6 Setting the hostList Resource Manually                 V1.3  G               On New Desktop systems, access to DECwindows Motif can be G               granted to a predefined set of users by specifying values D               to the *hostList and *numHosts resources in either theH               SYS.RESOURCES or DT.RESOURCES file. The *hostList resourceC               specifies the users (by host name or address) who are F               allowed access, and the *numHosts resource specifies the0               total number of users in the list.  H               Typically, these resources are modified automatically whenF               you implement or make changes to user-based security viaE               the Session Manager. However, if you maintain the user- I               based access lists by modifying *hostList manually, be sure <               to also set *numHost to the appropriate value.  I                                       System Management Release Notes 3-7            #     System Management Release Notes "     3.3 Security and Authorization    B           For additional information on defining global and system?           level resources, see the Getting Started With the New D           Desktop manual. For further information on enabling accessE           control, see the HP DECwindows Motif for OpenVMS Management            Guide manual.   =     3.3.7 Unknown Code Error Displayed When Enabling Kerberos              V1.3  =           If the Kerberos logical (KRB$ROOT) has not been set E           properly, the following error is displayed when you attempt E           to enable Kerberos from either the DECwindows Motif desktop .           or the DCL command line using KINIT:  2           "Unknown code 6 while initializing krb5"  ;           To correct this problem, reconfigure the Kerberos ;           for OpenVMS Security Client software as described <           in the Kerberos for OpenVMS Installation Guide and;           Release Notes available from the OpenVMS web site )           (http://www.hp.com/go/openvms).   D     3.3.8 Bad Atom Error Displayed When Running Applications Over an           Untrusted Connection             V1.3  ?           Any DECwindows Motif application that attempts to run @           over an untrusted connection without a security policyD           defined will either not start or will exit after starting.;           An untrusted connection is created when access is @           granted to an X server using a cookie generated by SET-           DISPLAY/GENERATE or XAUTH GENERATE.   @           In most cases where this problem occurs, the following%           error message is displayed:   #           X Error of failed request *           BadAtom (invalid Atom parameter)  =           To reduce the likelihood of application errors over B           untrusted connections, start the server with the defaultC           security policy file by setting the symbol DECW$SECURITY_ ;           POLICY to DECW$EXAMPLES:DECW$SECURITY_POLICY.TXT.   '     3-8 System Management Release Notes            I                                           System Management Release Notes I                                            3.3 Security and Authorization     B               Note however, that the following applications do notE               run cleanly over an untrusted connection, even with the ,               security policy file in place:                    Bookreader                   CDA Viewer                   DECterm                  DTPAD!                  OpenVMS Debugger                   Paint                  Print Screen                   Style Manager  G         3.3.9 Applications Running Over an Untrusted Connection May Not 7               Work with XINERAMA and SEC_XAG Extensions                  V1.3  H               Applications connected to the X server using an untrusted,A               generated cookie may not work when the XC-APPGROUP, ?               SECURITY, and XINERAMA server extensions are both G               loaded. The problem is caused by the order in which these D               extensions are initialized when the server is started.  H               To avoid the problem, always define DECW$SERVER_EXTENSIONSG               in DECW$PRIVATE_SERVER_SETUP.COM so that if both XINERAMA G               and SEC_XAG (combined SECURITY and XC-APPGROUP image) are 8               loaded, XINERAMA is listed before SEC_XAG.  "               For example, define:  <               $ decw$server_extensions == "XINERAMA,SEC_XAG"                 instead of:   <               $ decw$server_extensions == "SEC_XAG,XINERAMA"  D         3.3.10 Kerberos and TCP/IP Do Not Recognize a Node Name of 0                 V1.3  G               When using Kerberos with TCP/IP, providing a node name of E               0 (to indicate the local host) does not work correctly. I               The problem occurs only if Kerberos is initialized from the 3               server X authority file. For example:   I                                       System Management Release Notes 3-9            #     System Management Release Notes "     3.3 Security and Authorization    .           $ SET DISPLAY/TRANSPORT=TCPIP/NODE=0!           $ RUN DECW$EXAMPLES:ICO   R             Xlib: krb5_sname_to_principal failed: Hostname cannot be canonicalized             Cannot open display 6             : non-translatable vms error code: 0x182B2(             %rms-e-rnf, record not found  ?           Instead, provide the TCP/IP address of the local host            explicitly:   8           $ SET DISPLAY/TRANSPORT=TCPIP/NODE=11.22.33.44  >     3.3.11 Do Not Use DECwindows Motif Login When Initializing:            Kerberos Setup from the Server X Authority File             V1.3  ?           When initializing the Kerberos setup using the server @           X authority file, the DECwindows Motif login cannot be?           used. The reason for this is that DECwindows login is >           a privileged image and the Kerberos runtime image is>           not an installed image. Moreover, the clients run byA           login manipulate the Kerberos setup. Therefore, session <           management is not supported in this configuration.  D           To prevent the DECwindows login box from coming up, defineD           DECW$MAINAPP in SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM as           follows:             $ DECW$MAINAPP == " "   2     3.3.12 Help on Kerberos Login Box is Incorrect             V1.3  D           The online help for Revoke Ticket is incorrect. See the HPB           DECwindows Motif for OpenVMS New Features manual for the           correct description.  =     3.3.13 Do Not Insert Generated Cookies into the Default X             Authority File              V1.3  E           Inserting generated cookies in the default X authority file D           may interfere with the current session cookie. If you wantD           to propagate a generated cookie value, HP recommends usingA           the /XAUTH qualifier as follows to insert the generated 2           cookie in an alternate X authority file:  (     3-10 System Management Release Notes           I                                           System Management Release Notes I                                            3.3 Security and Authorization     W               $  SET DISPLAY/GENERATE=NOTIMEOUT/XAUTH=disk$:[dir]myauthority.decw$xauth   A               If you insert a generated cookie into the default X I               authority file during the current DECwindows Motif session, A               end the session to restore normal system operation.   A               If you insert a generated cookie into the default X C               authority file outside of a DECwindows Motif session, ?               delete the X authority file prior to logging into                DECwindows.            3.4 Desktop Management  H               This section describes important issues and considerationsB               related to managing desktops and their applications.  0         3.4.1 Trusted Unpause Operations Allowed                 V1.6  D               The ACME subsystem is now available in the OpenVMS I64I               environment. As a result, the trusted unpause functionality D               is now available on both OpenVMS Alpha and OpenVMS I64I               systems. For more information about the ACME subsystem, see 6               the HP OpenVMS Guide to System Security.  6         3.4.2 Color Problem in DECwindows Login Screen                 V1.2  C               A problem may occur on systems that have a customized B               DECW$LOGIN.DAT file. The Start Session dialog box isF               the color blue instead of tan. If this condition exists,H               look for a customized DECW$LOGIN.DAT file in the directoryI               SYS$COMMON:[DECW$DEFAULTS.USER] and move it to SYS$MANAGER. F               A DECW$LOGIN.DAT file in SYS$COMMON:[DECW$DEFAULTS.USER]D               prevents the *background: resource from being defined;6               thus, it will default to the color blue.  B               HP provides a copy of the DECW$LOGIN.DAT file in theI               SYS$COMMON:[DECW$DEFAULTS.SYSTEM] directory. Any customized F               versions of this file should reside only in SYS$MANAGER.      I                                      System Management Release Notes 3-11            #     System Management Release Notes "     3.5 Font and Keymap Management    "     3.5 Font and Keymap Management  D           The following sections contain release notes pertaining to"           font and keymap support.  A     3.5.1 Queries on TrueType Font Properties No Longer Reset the %           Display Server (Alpha Only)              V1.5  D           Previously, queries on TrueType font properties by desktopD           applications or the xlsfonts utility (using the -l option)D           caused the display server to partially reset and appear toE           hang. This problem has been fixed with DECwindows Motif for            OpenVMS Version 1.5.  +     3.5.2 Euro Currency Symbol Restrictions              V1.3  C           The following limitations exist with DECwindows Motif and 3           its support for the euro currency symbol:   @           o  When the euro symbol is pasted or sent to another X@              window application on a different platform (such asD              UNIX) using Compound Text format, the character may notD              be recognized as the euro symbol on the other platform.  @           o  The euro currency symbol is not included as part ofD              the scalable font sets available with DECwindows Motif.A              Applications using scalable fonts cannot display the               euro symbol.   @           o  Although you can use EDT to type the euro characterE              into a file, the symbol may not display correctly on the D              screen. For example, typing Compose o x displays the A4              character code.  D     3.5.3 Adjusting Resource Settings for Keymaps that Implement the           Mode_switch Modifier             V1.3  ?           When using a traditional DECwindows Motif keymap that A           implements the Mode_switch modifier, make sure that you C           first adjust the default Window Manager resource settings D           to enable window grabbing. Otherwise, you may be preventedE           from using the mouse to grab the handles of open windows on            the desktop.  (     3-12 System Management Release Notes           I                                           System Management Release Notes I                                            3.5 Font and Keymap Management     @               For example, the AUSTRIAN_GERMAN_LK401AG_TW keymapI               implements the compose key as a one-shot lockdown modifier. E               The first time a user presses the compose key with this C               keymap loaded, the Mode_switch modifier is activated, F               which prevents the user from grabbing the handles of any@               application windows currently open on the desktop.  I               To prevent this from occurring, redefine the default Window F               Manager resources as follows; then exit and restart your'               DECwindows Motif session:   )               o  For New Desktop systems:   6                  Edit the file CDE$USER_DEFAULTS:[APP-:                  DEFAULTS.C]DTWM.DAT, and set the value ofI                  Dtwm*ignoreModKeys and Dtwm*ignoreAllModKeys to TRUE. If I                  this file and directory do not already exist, create the F                  directory and copy the DTWM.DAT file from CDE$SYSTEM_:                  COMMON:[APP-DEFAULTS.C] to the directory.  <               o  For Traditional DECwindows Desktop systems:                    Edit the fileI                  DECW$SYSCOMMON:[DECW$DEFAULTS.USER]DECW$MWM.DAT, and set H                  the value of Mwm*ignoreModKeys and Mwm*ignoreAllModKeysC                  to TRUE. If this file does not already exist, copy G                  the DECW$MWM.DAT file from DECW$SYSTEM_DEFAULTS to the                   directory.   #         3.6 Proxy Server Management   H               The following sections contain release notes pertaining toF               the management of the Low-Bandwidth X (LBX) proxy server-               and related proxy applications.   E         3.6.1 LBX Proxy Servers Does Not Accept the Client Connection                Request                  V1.6  H               The LBX proxy server does not accept the client connectionG               request, as the application seems to be hung and does not I               generate any CPU or IO times. The changes that were part of D               DECwindows Motif V1.5 ECO1 broke the LBX proxy server.  I               This problem has been corrected in the DECWindows Motif for "               OpenVMS Version 1.6.  I                                      System Management Release Notes 3-13            #     System Management Release Notes      3.6 Proxy Server Management     A     3.6.2 Proxy Servers Do Not Support Use of XC-QUERY-SECURITY-1            Protocol             V1.3-1  B           The Low-Bandwidth X (LBX) proxy server (and other third->           party proxy servers) do not support use of XC-QUERY-A           SECURITY-1 authentication protocol. This authentication ;           protocol, which is enabled by the SECURITY server D           extension, is typically used by firewall servers to verifyC           the security configuration of the display server to which A           they are connecting. Normally, firewall servers connect D           directly to a display server and do not use a proxy server           as an intermediary.   D           If a client application uses a third-party proxy server toE           connect to an X display server using the XC-QUERY-SECURITY- D           1 protocol, the application may loop, block, or crash. TheB           LBX proxy server has been modified to detect whether theA           protocol is in use, and in this situation, produces the "           following error message:  8           Multi-pass authentication not supported by LBX  D           When using a proxy server to process connections to one orD           more X display servers, verify that the SECURITY extensionB           is not enabled on the X servers. Do this by scanning theB           DECW$PRIVATE_SERVER_SETUP.COM file on each server systemE           and checking that the parameter DECW$SERVER_EXTENSIONS does )           not contain a value of SEC_XAG.   >     3.6.3 Proxy Manager Process Does Not Restart Automatically             V1.3  A           The following problems can occur with the proxy manager B           when DECwindows Motif is configured to restart the proxy@           manager process automatically and the DECwindows Motif(           session is restarted manually:  C           o  If the proxy manager was running, a new process is not 8              invoked when DECwindows Motif is restarted.  @           o  If the proxy manager was not running, a new processA              is started; however, the owner of the process is the C              user who enters the startup command and not the SYSTEM               account.   (     3-14 System Management Release Notes           I                                           System Management Release Notes I                                               3.6 Proxy Server Management     C               Note that these problems do not occur when DECwindows F               Motif is restarted as part of an ordered system shutdown               (reboot).   H               To manually restart the proxy manager, enter the followingA               command for the active proxy manager process before *               restarting DECwindows Motif:                 $ STOP DECW$PROXY   D               Note that this command not only stops the active proxyC               manager process, but also terminates all proxy server 1               connections managed by the process.   F               To ensure that the owner of the proxy manager process isI               the SYSTEM account, always log in as SYSTEM when restarting                DECwindows Motif.   :         3.6.4 Proxy Manager Configuration File Restriction                 V1.3  I               The proxy manager does not support specifying more then one F               managed or unmanaged entry for the same proxy service inI               the configuration file. If there are multiple entries, only .               the first one will be processed.  '         3.7 X Display Server Management   H               The following sections contain release notes pertaining toB               the management of the DECwindows X11 Display Server.  H         3.7.1 Support for Choosing the Location of Dialogs in a Xinerama               Configuration                  V1.6  H               In a Xinerama configuration running the new desktop, thereI               are some help dialogs such as the Login Screen, Login Help, I               Set Password, Kerberos Login and Kerberos Help displayed in I               a split manner across all the displays, making it difficult H               to use. It is now possible to position these screens using:               appropriate resources in the resource files.  E               The resource file and resources for each of the dialogs                are:                 1. Login Screen   I                                      System Management Release Notes 3-15            #     System Management Release Notes #     3.7 X Display Server Management     7              cde$user_defaults:[config.c]xresources.dat %              Dtlogin*matte.x: <value> %              Dtlogin*matte.y: <value>   O              Default Positon for Login Screen without resources in the resource '              file is the screen center.              2. Login Help   7              cde$user_defaults:[config.c]xresources.dat 8              Dtlogin*help_message.defaultPosition: False,              Dtlogin*help_message.x: <value>,              Dtlogin*help_message.y: <value>  N              Default Position for Login Help without resources in the resource'              file is the screen center.               3. Set Password Dialog  7              cde$user_defaults:[config.c]xresources.dat 8              Dtlogin*help_message.defaultPosition: False,              Dtlogin*help_message.x: <value>,              Dtlogin*help_message.y: <value>  P              Default Position for Set Password without resources in the resource'              file is the screen center.   "           4. Kerberos Login Dialog  7              cde$user_defaults:[config.c]xresources.dat 8              Dtlogin*help_message.defaultPosition: False,              Dtlogin*help_message.x: <value>,              Dtlogin*help_message.y: <value>  Y              Default Position for Kerberos Login Dialog without resources in the resource '              file is the screen center.   !           5. Kerberos Help Dialog   7              cde$user_defaults:[config.c]xresources.dat 8              Dtlogin*help_message.defaultPosition: False,              Dtlogin*help_message.x: <value>,              Dtlogin*help_message.y: <value>  X              Default Position for Kerberos Help Dialog without resources in the resource'              file is the screen center.   (     3-16 System Management Release Notes           I                                           System Management Release Notes I                                           3.7 X Display Server Management     G         3.7.2 Adjusting Pixel Depth on Systems with ATI RADEON Graphics                Cards                  V1.5  C               The default settings for the ATI RADEON graphics card G               are 24 bits per pixel (pixel depth) and TrueColor (visual H               class). These settings can cause DECwindows Motif graphicsH               applications or utilities that assume specific pixel depthD               or visual type values to fail. For example, DECW$PAINTD               relies on a pixel depth of 8 bits in PseudoColor mode.  D               If display issues occur on a system with an ATI RADEOND               card, HP suggests that you adjust the default settingsG               using the DECW$SERVER_PIXEL_DEPTH or DECW$SERVER_DEFAULT_ I               VISUAL_CLASS system logical, as described in the HP OpenVMS                Release Notes.  E         3.7.3 Performance Degradation May Occur on XINERAMA Multihead                Systems                  V1.3  D               In some cases, multihead systems configured to use theC               XINERAMA extension perform slower than single-head or G               traditional multihead systems (without XINERAMA enabled). E               Slowed system performance typically occurs on multihead @               systems with three or more graphics cards that areB               also running multiple request-intensive applications               simultaneously.   D               This is expected behavior; the following design issues@               inherent to the XINERAMA implementation from X.Org?               contribute to the slowdown in system performance:   H               o  Added layer of processing when rendering drawable itemsG                  Instead of using the typical Proc* functions to render D                  drawable items onscreen (such as windows), XINERAMAF                  uses its own set of functions-inserting an additionalC                  layer of processing before the rendering functions B                  are called. For each screen in the configuration,F                  the XINERAMA functions supply the appropriate screen-E                  specific resource values to the rendering functions. G                  This extra layer of processing results in more compute G                  time spent comparing drawable regions, determining the D                  applicable screen, modifying the resources for each=                  screen, and completing the additional calls.   I                                      System Management Release Notes 3-17            #     System Management Release Notes #     3.7 X Display Server Management     >           o  More complex event handling for secondary screensE              Typically, events are destined for a single screen. On a C              multihead system, XINERAMA distributes events from the B              dispatch layer to the individual screens for display.B              Each time an event originates from a secondary screen@              (other than screen 0), a reverse lookup is required@              to locate the appropriate screen resource. XINERAMAB              then maps the event back to the virtual screen 0, and'              eventually, to the client.   5           o  Unavailability of graphics optimizations E              Each graphics card maintains a separate framebuffer that C              can be manipulated to optimize display performance. In B              single-head and traditional multihead configurations,A              the display optimization can be controlled with such D              mechansims as Direct Rendering Infrastructure (DRI) and+              on-card hardware acceleration.   @              With XINERAMA, however, these separate framebuffers;              are merged to form a single work surface. This >              merged framebuffer can prevent or impede graphicsA              optimizations, as each card only maintains a segment '              of the entire framebuffer.   ;           If you have configured a XINERAMA-based multihead B           system and are experiencing a notable decrease in systemC           performance, HP recommends that you do one or more of the -           following to improve response time:   ;           o  Decrease number of heads in the configuration.   ;           o  Limit the number of complex, request-intensive /              applications running concurrently.   D           o  Use the X server system as a display node only, keeping,              all clients on different nodes.  C           If you continue to experience a significant lag in system ?           response, HP recommends that you disable the XINERAMA A           extension, and configure a traditional multihead system D           as described in the manual HP DECwindows Motif for OpenVMS           Management Guide.       (     3-18 System Management Release Notes           I                                           System Management Release Notes I                                           3.7 X Display Server Management     3         3.7.4 Using XINERAMA on New Desktop Systems                  V1.3-1  I               The following restriction exists when using the New Desktop 8               on a multiheaded system based on XINERAMA.  H               Some DECwindows Motif dialog boxes are designed to displayF               at the center of the screen. If there are an even numberC               of screens in any one direction, the dialog boxes are C               displayed at the junction of two screens, making them F               difficult to view. Some dialog boxes can be repositionedE               on screen; however, the following cannot since they are @               displayed while the Window Manager is not running:  !                  Login dialog box &                  Login help dialog box.                  Login Set Password dialog box*                  Kerberos Login dialog box/                  Logout Confirmation dialog box :                  Workspace Restart Confirmation dialog boxI                  Move/Size coordinates displayed by the Workspace Manager   ?               You can manually reposition the New Desktop login >               dialog box by setting the following resources in<               the XRESOURCES.DAT file located in CDE$SYSTEM_"               DEFAULTS:[CONFIG.C]:  !               Dtlogin*matte.x: 50 "               Dtlogin*matte.y: 100  F                 ________________________ Note ________________________  A                 The XRESOURCES.DAT file in CDE$SYSTEM_DEFAULTS is C                 replaced each time you install DECwindows Motif. HP F                 recommends that you store modified copies of this fileF                 in CDE$USER_DEFAULTS:[CONFIG.C] to save any customized                 settings.   F                 ______________________________________________________  B               Once you have redefined the Dtlogin*matte resources,E               restart the login process. The login dialog box will be F               displayed at the specified (x, y) coordinates. If eitherH               position is omitted, or is set to zero, the screen will be$               centered on that axis.  I                                      System Management Release Notes 3-19            #     System Management Release Notes #     3.7 X Display Server Management     >           Note that the vertical position of the screen may be@           slightly above center if the console window is in use.  >     3.7.5 Some Combinations of Server Extensions Not Supported             V1.3  ;           Currently, the following combinations of X server '           extensions are not supported:                 XINERAMA and D2DX#              DBE and MULTIBUFFERING   C           Note that these extensions may be enabled concurrently on D           the same DECwindows Motif system. However, due to resourceC           or function conflicts, concurrent use of these extensions .           on the same system is not supported.  @     3.7.6 Extraneous Characters Displayed When Running XMAG in a9           Vertical Multihead Configuration Using XINERAMA              V1.3  C           When using XMAG to display an image on a multihead system C           using XINERAMA, a one-pixel line of extraneous characters ?           might appear between the screens when the screens are A           configured vertically. This problem does not occur when 2           the screens are configured horizontally.  ;     3.7.7 Incorrect Placement of Cascade Menus in Multihead '           Configurations Using XINERAMA              V1.3  ?           In some cases, DECwindows Motif cascade menus may not C           appear on the correct screen in a multihead configuration >           using XINERAMA. The menu is displayed in the correct>           position on the wrong screen. Currently, there is no           workaround.   ,     3.7.8 XINERAMA Supported in 2D Mode Only             V1.3  >           Using the XINERAMA extension to the X server with 3D>           applications, such as OpenGL, is not supported. This<           extension should be used in a 2D environment only.  (     3-20 System Management Release Notes                         I                                                                         4 I         _________________________________________________________________   I                                                 Programming Release Notes     H               This chapter contains release notes related to programming2               in the DECwindows Motif environment.           4.1 General Programming   C               This section contains release notes pertaining to the ?               general DECwindows Motif programming environment.   H         4.1.1 Applications Are Not Displayed Properly with Version 1.3-1               or higher                  V1.6  @               Applications that reported these problems used theF               ConnectionNumber macro defined in DECW$INCLUDE:XLIB.h toD               get the LCN to use to poll for events from the server.H               The implementation of the ConnectionNumber macro in V1.3-1G               or higher returned an EFN instead of the LCN. This caused F               V1.3-1 or higher applications not to receive events fromD               the server. Since the applications did not receive anyH               events from the server, they did not display correctly and:               the application seems to be in a hung state.  F               The implementation of the ConnectionNumber macro has nowE               been modified. The macro can now either return an event B               flag (for compatibility with DECwindows V1.2-6) or aF               logical connection number. The logical connection number@               is required for use with the DECW_Select function.  D               If compiled with the DECW_USE_LCN_FOR_CONNECTION macroH               set, the ConnectionNumber macro always returns the logicalB               connection number. If the macro has not been set andE               XInitThread is not called then ConnectionNumber returns F               the event flag number. If the macro has not been set andH               XInitThread has been called a logical connection number is               returned.   I                                             Programming Release Notes 4-1                 Programming Release Notes      4.1 General Programming     @           The XConnectionNumber function returns the event flag,>           if XInitThreads has not been called, and the logical<           connection number if it has been called and is notA           affected by the DECW_USE_LCN_CONNECTION macro. However, ?           if DECW_ USE_LCN_FOR_CONNECTION has been defined then C           XConnectionNumber is defined as a macro which maps to the E           DECW$ConnectionNumber function. This function is defined to /           return the logical connection number.        4.1.2 Xpoll.h Changes              V1.6  E           The header file XPOLL.H has been corrected so as to compile A           under relaxed_ansi mode. XPOLL.H differs from the X.org >           sample implementation in defining a type DECW_FD_SetA           instead of fd_set and macros DECW_FD_ZERO, DECW_FD_CLR, @           DECW_FD_SET, DECW_FD_ISSET, DECW_Select instead of FD_?           ZERO, FD_CLR, FD_SET, FD_ISSET and Select. This is to E           avoid conflict with different definitions which are made in E           socket.h and time.h as supplied by installation of OpenVMS. ?           If the macro DECW_USE_FD_SET is set, before including E           Xpoll.h, the standard names will be used but these standard 5           names will point to their DECW equivalents.   B           For example, if the DECW_USE_FD_SET macros is set beforeE           including xpoll.h, FD_CLR will be equivalent to DECW_FD_CLR E           and so on. Do not do this if the definitions from time.h or 2           select.h are also needed in the program.  B           Note that XPOLL.H defines a macro "DECW_Select" which isB           not the same as the socket function "select". The "DECW_E           Select" macro supports only the connection numbers provided B           by X-Lib and ICE and the "select" function only the file'           descriptors for open sockets.   :           The macros in XPOLL.H can be used whether or notC           XInitThreads has been called. However, note the following A           issues regarding the use of the ConnectionNumber macro.   0           Here is an example code using XPOLL.H:        !     4-2 Programming Release Notes            I                                                 Programming Release Notes I                                                   4.1 General Programming     >               while (!XEventsQueued (dpy, QueuedAfterReading))               { (               /* wait for more events */               DECW_FD_Set fds;"               DECW_FD_ZERO (&fds);8               DECW_FD_SET (ConnectionNumber(dpy), &fds);-               DECW_Select (1, &fds, 0, 0, 0);                }   I               For this code to work correctly it is important that events H               are not moved to the event queue, and unprocessed, betweenI               the XEventsQueued call and the DECW_Select call. This could D               happen if another thread called XEventsQueued. It alsoH               could happen if XSelectAsyncInput or XSelectAsyncEvent hadE               been called for the display. Therefore, the enabling of E               asynchronous event handling is not recommended with the #               DECW_Select function.            4.1.3 XLIBINT.H Changes                  V1.6  D               When the application that references the LockDisplay()F               macro in XLIBINT.H is compiled, it results in diagnosticB               warning messages as the SYS$SETAST() routine used by4               LockDisplay() do not have a prototype.  G               The header file XLIBINT.H has been corrected to fix these *               diagnostic warning messages.  =         4.1.4 Problem with Error Handling in _XDefaultIOError                  V1.6  I               A bug in the implementation of the _XDefaultIOError routine D               in V1.3 and V1.3-1 caused programs that exercised thisD               routine to return a $STATUS of 1 inspite of a failure.I               This problem has now been fixed. The change causes an "-E-" #               error to be signaled.             I                                             Programming Release Notes 4-3                 Programming Release Notes      4.1 General Programming     7     4.1.5 Problem with Error Handling in _XDefaultError              V1.6  C           A bug in the implementation of the routine _XDefaultError A           V1.3 and V1.3-1 caused programs with abnormal errors to C           exit. This problem has now been fixed. This change causes C           an "-E-" status error to be signaled. This means that the E           code causes the default error handler to continue. However, E           the X.Org specification of X-lib specifies that the default D           error prints a message and exits. This deviation should be           noted.  E     4.1.6 Motif Toolkit and X Window System Support and Compatibility              V1.5  A           The following table lists the versions of the OSF/Motif @           Toolkit and X Window System upon which each release of$           DECwindows Motif is based.  E           ___________________________________________________________ !           DECwindows    OSF/Motif E           Motif_________Toolkit___________X_Window_System____________   @           Versions      CDE Motif 1.0     Version 11 Release 6.63           1.3, 1.3-1,   (OSF/Motif        (X11R6.6) &           and 1.5       Release 1.2.5)  >           Versions      CDE Motif 1.0     Version 11 Release 51           1.2-4,        (OSF/Motif        (X11R5) &           1.2-5, and    Release 1.2.5)           1.2-6   /           Version       OSF/Motif 1.2.3   X11R5 (           1.2-3         (with extensions&                         for the Common                         Desktop #                         Environment                          (CDE))  /           Version 1.2   OSF/Motif 1.2.2   X11R5   >           Version 1.1   OSF/Motif 1.1.3   Version 11 Release 41                                           (X11R4)   E           Version_1.0___OSF/Motif_1.1.1___X11R4______________________   D           DECwindows Motif for OpenVMS Version 1.1 applications willC           continue to run without modification with current version @           of DECwindows Motif. Only those applications that have  !     4-4 Programming Release Notes            I                                                 Programming Release Notes I                                                   4.1 General Programming     G               been built against the OSF/Motif Release 1.2.2 or greater I               Toolkit can take advantage of Version 1.2 features, such as =               drag-and-drop functionality and tear-off menus.   :         4.1.7 Run-Time and Programming Environment Support                 V1.5  E               The following run-time and programming environments are H               provided with the DECwindows Motif for OpenVMS Version 1.5               software:   C               o  Run-time support is provided for the CDE Motif 1.0 E                  Toolkit (OSF/Motif Release 1.2.5), OSF/Motif Release 5                  1.1.3 Toolkit, and the XUI Toolkits.   F               o  Development support is provided for the CDE Motif 1.0                  Toolkit only.  D               o  Language support is provided for C++ as well as forI                  updated Motif language bindings for Pascal, Fortran, and                   C.   H               o  Language bindings for Ada are available for the OpenVMSH                  Alpha and OpenVMS VAX platforms only as part of the AdaI                  Version 3.5A for OpenVMS layered product. Note, however, F                  that these bindings do not include enhancements addedG                  subsequent DECwindows Motif for OpenVMS Version 1.2-6.   H               Although development support is expressly provided for theG               CDE Motif 1.0 Toolkit, you can choose during installation I               to save the OSF/Motif Release 1.1.3 programming environment G               that existed on your system prior to the DECwindows Motif 0               for OpenVMS Version 1.2-4 product.  G               If you install the software using the POLYCENTER Software B               Installation utility, and if programming support forE               the OSF/Motif Release 1.1.3 Toolkit is present, you can F               choose to save the header files and UIL compiler used toH               develop OSF/Motif Release 1.1.3 applications. If selected,F               the installation procedure creates a subdirectory calledG               [.DECW$113], and the previous programming files are moved (               into the new subdirectory.    I                                             Programming Release Notes 4-5                 Programming Release Notes      4.1 General Programming     D           See the HP DECwindows Motif for OpenVMS Installation GuideC           for additional information about saving the Release 1.1.3 C           programming environment. For additional information about D           Release 1.1.3 programming support on the OpenVMS Alpha and3           OpenVMS I64 platforms, see Section 4.3.3.   C     4.1.8 Multithreaded Applications with Upcalls Enabled No Longer /           Cause Address Corruption (Alpha Only)              V1.5  =           Previously, on systems running DECwindows Motif for D           OpenVMS Alpha Version 1.3 or higher, compiling and runningB           multithreaded DECwindows Motif applications with upcallsA           enabled could corrupt random addresses in the user-mode @           stack. This problem has been corrected with DECwindows(           Motif for OpenVMS Version 1.5.  D     4.1.9 DECwindows Display Server Blocks Write Operations When All&           Transport Buffers are in Use             V1.5  A           The DECwindows X display server blocks write operations C           to the DECwindows Motif client when all transport buffers C           are in use. If the client fails to read and free a buffer D           within the 30-second timeout period, the server closes theE           connection. During this timeout period, the server may hang 7           and not process any other requests or events.   D           Prior to DECwindows Motif Version 1.3, the client software=           would transfer events from the transport buffers to D           internal memory using a user-mode AST. Therefore, a clientC           would only fail to read a buffer if suspended or if user- 9           mode ASTs were disabled for a prolonged period.   A           Since Version 1.3, the DECwindows Motif client does not C           read from the transport buffer until a client function is E           called that either processes events or requires a reply. If E           a client is not actively processing events for a particular ?           display connection, the server may hang and close the @           connection when events do arrive. Programs that use XtB           to create an application context and then process events?           using XtAppMainLoop will not experience this problem.   !     4-6 Programming Release Notes            I                                                 Programming Release Notes I                                                   4.1 General Programming     D         4.1.10 Functions Calling getaddrinfo and getnameinfo are not1                Threadsafe Over TCP/IP Connections                  V1.5  ?               HP TCP/IP Services for OpenVMS does not currently C               provide threadsafe implementations of the getaddrinfo B               and getnameinfo functions. Therefore, the DECwindowsD               implementation of XOpenDisplay, IceOpenConnection, andG               images built upon these functions are also not threadsafe E               when opening connections over the TCPIP transport. This H               applies equally to TCPIP transport connections that follow2               either the IPv4 or IPv6 name format.  G         4.1.11 Increasing the Limit of Top-Level Widgets Allowed by the                 UIL Compiler                  V1.3-1  H               The UIL compiler has a maximum number of top-level widgetsC               that it can write to the UID file. A top-level widget D               is one that is named and not referenced within the UILG               compilation. By default, the maximum number of widgets is I               set to 1000. If this limit is exceeded, the following error 7               message is displayed by the UIL compiler:                  $  UIL test.uil F               %UIL-F-SUBMIT_SPR, internal error - submit defect report  I               To change this limit and prevent this error from occurring, H               use the logical DECW$MRM$MAX_MODULE_WIDGET. Make sure thatG               you define the logical prior to running the UIL compiler,                as follows:   7               $  DEFINE DECW$MRM$MAX_MODULE_WIDGET 2000                $  UIL test.uil   F                 ________________________ Note ________________________  B                 The error message noted above can also result fromD                 other compilation problems. If you have already usedB                 the DECW$MRM$MAX_MODULE_WIDGET logical to increaseF                 the maximum number of top-level widgets, and the errorE                 continues to be displayed during compilation, examine E                 the UIL file for other build issues and dependencies.   F                 ______________________________________________________  I                                             Programming Release Notes 4-7                 Programming Release Notes      4.1 General Programming     '     4.1.12 Increased Stack Requirements              V1.3  E           The addition of significant new functionality in the client C           libraries may increase the stack space used by DECwindows E           Motif at run time. Client applications that call DECwindows E           Motif functions from threads other than the main thread may &           experience a stack overflow.  @           If an overflow occurs, rebuild the application using a0           larger stack size for created threads.  D           Note that this problem does not occur with single-threaded?           applications or those multithreaded applications that @           make all their calls to DECwindows Motif from the main           application thread.   E     4.1.13 Privileges Required for ICE, Proxy Manager, and LBX Server             Processes             V1.3  B           The Inter-Client Exchange (ICE), proxy manager, and Low-?           Bandwidth X (LBX) proxy server each provide functions D           that can establish separate server processes. These server@           processes may require certain system resources to gainB           access to one or more transport interfaces and to manage           client connections.   D           The following table shows the minimum privileges required,?           according to network transport, to gain access to the             appropriate resources:  E           ___________________________________________________________ E           Transport___Privilege______________________________________              TCPIP       NETMBX  0           DECNET      TMPMBX, NETMBX, and SYSNAM  E           LOCAL_______PRMMBX_and_SYSGBL______________________________   1     4.1.14 Support for Display PostScript Removed              V1.2-6  ?           Starting August 1, 1998, support was discontinued for C           the Display PostScript software licensed by Adobe Systems D           Incorporated. This action resulted from Adobe ending their7           former ongoing support of Display PostScript.   !     4-8 Programming Release Notes            I                                                 Programming Release Notes I                                                   4.1 General Programming     A               Due to this decision, HP is contractually obligated B               to remove all Display PostScript capability from theB               DECwindows Motif software. This includes all relatedF               translated-image support and any functionality described=               in the following programming reference manuals:   E               o  VMS DECwindows Display PostScript System Programming                   Supplement   D               o  Display PostScript System: Perspective for Software                  Developers   D               o  Display PostScript System: Client Library Reference                  Manual   <               o  Display PostScript System: Color Extensions  C               o  Display PostScript System: pswrap Reference Manual   <               o  PostScript Document Structuring Conventions*                  Specification Version 2.1  I               There is no workaround. See the following sections for more H               information on the potential impact to applications in the+               DECwindows Motif environment.   8         4.1.14.1 Impact on DECwindows Motif Applications  G               Removing Display PostScript from DECwindows Motif impacts H               any application that relies on its capabilities to presentF               and display graphics and documents in PostScript format.  F               Unfortunately, this includes not only those applicationsC               developed by HP, such as the CDA Viewer, but also any G               third-party, user-written, or translated VAX applications C               that depend on one or more of the following files and E               libraries. These items are no longer a part the product H               kit and are removed from your system when upgrading from aC               previous version of DECwindows Motif client software.   %               o  PSWRAP command (DCL)   4               o  Display PostScript (XDPS) libraries  3                     [SYSLIB]XDPS$DPSBINDINGSSHR.EXE 1                     [SYSLIB]XDPS$DPSCLIENTSHR.EXE .                     [SYSLIB]XDPS$DPSLIBSHR.EXE  D               o  Display PostScript header files and sample programs  I                                             Programming Release Notes 4-9                 Programming Release Notes      4.1 General Programming     1           o  Translated-Image Support (TIS) files   :                 [SYSLIB]XDPS$DPSBINDINGSSHR_TV_SUPPORT.EXE8                 [SYSLIB]XDPS$DPSCLIENTSHR_TV_SUPPORT.EXE5                 [SYSLIB]XDPS$DPSLIBSHR_TV_SUPPORT.EXE 1                 [SYSLIB]CDA$ACCESS_TV_SUPPORT.EXE 3                 [SYSLIB]DDIF$VIEWSHR_TV_SUPPORT.EXE 2                 [SYSLIB]DECW$BKRSHR_TV_SUPPORT.EXE3                 [SYSLIB]DECW$MAILSHR_TV_SUPPORT.EXE   E           The actual effect of removing Display PostScript depends on D           the extent to which it was implemented in the application.A           Applications that call the PSWRAP command may fail only =           at the point where the command is invoked. However, @           applications that link against one or more of the XDPSD           libraries or TIS images will fail to function entirely due*           to unresolved links at run time.  ?           As a result, you may need to modify those portions of @           DECwindows Motif applications that rely on these files=           to run successfully in the current DECwindows Motif            environment.  (     4.1.14.2 Impact on Java Applications  D           The Java Development Kit (JDK) for OpenVMS Version 1.2.2-1B           contains two shareable images (JAVA$FONT_MANAGER_SHR.EXE@           and JAVA$FONT_MANAGER_G_SHR.EXE) that link against the?           Display PostScript (XDPS) libraries. As a result, all @           Java applications built with this kit that use DisplayE           PostScript capabilities will fail in the current DECwindows            Motif environment.  @           Note that this restriction only applies to the VersionD           1.2.2-1 kit. The Java machine for the 1.1* series, as wellC           as all releases of the JDK subsequent to Version 1.2.2-1, D           are not dependent on the Adobe Display PostScript software           or its libraries.   ;     4.1.15 Problems Using the DECW$INCLUDE:INTRINSIC.H File              V1.2-5  ?           The DECwindows header file, DECW$INCLUDE:INTRINSIC.H, ?           redefines the globalref macro to be extern when using C           the DEC C compiler, even when the /STANDARD=VAXC compiler D           switch is specified. This could have a wide impact on user           applications.   "     4-10 Programming Release Notes           I                                                 Programming Release Notes I                                                   4.1 General Programming     B               This redefinition in INTRINSIC.H is required because@               DECwindows needs to ensure that references to dataE               located in the DECwindows shared images by user-written G               applications use the same extern model that was used when 9               the DECwindows shared images were compiled.   A               To workaround this problem, rather than having your A               application use globalref and globaldef for its own B               variables, use the following preprocessor directive:  0               #pragma extern_model strict_refdef  F               This workaround has the advantage of being strictly ANSIH               compliant. This pragma directive is described in the DEC C6               User's Guide for OpenVMS Systems manual.  :         4.1.16 DECW$WML.EXE Looks in Current Directory For"                DECW$WML_TOKENS.DAT                 1.2-4   @               The program SYS$SYSTEM:DECW$WML.EXE can be used toD               customize the parsing of UIL files. It reads a list ofC               tokens from the file DECW$WML_TOKENS.DAT. In previous G               versions of DECwindows Motif, this tokens file was always F               read from SYS$LIBRARY. However, starting with DECwindowsG               Motif for OpenVMS Version 1.2-4, DECW$WML.EXE first looks G               for this file in the current directory before looking for H               it in SYS$LIBRARY. This allows a customized tokens file to               be used.  H         4.1.17 Running Translated Images on OpenVMS Systems (Alpha Only)                 V1.2-3  D               The OpenVMS operating system provides translated imageD               support (TIS) that addresses the following issues whenG               migrating from the OpenVMS VAX to OpenVMS Alpha operating                system platform:  :               o  Lack of full-language programming support  @               o  Unavailability of source code for recompilation  A               o  Difficulty recompiling code that depended on VAX &                  architecture features  I                                            Programming Release Notes 4-11                 Programming Release Notes      4.1 General Programming     ;           The translated-image environment supports the VAX A           programming language features that were introduced with A           the VMS Version 5.5-2 release. The TIS environment also B           provides support for those images that are restricted toB           using the VMS Version 5.5-2 system services and run-time           library entry points.   B           DECwindows Motif offers translated-image support as part=           of the installation procedure. The DECwindows Motif A           TIS environment includes support for running translated ?           DECwindows Motif for OpenVMS VAX images on an OpenVMS B           Alpha system, provided the images were built against the@           OSF/Motif Release 1.1.3 libraries. It does not include?           support for running translated images that were built D           against a later version of the OSF/Motif Release libraries           (1.2 or greater).   D           If you want to run an application that was built against aB           later version of the OSF/Motif libraries (available with?           DECwindows Motif for OpenVMS Versions 1.2 and later), B           you must compile and link the application natively on an.           OpenVMS Alpha or OpenVMS I64 system.  @           If you cannot build your VAX application on an OpenVMS>           Alpha system, you can translate it using the OpenVMS>           Migration Software for VAX to Alpha (OMSVA) product,>           provided that your application was built against the:           OSF/Motif Release 1.1.3 programming environment.  C           Most VAX images built against the OSF/Motif Release 1.1.3 C           programming environment can be copied to an OpenVMS Alpha B           system, translated, and run successfully. Note, however,@           that the OSF/Motif Release 1.1.3 shareable images that@           are used with translated images are different from and@           incompatible with the shareable images used for native?           images. As a result, the following image restrictions            apply:  B           o  Do not use both native and translated images that use@              DECwindows Motif software in a process. Either portB              or translate all the images that use DECwindows Motif:              software and all images that call each other.  E           o  Translated images that dynamically activate a DECwindows ;              Motif image using LIB$FIND_IMAGE_SYMBOL from a 0              translated image are not supported.  "     4-12 Programming Release Notes           I                                                 Programming Release Notes I                                                   4.1 General Programming     B               For information on enabling the DECwindows Motif TISB               environment, see the HP DECwindows Motif for OpenVMSC               Installation Guide. For more information on OSF/Motif ?               application programming support, see Section 4.3.   E         4.1.18 UIL Compilation Problems with Looped Object References                  V1.2  F               The UIL compiler can omit information about some objectsH               from the UID file when there is a self-contained hierarchyA               of objects and each named object is only referenced I               internally (by another object in the hierarchy). Minimally, F               one of the references in the hierarchy must be something.               other than a child relationship.  C               To determine which objects contain omissions, use the H               /LIST and /MACHINE_CODE qualifiers during compilation. TheH               resulting list file indicates the objects that are missing               information.  F               To prevent this from occurring, add a name to one of the/               unnamed objects in the hierarchy.   8         4.1.19 Compiling Applications Written in Fortran                 V1.1  I               Some of the include files used for writing DECwindows Motif G               applications in Fortran, such as the DECW$MOTIF.FOR file, D               contain structure definitions that cause memory layout?               changes, depending on the compiler switches used.   .               You can do one of the following:  F               o  Use the CDEC$ OPTIONS in the source code so that yourD                  Fortran programs work correctly with the DECwindows*                  Motif run-time libraries:  E                  -  Before you include files in your program, add the (                     following statement:  8                     CDEC$ OPTIONS /ALIGN=RECORDS=NATURAL  F                  -  Following the INCLUDE statement, add the following                     statement:  %                     CDEC$ END OPTIONS   I                                            Programming Release Notes 4-13                 Programming Release Notes      4.1 General Programming                      For example:  4                 CDEC$ OPTIONS /ALIGN=RECORDS=NATURAL(                 INCLUDE "DECW$MOTIF.FOR"!                 CDEC$ END OPTIONS   E           o  Use the Fortran compiler switch, /ALIGN=RECORDS=NATURAL, ,              when you compile your programs.  .     4.1.20 Compiling Applications Written in C             V1.0  >           With DEC C, header files do not need to be extractedC           from the text library if you define the DECC$TEXT_LIBRARY "           logical name as follows:  @           $ DEFINE DECC$TEXT_LIBRARY SYS$LIBRARY:DECC$RTLDEF.TLB       4.2 Application Programming   ;           This section contains release notes pertaining to :           developing applications for the DECwindows Motif           environment.        4.2.1 CDA Viewer Programming  E           This section contains programming information about the CDA ,           application and run-time services.  B     4.2.1.1 Corrected Image Ident for SYS$LIBRARY:DDIF$VIEWSHR.EXE             (Alpha Only)             V1.3  >           The SYS$LIBRARY:DDIF$VIEWSHR.EXE image supplied withC           DECwindows Motif for OpenVMS Alpha Version 1.2-6 included D           the wrong image ident. Programs linked against the VersionC           1.2-6 image could not load and would report SHRIDMISMATCH =           error. This has been corrected, and the image ident )           restored to its original value.   E           Applications linked against the image supplied with Version D           1.2-6 of DECwindows Motif will need to be relinked againstA           the corrected image. Note that this only impacts images A           linked against the V1.1.3 compatibility version of DDIF B           (such as, DECwindows interface to Notes for OpenVMS) and<           not images using the current DDIF$VIEWSHR12 image.  "     4-14 Programming Release Notes           I                                                 Programming Release Notes I                                               4.2 Application Programming     0         4.2.1.2 Message for Style Guide Fallback                 V1.2  I               The following message is displayed when a local style guide                cannot be found:  F          STYGDEFBK,  Fallback to nonlocale-specific style guide: file-             spec                Level: Informational  H             Explanation: Since the locale-specific style guide cannot beG             found, the nonlocale-specific version of the style guide is              used.   9         4.2.1.3 Using Logical Names with CONVERT Commands                  V1.2  E               During a document conversion, if a logical name is used F               to specify the directory of the primary document and theE               document file extension is omitted, external references A               that contain relative file specifications cause the !               conversion to fail.   I               This failure occurs because the back-end converter examines F               the converter processing options, although the front-endC               converter opens the input file. Because the converter E               software cannot predict what default file extension the G               front-end converter might apply, it uses the OpenVMS file I               services to resolve the logical name and to find the actual H               file specification so that the directory can be parsed and5               extended with a relative specification.   H               The conversion fails only when the external reference uses-               a format such as the following:                  sys$login:mydoc   C               In this case, the reference will not be resolved. The D               reference is resolved in all other cases. For example:  !               sys$login:mydoc.doc                 disk$:[smith]mydoc$               disk$:[smith]mydoc.doc  I                                            Programming Release Notes 4-15                 Programming Release Notes      4.2 Application Programming          4.2.2 DEClinks Programming  A           This section contains programming information about the 5           DEClinks application and run-time services.   A     4.2.2.1 DEClinks Shareable Libraries Not Available (I64 only)              V1.5  A           The DEClinks shareable libraries (LWK$DXMSHR*.EXE) have D           not been ported to the OpenVMS I64 environment and are notD           available with DECwindows Motif for OpenVMS Version 1.5 or,           later on the OpenVMS I64 platform.  @           These shareable libraries were retained in the OpenVMS:           Alpha environment to prevent regression in otherB           applications. The libraries may be available in a futureB           release if they are deemed functionally necessary in the"           OpenVMS I64 environment.       4.2.3 DECterm Programming   A           This section contains programming information about the 4           DECterm application and run-time services.       4.2.3.1 DECCRA Sequence              V1.2  =           DECterm supports the DECCRA (Copy Rectangular Area) @           sequence in a limited way. The entire page needs to beB           copied at once, and either the source or the destinationE           page must be the current page (for example, you cannot copy /           from one off-screen page to another).        4.2.3.2 DECLFKC Sequence             V1.2  B           Since DECterm does not have a user interface to redefine=           the F5 (Break) key, the DECLFKC (Local Function Key D           Control) sequence redefines the F5 key when "0" (all keys)8           is used to select which key is to be modified.       4.3 OSF/Motif Toolkit (Xm)  E           This section describes restrictions and corrections related (           to the OSF/Motif Toolkit (Xm).  "     4-16 Programming Release Notes           I                                                 Programming Release Notes I                                                4.3 OSF/Motif Toolkit (Xm)     C         4.3.1 OSF/Motif Release 1.2.2 and X11 Release 5 and Greater !               Shareable Libraries                  V1.2  A               Because the OSF/Motif Release 1.2.2 Toolkit and the H               OSF/Motif Release 1.1.3 Toolkit are not binary compatible,C               applications must link with one toolkit or the other. I               Applications based on OSF/Motif Release 1.2.2 can only link F               against OSF/Motif 1.2.2-based and X11 R5-based shareableF               libraries. Applications based on OSF/Motif Release 1.1.3E               can only link against OSF/Motif 1.1.3-based and X11 R4- (               based shareable libraries.  I               To provide both OSF/Motif Release 1.2.2-based and OSF/Motif I               Release 1.1.3-based shareable libraries, the Release 1.1.3- G               based libraries have the same file names as in DECwindows F               Motif Version 1.1, and the Release 1.2.2-based libraries6               contain a suffix of either "R5" or "12".  E               Shareable libraries that work with either the OSF/Motif B               Release 1.1.3 Toolkit or the OSF/Motif Release 1.2.2B               Toolkit do not have a suffix. These libraries are as               follows:                 V1.2-6                 o  CDA$ACCESS.EXE   $               o  DECW$D2DXLIBSHR.EXE  $               o  DECW$XEXTLIBSHR.EXE  !               o  DECW$XLIBSHR.EXE                  o  XIE$SHRLIB.EXE   D               Shareable libraries that are linked with Release 5 andH               greater of the Xt Toolkit have a suffix of "R5". LibrariesF               based on the XUI Toolkit have no R5 equivalent librariesG               and should not be included in a linker options file based F               on X11R5, X11R6.6, or OSF/Motif Release 1.2.2. Table 4-1%               lists these file names.   F                 ________________________ Note ________________________  C                 The DECW$XLIBSHR.EXE file is the X11R5 version, not *                 the X11R4 version of Xlib.  F                 ______________________________________________________  I                                            Programming Release Notes 4-17                 Programming Release Notes      4.3 OSF/Motif Toolkit (Xm)    B           Table 4-1 Names of Shareable Libraries Based on X11R5 orE           __________Greater__________________________________________   C                                       Names of Files Based on R5 or E           Names_of_Files_Based_on_R4__Greater________________________   ,           DECW$DWTLIBSHR.EXE          (None)  ,           DECW$DWTSHR.EXE             (None)  :           DECW$XMULIBSHR.EXE          DECW$XMULIBSHRR5.EXE  <           DECW$XTRAPLIBSHR.EXE        DECW$XTRAPLIBSHRR5.EXE  E           DECW$XTSHR.EXE______________DECW$XTLIBSHRR5.EXE____________   B           Releases 5 and greater do not provide an equivalent fileA           for DECW$DWTLIBSHR.EXE or DECW$DWTSHR.EXE. Applications >           that are built for Releases 5 and beyond cannot link           against these files.  D           Shareable libraries that are linked with OSF/Motif ReleaseA           1.2.2 have a suffix of "12". They should be linked only >           with libraries compatible with X11R5 or X11R6.6, andD           OSF/Motif Release 1.2.2. Table 4-2 lists these file names.  C           Table 4-2 Names of Shareable Libraries Based on OSF/Motif E           __________Release_1.2.2____________________________________   E           Names of Files Based on     Names of Files Based on Release E           Release_1.1.3_______________1.2.2__________________________   8           DDIF$VIEWSHR.EXE            DDIF$VIEWSHR12.EXE  7           DECW$BKRSHR.EXE             DECW$BKRSHR12.EXE   :           DECW$DXMLIBSHR.EXE          DECW$DXMLIBSHR12.EXE  8           DECW$MAILSHR.EXE            DECW$MAILSHR12.EXE  :           (None)                      DECW$MRMLIBSHR12.EXE  ,           DECW$PRINTWGTSHR.EXE        (None)  <           DECW$TERMINALSHR.EXE        DECW$TERMINALSHR12.EXE  9           DECW$XMLIBSHR.EXE           DECW$XMLIBSHR12.EXE   7           DGIT$LIBSHR.EXE             DGIT$LIBSHR12.EXE   6           IMG$SHRLIB.EXE              IMG$SHRLIB12.EXE  E                                              (continued on next page)   "     4-18 Programming Release Notes           I                                                 Programming Release Notes I                                                4.3 OSF/Motif Toolkit (Xm)     E               Table 4-2 (Cont.) Names of Shareable Libraries Based on I               __________________OSF/Motif_Release_1.2.2__________________   I               Names of Files Based on     Names of Files Based on Release I               Release_1.1.3_______________1.2.2__________________________   :               LWK$DXMSHR.EXE              LWK$DXMSHR12.EXE  I               XNL$SHR.EXE_________________XNL$SHR12.EXE__________________   G               There is no DECW$PRINTWGTSHR12.EXE file; the Print Widget 7               is part of the DECW$DXMLIBSHR12.EXE file.   H               The DECW$MRMLIBSHR12.EXE file is a new image that includesF               Motif Resource Manager (Mrm) routines that were formerlyF               part of the DECW$XMLIBSHR.EXE file. Any program based onG               OSF/Motif Release 1.2.2 that calls Mrm routines to access 7               .UID files should link with this library.   F               For example, a typical linker options file for a programC               based on OSF/Motif Release 1.1.3 might be as follows:   *               SYS$SHARE:DECW$XLIBSHR/SHARE(               SYS$SHARE:DECW$XTSHR/SHARE,               SYS$SHARE:DECW$DWTLIBSHR/SHARE+               SYS$SHARE:DECW$XMLIBSHR/SHARE ,               SYS$SHARE:DECW$DXMLIBSHR/SHARE  D               To link this program with OSF/Motif Release 1.2.2, the7               linker options file should be changed to:   *               SYS$SHARE:DECW$XLIBSHR/SHARE-               SYS$SHARE:DECW$XTLIBSHRR5/SHARE -               SYS$SHARE:DECW$XMLIBSHR12/SHARE .               SYS$SHARE:DECW$MRMLIBSHR12/SHARE.               SYS$SHARE:DECW$DXMLIBSHR12/SHARE  F               These changes eliminate the reference to the XUI ToolkitD               (DECW$DWTLIBSHR.EXE) and links with the Motif Resource-               Manager (DECW$MRMLIBSHR12.EXE).           I                                            Programming Release Notes 4-19                 Programming Release Notes      4.3 OSF/Motif Toolkit (Xm)    7     4.3.2 OSF/Motif Release 1.2.2 Callable UIL Compiler              V1.2-6  A           The OSF/Motif Release 1.2.2 Toolkit contains a callable >           User Interface Language (UIL) compiler. You can linkD           against this image by including the following in your link           options:  %           SYS$SHARE:DECW$UILSHR/SHARE   ?           For information about the callable interface, see the B           OSF/Motif Programmer's Guide published by Prentice Hall.  =     4.3.3 OSF/Motif Release 1.1.3 Programming Support and XUI   D           The following sections describe issues related to buildingC           OSF/Motif Release 1.1.3 applications in the OpenVMS Alpha '           and OpenVMS I64 environments.   D     4.3.3.1 Building Release 1.1.3 Applications in the OpenVMS Alpha$             Environment (Alpha Only)             V1.2  D           The X Window and OSF/Motif libraries that are shipped withB           DECwindows Motif Versions 1.2 and later are incompatible=           with those shipped with previous versions. Run-time D           compatibility has been preserved but backwards programmingE           compatibility has not. As a result, support for programming @           in the XUI or Motif Release 1.1.3 environment that wasB           provided in previous versions of DECwindows Motif is not>           available in DECwindows Motif Versions 1.2 or later.  =           If you have legacy applications built against Motif ?           Release 1.1.3, you can choose to preserve the Release ?           1.1.3 programming environment during DECwindows Motif @           installation. The installation procedure gives you theC           option of saving the programming files that already exist A           on your system. If you choose to save these files, they ?           are moved to subdirectories where you can access them C           for programming. Specifically, the installation creates a D           subdirectory called [.DECW$113] in each of the directoriesC           listed in Table 4-3 and moves the previous files into the            new subdirectory.   "     4-20 Programming Release Notes           I                                                 Programming Release Notes I                                                4.3 OSF/Motif Toolkit (Xm)     F               For more information about saving the programming files,B               see the HP DECwindows Motif for OpenVMS Installation               Guide.  I               Table 4-3 Directories for Previous XUI or Motif Programming I               __________Environment______________________________________   I               Directory_____Contents____New_Location_____________________   K               DECW$INCLUDE  C header    SYS$SYSROOT:[DECW$INCLUDE.DECW$113] !                             files   E               SYS$SYSTEM    UIL         SYS$SYSROOT:[SYSEXE.DECW$113] $                             compiler  E               SYS$LIBRARY   Non-C       SYS$SYSROOT:[SYSLIB.DECW$113] $                             languageI               ______________bindings_____________________________________   F               To program with these files, include the new [.DECW$113]G               subdirectories in the search path for each of the logical 8               names. For example, perform the following:  B               o  Change the definition of DECW$INCLUDE as follows:  ,                  $ SHOW LOGICAL DECW$INCLUDEV                     "DECW$INCLUDE" = "SYS$SYSROOT:[DECW$INCLUDE]" (DECW$LOGICAL_NAMES)B                          = "SYS$SYSROOT:[DECW$INCLUDE.EXTENSIONS]"  K                  $ DEFINE/EXECUTIVE/TABLE=DECW$LOGICAL_NAMES DECW$INCLUDE - 8                   SYS$SYSROOT:[DECW$INCLUDE.DECW$113], -/                   SYS$SYSROOT:[DECW$INCLUDE], - 7                   SYS$SYSROOT:[DECW$INCLUDE.EXTENSIONS]   H               Place the new [.DECW$113] subdirectory first in the searchF               list, since many of the files that have been updated forD               this release have the same name as the files that wereG               moved to the [.DECW$113] subdirectory. Thus, the files in <               [.DECW$113] are used for software development.  1               If DECW$INCLUDE is redefined in the H               SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM command procedure,@               then modify the previous instructions accordingly.    I                                            Programming Release Notes 4-21                 Programming Release Notes      4.3 OSF/Motif Toolkit (Xm)    E           To use the UIL compiler for XUI or OSF/Motif Release 1.1.3, &           perform the following steps:  !           1. Create a file called C              SYS$SYSROOT:[SYSEXE.DECW$113]DECW$UILCOMPILER.CLD that )              contains the following text:   '              define type trace_keywords                keyword tokens               keyword symbols   )              define type warning_keywords                 keyword nowarnings&               keyword noinformationals  )              define type version_keywords (               keyword V1, syntax=xui_uil1               keyword V2, syntax=xui_uil, default /               keyword MOTIF11, syntax=motif_uil   "              define syntax xui_uil$               image decw$uilcompiler  $              define syntax motif_uil!               image decw$uilmotif                 define verb uil$               image decw$uilcompiler.               parameter p1, label=source_file,H                prompt="File", value(required,noconcatenate,type=$infile)0               qualifier trace, label=trace_qual,J                value(list,noconcatenate,type=trace_keywords), nonnegatable6               qualifier warnings, label=warnings_qual,>                value(list,noconcatenate,type=warning_keywords)1               qualifier list, label=listing_file, *                batch, value(type=$outfile)4               qualifier machine, label=machine_qual,4               qualifier output, label=resource_file,,                default, value(type=$outfile)=               qualifier version, label=version_qual, default, ,                value(type=version_keywords),                nonnegatable B               qualifier XUI, default, nonnegatable, syntax=xui_uil=               qualifier MOTIF, nonnegatable, syntax=motif_uil   C               qualifier widget_meta_description, label=widget_qual, ;                value(required, noconcatenate, type=$infile)   "     4-22 Programming Release Notes           I                                                 Programming Release Notes I                                                4.3 OSF/Motif Toolkit (Xm)     (                   disallow XUI and MOTIF  I               2. Set the DCL command table to use the XUI UIL compiler as                   follows:   P                  $ SET COMMAND SYS$SYSROOT:[SYSEXE.DECW$113]DECW$UILCOMPILER.CLD  F                 ________________________ Note ________________________  F                 If you want to revert back to the previous UIL command:                 definition, execute the following command:  >                 $ SET COMMAND SYS$LIBRARY:DECW$UILCOMPILER.CLD  F                 ______________________________________________________  F         4.3.3.2 Building Release 1.1.3 Applications in the OpenVMS I64&                 Environment (I64 Only)                 V1.5  E               Note that although DECwindows Motif for OpenVMS Version D               1.5 includes an updated set of OSF/Motif Release 1.1.3G               shareable libraries, it does not include a Release 1.1.3- H               based UIL compiler or set of related C header files on theI               OpenVMS I64 platform (as consistent with recent releases of 2               DECwindows Motif for OpenVMS Alpha).  I               To perform a native build of one or more applications based I               on the Release 1.1.3 images in the OpenVMS I64 environment:   B               1. Compile your application source files using the CD                  header files (.H) from a previous, saved version ofF                  the OSF/Motif Release 1.1.3 environment on an OpenVMS                  Alpha system.  H               2. Link against the ported shareable images. Note that theH                  ported image names do not have a suffix such as "R5" orG                  "12". For example, for Release 1.1.3-based builds, you H                  should link against DECW$XTSHR and DECW$XMLIBSHR rather:                  than DECW$XTLIBSHRR5 and DECW$XMLIBSHR12.  )               3. Do one of the following:   D                  o  If you do not need to make UIL changes, run yourH                     application(s) with UID files copied from an OpenVMSI                     Alpha system to the OpenVMS I64 run-time environment.   I                                            Programming Release Notes 4-23                 Programming Release Notes      4.3 OSF/Motif Toolkit (Xm)    C              o  If changes are necessary, use the UIL compiler from B                 a previous, saved version of the OSF/Motif ReleaseA                 1.1.3 programming environment on an OpenVMS Alpha ?                 system, and copy the resulting UID files to the 1                 OpenVMS I64 run-time environment.   C     4.3.3.3 Additional Motif Release 1.1.3 Compilation and Run-time              Restrictions             V1.2-3  >           You will encounter problems if you save the previous@           (Release 1.1.3) programming environment and attempt toE           run an OSF/Motif Release 1.1.3 (Xlib Release 4) application B           created on a system running DECwindows Motif Version 1.2E           or later from an executable on a Motif Release 1.1.3 target B           system. That is, if you build an application on a systemB           running DECwindows Motif Version 1.2 or later, the imageC           is linked with Xlib Release 5, by default. If you attempt D           to run that executable on a system where OSF/Motif ReleaseC           1.1.3 is installed, the result is an ident mismatch fatal            error.  >           In addition, the OSF/Motif Release 1.1.3 and ReleaseA           1.2.2 UIL compilers produce different output; they have D           different structures and are therefore not compatible. UseA           the appropriate UIL compiler to produce the correct UID            file.   C           To prevent these issues from occurring, do the following:   :           1. Rename the Release 1.1.3 executable compiler,@              DECW$UILMOTIF.EXE, to DECW$UILMOTIF113.EXE and keepE              the file in the SYS$COMMON directory. By doing this, the C              name of the Release 1.2.2 compiler, DECW$UILMOTIF.EXE, :              does not conflict with the previous compiler.  C           2. Copy the DECW$XLIBSHR.EXE file (Xlib Release 4) to the 4              SYS$COMMON:[SYSEXE.DECW$113] directory.  @              The Xlib Release 5 or greater versions of Xlib haveA              the same name; however, a logical name is defined to D              use the Release 4 version when the programs are linked.C              The changes in minor ident of DECW$XLIBSHR.EXE between ?              DECwindows Motif Version 1.2 and later versions of D              DECwindows caused a loss of backward compatibility with*              native Release 1.1.3 systems.  "     4-24 Programming Release Notes           I                                                 Programming Release Notes I                                                4.3 OSF/Motif Toolkit (Xm)     H               3. If you save the previous programming environment duringF                  installation, create the following two files and copyD                  them to the SYS$COMMON:[SYSEXE.DECW$113] directory:  +                  o  DECW$UILCOMPILER113.CLD   B                     This file enables UIL/OSF Motif and UIL/XUI toF                     function for either XUI or OSF/Motif Release 1.1.3D                     if you select DECW$UILMOTIF113.EXE for OSF/MotifB                     Release 1.1.3 or DECW$UILCOMPILER.EXE for XUI.  /                  o  DECW$DEFINE113_LOGICALS.COM   E                     This file points to the saved header files, which F                     in turn point to the Xlib Release 4 version of the*                     DECW$XLIBSHR.EXE file.  C               4. An application must be run on the same version (or E                  higher) of the operating system as the version where I                  it is linked. For example, an application that is linked D                  on a OpenVMS Version 7.3-2 system must be run on an2                  OpenVMS 7.3-2 (or higher) system.  I         4.3.4 Memory Leaks in Cascade and Toggle Buttons Corrected (Alpha                Only)                  V1.5  C               Previously, when creating and subsequently destroying E               cascade or toggle buttons (or their gadgets) on systems D               running DECwindows Motif for OpenVMS Version 1.2-4 andB               higher, unused graphics context objects were be leftD               behind. These objects resulted in memory leaks in bothG               the client and server that persisted until the client was                terminated.   G               The problem occurred when widgets associated one graphics I               context with normal state and another with the armed state. G               Under normal use, most widgets share the same colors, and F               therefore, share a pair of graphics contexts. The memoryC               leaks were only significant if many such widgets with G               differing background colors or selected text were created                and destroyed.  E               This problem has been corrected in DECwindows Motif for "               OpenVMS Version 1.5.  I                                            Programming Release Notes 4-25                 Programming Release Notes      4.3 OSF/Motif Toolkit (Xm)    @     4.3.5 Memory Leaks in Bulletin Boards Corrected (Alpha Only)             V1.5  D           Previously on systems running DECwindows Motif for OpenVMS=           Version 1.2-4 or later, when a BulletinBoard widget @           was created and the default font list was used for theA           XmNbuttonFontList, XmNlabelFontList, or XmNtextFontList C           resources, the reference count to the font list entry was D           cached incorrectly. This prevented the memory used for theE           font list from being freed when the font list was no longer            required.   @           This problem only occurred when the bulletin board was>           created as a descendant of another bulletin board orE           vendor shell widget whose own default font lists were later            changed.  A           This problem has been corrected in DECwindows Motif for            OpenVMS Version 1.5.  >     4.3.6 Compile-Time Incompatibilities in Motif Header Files             V1.2-3  E           Several macro definitions are removed from the Motif header A           files in the OSF/Motif programming support. The changes ,           affect the following header files:             o  DECW$INCLUDE:XMP.H   3              The following definitions are removed:   5              -  #define XmLONGBITS sizeof(Cardinal)*8   5              -  #define XmHALFLONGBITS (XmLONGBITS/2)   C              These macros are replaced in the same header file with !              the following macro:                 -  XmOFFSETBITS  <              Update the code to call the XmOFFSETBITS macro.  !           o  DECW$INCLUDE:TEXTP.H   3              The following definitions are removed:   )              -  #define MAXINT 2147483647 9                 /* Biggest number that can fit in long */   &              -  #define NODELTA MAXINT  "     4-26 Programming Release Notes           I                                                 Programming Release Notes I                                                4.3 OSF/Motif Toolkit (Xm)     H                  The definition of MAXINT is operating-system dependent.F                  Include this definition in applications in one of the                   following ways:  >                  -  Include the appropriate system-header file  '                  -  Define the constant   !         4.3.7 Use of _Xm Routines                  V1.2  G               The OSF/Motif Toolkit libraries contain many undocumented G               routines, which are prefixed with _Xm. These routines are E               intended to be used only by the standard Motif widgets. G               OSF reserves the right to modify the API or functionality G               of these routines, or to delete them altogether in future                releases.   G                 _______________________ Caution _______________________   A                 HP supplies access to the _Xm routines by copying E                 them into the shareable image transfer vector for the E                 OSF/Motif Release 1.2.2 Toolkit. HP does not document F                 or support these routines or guarantee their continuedD                 existence in future releases. Application developers?                 who use these routines do so at their own risk.   F                 ______________________________________________________  ,         4.3.8 UID Files for Example Programs                 V1.2  C               The UID files used by the Motif example programs must F               be located in either the current directory, DECW$SYSTEM_H               DEFAULTS, or your DECW$USER_DEFAULTS directory. DECwindowsI               Motif does not support accessing remote UID files using the D               DECNET (DECnet or DECnet-Plus) transport. As a result,@               the default directories do not support a node nameF               specification. Entering a node name in the UID directoryI               specification fails to start the application and results in 0               an error similar to the following:  _               X Toolkit Warning: I18NOpenFile: Could not open file decburger.uid - MrmNOT_FOUND "               can't open hierarchy  I                                            Programming Release Notes 4-27                 Programming Release Notes      4.3 OSF/Motif Toolkit (Xm)    <           The UID files can be copied from the DECW$EXAMPLESA           directory. To access a remote UID file, either copy the A           file to a local node on the cluster, or use Distributed D           File System (DFS) to mount the disk that contains the file           on the cluster.   (     4.3.9 Motif Text Widget Translations             V1.0  B           To implement virtual bindings, it is necessary for HP to?           modify the default XmText and XmTextField translation A           manager syntax. Specifically, the following syntax line            is removed:   B           Shift ~Ctrl ~Meta ~Alt <Key>osfDelete:   cut-clipboard()  A           If you use virtual bindings in which the osfCut virtual :           keysym is not bound, no key sequence is bound to=           the cut-clipboard action by default. To work around >           this limitation, override the XmText and XmTextField7           translations in your DECW$XDEFAULTS.DAT file.   7     4.3.10 Restrictions on Mixing Motif and XUI Widgets              V1.0  A           Mixing Motif and XUI widgets is restricted. The problem B           results from the fact that both XUI and Motif have their=           own Vendor Shell widget class. If an application is @           linked against XUI and not Motif, the XUI Vendor ShellA           widget class is used in order to maintain compatibility B           with DECwindows XUI. If an application is linked againstC           Motif, the Motif Vendor Shell widget class is used. Motif A           widgets require the Motif Vendor Shell; XUI widgets are D           compatible with the Motif Vendor Shell. The problem occursC           when an XUI-only application dynamically activates (using C           LIB$FIND_IMAGE_SYMBOL) a shareable image that uses Motif. D           The toolkit makes the decision to use the XUI Vendor ShellB           when the toolkit is initialized and the Motif widgets in@           the dynamically activated shareable image do not work.  @           The workaround is to add the application image name toA           the DECW$USE_XM_VENDOR_SHELL logical name. This logical A           name contains a comma-separated list of image names for A           which the toolkit is to use the Motif Vendor Shell. The D           value of DECW$USE_XM_VENDOR_SHELL logical name defaults to  "     4-28 Programming Release Notes           I                                                 Programming Release Notes I                                                4.3 OSF/Motif Toolkit (Xm)     G               NOTES$MAIN. To add additional image names to this logical (               name, enter the following:  =               $ DEFINE DECW$USE_XM_VENDOR_SHELL "NOTES$MAIN,- +               _$ yourimage1,yourimage2,..."   @               Note that DECW$USE_XM_VENDOR_SHELL does not affectF               applications that use Motif since they are already using%               the Motif Vendor Shell.   0         4.4 DECwindows Extensions to Motif (DXm)  D               This section contains information about the DECwindows.               extensions to the Motif Toolkit.  4         4.4.1 DXmFormSpaceButtonsEqually Restriction                 V1.1  F               The convenience routine DXmFormSpaceButtonsEqually sizesD               and spaces all widgets or gadgets equally if they haveE               a subclass of XmLabel or XmLabelGadget. The results are B               undefined if a widget or gadget is not a subclass of'               XmLabel or XmLabelGadget.   C         4.4.2 SVN Widget Does Not Support Horizontal Live Scrolling                  V1.0  C               Horizontal live scrolling is not supported in the SVN                widget.   (         4.5 X Window System Toolkit (Xt)  E               This section contains release notes pertaining to the X )               Window System Toolkit (Xt).   F         4.5.1 Problem with the Implementation of XtAppAddTimeOut( ) in               DECwindows                 V1.6  C               There was a bug in the way that DECwindows implements H               XtAppAddTimeout( ). When the system time changes (or fallsF               back) to an early time, (like the transition from DST toI               STD time), the time difference is added onto the timer. For F               example if a 10 second timer is set and then system timeE               changes from DST to STD then the timer goes off after 1 A               hour and 10 sec instead of the expected 10 seconds.   I                                            Programming Release Notes 4-29                 Programming Release Notes $     4.5 X Window System Toolkit (Xt)    E     4.5.2 NULL Argument Passed to XtRemoveTimeOut()  Causes an Access            Violation              V1.6  B           The XtRemoveTimeOut function takes timer ID as the input=           that is returned from a XtAddTimeOut()  call. If an C           application passes zero as the input to XtRemoveTimeOut() /           function, it causes access violation.   E           This problem has been corrected in the DECWindows Motif for            OpenVMS Version 1.6.  7     4.5.3 XtGetValues Function and Null Argument Values              V1.3  =           The XtGetValues and XtVaGetValues functions provide 8           argument values through an argument array. TheC           specification of Xt states that value members of argument A           structures must point to an appropriately sized object. C           However, the implementation of Xt has allowed the passing A           of null value members, provided the argument value does C           not exceed 32 bits in length. In this case, Xt writes the ?           argument value directly to the argument value member.   ?           Systems running DECwindows Motif Version 1.3 or later =           still support this usage but generate an Xt warning A           message similar to the following if a null value member C           is detected (where function_name is either XtGetValues or            XtVaGetValues):   >                X Toolkit Warning: NULL ArgVal in function_name  C           If this message is displayed when compiling or running an D           application, modify the application, and eliminate the use            of null member values.  ;     4.5.4 Composite Class Extension Record Run-Time Warning              V1.3  D           With X11R6.6, the boolean option allows_change_managed_setE           was added to the CompositeClassExtensionRec data structure. ?           As a result of this change, applications built with a D           previous version of CompositeClassExtensionRec may displayA           a warning message at run time similar to the following:   "     4-30 Programming Release Notes           I                                                 Programming Release Notes I                                          4.5 X Window System Toolkit (Xt)     W               X Toolkit Warning:  widget class Calc has invalid CompositeClassExtension                record.   B               To prevent this message from displaying, rebuild theE               application with the latest version of the CompositeP.h D               file. Check that the value of the new option is as youH               desire. If the memory is initialized to zero, then it willD               have the same behavior as before. If uninitialized the.               behavior could be unpredictable.  8         4.5.5 XtOpenDisplay Routine and Case Sensitivity                 V1.2-6  G               In some cases the application name in XtOpenDisplay comes_H               from argv[0], which represents the name of the application"               on the command line.  ?               This could be an issue in environments where case E               sensitivity must be preserved (such as when referencing I               ODS-5 system with case preservation enabled or when passingi(               a user-defined argv list).  *         4.6 X Window System Library (Xlib)  I               This section contains information about the X Window System                library (Xlib).   >         4.6.1 Motif Error - Xlib: Unexpected Async Reply Fixed                 V1.6  C               A few applications use ASTs and process events withint@               the ASTs. This caused unexpected async reply errorB               from the Xlibrary. This is not very good programmingH               practice. However, these kinds of situations have now been*               accommodated to some extent.  B         4.6.2 XPutImage Now Displays Wide Graphic Images Correctly                 V1.5  C               An erroneous stop condition within XPutImage has been C               corrected. Applications that call this recursive Xlib E               procedure can now process and paint wide graphic images H               successfully without noticeable clipping or stack overflow               conditions.   I                                            Programming Release Notes 4-31_ _              Programming Release Notesc&     4.6 X Window System Library (Xlib)    /     4.6.3 Xlib Routines Now Use Recursive Locksm             V1.5  9           Display locks implemented in multithreaded Xlib >           applications are now implemented as recursive locks.@           When threading is enabled, any calls to XCheckIfEvent,6           XIfEvent, or XPeekIfEvent are enclosed in anC           XLockDisplay/XUnlockDisplay pair. This prevents deadlocks >           from occurring within a single thread when predicate/           functions are called by these events.o  =           For example, without recursive locks, deadlocks cann@           occur in threaded Motif applications and threaded Java0           applications that use the awt library.  B     4.6.4 Memory Leaks in XOpenDisplay and XCloseDisplay Corrected           (Alpha Only)             V1.5  C           Small memory leaks that occurred when opening and closingrB           display connections have been fixed. As a result, clientD           applications that open and close many connections will notD           need as many virtual pages and can function with a reduced3           page file count and channel count quotas.n  B     4.6.5 XOpenDisplay Calls No Longer Leave a Pending Wake (Alpha           Only)              V1.5  E           The initial call of XOpenDisplay no longer leaves a pending D           wake status on the process, which caused the next LIB$WAIT.           or SYS$WAKE call to end immediately.  C     4.6.6 State of Event Flag Number 63 Changed Only After Reserved            (Alpha Only)             V1.5  D           DECwindows Motif no longer changes the state of event flag@           number (EFN) 63 without first having reserved it. ThisE           problem previously occurred when opening a display, writingsC           data (if the transport queue to the server was full), andMD           reading data from the server on systems running DECwindows8           Motif for OpenVMS Alpha Version 1.3 or higher.  "     4-32 Programming Release Notes -         I                                                 Programming Release NotesAI                                        4.6 X Window System Library (Xlib)i    H         4.6.7 Xpoll.h Header File and ConnectionNumber Macro Restriction                 V1.5  G               The current version of the Xpoll.h header file implements @               an interface to DECW$LCN_SELECT. This interface isH               incompatible with the C Run-Time Library (CRTL) definitionH               of the select function. Specifically, DECW$LCN_SELECT doesD               not implement support for the display ConnectionNumber5               macro when threads are not initialized.   G               If your application uses Xpoll.h and the ConnectionNumber G               macro, HP recommends that you replace this macro with the.<               following to prevent conflicts from occurring:  #               #include <X11/Xlib.h> L               #define DECW$LCNConnectionNumber(dpy) ((_XDisplayPriv)dpy->fd)  H         4.6.8 Changed Record Format for Connection Failure Error Message                 V1.3-1  I               When a connection request is rejected, the X display server G               generates an informational message, which Xlib outputs to F               stderr. Previously, the format of the message output wasI               one character per record. The format of the output has been D               changed to pass the entire message as a single record.  H               This change is only noticeable in error message files thatE               are record oriented. For example, the changed format is G               visible in message files generated by the HP Digital Testn               Manager (DTM).  .         4.6.9 Retired and Changed Entry Points                 V1.3  C               The following unsupported Xlib entry points have been 2               removed from the DECW$XLIBSHR image:  %                  XCMSCIELAB_VALIDSPEC.%                  XCMSCIELUV_VALIDSPEC %                  XCMSCIEUVY_VALIDSPECl%                  XCMSCIEXYY_VALIDSPEC.%                  XCMSCIEXYZ_VALIDSPEC *                  XCMSLRGB_RGBI_PARSESTRING)                  XCMSLRGB_RGB_PARSESTRING %                  XCMSTEKHVC_VALIDSPECn  I                                            Programming Release Notes 4-33                 Programming Release NotesL&     4.6 X Window System Library (Xlib)    ?           Any application using these functions will need to bee           modified..  D     4.6.10 Meaning of XConnectionNumber and ConnectionNumber Changed             V1.3  ;           The meaning of the XConnectionNumber function andm?           ConnectionNumber macro has changed on systems runningh1           DECwindows Motif Version 1.3 or higher.   =           For previous versions of DECwindows Motif, both the.E           function and macro returned an event flag number (EFN). ThegE           event flag was set when input arrived, with calls typically.!           implemented as follows:.  /             sys$clref (ConnectionNumber (dpy)); 9             while (XPending (dpy) != 0) XNextEvent (dpy);.0             sys$waitfr (ConnectionNumber (dpy));  B           For DECwindows Motif Version 1.3, a change has been madeA           so that these items behave differently when support foreD           multithreading has been enabled by a call to XInitThreads.?           With multithreading enabled, these items now return ab*           logical connection number (LCN).  B           The LCN is in the read set state whenever there is inputA           available from the server. It is in the write set statewC           unless all output buffers are in use. The except state is.!           reserved for use by HP.   <           To use an LCN instead of an EFN, replace the above,           implementation with the following:             int readState;9             while (XPending (dpy) != 0) XNextEvent (dpy);.E             decw$lcn_select_one (ConnectionNumber (dpy), &readState);.  A           Note that you must make the select call after the event D           queue has been cleared, since the LCN state reflects inputD           from the server and does not include any events that might2           have been queued while handling replies.  A           You can force the ConnectionNumber macro to get the LCN D           value (which is always available) by including XLIB.H withE           the DECW_CONNECTIONNUMBER_IS_LCN macro set to true (1), for9           example:  "     4-34 Programming Release Notes           I                                                 Programming Release NotestI                                        4.6 X Window System Library (Xlib)o    4               #define DECW_CONNECTIONNUMBER_IS_LCN 1#               #include <X11/Xlib.h>.               .                .2               .y  G               This is useful when using this macro in a shared image or.I               object library where the application must function the same ;               whether or not threads have been initialized.r  C               For more information on the LCN interface, see the HPc?               DECwindows Motif for OpenVMS New Features manual..  0         4.6.11 Locale Support in OpenVMS Systems                 V1.2-4  G               The locale support provided on systems running DECwindowsiE               Motif for OpenVMS Version 1.2-4 or higher is compatible.D               with the locale support in the DEC C Run-Time Library.E               If you write internationalized applications using theserD               functions in the locale environment, do the following:  @               o  For Xlib applications, include <X11/Xlocale.h>.A                  If you include <stdlib.h>, you must do so beforei!                  <X11/Xlocale.h>.   I               o  For Motif applications, <X11/Xlocale.h> is automatically                   included.  9               o  Turn on the following compilation flags:e  E                  /define=(X_LOCALE,X_WCHAR,_WCHAR_T_,XLIB_XPG4_FUNCS).  ?         4.6.12 XSelectAsyncEvent and XSelectAsyncInput Routines                  V1.1  B               The XSelectAsyncEvent and XSelectAsyncInput routines=               allocate memory for the storage of AST delivery.F               information. This memory is freed in the following ways:  D               o  If you close a display (XCloseDisplay), all the ASTI                  delivery information associated with all windows on that."                  display is freed.  B               o  If you destroy a window (XDestroyWindow), the AST?                  delivery information for that window is freed.   I                                            Programming Release Notes 4-35                 Programming Release Notes.&     4.6 X Window System Library (Xlib)    E           The AST delivery information for subwindows is not freed by.           XDestroyWindow..  @           If you want to turn off AST notification for all event;           types within a given window and also free the ASTt?           delivery information, the client application can call C           XSelectAsyncEvent or XSelectAsyncInput passing the event_ A           mask argument equal to minus one (all bits set) and the.-           ast_routine argument equal to zero.   C              ________________________ Note ________________________   ?              On systems running DECwindows Motif Version 1.3 or.A              higher, XSelectAsyncInput and XSelectAsyncEvents are B              not supported if multithreading has been enabled by aC              call to XInitThreads. The equivalent functionality canA:              be obtained by using threaded Xlib functions.  A              See HP DECwindows Motif for OpenVMS New Features for.>              more information about using these functions in a'              multithreaded environment.   C              ______________________________________________________   .     4.6.13 Command Procedure Builds .PEN Files             V1.0  ?           To allow Pascal programs to inherit environment files2;           for Xlib and Motif, execute the command procedure.@           SYS$LIBRARY:DECW$PEN_BUILD.COM. This command procedureB           generates the DECW$XLIBDEF.PEN and DECW$MOTIF.PEN files.E           The .PEN files compile into Pascal programs faster than the.           provided .PAS files.  1     4.6.14 Parameter/Protocol Datasize Mismatches              V1.0  C           Several Xlib routines accept longword parameters that are8E           not sent in their entirety in the X Protocol message to the9C           server. In each case, the Xlib routine sends out only the.E           least significant 16 bits of the parameter value. This is a.E           constraint of the field size within the X Protocol message..  "     4-36 Programming Release Notes .  .      I                                                 Programming Release Notes I                                        4.6 X Window System Library (Xlib)     F               Table 4-4 lists routine names and the longword arguments2               that are sent only as 16-bit values.  I               Table_4-4_Routine_Names_and_Arguments_Sent_as_16-Bit_ValuesO  I               Routine_Name_______________________Routine_Arguments_______.  @               XAllocColorCells/ALLOC_COLOR_      nplanes,npixels               CELLS   B               XDrawArc/DRAW_ARC                  x,y,width,height,>                                                  angle1,angle2  <               XDrawLine/DRAW_LINE                x1,x2,x3,x4  4               XDrawPoint/DRAW_POINT              x,y  A               XDrawRectangle/DRAW_RECTANGLE      x,y,width,height   4               XDrawString/DRAW_STRING            x,y  4               XDrawString16/DRAW_STRING16        x,y  4               XDrawText/DRAW_TEXT                x,y  4               XDrawText16/DRAW_TEXT16            x,y  ;               XFillArc/FILL_ARC                  x,y,width, E                                                  height,angle1,angle2.  I               XFillRectangle/FILL_RECTANGLE______x,y,width,height________e                            I                                            Programming Release Notes 4-37.                Programming Release Notes.0     4.7 X Window System Extensions and Protocols    0     4.7 X Window System Extensions and Protocols  A           This section contains release notes pertaining to the X D           Window System extensions implemented for DECwindows Motif.  '     4.7.1 Using XCopyArea with XINERAMA.             V1.3-1  ?           Note that graphic expose events are now generated for B           XCopyArea requests. All programs that call the XCopyAreaD           function must have graphics expose enabled at all times onA           the graphics context resource (gc) used in the request.3  =     4.7.2 XINERAMA Does Not Correctly Report VisibilityNotifyl             V1.3-1  C           When applications display on a XINERAMA multihead system, A           the VisibilityNotify event does not properly report the.=           state of the window. When a window is displayed and B           VisibilityNotify is selected, the state of the window isE           reported as Unobscured when in fact it may be Unobscured or C           PartiallyObscured. To prevent this from occurring, change E           the applications so that they treat VisibilityNotify events            as PartiallyObscured..  @           Once the window has been displayed, no more visibilityB           events are reported. For example, when a window that hasA           VisibilityNotify selected is covered by another window,l@           an event indicating that it is FullyObscured should be+           reported. This event is not sent.3  .     4.7.3 EVI Extension and Colormap Conflicts             V1.3  D           The DECwindows X11 Display Server does not return colormapC           conflict information when the Extended Visual Information >           (EVI) extension is used to request information about<           available visuals. In all cases, the data returned5           indicates that no colormap conflicts exist.m      "     4-38 Programming Release Notes           I                                                 Programming Release Notes0I                              4.7 X Window System Extensions and Protocols.              4.7.4 Dead Mouse Support                 V1.3  C               Dead Mouse capabilities previously available with the.F               AccessX extension have been incorporated into the subsetH               of features available with the X Keyboard extension (XKB).D               These capabilities are now collectively referred to as               Mouse Keys.L  E               Note that since the Dead Mouse functions were also made.F               part of the X server in a previous version of DECwindowsI               Motif, they remain available even when the XKB extension isa               not enabled.  3         4.7.5 AccessX Extension No Longer Supported                  V1.3  A               Support for the AccessX keyboard extension has beenmE               removed. All functions provided by this extension (such.I               as sticky keys) are available with the X Keyboard extension I               (XKB). See the HP DECwindows Motif for OpenVMS New Features 5               for more information on this extension..  H         4.7.6 Group Validation Not Performed by Security and Application               Group Extensions                 V1.3  @               The validation of groups is not being performed by@               the Security (SECURITY) and Application Group (XC-E               APPGROUP) extensions. Although a group ID can be passed I               to XSecurityGenerateAuthorization, it is not being checked.iC               Authorization is provided regardless of the group ID.l  F         4.7.7 Do Not Remove Watch Procedures from Open ICE Connections                 V1.3  I               Avoid removing ICE watch procedures while an ICE connection G               remains open. If a watch procedure allocates memory to an G               open connection, and the procedure is removed, the memoryiF               cannot be freed since the proper callback is not made to"               the watch procedure.  I                                            Programming Release Notes 4-39  .              Programming Release Notes.0     4.7 X Window System Extensions and Protocols    -     4.7.8 BAD_LOCAL_NODE Error When Using ICEa             V1.3  @           The original transport implemented by DECwindows Motif@           ignored the node specification when using LOCAL as theA           network transport. With the ICE protocol, the node nametC           must always either be a value of 0 or a string consistingrA           of the system name. Since ICE uses the LOCAL transport,.B           the BAD_LOCAL_NODE warning message is displayed when ICE4           attempts to verify the node specification.  5     4.7.9 SmsGenerateClientId Does Not Generate an ID              V1.3  B           The XSMP request SmsGenerateClientId fails to generate a@           client ID on any system that does not have an assigned#           DECnet or TCP/IP address.   -     4.7.10 Specifying Extension Include Files.             V1.2  @           To ensure that programs that contain extension includeC           files compile properly, add the logical name DECW$INCLUDE 1           to the C include directory search list..  ?           To add the logical name, enter the following command:   1           $ DEFINE DECC$USER_INCLUDE DECW$INCLUDE   :     4.8 X Window System Internationalization Library (Xnl)  B           This section contains information about the Xnl library.  /     4.8.1 The I18N library Now Supports GB18030              V1.6  E           Support for GB18030 has now been added to the I18N library.x        "     4-40 Programming Release Notes           I                                                 Programming Release NoteseI                    4.8 X Window System Internationalization Library (Xnl)N             4.8.2 xnl_parsedatetime                  V1.2-5  E               xnl_parsedatetime (and its VAX binding, XNL$PARSE_DATE_oF               TIME) accepts two-digit or four-digit years in the inputF               argument XmString s (which is the date-time string to beE               parsed). Valid years in the two-digit format are in theuE               range 70 to 99, which mean the years from 1970 to 1999.aH               Values from 00 to 69 are invalid. Year 2000 and later must4               be specified in the four-digit format.           4.8.3 xnl_langinfo                 V1.2-5  F               xnl_langinfo (and its VAX binding, XNL$LANGINFO) returnsE               a string for date-time formatting when D_FMT or D_T_FMT1F               is specified in the item argument. In the locales listedI               below, this function returns a formatting string containing G               %y. This formatting string should be used carefully after G               the year 2000, as %y indicates the two-digit year format.                  o  es_ES Spanish  %               o  fr_BE French Belgium   $               o  fr_CA French Canada                 o  iw_IL Hebrew                   o  no_NO Norwegian  !         4.9 Transport Programming.  C               This section contains information about the Transportl               interface.  3         4.9.1 User-Written Transports Not Supportede                 V1.3  D               With DECwindows Motif Version 1.3, significant changesD               were made to the DECwindows Motif transport library toG               accommodate multithreading and the communication needs of E               the Inter-Client Exchange (ICE) protocol, Low-Bandwidth @               X (LBX) proxy server, and Input Method servers. InF               particular, support for an alternate method of assigningC               numbers to server connections was added, as described F               in HP DECwindows Motif for OpenVMS New Features. Support  I                                            Programming Release Notes 4-41                 Programming Release Notes.     4.9 Transport Programming     B           for the logical connection number (LCN) interface is theC           only transport-related feature that will be published for            external use.A  >           The DECnet, TCP/IP, LAT, and local network transportB           interfaces have been updated, remain available, functionC           as expected in the DECwindows Motif Version 1.3 or higher C           environment, and are compatible with the previous version D           of the client libraries. However, any custom, user-writtenB           transports built against previous versions of DECwindows@           Motif, will not function as expected and are expresslyC           not supported on systems running DECwindows Motif Version B           1.3 or higher. This includes transports built and linked&           against the following files:  (              SYS$LIBRARY:DECW$XPORTCOM.H*              SYS$LIBRARY:DECW$XPORTCOM.MAR*              SYS$LIBRARY:DECW$XPORTCOM.R32(              SYS$LIBRARY:DECW$XPORTDEF.H*              SYS$LIBRARY:DECW$XPORTDEF.MAR*              SYS$LIBRARY:DECW$XPORTDEF.R32  ?           These files have been removed from the kit and are no.D           longer available. The VMS DECwindows Transport Manual willE           be archived and the new libraries will not be documented or "           made available publicly.  @           If you have implemented a custom transport and want to@           migrate that transport to the DECwindows Motif Version=           1.3 or higher environment, contact your HP customerd9           representative to develop a migration strategy..                            "     4-42 Programming Release Notes o  m                    I                                                                         5 I         _________________________________________________________________   I                                               Documentation Release Notes.    ?               This chapter briefly describes corrections to theDG               DECwindows Motif documentation. For a complete listing ofpI               additions and changes to the DECwindows Motif documentation.H               set, see the HP DECwindows Motif for OpenVMS Documentation               Overview.f  0         5.1 Getting Started With the New Desktop  D               This section contains documentation corrections to the:               Getting Started With the New Desktop manual.  *         5.1.1 Corrected File Specification                 V1.2-5  E               A file specification for a command procedure in Getting.G               Started With the New Desktop (part number AA-QUW1A-TE) isdI               incorrect. The file specification appears in Section 3.4.9,p&               paragraph 5, as follows:  C               "Optional DECwindows applications, such as DECwindowslB               Notes, may not provide any information and thereforeC               are not restarted. For such cases, there is a command A               procedure called disk$:[user.DT]SESSIONETC.COM thatlB               you can use to start any applications that cannot beE               restarted automatically. This procedure is analogous to H               the DECW$LOGIN.COM procedure in the traditional DECwindows               environment."d  0               The correct file specification is:  4               disk$:[user.DT.SESSIONS]SESSIONETC.COM        I                                           Documentation Release Notes 5-1f n  .           Documentation Release Notes *     5.2 Using DECwindows Motif for OpenVMS    *     5.2 Using DECwindows Motif for OpenVMS  @           This section contains documentation corrections to the4           Using DECwindows Motif for OpenVMS manual.  8     5.2.1 Corrections to the Example for Changing a Logo             V1.2  B           The example "Changing Your Logo" in the Using DECwindowsA           Motif for OpenVMS is incorrect. To correct the problem, 8           change the following code example in step one:  F           $ COPY SYS$COMMON:[SYSMGR]DECW$PRIVATE_APPS_SETUP.TEMPLATE -E           _$ SYS$SPECIFIC:[SYSMANAGER]DECW$PRIVATE_APPS_SETUP.COM/LOG   2           The code example should read as follows:  F           $ COPY SYS$COMMON:[SYSMGR]DECW$PRIVATE_APPS_SETUP.TEMPLATE -A           _$ SYS$SPECIFIC:[SYSMGR]DECW$PRIVATE_APPS_SETUP.COM/LOG   7     5.3 DECwindows Motif for OpenVMS Applications Guidet  =           This section contains documentation corrections and.:           enhancements to the DECwindows Motif for OpenVMS$           Applications Guide manual.  6     5.3.1 Clarifications to the Finish Printing Option             V1.2-3  A           In DECwindows Motif for OpenVMS Applications Guide, the A           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 menuB           closes the print job and toggles Auto Print mode back to           Normal Print mode.          #     5-2 Documentation Release Notes. .  .      I                                               Documentation Release NotesiI                       5.3 DECwindows Motif for OpenVMS Applications Guide     G         5.3.2 Correction to Adding Target Screen Options to Application                 Menu Items Example                 V1.2  F               The example "Adding Target Screen Options to ApplicationF               Menu Items" in DECwindows Motif for OpenVMS ApplicationsD               Guide is incorrect. To correct the problem, remove the5               first occurrence of the following line:   "               $ select_qualifiers:  @         5.4 DECwindows Motif for OpenVMS Guide to Non-C Bindings  B               This section contains documentation enhancements andF               corrections to the DECwindows Motif for OpenVMS Guide to$               Non-C Bindings manual.  ;         5.4.1 Access to GET_CHAR_STRUCT Function Correction                  V1.2-3  I               The access related to the char_struct argument for the XLIBiG               GET_CHAR_STRUCT function is incorrectly documented in the G               DECwindows Motif for OpenVMS Guide to Non-C Bindings. The4&               correct access is write.  =         5.5 DECwindows Motif Guide to Application Programminge  D               This section contains documentation corrections to theG               DECwindows Motif Guide to Application Programming manual..  C         5.5.1 Location of UIL Source Code for the OpenVMS DECburgert                Sample Application                 V1.2-3  F               In the DECwindows Motif Guide to Application ProgrammingB               manual, the introduction to the section in Chapter 4I               called "Creating the Help Widget with UIL" does not clearly)E               state that the complete UIL source code for the OpenVMSeC               DECburger application is included in DECW$EXAMPLES on.               OpenVMS systems.    I                                           Documentation Release Notes 5-3e V  a           Documentation Release Notes 9     5.5 DECwindows Motif Guide to Application Programming     6     5.5.2 Corrections to the Help Widget Documentation             V1.2-3  B           In the DECwindows Motif Guide to Application Programming<           manual, the following corrections should be noted:  D           o  The title of Example 4-7, "Help Widget Implementation-CA              Language Module", DECBURGER.C should be added to thee              title as follows:  :              "Help Widget Implementation-C Language Module              (DECburger.C)"   =           o  The title of Example 4-8 should read as follows:.  ?              "Help Widget Implementation-Callbacks (DECburger.C               continued)"  ?           o  The title of Section 4.10, "Using the Toolkit Help B              Widget Creation Routine," does not accurately reflectA              the contents of this section. The title should read,p3              "Using UIL to Create the Help Widget".l  =           o  The introductory paragraph to Example 4-9 in thehC              section called "Using the Toolkit Help Widget CreationFE              Routine" is incomplete. The information should state then              following:   D           o  "The code in Example 4-9 is included in DECburger.C butC              is commented and will not be compiled when the example               program is built."a  C              The implementation in this example is not complete; it.>              requires some sections from Examples 4-7 and 4-8.  &     5.6 DECwindows Extensions to Motif  @           This section contains documentation corrections to the0           DECwindows Extensions to Motif manual.  B     5.6.1 Corrected List of DXmNlayoutDirection Resource Constants             V1.2-3  ?           In the DECwindows Extensions to Motif, the section onyA           the DXmNlayoutDirection Resource in Chapter 2 lists the.           following constants:              o  DXmLAYOUT_LEFT_DOWN  #     5-4 Documentation Release Notes  .         I                                               Documentation Release NoteswI                                        5.6 DECwindows Extensions to Motifn    "               o  DXmLAYOUT_LEFT_UP  %               o  DXmLAYOUT_RIGHT_DOWND  #               o  DXmLAYOUT_RIGHT_UP   A               Note that the following constants are not currently =               available for the DXmNlayoutDirection resource:3  "               o  DXmLAYOUT_LEFT_UP  #               o  DXmLAYOUT_RIGHT_UP   H               Also note that the introduction to Table 2-1 is incorrect.H               Table 2-1 describes the effect of the constants DXmLAYOUT_B               LEFT_DOWN and DXmLAYOUT_RIGHT_DOWN on the functions.                 V1.2  B               In Section 2.2 of the DECwindows Extensions to MotifG               manual, the description of DXmChildren indicates that the E               routine can be used to learn the length of widget_list..  G               The documentation is incorrect. The sentence should read,DI               "You can use the DXmNumChildren routine to learn the lengthp:               of the widget list returned by DXmChildren."                                      I                                           Documentation Release Notes 5-5. .  .                    I                                                                         A I         _________________________________________________________________   I                                       OSF/Motif Release 1.2 Release Notes     G               The release notes in this document are based on Chapter 3 H               of the OSF/Motif Release Notes for Release 1.2 and includeH               a few other notes relevant to programmers developing MotifC               applications. Most of the notes describe changes madeiF               for Release 1.2. The first two notes discuss performanceH               improvements and information about backward compatibility.  F               These release notes support the Motif software currentlyH               provided with the HP DECwindows Motif for OpenVMS product.  $         A.1 Performance Improvements  D               The Open Software Foundation (OSF) set as its goal forI               OSF/Motif Release 1.2 to improve performance where possible E               and, at a minimum, to not allow it to degrade below the 3               performance of OSF/Motif Release 1.1.   :               Performance testing was done in three areas:  -               o  Aspects obvious to end usersf  !               o  Data space usage                  o  Memory leakage.  H               The performance of user-perceptible events such as postingH               and unposting dialog boxes and pop-up menus are comparableI               or better than the performance for OSF/Motif Release 1.1.4..G               A significant improvement was made for scrolling inside aiH               Scrolled Text region that contains a large amount of test.  D               Data space usage has improved throughout the OSF/MotifG               Toolkit, particularly for the Text widget. In some cases, B               data space usage has been reduced by as much as 40%.H               Also, the memory used for the text in a Text widget is nowG               correctly reduced when that text is replaced by a smaller                amount of text.i  I                                   OSF/Motif Release 1.2 Release Notes A-1-           '     OSF/Motif Release 1.2 Release Notes       A.1 Performance Improvements    C           Memory leakage has been reduced to a minimum for multiple.C           creates and destroys of all Toolkit widgets. Although theoA           Motif tests showed small memory leaks, the OSF believese?           that this amount of memory is required as part of the.9           startup overhead and is not a true memory leak.e  B           The OSF did find some memory leaks that they plan to fix@           in a future release. Three widgets-File Selection Box,E           Command, and Drawn Button - leak approximately 500 bytes of            memory per instance.       A.2 Backward Compatibility  =           The OSF tested OSF/Motif Release 1.2 for both link- =           time compatibility as well as visual and behavioral-           compatibility.  -     A.2.1 Visual and Behavioral Compatibility   ;           The OSF ran automated tests that compared current C           visuals with those recorded using OSF/Motif Release 1.1.4.E           libraries. Once all differences between the Release 1.2 and.E           Release 1.1.4 versions were accounted for, the visuals were.B           rerecorded using Release 1.2 visuals. These new recorded4           visuals were used in all subsequent tests.  A           The OSF believes that Motif Release 1.2 is visually andl>           behaviorally compatible with Release 1.1.4. However,@           they have made extensive improvements to the Traversal@           and Geometry Management algorithms that result in some?           differences between those versions. These differences.@           reflect efforts to fix defects in the earlier release.  D           For example, one such modification involves the new policyA           in which an initial size set for a manager widget in an A           application is now honored by the Toolkit. In OSF/Motif >           Release 1.1, applications set the initial size for aA           manager widget, but did not, in fact, use that size. In ?           Release 1.2, Motif now uses that size setting and the 0           initial layout is changed accordingly.          +     A-2 OSF/Motif Release 1.2 Release Notes  1         I                                       OSF/Motif Release 1.2 Release Notes I                    A.3 Changes and New Features for OSF/Motif Release 1.2     >         A.3 Changes and New Features for OSF/Motif Release 1.2  G               This section summarizes changes and new features that the I               OSF has made to OSF/Motif Release 1.2. Detailed information A               about these modifications is contained in the Motif.D               reference pages and the Motif Release 1.2 revisions of               following books:  &               o  OSF/Motif Style Guide  -               o  OSF/Motif Programmer's Guidew  F               The following sections discuss the OSF/Motif Release 1.2               enhancements..  %         A.3.1 General Toolkit Changese  D               This section discusses the changes made to the overall,               OSF/Motif Release 1.2 Toolkit.  $         A.3.1.1 Include File Changes  G               The following header files that were in OSF/Motif Releaset.               1.1 are obsolete in Release 1.2:                    ExtObject.h                  Traversal.h                  VaSimple.ht                  VendorE.h                  VendorEP.h   B               A new public header file, XmAll.h, has been added toF               OSF/Motif Release 1.2. This header file includes all the&               documented header files.  '         A.3.2 Change in XT Translationsg  H               As a result of fixing a problem in the XT translation codeC               (Patch 25 for X11 R5), the translations in Xt are nowiF               handled strictly and no longer accept any possible matchH               as they did before. This change has caused a change in theG               behavior of the QATS and Motif VTS test suites, which now G               make incorrect assumptions for certain keyboards, such as.I               those that have the arrow keys defined in the keypad. Other.;               Motif applications might be affected as well.   G               You can avoid this problem by creating a file to redefine I               the bindings for the keys in question and then passing that *               file to the xmodmap utility.  I                                   OSF/Motif Release 1.2 Release Notes A-3. .  .      '     OSF/Motif Release 1.2 Release Notesl:     A.3 Changes and New Features for OSF/Motif Release 1.2    C           The following example changes the bindings for the keypad D           keys that match the arrow keys so that only the arrow keysC           are produced, not the keypad numbers. The new definitions E           allow the application to use modifiers with the arrow keys.              !            ! Always force:C           !   KP_2 = Down            !   KP_8 = Up.           !   KP_4 = Left            !   KP_6 = Right           keycode 120 = Down           keycode 76  = Up           keycode 98  = Left           keycode 100 = Right        A.3.3 ANSI C Compliancee  C           All references to caddr_t have been changed to XtPointer.rA           This change affects all callback routines and any otherSC           routines that reference caddr_t. The OSF made this change.C           so that OSF/Motif Release 1.2 would be compliant with the            ANSI C specification.   *     A.3.4 Display and Screen Specific Data  E           Motif now has an XmDisplay object that supports per-display D           data and resources. An XmScreen object has been added that1           supports per-screen data and resources..       A.3.5 Drag and Drop-  C           OSF/Motif Release 1.2 supports the drag and drop metaphor C           for data interchange. The drag-and-drop specification has.D           been fully implemented. See the Release 1.2 version of theB           OSF/Motif Programmer's Guide for information on the drag           and drop interface.   C              ________________________ Note ________________________   A              If you want to use Btn2 to have pop-up menus pop up,eB              drag and drop will not function properly. You need to5              disable drag and drop in such instances.d  C              ______________________________________________________   +     A-4 OSF/Motif Release 1.2 Release Notesa l  e      I                                       OSF/Motif Release 1.2 Release NotesiI                    A.3 Changes and New Features for OSF/Motif Release 1.2a             A.3.6 Tear-Off Menus  C               With tear-off menus, the user can retain menus on thenC               display area for subsequent selections. Each tearable G               menupane is a tear-off button. When the mouse drag buttonhG               is pressed on the tear-off button, the pane tears off and H               can be dragged and then placed by releasing the mouse dragH               button. The window manager surrounds the tear-off menupaneG               with a menu button and a title. Shifting focus to a torn- G               off menu's windowpane follows the standard window manager                policy..  I               Tear-off behavior is enabled by setting the XmNtearOffModel I               resource to XmTEAR_OFF_ENABLED. (The default is XmTEAR_OFF_s               DISABLED).  D               Note that there is no resource converter preregisteredF               by XmNtearOffModel. To allow the tear-off function to beH               enabled through the resource database, an application mustI               register its own resource converter for the XmNtearOffModel F               resource using the XmRepTypeInstallTearOffModelConverter               function.i  G               The converter is not automatically installed because manyOH               applications use map or cascading callbacks to dynamicallyG               set the sensitivity of items within their menus. However,sG               if a tear-off menu is mapped, the sensitivity of its menusB               items must be changed immediately to reflect changesD               in other application states. Existing applications areF               unlikely to change menu item sensitivity in this manner.G               Thus, allowing their menus to be torn off could result inaE               operations being enabled at unexpected times. If a user D               activates one of these menu items, the application can<               crash or the persistent data can be corrupted.  !         A.3.7 Insensitive Visualsc  A               Motif provides visual indications to show whether aaC               component can respond to input from users. Labels and H               buttons have had this behavior in previous Motif releases.G               In OSF/Motif Release 1.2, this behavior has been extended '               to the following widgets:p                    XmArrowButton                  XmLista                  XmScrollBar                  XmTexta  I                                   OSF/Motif Release 1.2 Release Notes A-5o a         '     OSF/Motif Release 1.2 Release Notesd:     A.3 Changes and New Features for OSF/Motif Release 1.2                  XmTextField       A.3.8 Other Visual Changes  @           OSF/Motif Release 1.2 has made other visual changes as           follows:  A           o  Several pixels have changed in the three-dimensionall              beveled look.  A           o  Minor changes have been made to the color generationx=              routines. In particular, the new XmScreen object <              contains resources that allow for tailoring the>              generation of default colors. Some of the default@              values for thresholds have been adjusted to produce-              more contrast on color monitors.   C           o  Motif now adds a location cursor to surround all itemsnC              in a List whenever a List widget has the focus and thee2              current keyboard item is not visible.  C           o  There are minor layout differences because of fixes in !              geometry management.e       A.3.9 Titles for Frames   B           In OSF/Motif Release 1.2, you can specify a Title widget@           in a Frame widget. The release has added the followingB           new constraint resources for specifying the position and.           alignment of the title in the Frame:  (              XmNchildHorizontalAlignment&              XmNchildHorizontalSpacing              XmNchildType.&              XmNchildVerticalAlignment       A.3.10 Audible Warning  @           The VendorShell has a new resource, XmNaudibleWarning,D           that can specify whether an audible cue should accompany aD           warning message. Text widgets determine the value for this7           resource from the value of XmNaudibleWarning.       +     A-6 OSF/Motif Release 1.2 Release Notesa e         I                                       OSF/Motif Release 1.2 Release Notes I                    A.3 Changes and New Features for OSF/Motif Release 1.2     !         A.3.11 Color Enhancementsr  B               The following three resources have been added to theC               XmScreen widget so that users can specify the defaulteE               background color and thresholds for shadow calculation:   "                  XmNlightThreshold!                  XmNdarkThresholdo'                  XmNforegroundThresholdc  I               Motif has added the XmChangeColor function that changes thepA               background and other colors for a specified widget.u  !         A.3.12 Baseline Alignment   G               Motif has added two functions for baseline alignment. The F               XmWidgetGetBaselines function determines the position ofD               the widget's text baseline. The XmWidgetGetDisplayRectG               function determines the size and position of the bounding 4               box for the widget's character string.  %         A.3.13 Expanded Traversal Set   C               In OSF/Motif Release 1.2, you can use more widgets to,G               support traversal using the keyboard. For example, insidenG               a tab group, users can now use the arrow keys to traverse F               to all control descendants that are not contained withinH               a nested tab group and that are eligible to receive focus,E               even if the controls are not direct children of the tab                group.  -         A.3.14 Two-Dimensional Menu Traversalc  G               With OSF/Motif Release 1.2, the left, right, up, and downeI               traversal arrows now navigate within a menupane. The up andnF               down arrow keys wrap between columns. The right and leftE               arrow keys post the previous or next menupane when they E               are pressed in the rightmost and leftmost column of the %               menupane, respectively.            A.3.15 Input Focus  A               OSF/Motif Release 1.2 has added the XmNinitialFocus D               resource to the Manager class. This resource specifiesH               the first widget to receive input focus. This resource canH               only specify a widget; it is ignored for all pop-up menus,:               menubars, option menus, and pull-down menus.  I                                   OSF/Motif Release 1.2 Release Notes A-7e f  a      '     OSF/Motif Release 1.2 Release Notes :     A.3 Changes and New Features for OSF/Motif Release 1.2    %     A.3.16 Traversal Access Functions,  E           OSF/Motif Release 1.2 has added the following new functions @           to support better interaction with keyboard traversal:                XmGetFocusWidgetv              XmGetTabGroup              XmGetVisibility              XmIsTraversable              XmIsVisible  C           The XmTrackingLocate function has been modified to do theb           following:  7           o  Field all events, not just a button press.   5           o  Return on any keystroke or button press.o  0           o  Be called for nonsensitive widgets.  C           In addition, the XmTrackingEvent function has been added.rC           This function is similar to XmTrackingLocate, except thatn.           it returns a pointer to the X event.       A.3.17 Virtual Keysy  E           OSF/Motif Release 1.2 has added the XmTranslateKey functioneD           that allows applications to override the default XtKeyProc'           to handle Motif virtual keys.   0           Motif defines two new virtual keysyms:                osfPageLeft              osfPageRight   @           You must have the X11 Release 5 XKeysymDB installed inC           /usr/lib/X11 to use these new virtual keys. Otherwise you C           get a warning message on application startup. Specify thea6           following information in the XKeysymDB file:  #           osfPageLeft     :1004FF40r  #           osfPageUp       :1004FF41m  #           osfPageDown     :1004FF42   #           osfPageRight    :1004FF43i  ?           To comply with the OSF/Motif Style Guide, the defaultd>           binding for osfMenu has been changed from <key>F4 to           Shift<key>F10.  +     A-8 OSF/Motif Release 1.2 Release Notes            I                                       OSF/Motif Release 1.2 Release Notes I                    A.3 Changes and New Features for OSF/Motif Release 1.2_    D               In X11 Release 5, the HP keysyms in the XKeysymDB fileH               have the prefix hp. This prefix is not reflected in the HPH               bindings file in the /bindings directory. If you are usingD               an X11 Release 5 XKeysymDB file, you might see warningI               messages at application startup. To eliminate these warning G               messages, add the hp prefix as follows to the appropriate                 lines in the file:  3               osfDelete :         <key>hpDeleteChare  3               osfInsert :         <key>hpInsertChar   3               osfPrimaryPaste :   <key>hpInsertLineC  3               osfQuickPaste :     <key>hpDeleteLinem  G               OSF/Motif Release 1.2 has a new client, xmbind, that setseD               up the virtual bindings for use by Motif applications.D               Since virtual binding is automatically set up at MotifG               Window Manager (MWM) startup, you only need to use xmbindtE               if MWM is not used or if you need to change the virtualt.               bindings without restarting MWM.  A               Virtual bindings can now be specified by individual A               vendors. If there is no .motifbind file in the home E               directory, you can use the xmbind.alias file to provideoI               a mapping from the server vendor name to the bindings file. H               You can set up user vendor bindings as well as system-wide               vendor bindings.  "         A.3.18 Resource Management  G               OSF/Motif Release 1.2 has the following new functions for ,               managing representation types:  "                  XmRepTypeRegister$                  XmRepTypeAddReverse$                  XmRepTypeValidValue'                  XmRepTypeGetRegistered                   XmRepTypeGetIdo%                  XmRepTypeGetNameListc#                  XmRepTypeGetRecord.  C               These functions are useful for developers who want to_G               define new resource converters that use an enumerated set_               of values.  I                                   OSF/Motif Release 1.2 Release Notes A-9  .         '     OSF/Motif Release 1.2 Release Notes :     A.3 Changes and New Features for OSF/Motif Release 1.2    1     A.3.19 Changes for CUA and Windows Compliancee  D           In OSF/Motif Release 1.2, pressing the Return key or using@           the key bound to osfActivate (usually the Enter key onB           the numeric keypad) no longer activates a button that isD           outside a menu. For example, pressing such a key no longer@           pops up an OptionMenu or activates a ToggleButton in a           dialog box.r  E           If your application has a default button associated with aneA           XmBulletinBoard, pressing Return (except in a multilineM?           XmText), Ctrl/Return, or the key bound to osfActivateeA           while the focus is in the XmBulletinBoard now activatesw           the default button.   4     A.4 Changes and Enhancements to Specific Widgets  A           This section summarizes the changes to specific widgetse2           that were made in OSF/Motif Release 1.2.       A.4.1 XmClipboardu  B           OSF made several corrections to the XmClipboard function>           parameters. These changes are binary compatible with@           earlier releases of Motif. However, in some instances,@           you might see warning messages when you recompile yourA           applications. The modifications involved changing (chartD           *) to XtPointer, int to long, and (int *) to (long *). The@           related functions affected by these modifications are:             o  XmClipboardCopy  "           o  XmClipboardCopyByName  $           o  XmClipboardInquireCount  %           o  XmClipboardInquireFormat   &           o  XmClipboardRegisterFormat              o  XmClipboardRetrieve  !           o  XmClipboardStartCopy   &           o  XmClipboardWithdrawFormat  ,     A-10 OSF/Motif Release 1.2 Release Notes .         I                                       OSF/Motif Release 1.2 Release Notes I                          A.4 Changes and Enhancements to Specific Widgets              A.4.2 XmCommand   @               In OSF/Motif Release 1.2, a correction was made toE               XmCommandGetChild so that it now accepts XmDIALOG_WORK_.5               AREA as a value for the child argument.            A.4.3 XmList  G               To enhance its capabilities for managing lists, OSF/Motif ?               Release 1.2 includes the following new functions:d  )               o  XmListAddItemsUnselected   &               o  XmListDeletePositions  $               o  XmListGetKbdItemPos  $               o  XmListIsPosSelected  "               o  XmListPosToBounds  -               o  XmListReplaceItemsUnselectedp  0               o  XmListReplaceItemsPosUnselected  '               o  XmListReplacePositions   $               o  XmListSetKbdItemPos  )               o  XmListUpdateSelectedList                  o  XmListYToPos   ;               The XmList widget includes a new translation:_                 o  <Copy>   7                  Copies the selection to the clipboard.e  +               XmList includes a new action:r  -               o  ListScrollCursorVertically()   @                  Scrolls the cursor vertically based on an input,                  percentage or a y position.  F                 ________________________ Note ________________________  0                 This action was mistakenly namedE                 ListScrollCursorVisible in OSF/Motif Release 1.2. ThenC                 name will be corrected in a later release of Motif.n  F                 ______________________________________________________  I                                  OSF/Motif Release 1.2 Release Notes A-11o i  r      '     OSF/Motif Release 1.2 Release Notesh4     A.4 Changes and Enhancements to Specific Widgets    D           The XmNvisibleItemCount resource has been modified so that@           the default value is dynamic, and is based on the item           count and the height.   <           In OSF/Motif Release 1.2, if the selectedItems and=           selectedItemCount resources for a list are set in a B           resource file, the location cursor appears over the last@           item in the selectedItems list, not the first selected           item.        A.4.4 XmMessageBox  D           In OSF/Motif Release 1.2, MessageBox supports the addition@           of one MenuBar, one work area, and multiple PushButton           children.   D           A new dialog type, XmDIALOG_TEMPLATE, creates a MessageBoxB           that contains only a Separator. The application provides           additional children.  =           XmCreateTemplateDialog creates an XmDIALOG_TEMPLATE ,           XmMessageBox inside a DialogShell.       A.4.5 XmRowColumn and Menus   4           OSF/Motif Release 1.2 adds a new resource,@           XmNentryVerticalAlignment, that specifies the vertical           alignment style.  ?           Another resource, XmNunpostBehavior has been added toLA           the XmScreen object. This resource can be set to enables?           external button events to be replayed after a menu iss           unposted.        A.4.6 XmScrollBare  >           In OSF/Motif Release 1.2, XmScrollBar includes a new           translation:             o  <Cancel>I  -              Cancels the current slider drag.o      ,     A-12 OSF/Motif Release 1.2 Release Notes    i      I                                       OSF/Motif Release 1.2 Release Notes I                          A.4 Changes and Enhancements to Specific Widgets              A.4.7 XmScrolledWindow  G               OSF/Motif Release 1.2 adds the function, XmScrollVisible, A               that scrolls an automatic scrolled window to make ae>               partially or completely obscured widget visible.  E               Another resource, XmNtraverseObscuredCallback, has been F               added that specifies a list of callbacks that are calledI               when a traversal event is requested to a nonvisible widget. I               A new callback structure, XmTraverseObscuredCallbackStruct,o6               has been added to support this callback.  0         A.4.8 XmSelectionBox, XmFileSelectionBox  >               In OSF/Motif Release 1.2, the XmSelectionBox andH               XmFileSelectionBox widgets support the addition of MenuBarD               and PushButton children, as well as a work area child.  I               A new resource, XmNchildPlacement, controls the location of "               the work area child.  A               The value, XmDIALOG_TEMPLATE, has been added to thee%               XmNdialogType resource.e  E               By default, XmSelectionBoxDialog and its subclasses useeB               XmTextField instead of XmText. You can revert to theH               earlier behavior by defining USE_TEXT_IN_DIALOGS when yourI               application builds XmSelectionBox or any of its subclasses.            A.4.9 XmText  I               OSF/Motif Release 1.2 has added two functions to XmText for I               making update changes to the widget: XmTextDisableRedisplaye(               and XmTextEnableRedisplay.  A               Two other functions facilitate string manipulation:$6               XmTextFindString and XmTextGetSubstring.  D               In Release 1.2, the destination cursor now follows theA               insert cursor and is no longer independently drawn.n  5               XmText includes three new translations:e                 o  <Backspace>  8                  Deletes any non-null primary selection.                 o  <Delete>   8                  Deletes any non-null primary selection.                 o  <LeaveWindow>  I                                  OSF/Motif Release 1.2 Release Notes A-13o L  c      '     OSF/Motif Release 1.2 Release Notes 4     A.4 Changes and Enhancements to Specific Widgets    C              Continues a selection action by scrolling after a time               delay.e  *           XmText includes two new actions:  '           o  scroll-cursor-vertically()b  A              Scrolls the cursor vertically based on a y position.t              o  toggle-overstrike()  :              Switches between insert and overstrike modes.  C              ________________________ Note ________________________e  <              There is a potential problem in both XmText and@              XmTextField with rendering strings in fonts or font=              sets that contain characters whose ascenders can ?              rise above the font ascent. If the text containingf=              these characters is highlighted, any overlapping ?              descenders in the previous line may be overwrittent5              by the ascenders in the succeeding line.e  C              ______________________________________________________        A.4.10 XmTextField  A           OSF/Motif Release 1.2, the XmTextField widget has a new E           resource, XmNfocusCallback, that specifies the callbacks too8           be called when the widget accepts input focus.  ?           Another new function, XmTextFieldGetSubstring, gets a ,           substring by length from a widget.  @           In Release 1.2, the destination cursor now follows the=           insert cursor and is no longer independently drawn.   4           XmTextField includes two new translations:             o  <Backspace>  4              Deletes any non-null primary selection.             o  <Delete>h  4              Deletes any non-null primary selection.  ,     A-14 OSF/Motif Release 1.2 Release Notes D  L      I                                       OSF/Motif Release 1.2 Release NotesnI                          A.4 Changes and Enhancements to Specific Widgetsl    3         A.4.11 XmToggleButton, XmToggleButtonGadgetp  E               In OSF/Motif Release 1.2, setting XmNfillOnSelect to beeI               true when XmNindicatorOn is false now causes the backgroundeG               of a set XmToggleButton to be filled with XmNselectColor.   I               The default value for XmNfillOnSelect is dynamic so that ite2               matches the state of XmNindicatorOn.  -         A.5 Motif Window Manager Enhancementss  C               This section highlights the enhancements to the Motifo#               Window Manager (MWM).x           A.5.1 Changes to MWM  >               OSF/Motif Release 1.2 incorporates the following"               enhancements to MWM:  1               o  An internationalized .mwmrc fileG  2               o  Internationalized dialog messages  -               o  A built-in default root menuh  G               o  Support for the <Return> continuation character (\) in                    the .mwmrc file  D               o  Search capability with XBMLANGPATH for bitmap files  F               o  Support for pop-down and replay event behavior in mwm                  menus  >               o  Documentation of the widget names used by mwm  F               o  Support for scrolled window traversal to scrolled-off)                  children in the icon boxi  H               o  Support for treating the <Alt> and <Meta> key modifiers*                  as two distinct modifiers  F               o  Support for the SHAPE nonrectangular window extension  ,         A.5.2 New and Enhanced MWM Resources  C               The OSF/Motif Release 1.2 window manager includes the 2               following new or enhanced resources:  !               o  feedbackGeometry   F                  Sets the position of the move/resize feedback window.B                  The default position is the center of the screen.  I                                  OSF/Motif Release 1.2 Release Notes A-15o r         '     OSF/Motif Release 1.2 Release Notesa)     A.5 Motif Window Manager Enhancementsh               o  frameBorderWidthb  C              Now bases its default value on the size and resolutiont              of the screen.w             o  iconPlacement  A              Now takes the addition value, tight, which specifiesoA              automatic icon placement with no gaps between icons.              o  maximumClientSize  =              Can now take the values vertical and horizontal.p             o  moveOpaquea  ?              Controls whether an image of the window or just ane,              outline of the window is moved.             o  resizeBorderWidth  C              Now bases its default value on the size and resolutionr              of the screen.n             o  usePPosition_  >              Uses the values of on, off, or nonzero to control:              whether program-specified positions are used.  (     A.5.3 New and Enhanced MWM Functions  B           OSF/Motif Release 1.2 has the following new and enhanced           MWM functions:             o  f.lower  A              Includes a within argument to move the window withinnC              the application stacking order, but retains the parenty>              window below the children rule. The function also>              includes a freeFamily argument to move the windowA              absolutely without regard to its local family stack..C              Both modifiers move the window within the local family_5              stack, but do not move the family stack.c             o  f.minimize   9              Can now be used from an icon in an icon box.              o  f.raise  ,     A-16 OSF/Motif Release 1.2 Release Notes m  s      I                                       OSF/Motif Release 1.2 Release Notes I                                     A.5 Motif Window Manager Enhancementsl    E                  Includes a within argument to move the window within.G                  the application stacking order, but retains the parentnB                  window below the children rule. The function alsoB                  includes a freeFamily argument to move the windowE                  absolutely without regard to its local family stack.rG                  Both modifiers move the window within the local familyu9                  stack, but do not move the family stack.u                 o  f.raise_lower  E                  Includes a within argument to move the window withinDG                  the application stacking order, but retains the parentaB                  window below the children rule. The function alsoB                  includes a freeFamily argument to move the windowE                  absolutely without regard to its local family stack.OG                  Both modifiers move the window within the local familyo9                  stack, but do not move the family stack.t                 o  f.restore  I                  Restores a window to its previous state. Double clicking H                  on a root icon is bound to this function rather than to                  f.normalize.   $               o  f.restore_and_raise  I                  Restores a window to its previous state and raises it to H                  the top of the window stack. Double clicking on an iconH                  in an icon box is bound to this function rather than to                  f.normalize.d                 o  f.screen   G                  Traverses to the screen specified by arg. Legal values D                  for arg are: next, prev, last, or a specific screen                  number.           A.5.4 New MWM Action  ;               OSF/Motif Release 1.2 has one new MWM action:b                 o  <Alt> <Esc>  F                  This key combination behaves similarly to f.next_key,G                  except that the window is always raised, regardless of -                  the value of focusAutoRaise.y  I                                  OSF/Motif Release 1.2 Release Notes A-17e e  o      '     OSF/Motif Release 1.2 Release Notesr.     A.6 Changes to the User Interface Language    .     A.6 Changes to the User Interface Language  E           OSF/Motif Release 1.2 has the following changes in the User #           Interface Language (UIL):p  B           o  There is a new command flag, -s, that enables the use@              of setlocale and the creation of localized Compound              Strings..  C              ________________________ Note ________________________i  @              There is a serious problem in parsing double quotedC              strings with the -s flag. If you need to use this flagtA              for parsing double quoted strings, you must obtain aa               patch from the OSF.  C              ______________________________________________________   C           o  New UIL syntax now supports font sets and font tables.   @           o  New UIL syntax now supports wide character strings.  B           o  Support has been added for using widget references as              callback tags.   D           o  New UIL syntax specifies the resources of automatically              created children.  C           o  Syntax changes to the Widget Meta-Language (WML) allow D              for the definition of automatically created children of              composite widgets.y  >           o  UIL can now use the -wmd file flag to read binary@              databases (WML files) that contain WML information.  ,           o  Mrm includes two new functions:  *              -  MrmOpenHierarchyPerDisplay  E                 This function is the same as the old MrmOpenHierarchy >                 function, except that in the new function, the?                 display is passed as an explicit argument. Thisi3                 function replaces MrmOpenHierarchy.o  %              -  MrmFetchBitmapLiteral   C                 This function fetches a bitmap literal with a depth                  of 1.   ,     A-18 OSF/Motif Release 1.2 Release Notes           I                                       OSF/Motif Release 1.2 Release NoteslI                                      A.7 OSF/Motif List of Known Problemsi    ,         A.7 OSF/Motif List of Known Problems  A               Included in the DECwindows Motif software is an OSFsE               file that contains the OSF/Motif known problems. During B               the installation this file is copied from the kit to6               SYS$HELP:DECW$MOTIF_OSF_BUGLIST_V12.TXT.                                                                              I                                  OSF/Motif Release 1.2 Release Notes A-19d i  h                    I                                                                         B I         _________________________________________________________________t  I                                                OSF/Motif Example Programsc    H               This appendix describes the example programs from the OpenF               Software Foundation (OSF) Motif that are included in the(               DECwindows Motif software.    )         B.1 Cut and Paste Example Programp                 V1.2  G               This example demonstrates the use of the Motif Clipboard.iD               You can cut and paste application-defined data formats(               using the XmClipboard API.  G               Run two cut/paste clients and transfer graph values usingN-               the pull-down and pop-up menus.   #         B.2 DNDDemo Example Program                  V1.2  I               This example illustrates a typical use of the drag-and-drop                feature.  F               When the example starts, it does not have any valid dropG               sites. It starts with different color rectangles that actnH               as drag sources for dragging the colors around. Create the$               drop sites as follows:  C               o  Move the pointer into the drawing area (with white                   background).L  I               o  Press MB1 and drag. You see the "rubber-banding" effect.i  ?               o  Release MB1 after dragging a desired distance.e  B                  A black rectangle appears. You can create as many(                  rectangles as you like.  I                                            OSF/Motif Example Programs B-1n t              OSF/Motif Example Programs     B.2 DNDDemo Example Program     A           The rectangles inside the drawing area that you created B           act as valid drop sites for colors. You can test this byA           initiating the drag from the yellow color rectangle and C           dragging over to one of the rectangles inside the drawingw!           area and releasing MB2.   ?           To initiate a drag, move the pointer over to the drag <           source, press BTransfer (which is MB2 by default),@           and start to drag. Notice that the cursor changes to aD           painter's palette in the same color as the color rectangle+           from which the drag is initiated.M  7           While you are dragging, notice the following:h  >           o  When dragging over the root window, the drag icon4              consists of only the painter's palette.  E           o  When dragging over parts of the drawing area where therefB              are no rectangles, the drag icon changes to include aB              "DO NOT ENTER!" sign on top of the painter's palette.  @           o  When dragging over any of the rectangles inside theD              drawing area, the "DO NOT ENTER!" sign is replaced with              a painter's brush.   A           To perform a drop, release MB2. If you release MB2 withl?           the pointer over any part of the drawing area outside @           of the rectangles, or anywhere on the root window, the>           drag icon snaps back to the point of drag initiationA           and disappears. This is an indication that the drop youdD           attempted failed. If you release MB2 with the pointer overA           any of the rectangles inside the drawing area, the drag B           icon disappears into the background; this indicates thatA           the drop was a success. The rectangle on which the drop B           was attempted, becomes filled in with the color that was           dragged.  E           The rectangles inside the drawing area act as drag sources.fB           Initiate the drag with the pointer on any rectangle, and?           the cursor changes to a rectangle (either of the samep?           size or a smaller size depending on the X cursor size B           constraints). Drag the rectangle from one place and dropD           it onto a new place inside the drawing area. The rectangle2           is physically moved to the new position.  "     B-2 OSF/Motif Example Programs i         I                                                OSF/Motif Example Programs I                                               B.2 DNDDemo Example Programn    F               If you want to copy the rectangle to a new position, useI               the appropriate modifier key while dragging, or at the time E               you attempt the drop (Ctrl is the modifier key for copy G               in the current implementation). When you drag a rectanglecI               with no modifier key pressed or with the Shift key pressed,eF               the solid rectangle from where the drag was initiated isF               replaced by a hollow rectangle with dotted-line borders.I               It continues this way for the duration of the drag or untilnD               you press the Ctrl key, which changes the operation toD               Copy. At that time it regains its original solid form.  F                 ________________________ Note ________________________  C                 During dragging you can cancel the drag by pressingtF                 the Cancel key (F11). Also, you can press the Help keyF                 to get information about whether the drop will succeed-                 and possible drop operations.s  F                 ______________________________________________________            B.3 Dogs Example Program                 V1.1  H               This example uses the dog and square widgets. It shows howI               to incorporate new widgets into the UIL source by using theo$               user-defined function.  ?               The dogs example program allows you to change the,F               DogNwagTime and SquareNmakeSquare resources dynamically.  F               If you have a system with sound generation features, youG               might want to change the bark callback to something other                than XBell().            B.3.1 Dog Widget                 V1.1  H               The dog widget (DogWidget) demonstrates how to subclassifyD               a primitive widget that remains binary compatible withF               future versions of Motif. It uses XmResolvePartOffsets():               and associated macros and implements all theB               recommendations in the XmResolvePartOffsets manpage.  I                                            OSF/Motif Example Programs B-3C N  E           OSF/Motif Example Programs     B.3 Dogs Example Program    B           The dog widget is a subclass of XmPrimitive. It can barkA           and wag its tail. If you want more advanced tricks, you]E           must subclassify it, or replace up.bm, down.bm, and bark.bmn%           with more advanced bitmaps.s  5           The dog widget has the following resources:   ?           o  DogNwagTime: Time in milliseconds between each wag   C           o  DogNbarkTime: Time in milliseconds the bark graphic is               displayed  A           o  DogNbarkCallback: Callback called by the bark actionc  8           The dog widget has the following translations:  0           o  osfActivate/Return/Space/MB1 = Bark             o  W/MB2 = Wag taile  ,           o  S/Shift-MB2 = Stop wagging tail             o  osfHelp = Helpc       B.3.2 Square Widget2             V1.1  ;           The square widget (SquareWidget) demonstrates how 9           to subclassify a constraint widget that remains :           binary compatible with future versions of Motif.;           It uses XmResolveAllPartOffsets()  and associatedr>           macros and implements all the recommendations in the*           XmResolveAllPartOffsets manpage.  =           The square Widget is a subclass of XmBulletinBoard. @           It forces its children to be square using a constraint           resource.   C           The square widget has the resource SquareNmajorDimension.a>           This resource determines which dimension is used for>           the new size of the child. Values are SquareWIDTH or           SquareHEIGHT.   7           The square widget has the constraint resourcehA           SquareNmakeSquare. This resource determines whether theiE           child is forced to be square or set to its preferred shape.   "     B-4 OSF/Motif Example Programs    1      I                                                OSF/Motif Example ProgramsEI                                              B.4 Helloint Example Programe    $         B.4 Helloint Example Program                 V1.2  H               This example is a simple UIL/Xm program with a label and a               push button.  H               With this version, you can choose a Kanji, Hebrew, French,/               or English interface at run time.   @               The program uses the file LOCALSTRINGS.UID for all@               language-specific interfaces. To change languages,D               copy one of the LOCALSTRINGS_*.UID files to DECW$USER_C               DEFAULTS:LOCALSTRINGS.UID. Then, use the logical namePE               LANG or the xnlLanguage resource to set the locale. SetsG               the LOCALSTRINGS suffix and the locale name to one of ther               following:  I               ___________________________________________________________sI               Locale______Interface_Type_________________________________i                 Japan       Kanjin                  Hebrew      Hebrew                  French      French  I               English_____Standard_English_______________________________   H               To define the xnlLanguage resource, add the following line.               to your DECW$XDEFAULTS.DAT file:  !               *xnlLanguage:localeL  E               The following fonts are needed for the helloint examplep               program:  I               ___________________________________________________________ I               Locale____Font_Name________________________________________a  H               French    -adobe-helvetica-medium-r-normal-12-120-75-75-p-$                         67-iso8859-1  I               English   -adobe-times-medium-r-normal-14-100-100-100-p-74-s!                         iso8859-1r  F               Hebrew    -Misc-Fixed-Medium-R-Normal-13-120-75-75-C-80-!                         ISO8859-8   *               Japan     -*-JISX0208.1983-1  I               __________-*-JISX0201.1976-0_______________________________   I                                            OSF/Motif Example Programs B-5e c  k           OSF/Motif Example Programs      B.4 Helloint Example Program    B           If you do not have these fonts installed on your system,A           either change the UIL files to reference other fonts or D           install the *.DECW$BDF fonts provided in the DECW$EXAMPLESC           directory. See HP DECwindows Motif for OpenVMS Managementr=           Guide for instructions on how to install new fonts.i  "     B.5 Hellomotif Example Program             V1.2  D           This example is a simple UIL/Xm program with a label and a           push button.  !     B.6 Motifanim Example Program              V1.1  D           The motifanim program demonstrates the following OSF/Motif           features:p  A           o  Declaration of icon/bitmap using UIL for portabilityU              across visualsn  :           o  Exchange of value between UIL and C using Mrm  )           o  Use of the Motif form widgety  E           o  Background procedure running while the client process is 6              waiting for input (Xt intrinsics feature)  @           This example lets you animate a set of pixmaps in an XE           window. The pixmaps are not fixed by motifanim but are read -           at startup from existing UID files.d  A           The syntax of all the animation.uid files can add a newgB           set of pixmaps to be animated using motifanim. Some tree3           examples of animation data files include:t                dog.uil              plane.uil  C           The default animation is dog. To run the example with thei7           other animations, use the following commands:s  %           $ SET DEFAULT DECW$EXAMPLES 3           $ motifanim := "$DECW$EXAMPLES:motifanim"o!           $ motifanim -anim planet  E           The files motiflogo.uil, motifanim.uil, and motifanim.c arei-           the core components of the program.,  "     B-6 OSF/Motif Example Programs p  e      I                                                OSF/Motif Example ProgramsSI                                    B.7 Motifgif and Pict Viewing Programs     .         B.7 Motifgif and Pict Viewing Programs                 V1.2  4               The following .gif files are provided:  C               o  TOUCAN.GIF, which is a picture of a tropical bird.   H               o  CHALLENGER.GIF, which is a picture of the space shuttle                  Challenger.                 V1.1  E               The motifgif and pict programs work together to displayeE               a .gif formatted picture. The motifgif program displaysiG               a .gif file within Motif constructs. The motifgif program <               looks for .gif files in the current directory.  D               The motifgif program has three significant components:                 o  motifgifn  F                  The source and executable code in this directory is aE                  Motif program driving the display of a .gif picture.e                 o  pict   F                  The program called by motifgif that displays a bitmapI                  of a .gif picture file. This program used to be xgif but 3                  has since been converted to Motif.   9               The following problems exist with motifgif:   2               o  Resizing a picture does not work.  G               o  The -d option is not used when calling pict, so remote D                  displays must set the DISPLAY environment variable.  &         B.8 Motifshell Example Program                 V1.2  D               The motifshell program is an example of an environmentC               created using Motif. The purpose of the example is to D               show how Motif may be used as a standalone environment;               for dispatching other programs and utilities.   I                                            OSF/Motif Example Programs B-7                 OSF/Motif Example Programs"     B.8 Motifshell Example Program    C           The motifshell program is written in C code. There are no            UIL references.i  C              ________________________ Note ________________________   C              Displaying a file listing or process status takes somehB              time. These operations are accomplished by spawning aB              DCL command, capturing the output in a file, and then              reading the file.  <              The default font is proportionally spaced. Some@              listings are more readable if a fixed space font isC              used, such as Courier. Use the Font option to select a               different font.  C              ______________________________________________________t        B.9 Periodic Example Program             V1.2  D           The periodic example is a demonstration of the displayableC           widgets in Motif. The program displays Motif widgets in a             periodic chart format.  !     B.10 Textedit Example Program              V1.2  B           The textedit program is a primitive text editor based onA           the Motif XmText widget that makes use of its XmNsource A           resource to allow multiple views of the same underlying            text.t  4           Table B-1 describes the View menu options.  E           Table_B-1_View_Menu_Options________________________________   E           Option_______Description___________________________________   B           Split Pane   Adds a new independently scrollable view of                         the text.  1           Remove Pane  Removes a designated pane.Y  E                                              (continued on next page)o  "     B-8 OSF/Motif Example Programs           I                                                OSF/Motif Example ProgramsrI                                             B.10 Textedit Example Programs    I               Table_B-1_(Cont.)_View_Menu_Options________________________   I               Option_______Description___________________________________e  I               One_Pane_____Removes_all_panes_except_the_designated_pane._s  E               The designated pane is determined in the following way:o  G               o  If using an explicit focus policy, it is the last viewM!                  which had focus.S  E               o  If using a pointer focus policy, it is the last vieww0                  with which the user interacted.  A               The designated pane is also the one whose clipboardlF               contents are pasted when Paste is selected from the Edit               Menu.o  I               The textedit sources are separated into independent layers.IE               Textedit contains the source files listed in Table B-2.   I               Table_B-2_Textedit_Source_Files____________________________                  FileI               Name_____Description_______________________________________   G               tfile.c  The code to read, write, and remove files. Hides G                        any operating system or filesystem dependencies.   I               app.c    Uses tfile.c to provide all the code to manipulate H                        files and their related buffers. This is toolkit-!                        dependent.h  I                                                  (continued on next page)                       I                                            OSF/Motif Example Programs B-9l b  s           OSF/Motif Example Programs!     B.10 Textedit Example Programf    E           Table_B-2_(Cont.)_Textedit_Source_Files____________________k             FileE           Name_____Description_______________________________________i  ;           tk.c     Isolates dependencies on the Xm Toolkit.D  >                    The first half of the file provides utility:                    routines and a toolkit-independent (butC                    application-specific) interface that can be useddA                    by the toolkit-independent dialog layer of thea                    application.r  >                    The second half of the file defines all the@                    callback routines. Many of these update stateD                    internal to this layer; others perform additionalB                    actions. Those actions unambiguously correspondE                    to toolkit-specific action routines defined in theeB                    first half of the file. Otherwise, an upcall isB                    made to the toolkit-independent dialog layer to%                    decide what to do.   E           dlg.c    Uses tk.c to manage dialog with the user. The codeS*                    is toolkit-independent.  ?           textedit.Initializes the application and instantiates @                    widget hierarchies. The code hides the use ofE           _________UIL_and_Mrm_from_the_rest_of_the_application._____   C              ________________________ Note ________________________   7              Moving and removing files is not currentlyo              implemented.   C              ______________________________________________________a  "     B.10.1 Additional Translations             V1.2  A           Users familiar with emacs may want to add the followingt9           translations to their DECW$XDEFAULTS.DAT files:t      #     B-10 OSF/Motif Example Programso           I                                                OSF/Motif Example Programs I                                             B.10 Textedit Example Programr    U               *XmText.translations:     Mod1<Btn3Down>: scroll-cursor-vertically()\n\d?                 Mod1<Btn3Motion>: scroll-cursor-vertically()\n\ 1                Ctrl<key>a: beginning-of-line()\n\c2                Ctrl<key>b: backward-character()\n\5                Ctrl<key>d: delete-next-character()\n\e+                Ctrl<key>e: end-of-line()\n\ 1                Ctrl<key>f: forward-character()\n\c$                Ctrl<key>g: beep()\n\9                Ctrl<key>h: delete-previous-character()\n\ +                Ctrl<key>i: cut-primary()\n\o2                Ctrl<key>j: newline-and-indent()\n\U                Ctrl<key>k: set-anchor() end-of-line() key-select() cut-clipboard()\n\ .                Ctrl<key>l: redraw-display()\n\'                Ctrl<key>m: newline()\n\s)                Ctrl<key>n: next-line()\n\ 2                Ctrl<key>o: newline-and-backup()\n\-                Ctrl<key>p: previous-line()\n\ )                Ctrl<key>v: next-page()\n\p-                Ctrl<key>w: cut-clipboard()\n\ /                Ctrl<key>y: paste-clipboard()\n\r2                Ctrl<key>z: scroll-one-line-up()\n\-                Mod1<key>b: backward-word()\n\a0                Mod1<key>d: delete-next-word()\n\,                Mod1<key>f: forward-word()\n\4                Mod1<key>h: delete-previous-word()\n\,                Mod1<key>i: copy-primary()\n\5                Mod1<key>k: delete-to-end-of-line()\n\a-                Mod1<key>v: previous-page()\n\R.                Mod1<key>w: copy-clipboard()\n\4                Mod1<key>z: scroll-one-line-down()\n\7                Mod1 Shift<key>greater: end-of-file()\n\o4                Mod1<key>less: beginning-of-file()\n\1                Mod1<key>]: forward-paragraph()\n\ /                Mod1<key>[: backward-paragraph()   !         B.11 View Example Programe                 V1.2  F               The view program is similar to the DCL command TYPE/PAGEF               using Motif with internationalization support. It allows5               you to view files in several languages.m      I                                           OSF/Motif Example Programs B-11o                OSF/Motif Example Programs     B.11 View Example Programa    B           The command file DECW$EXAMPLES:FILEVIEW.COM is provided,D           which allows you to select a language. Valid languages areD           French, English, and German. To select a language, perform!           the following commands:i  *           $ SET DEFAULT DECW$USER_DEFAULTS,           $ @DECW$EXAMPLES:FILEVIEW language  A           This command file copies the .UID and .DAT files to the ?           current directory. It sets the appropriate locale anda4           executes the file viewing example program.  D           When the application is started, a primary top-level shell?           is created. From the primary top-level shell, you cano"           create secondary shells.  E           Each top-level shell is a parent of a Main Window, the workb)           area of which is a PanedWindow.e  1           The menu bar has the following entries:   E           o  File-opening and closing files, creating new shells, andi              exiting  :           o  View-controlling the panes in the pane window             File Menu   7           The file menu contains the following options:              o  Open New File  B              A file selection box is mapped to choose the file. If@              OpenFile is successful, the current file is closed,B              all existing panes are destroyed, and the new file is              displayed.p             o  Open New Shell   D              Creates a secondary shell similar to the primary shell.=              Files can be viewed in each shell independently.a             o  Close  @              This entry only exists on the secondary windows. It>              destroys the top-level shell and closes the file.             o  Exit   C              This entry only exists on the primary shell; it closes $              the file and the shell.  #     B-12 OSF/Motif Example ProgramsL e  a      I                                                OSF/Motif Example Programs I                                                 B.11 View Example Program                    View Menur  ;               The view menu contains the following options:n                 o  New Panen  8                  Creates a new pane in the paned window.                 o  Delete Pane  *                  Deletes the current pane.                 o  Search   D                  Causes a dialog box to pop up for searching text inE                  the file. The OK callback of the dialog box searcheseG                  the string. If the string is found, it is displayed inCG                  the current pane. If the string is not found, then the $                  dialog box pops up.  I               Opening a second file in a window causes the application to C               end abruptly. The View options do not work correctly.n  $         B.12 Xmpiano Example Program                 V1.2  F               The xmpiano program shows how to write a Motif InterfaceG               to Dumb Instruments (MIDI) application. Both a staff, for 7               writing music, and keyboard are provided.a  D               At the bottom of the window is a set of notes that mayG               be used on the staff. Selecting one of these note buttonstG               changes the active note accordingly. The selected note isn5               also displayed as the new mouse cursor.c  E               Though the note selection is limited, it is possible totH               play sharps as well as naturals. The program interface hasE               not been written to play flats. The staff automaticallyAF               resizes larger as notes are added past the right side ofG               the staff. To see these notes, scroll the score window as                needed.   C               To use this application, press the right mouse buttoneF               on a staff that is visible. The following menu items are               displayed:                 o  Add Voice  I                                           OSF/Motif Example Programs B-13t    r           OSF/Motif Example Programs      B.12 Xmpiano Example Program    E              Connects another display to a new staff. After selecting >              this command, you are prompted for the display toA              connect. Any music written in the new staff plays to D              this display. Note that pressing the right mouse buttonB              on the new staff shows the name of the display in theC              menu title. In addition, the menu commands in the menuo=              bar relate to the staff that is being displayed.              o  Remove Voice   ?              Removes the staff as well as the connection to thee=              corresponding display. There is no undo for this @              command-all music written in this staff is deleted.             o  Clear Voice  D              Erases all notes on the staff. This does not affect the               display connection.             o  Play Voicei  B              Plays the voice of the staff in which the right mouseE              was pressed. If the voice is the same as the local host, B              the keys on the keyboard that correspond to the notesE              appear as though they are being pressed as the notes aremC              played. It is possible to make the keyboard play alongeE              with all voices at the same time; however, the code must E              be compiled with the -DCHORDS option. Note that this cantE              slow down the application significantly on many servers.a             o  Play All   =              Plays all voices at the same time on each of theb               specified displays.             o  Save Voiceo  7              Saves the corresponding voice to a file. A D              FileSelectionDialog is displayed to prompt for the name@              of the file in which to save the voice. The display1              connection information is not saved.R             o  Load VoiceS  <              Loads (appends) a previously saved voice to the!              corresponding staff.              o  Quit   '              Exits the example program.d  #     B-14 OSF/Motif Example Programsp t         I                                                OSF/Motif Example Programs I                                              B.12 Xmpiano Example Program     D               This version does not allow editing of notes. To edit,F               clear the staff and start again, or read the data from a               saved file.s  H               To set the color of the notes, change the foreground colorG               of the application. To do this, use the -fg option on thea(               command line. For example:  2               $ xmpiano :== $DECW$EXAMPLES:xmpiano                $ xmpiano -fg blue  %         B.13 Xmtravel Example Program                  V1.2  C               The xmtravel example is a front end to a travel agent D               client and flight database. The program is designed toG               illustrate various user-interface design concepts as welln=               as be compliant with the OSF/Motif Style Guide.3  G               The program is just an example, many of the functions are @               either not implemented or use predefined settings.  '         B.14 Additional Sample Programsw                 V1.2  C               Table B-3 lists sample programs showing various Motife$               Toolkit functionality.  I               Table_B-3_Motif_Sample_Programs____________________________w  I               File_Name_____Description__________________________________n  *               xmdialogs.c   dialog sampler  (               xmfonts.c     font browser  '               xmeditor.c    text editory  (               xmlist.c      list example  <               xmprotocol.c  window manager protocols example  5               xmter.c       shape & animation example   3               xmform.c      form attachment example   ?               xmforc.c      form attachment + rowcolumn example   I                                                  (continued on next page)r  I                                           OSF/Motif Example Programs B-15t c  s           OSF/Motif Example Programs#     B.14 Additional Sample Programs     E           Table_B-3_(Cont.)_Motif_Sample_Programs____________________.  E           File_Name_____Description__________________________________   <           xmmap.c       drawingarea + scrolledwindow example  1           xmgetres.c    resource fetching examplee  E           xmapdef.c_____app_defined_scrolled_window_example__________i  =           The following notes apply to these sample programs:   A           1. The xmfonts program defaults to displaying the fonts C              whose name length are less than 10 characters. On some @              systems, the font path contains only long XLFD fontB              names. It may be necessary either to set the resourceD              XMFONTS*maxLen to a larger number (80), or to specify a&              numColumns resource of 1.  ?           2. If you run the program xmter with a window manager A              other than Motif Window Manager, that window manager C              has to remove all the window decorations (for example, E              borders). The program xmter directs Motif Window ManagerM.              to remove the window decorations.  ?           3. The xmform program displays a string made of Motif D              widgets embedded in a Form. Use the following commands:  /              $ xmform :== $DECW$EXAMPLES:xmformi              $ xmform string  D              The variable string is optional. If string is supplied,@              the available letters for string are F,I,M,O,T. The@              string of letters that you use must be in uppercaseC              and enclosed in quotation marks. If string is omitted,l$              xmform returns "MOTIF".  =           4. The xmgetres program is an example of how to use C              XmGetSecondaryResourceData. Use the following commands                to invoke xmgetres:  3              $ xmgetres :== $DECW$EXAMPLES:xmgetrest#              $ xmgetres WidgetClass   D              The variable WidgetClass is optional. If WidgetClass isD              omitted, it defaults to a class named "Widget". You canC              also use the class "All", which displays the resources D              for all the Xt and the Motif widgets. See the OSF/Motif  #     B-16 OSF/Motif Example Programs            I                                                OSF/Motif Example ProgramstI                                           B.14 Additional Sample Programsu    F                  Programmer's Reference manual for a list of available                   widget classes.  0         B.15 Resource Files for Example Programs                 V1.2  I               Many of the example programs have associated resource files C               for defining various display attributes. To use these F               files, either copy them from the directory DECW$EXAMPLESI               to your DECW$USER_DEFAULTS directory, or add their contents .               to your DECW$XDEFAULTS.DAT file.  A               The list of example programs and the resource files.1               associated with them is as follows:   I               ___________________________________________________________ I               Example_Program_______Resource_File________________________   5               DECW$CDPLAYER.EXE     DECW$CDPLAYER.DATd  0               FILEVIEW.EXE          FILEVIEW.DAT  0               PERIODIC.EXE          PERIODIC.DAT  1               MOTIFANM.EXE          MOTIFANIM.DAT   /               XMAPDEF.EXE           XMDEMOS.DAT   /               XMDIALOGS.EXE         XMDEMOS.DAT   /               XMEDITOR.EXE          XMDEMOS.DAT   /               XMFONTS.EXE           XMDEMOS.DAT.  /               XMFORC.EXE            XMDEMOS.DAT   /               XMFORM.EXE            XMDEMOS.DAT   /               XMGETRES.EXE          XMDEMOS.DAT   /               XMLIST.EXE            XMDEMOS.DATp  /               XMMAP.EXE             XMDEMOS.DATe  /               XMPROTOCOL.EXE        XMDEMOS.DATh  /               XMTER.EXE             XMDEMOS.DAT   I               XMTRAVEL.EXE__________XMTRAVEL.DAT_________________________e  H               If a resource file is not found, the example programs run,B               but some of the display attributes may be incorrect.  I                                           OSF/Motif Example Programs B-17/ b  h                            F      _________________________________________________________________  F                                                                  Index      :      A                                 CDA Viewer (cont'd)F      _______________________________     viewing large DDIF files with;      AccessX extension,  4-39               eXcursion, 2-18t0      Application Group extension       CD PlayerC         (XC-APPGROUP)                    required privileges,  2-30o<        group validation, 4-39          C header files,  4-14:        loading with XINERAMA, 3-9      Client applicationsC      Applications                        delay during closing,  2-7 C        compiling Fortran, 4-13           response time issues,  2-6 >        compiling multithreaded with      running locally,  2-6,          upcalls enabled,  4-6         ClockC      Auto Repeat setting                 updating after system time 7        changing, 2-24                       reset, 2-19   E                                          using the Front Panel Clock, 0      B______________________________        2-14  7      Bookreader                        Color customizerLD        support for Display               using with DECwindows Mail,0          PostScript removed,  2-18          2-31@      Browser support,  2-5               using with Motif Window9                                             Manager, 2-36sD      C______________________________     using with Session Manager,0      Calculator                             2-34=        default width, 2-10             Compiling applications_  >      CDA Viewer                          See also Applications7        applications, 2-18                Fortran,  4-13 ?        image ident, 4-14               Compose character,  2-36 7        logical names with CONVERT,     Copyright notice @          4-15                            displaying in a DECterm8        style guide message, 4-15            window, 2-24>        support for Display             CREATE/TERMINAL command;          PostScript removed,  2-19       /PROCESS qualifierW=        tear-off menu support, 2-8           restriction, 2-29   F                                                                Index-1                   7     CREATE/TERMINAL command            DECterm (cont'd) A        (cont'd)                         supported logicals,  2-25WE       using to create a virtual         terminal emulator limitations 1          terminal, 2-28                    , 2-28 A       using to display broadcast        text display on multihead 8          messages, 2-20                    systems, 2-22A       using with IPv6 support,          using the debugger,  2-28oB          2-20                           using to display broadcast9                                            messages, 2-20 A     D______________________________     virtual terminal support, /     DEClinks,  4-16                        2-28_C     DECterm                            DECTERM_ERROR.LOG file, 2-27.-       changing the Auto Repeat         DECTPU A          setting, 2-24                  delay when exiting,  2-12tD       DECCRA sequence,  4-16            display monitor restriction,.       DECLFKC sequences,  4-16             2-2  4       diagnostic crash file,  2-27     DECW$CDPLAYER  5       displaying the copyright          See CD Player B          notice, 2-24                  DECW$COMPARE_VERSIONS file,,       euro currency symbol               3-4C          restrictions, 2-21            DECW$DECTERM_OUTPUT logical,n-       fails with Kerberos enabled,       2-28 ?          2-21                          DECW$INCLUDE:INTRINSIC.Hn;       finish printing option,  5-2       header file,  4-10WB       font selection,  2-24            DECW$INCLUDE:TEXTP.H header-       graphics,  2-26                    file A       hold-screen response time,        definition changes,  4-26 E          2-26                          DECW$INCLUDE:XMP.H header fileA  =       ignoreVisibility resource,        See also Header filesr6          2-21                           changes,  4-26;       IPv6 restriction,  2-20           removed definitionsi@       maximum number of windows,           XmHALFLONGBITS,  4-26<          2-23                              XmLONGBITS,  4-26C       positioning windows,  2-20       DECW$IPV6_SUPPORT parameter,u-       problem with ReGIS                 2-20lA          applications, 2-19            DECW$MRM$MAX_MODULE_WIDGET 6       /PROCESS problem,  2-29            logical,  4-7E       ReGIS locator report,  2-30      DECW$SERVER_PRIORITY parameter /       reporting window size,  2-23       ,  2-7a8       resizing the terminal,  2-23     DECW$STARTUP fileA       resource file name,  2-22         required privileges,  3-3tA       resource usage,  2-27             running from the operatord7       screen print services,  2-25         console, 3-4e       shrinking window,  2-22i       Index-2  h  i              G         DECwindows                        DXmLAYOUT_RIGHT_DOWN constant I          privileges required for            DXmNlayoutDirection resource,a1             system startup,  3-3              5-5oE          starting from the operator       DXmLAYOUT_RIGHT_UP constant I             console,  3-4                   DXmNlayoutDirection resource,u1          version support,  3-1                5-5sF         DECwindows Extensions to Motif    DXmNlayoutDirection resource:           ,  4-29                           constants, 5-4           DECwindows MailcI          See Mail                         E______________________________r  5         DECwrite                          Euro symbol E          icon does not open program,        may not display correctlydD             2-12                              using eXcursion,  2-21>         Development support, 4-5            restrictions, 3-127         Display devices                   EVI extension D          bad parameter error message,       colormap conflicts, 4-383             2-1                           eXcursioneI          problems deleting,  2-2            displaying DECterm windows onsF          revoking generated cookies,          multihead systems,  2-21?             2-1                             euro symbol displaytA         Display PostScript                    restrictions,  2-21mD          support discontinued,  2-7,        using to view large DDIF:             2-18, 2-19, 2-30, 4-8             files,  2-184         DtCalc                            ExtensionsC          default width,  2-10               AccessX extension, 4-39uH         DtFile                              Application Group extension,2          extended file specification          4-39?             restrictions,  2-12             EVI extension, 4-38ED          moving a large number of           Security extension, 4-39E             files,  2-10                    specifying include files,a2          restoring files,  2-10               4-40E         dximageview, 2-12                   unsupported combinations,c2         DXmFormSpaceButtonsEqually            3-20D           routine                           XINERAMA extension, 3-9,D          sizing and spacing widgets,          3-17, 3-19, 3-20, 4-38F             4-29                            X Keyboard extension, 4-39$         DXmLAYOUT_LEFT_DOWN constantI          DXmNlayoutDirection resource,    F______________________________d6             5-4                           File ManagerG         DXmLAYOUT_LEFT_UP constant          extended file specification A          DXmNlayoutDirection resource,        restrictions,  2-12 D             5-5                             moving a large number of  :                                               files,  2-10A                                             restoring files, 2-10   I                                                                   Index-3                    =     File Manager (cont'd)              hostList resource, 3-7i  <       search limitations,  2-15        HP Secure Web Browser/     File names                          See SWBg       displayed in UNIX format, F          2-13                          I______________________________4     FileView                           Image displayA       application startup,  2-34        displaying scaled bitonalg6       private logo restriction,            images, 2-6E          2-34                           viewing large DDIF files withe;     Finish printing option                 CDA Viewer, 2-18r>       DECterm,  5-2                     viewing TIF files with	     FontsD<       DECterm restrictions,  2-24          dximageview, 2-123       euro symbol restrictions,        InstallationdE          3-12                           compare file limitation,  3-4fC       queries on TrueType               using shareable linkages to >          properties, 3-12                  install images, 3-3=     Font Server Information             version support,  3-2TE        Utility (fsinfo)                Inter-Client Exchange protocolmC       problems invoking,  2-40          BAD_LOCAL_NODE error,  4-40xB     Fortran                             removing watch procedures,/       compiling applications,  4-13        4-39w?     fsinfo                              required privileges fort@       See Font Server Information          server processes, 4-8  B          Utility                       Internet Protocol Version 6  0       See Font Server Information       See IPv6+          Utility (fsinfo)              IPv6iD                                         CREATE/TERMINAL restriction,/     G                                      2-20l#     _______________________________TF     GENPWD flag,  3-6                  J______________________________;     GET_CHAR_STRUCT function           Java Development Kit C       access,  5-3                      Display PostScript support,a/     GKS,  2-7                              4-10        Graphics Kernel System  F       See GKS                          K______________________________  /     H                                  Kerberos E     _______________________________     cannot parse node name 0 with 6     Header files                           TCP/IP, 3-9E       DECW$INCLUDE:INTRINSIC.H,         causes DECterm failure,  2-21D<          4-10                           does not support SET@       DECW$INCLUDE:TEXTP.H,  4-26          DISPLAY/GENERATE, 3-7D       DECW$INCLUDE:XMP.H,  4-26         incorrect help on Login Box,  /                                            3-10        Index-4                    G         Kerberos (cont'd)                 Motif Window Manager (cont'd)   D          unknown code error,  3-8           configuration file, 2-37A          using DECwindows login,  3-10      customizing colors oneF         Key bindings, 2-36                    multihead systems,  2-38F          changing function keys,  2-37      help text not displayed onF         Keymaps                               multihead systems,  2-35G          restriction with Mode_switch       moving the icon box off theo;             modifier,  3-12                   screen,  2-38E  <                                             restarting, 2-37H         L______________________________     supporting customization for  H         Locale support, 4-35                  monochrome monitors,  2-38;         Login screen                      Multihead systemse@          control characters not             cascade menus placed@             recognized,  2-16                 incorrectly,  3-20D          moving between text fields,        customizing colors, 2-38E             2-16                            DECterm scrolling issues, 2          password entry,  2-16                2-21F         Low-Bandwidth X proxy server        incorrect security options>          required privileges for              displayed,  2-11C             server processes,  4-8          MWM help text displayed @          restrictions,  3-14                  incorrectly,  2-35E                                             New Desktop restrictions,A2         M______________________________       3-19D         Magic Cookie                        performance limitations,2          inserting generated cookies          3-17G             into an X authority file,       problems running XMAG, 3-20 I             3-10                            VisibilityNotify restriction, 2         Mail                                  4-38A          activating pushbuttons in          window text displayedL@             dialog boxes,  2-31               incorrectly,  2-228          changes in keyboard actions,     MultiNet,  3-2E             2-31                          Multithreaded applications,t0          color customizer,  2-31             4-6  -          highlighting selections,         MWM   D             2-31                            See Motif Window Manager             pasting messages,  2-31I          support for Display              N______________________________i  5             PostScript removed,  2-30     New Desktop I         Motif and XUI widgets               default screen saver settings(5          mixing,  4-28                        ,  2-11 G         Motif Window Manager                default workspace backdrop, 2          centering lines for multiline        2-17             icon titles,  2-38           color customizer,  2-36  I                                                                   Index-5y q  e              8     New Desktop (cont'd)               OSF/Motif Toolkit9       file names displayed in UNIX      examples (cont'd)e  6          format, 2-13                      view,  B-119       Front Panel Clock,  2-14             xmpiano,  B-13e:       login and pause screen text          xmtravel,  B-15=          limitations, 2-16              known problems,  A-19        saving and restoringF          applications, 2-14            P______________________________,       selecting fonts,  2-17           PaintC       text editor restrictions,         creating private colormaps, /          2-13                              2-32sD       ToolTalk Action definition        enhancing performance duringA          support, 2-14                     basic operations, 2-32g9     Notepad                            Parameter datasizee9       Motif Release 1.2 limitations     mismatches,  4-36d0          , 2-32                        PEN filesC       tear-off menu support,  2-8       using with Pascal programs, /     numHosts resource,  3-7                4-36t  3                                        Print screeneC     O______________________________     tear-off menu support,  2-8d  D     OpenVMS Debugger                   Programming environments, 4-5:       redirecting to a DECterm         Programming supportE          window, 2-28                   increased stack requirements, .     OSF/Motif Toolkit                      4-8C       examples,  B-1                   Programming support and XUI, -          cutpaste,  B-1                  4-20 4          dnddemo,  B-1                 Proxy Manager:          Dogs,  B-3                     configuration file<             widget,  B-3                   restriction, 3-15B          helloint,  B-5                 problems restarting,  3-14?          hellomotif,  B-6               required privileges for @          MOTIFANIM,  B-6                   server processes, 4-8          MOTIFGIF,  B-7 F          motif samples,  B-15          R______________________________8          motifshell,  B-7              ReGIS, 2-19, 2-26C          periodic,  B-8                 locator report issue,  2-30m<          pict,  B-7                    Run-time support, 4-5          PICT,  B-7 #          resource files for exampleo             programs, B-17          Square widget,  B-4          textedit,  B-8           UID files for example             programs, 4-27       Index-6     x              @                                           Style Manager (cont'd)F         S______________________________     font selection limitation,  2         Screen saver, 2-11                    2-17I         Security extension (SECURITY)       incorrect security options on F          group validation,  4-39              multihead systems,  2-114          loading with XINERAMA,  3-9      SVN widgetF          restriction on generating          live horizontal scrolling,2             authorization keys,  3-7          4-293          use of XC-QUERY-SECURITY-        SWB,  2-5u9             1 protocol with proxy         System menu bar 9             servers,  3-14                  messages, 2-8 A         Security options                  System parameters,  3-5i            Session Manager,  2-33 I         Session Manager                   T______________________________ :          application startup,  2-34       TCP/IP transport?          color customizer,  2-34            third-party support ?          private logo restriction,            limitations,  3-2b7             2-34                          TCPware,  3-2o8          specifying node names for        Tear-off menus@             authorized users,  2-33         limited support, 2-85          stopping a process,  2-34        Text Editor >         SET DISPLAY command                 restrictions, 2-131          bad parameter error message,     Toolkit >             2-1                             compatibility, 4-4B          /GENERATE restriction with            naming in OSF/MotifH             Kerberos enabled,  3-7               Release 1.2.2 and X11R5F          problems deleting devices,              and Greater ShareableA             2-2                                  Libraries,  4-17t6          revoking generated cookies,        extensionsI             2-1                                CompositeClassExtensionRec 8         Shareable linkages                       ,  4-30D          using to install images,  3-3      memory leak corrections,8         Start Session                         4-25, 4-26I          blue login screen,  3-11           mixing Motif and XUI Widgets,r2         Startup files                         4-28@          required privileges,  3-3          modifying XmText andE          restriction running from             XmTextField translation C             operator console,  3-4            manager syntax,  4-28   B         Structured Visual Navigation        OSF/Motif Release, 4-4  F          See SVN                            release 1.1.3 applications9         Style Manager                         abort,  2-8P4          changing the default backdrop      routines@             ,  2-17                            XtGetValues, 4-30  B                                                XtOpenDisplay, 4-31  I                                                                   Index-7e    e              A     Toolkit (cont'd)                   WM_SAVE_YOURSELF protocol,e-       saving programming                 2-14o1          environments, 4-24            Workspaces ?       UIL compiler,  4-20               default backdrop,  2-17          using _Xm routines,  4-27eF     ToolTalk actions                   X______________________________  ,       limited support,  2-14           xauth?     Translated-image support,  4-9      See X Authority Utilityt2       running on OpenVMS systems,          (xauth)B          4-11                          X Authority Utility (xauth);     Transports                          file locking,  2-39 A       user-written not supported,       restriction on generatingeB          4-41                              authorization keys, 3-7D     TrueType fonts,  3-12               specifying file names,  2-39  D     U                                  XC-QUERY-SECURITY-1 protocol,-     _______________________________      3-14e9     UAF parameters,  3-5               XINERAMA extensiona=     UID files                           extraneous characterst:       accessing remotely,  4-27            displayed, 3-20A     UIL files                           loading with XC-APPGROUP,n.       changing the top-level widget        3-9@          maximum, 4-7                   mode restrictions,  3-20A       compiling,  4-20                  New Desktop restrictions,l/       parsing,  4-11                       3-19n@       problems with looped object       performance limitations,/          references, 4-13                  3-17 C     UIL source code                     placement of cascade menus, /       documentation,  5-3                  3-20 E     Untrusted connections               VisibilityNotify restriction, /       running applications,  3-8           4-38n  D     User Authorization File             XCopyArea restriction,  4-38A        parameters                      X Keyboard extension (XKB)e  A       See UAF parameters                dead mouse support,  4-39n+                                        XlibrA     W______________________________     ConnectionNumber changes, /     Welcome screen                         4-34 ;       text not displayed,  2-17         EFN 63 state changew;     Widgets                                correction, 4-32hC       See also Motif and XUI            error message format,  4-33 B          widgets, 4-28                  files for Pascal programs,/       sizing and spacing using             4-36e=          DXmFormSpaceButtonsEqually     locale support,  4-35lD          , 4-29                         parameter datasize mismatch,/                                            4-36        Index-8u e  i              5         Xlib (cont'd)                     XNL libraryiC          retired entry points,  4-33        xnl_parsedatetime, 4-41hB          routines                           xnl_xnl_langinfo, 4-416             XSelectAsyncEvent,  4-35      xnl_langinfoA             XSelectAsyncInput,  4-35        year 200 issues, 4-41 ;          XCloseDisplay correction,        xnl_parsedatetime B             4-32                            year 2000 issues, 4-41C          XConnectionNumber changes,       XSelectAsyncEvent routine C             4-34                            allocating memory, 4-35rC          XOpenDisplay correction,         XSelectAsyncInput routine1C             4-32                            allocating memory, 4-35e2          XPutImage correction,  4-31      X ServerH         X Library                           unsupported extensions, 3-20G                                           X Session Management ProtocoleE          See Xlib                           SmsGenerateClientId, 4-40a  .                                           XSMP  D                                             See X Session Management6                                               Protocol  3                                           X Toolkit   7                                             see Toolkith                                          I                                                                   Index-9f