                   H                     ____________________________________________________$                     DECwindows Motif-                     Version 1.2-5 for OpenVMS !                     Release Notes     !                     December 1998   @                     This manual describes new features, software<                     problems, corrections, restrictions, andD                     documentation changes that pertain to DECwindowsE                     Motif Version 1.2-5 for OpenVMS Alpha and OpenVMS                      VAX.              H                     Revision/Update Information:  This manual supersedes@                                                   the DECwindowsE                                                   Motif Version 1.2-4 E                                                   for OpenVMS Release 8                                                   Notes.  G                     Operating System:             OpenVMS Alpha Version 5                                                   6.2 C                                                   VMS Version 5.5-2   B                     Software Version:             DECwindows MotifC                                                   Version 1.2-5 for ?                                                   OpenVMS Alpha B                                                   DECwindows MotifC                                                   Version 1.2-5 for =                                                   OpenVMS VAX         /                     Compaq Computer Corporation "                     Houston, Texas                 J           ________________________________________________________________           December 1998   >           Compaq Computer Corporation makes no representationsA           that the use of its products in the manner described in B           this publication will not infringe on existing or futureB           patent rights, nor do the descriptions contained in thisB           publication imply the granting of licenses to make, use,>           or sell equipment or software in accordance with the           description.  B           Possession, use, or copying of the software described inA           this publication is authorized only pursuant to a valid C           written license from Compaq or an authorized sublicensor.   A           Compaq conducts its business in a manner that conserves C           the environment and protects the safety and health of its 2           employees, customers, and the community.  B            Compaq Computer Corporation 1998. All rights reserved.  9           The following are trademarks of Compaq Computer E           Corporation: Alpha, Compaq, DECdirect, DECwindows, DIGITAL, E           OpenVMS, VAX, VAX DOCUMENT, VAXcluster, VMS, and the Compaq            logo.   3           The following are third-party trademarks:   ;           Adobe, Adobe Illustrator, Display POSTSCRIPT, and ?           POSTSCRIPT are registered trademarks of Adobe Systems            Incorporated.   D           Motif, OSF, OSF/1, OSF/Motif, and Open Software FoundationD           are registered trademarks of the Open Software Foundation,           Inc.  D           Mosaic and NCSA Mosaic are trademarks of the University of           Illinois.   6           POSIX is a registered trademark of the IEEE.  =           X Window System is a trademark of the Massachusetts "           Institute of Technology.  @           All other trademarks and registered trademarks are the/           property of their respective holders.   E                                                                ZK6470   /           This document is available on CD-ROM.                                  C   _________________________________________________________________   C                                                            Contents       C   Preface...................................................     xi      1  General User Release Notes   <         1.1   General User Release Notes Specific to the NewC               Desktop (Alpha Only)..........................    1-1 C         1.1.1     dximageview TIF Error Messages............    1-1 6         1.1.2     Text Editor Supports Standalone ModeC                   Only......................................    1-1 4         1.1.3     Text Editor Does Not Support SpellC                   Checking..................................    1-1 :         1.1.4     Tab Size Within the Text Editor Is Not 8C                   Characters Wide...........................    1-2 C         1.1.5     Some File Names Appear in UNIX Format.....    1-2 9         1.1.6     DECwindows Interface for the TPU Editor C                   Does Not Save Itself......................    1-2 C         1.1.7     Front Panel Clock.........................    1-2 C         1.1.8     Using MB3 on Front Panel Icons............    1-2 C         1.1.9     Selecting Screens on Application Launch...    1-3 C         1.1.10    Detached Processes........................    1-3 C         1.1.11    ToolTalk Actions Not Supported............    1-3 .         1.1.12    Session Manager Save/RestoreC                   Limitations...............................    1-4 :         1.1.13    Limitations of dtfile (New Desktop-AlphaC                   Only).....................................    1-4 C         1.1.14    Login and Pause Screen Text Fields........    1-5 :         1.1.14.1    Control Characters Not Recognized WhenC                     Entering Username.......................    1-5 9         1.1.14.2    Return Key Used to Move Between Login C                     Text Fields.............................    1-6 ;         1.1.14.3    First Character Discarded When Entering C                     Pause Screen Password...................    1-6     C                                                                 iii                    8           1.1.14.4    Text On The Welcome Screen May NotE                       Appear..................................    1-6 9           1.1.15    Use SET DISPLAY/CREATE Within DECterm E                     Windows...................................    1-6 E           1.1.16    Viewing Reference Pages...................    1-7 E           1.1.17    Font Selection Limitations................    1-8 E           1.1.18    Default Workspace Limitations.............    1-8 <           1.1.19    Alt + Space Key Does Not Post the WindowE                     Menu .....................................    1-8 8           1.1.20    DECwrite Icon Does Not Open DECwriteE                     Program...................................    1-9 ;           1.2   DECwindows Support of OpenVMS Extended File E                 Specifications (EFS)..........................    1-9 E           1.2.1     The File Selection Popup..................    1-9 3           1.2.2     The FileView Application in the E                     Traditional DECwindows Desktop............   1-10 ;           1.2.3     The File Manager Application in the New E                     Desktop...................................   1-10 9           1.2.3.1     File Manager Problems with EFS (New E                       Desktop Only)...........................   1-10 E           1.2.4     The Programming Libraries.................   1-12 >           1.2.5     The Translated Image Support (TIS) LibraryE                     (Alpha Only)..............................   1-13 =           1.3   Alt + Space Key Does Not Post the Window Menu E                 (DECwindows Desktop Only).....................   1-13 E           1.4   Using Drag and Drop...........................   1-13 E           1.5   Using Tear-Off Menus..........................   1-14 8           1.6   Access Control Not Explicitly Enabled byE                 Default.......................................   1-14 E           1.7   Color Customizer Example Program..............   1-14 E           1.7.1     Supported Displays........................   1-15 E           1.7.2     Supported Applications....................   1-15 <           1.7.3     Building the Color Customizer on OpenVMSE                     Systems...................................   1-15 E           1.7.4     Running the Color Customizer..............   1-16 E           1.7.5     Modifying the DECW$LOGIN.COM File.........   1-16 E           1.7.6     Command Interface Summary ................   1-17 6           1.7.7     Changing the Mapping Between ColorE                     Resources and Color Cells.................   1-18 E           1.7.8     DECterm Windows Not Affected..............   1-20 5           1.7.9     Changing the Default Value of the E                     Automatic Shadowing Toggle Button.........   1-20            iv                   9               1.7.10    Using the Customizer on Multihead I                         Systems...................................   1-20 A               1.7.11    Using the XSETROOT_CUST.EXE Demonstration I                         Program...................................   1-21 I               1.8   Display PostScript No Longer Supported........   1-21 I               1.9   DECwindows Motif Application Notes............   1-21 I               1.9.1     Bookreader................................   1-22 I               1.9.1.1     Bookreader Printing Improved............   1-22 I               1.9.1.2     Multiple-Byte Character Limitation......   1-22 =               1.9.1.3     Including Comment Characters in the I                           DECW$BOOKSHELF File.....................   1-22 I               1.9.2     Calendar-Year 2000 Support................   1-22 I               1.9.3     CDA Run-Time Services.....................   1-23 I               1.9.3.1     CDA Dynamic Font Support................   1-23 I               1.9.3.2     CDA WRITE$FONTS Logical Name............   1-24 I               1.9.3.3     CDA Documents...........................   1-24 I               1.9.4     CDA-Additional Applications...............   1-25 I               1.9.4.1     Pack and Unpack Applications............   1-25 I               1.9.4.2     Pack Application........................   1-26 I               1.9.4.3     Unpack Application......................   1-27 I               1.9.4.4     Pack and Unpack Error Messages..........   1-28 :               1.9.5     CDA-Hints, Restrictions, and KnownI                         Problems..................................   1-29 I               1.9.5.1     Message for CDA Viewer..................   1-29 I               1.9.5.2     CDA Paper Size Button Renamed...........   1-29 I               1.9.6     Clock-DECsound Capability.................   1-29 I               1.9.7     DECsound Application......................   1-30 I               1.9.7.1     DECsound Prerequisites..................   1-30 I               1.9.7.2     DECsound Problems.......................   1-30 I               1.9.8     DECterm Features..........................   1-30 I               1.9.8.1     New DECterm Default Font Sizes..........   1-30 I               1.9.8.2     DECterm Resource File Name..............   1-31 I               1.9.8.3     Escape Sequences........................   1-32 I               1.9.8.4     Scrolling Through the Keyboard..........   1-32 I               1.9.8.5     Reporting the DECterm Window Size.......   1-32 I               1.9.8.6     Resizing the Terminal...................   1-32 >               1.9.8.7     Timeout for Displaying the CopyrightI                           Notice..................................   1-33               I                                                                         v                    E           1.9.9     DECterm-Restrictions and Problems.........   1-33 E           1.9.9.1     Maximum Number of DECterm Windows.......   1-33 E           1.9.9.2     Changing the Auto Repeat Setting........   1-33 E           1.9.9.3     Positioning DECterm.....................   1-33 E           1.9.9.4     User Font Selection.....................   1-34 E           1.9.9.5     Local Echo..............................   1-35 E           1.9.9.6     Answerback Message......................   1-35 E           1.9.9.7     Seven-Bit Printer Support...............   1-36 E           1.9.9.8     VT330 and VT340 Terminal Emulation......   1-36 E           1.9.9.9     CREATE/TERMINAL/DETACHED/PROCESS........   1-36 E           1.9.9.10    Printing to an Attached Printer.........   1-37 E           1.9.9.11    DECterm Graphics........................   1-37 E           1.9.9.12    DECterm Resource Usage..................   1-38 E           1.9.9.13    Diagnostic Crash File and Messages......   1-39 E           1.9.9.14    ReGIS Locator Report....................   1-39 E           1.9.10    DECW$CDPLAYER.............................   1-39 E           1.9.11    DECwindows Mail...........................   1-39 E           1.9.11.1    DECwindows Mail Problems with MB3.......   1-40 9           1.9.11.2    Pasting Messages from the Directory E                       Window..................................   1-40 E           1.9.11.3    Responses to Keyboard Actions...........   1-40 5           1.9.11.4    Using the Color Customizer with E                       DECwindows Mail.........................   1-41 E           1.9.12    DECwindows Motif Window Manager...........   1-41 5           1.9.12.1    Using the Color Customizer with E                       DECwindows Motif Window Manager.........   1-41 E           1.9.12.2    Configuration File......................   1-41 E           1.9.12.3    DECwindows XUI Applications.............   1-42 E           1.9.12.4    Restarting Motif Window Manager.........   1-42 E           1.9.13    Motif Window Manager-Known Problems.......   1-42 =           1.9.13.1    Customizing Color-Related Resources for E                       Monochrome Monitors.....................   1-42 E           1.9.13.2    Moving the Icon Box Off Screen..........   1-43 E           1.9.13.3    Multihead Systems-Customizing Colors....   1-43 E           1.9.13.4    Multiline Icon Title Not Centered ......   1-43 E           1.9.14    Notepad...................................   1-43 :           1.9.14.1    Notepad Is Linked with the OSF/MotifE                       Release 1.1.3 Toolkit...................   1-43 E           1.9.15    Paint.....................................   1-44 E           1.9.15.1    Private Colormaps.......................   1-44 =           1.9.15.2    Enhancing the Performance of Some Paint E                       Operations..............................   1-44            vi                   I               1.9.16    Print Screen..............................   1-44 8               1.9.16.1    Print Screen-PostScript OutputI                           Problem.................................   1-44 I               1.9.17    Session Manager and FileView .............   1-45 <               1.9.17.1    Invoking DECchart from the SessionI                           Manager Applications Menu...............   1-45 I               1.9.17.2    Security Options........................   1-47 A               1.9.17.3    Using the Color Customizer with Session I                           Manager.................................   1-47 B               1.9.17.4    Input Focus Change When Starting PrivateI                           Logo....................................   1-48 I               1.9.17.5    Session Manager Process-Stopping........   1-48 I               1.10  Window Dump to Print File (xpr) Utility.......   1-48 <               1.11  Keyboard Enhancements for Disabled UsersI                     (Alpha Only)..................................   1-56 I               1.11.1    Sticky Keys...............................   1-56 I               1.11.2    Mouse Keys................................   1-56 I               1.11.3    Toggle Keys...............................   1-57 I               1.11.4    Repeat Keys...............................   1-57 I               1.11.5    Slow Keys.................................   1-57 I               1.11.6    Bounce Keys...............................   1-57 I               1.11.7    Time Out..................................   1-57 I               1.12  Printing from Applications....................   1-58_@               1.13  Unsupported Translations by the Motif XmTextI                     Widget........................................   1-58 >               1.14  Spyglass Enhanced Mosaic Browser No LongerI                     Supported.....................................   1-59bI               1.15  NCSA Mosaic Browser (VMS 5.5-2 Only)..........   1-60nI               1.15.1    Starting Mosaic Software..................   1-61 I               1.15.2    Creating a Home Page......................   1-61 @               1.15.3    Configuring Mosaic to Process MultimediaI                         Files.....................................   1-62 I               1.15.4    Customizing the Mosaic Browser............   1-63 A               1.15.5    Restrictions for Using Mosaic from Behind I                         a Firewall................................   1-77tI               1.15.5.1    ProxyGateway Resource...................   1-77 I               1.15.5.2    NoProxy Resource........................   1-78                 I                                                                       vii                    #     2  System Manager Release Notes.  E           2.1   Recommended Reboot After Installation.........    2-1 ;           2.2   Log Off Console Before DECwindows Can StartsE                 ..............................................    2-1 <           2.3   Installation Verification Procedure Error inE                 UIL Compiler..................................    2-2 >           2.4   Problem With Delayed DECwindows Startup (AlphaE                 Only).........................................    2-5 9           2.5   DECwindows Motif Login Screen-Known ColoreE                 Problem.......................................    2-7nE           2.6   System Tuning for Non-VGA Devices.............    2-7iE           2.7   Previously Optional Files Moved...............   2-12d:           2.8   Using Shareable Linkages to Install ImagesE                 (Alpha Only)..................................   2-13 ;           2.9   Define DECW$UTILS Global Symbol When Moving,E                 DECW$EXAMPLES Global Symbol...................   2-14 6           2.10  FileView Creates Detached Processes byE                 Default.......................................   2-14cE           2.11  Performance Problem with Certain Keymaps......   2-15mE           2.12  Customizing the Login Screen..................   2-17s:           2.12.1    Customizing the DIGITAL Logo and LoginE                     Screen Colors.............................   2-17d;           2.12.2    Changing Positions of the Start SessionpE                     and Set Password Dialog Boxes.............   2-18E>           2.12.3    Disabling a Node Name Display in the StartE                     Session Dialog Box........................   2-19eE           2.13  Customized Login Logos........................   2-19eE           2.14  Version Checking Command Files................   2-20 >           2.15  Implications of the Message, "System Menu Bar:E                 Pseudo Mouse Not Available"...................   2-22 :           2.16  CDA and DECsound Installation Problem (VAXE                 Only).........................................   2-22sE           2.17  DECterm System Management Issues..............   2-23kE           2.17.1    DECterm Logical Names.....................   2-23 E           2.17.2    Automatic Window Positioning..............   2-24rE           2.17.3    DECterm Window Shrinking Problem..........   2-24 E           2.17.4    Hold Screen Response Time.................   2-25bE           2.17.5    Using the Debugger........................   2-25_E           2.17.6    Virtual Terminal Support..................   2-25 :           2.17.7    DTSESSION Logging Problem (New DesktopE                     Only).....................................   2-26 E           2.18  Console Window Application....................   2-26sE           2.19  Window Manager Overlay Support................   2-28.       viii -                 #         3  Programmer Release Notes.  9               3.1   Programming Release Notes Specific todI                     DECwindows Motif for OpenVMS Software.........    3-1 8               3.2   DECwindows Motif for OpenVMS ToolkitI                     Versions......................................    3-1 I               3.3   Run-Time and Programming Environments.........    3-2h?               3.4   DECW$WML.EXE Looks in Current Directory For I                     DECW$WML_TOKENS.DAT...........................    3-3wI               3.5   DECW$COMPARE_VERSIONS Command File Problem....    3-3fI               3.6   OSF/Motif Toolkit Compatibility...............    3-3.I               3.6.1     _Xm Routines..............................    3-4.A               3.6.2     OSF/Motif Release 1.2.2 and X11 Release 5iI                         Shareable Libraries.......................    3-5.I               3.7   Language Bindings.............................    3-8.I               3.7.1     OSF/Motif Release 1.1.3 Ada Bindings......    3-8 ?               3.8   OSF/Motif Release 1.1.3 Programming Support3I                     and XUI.......................................    3-8.B               3.9   Adding POSIX for OpenVMS Support to DECwindowsI                     Transports....................................   3-13cI               3.9.1     POSIX fork() Routine .....................   3-13.I               3.9.2     SYS$POSIX_FORK_CONTROL System Service.....   3-14iI               3.10  Translated Image Support (Alpha Only).........   3-14 <               3.10.1    Running Translated Images on OpenVMSI                         Systems...................................   3-15 >               3.10.2    DECwindows Motif Toolkit FunctionalityI                         (Alpha Only)..............................   3-17y?               3.11  Problems Using the DECW$INCLUDE:INTRINSIC.H.I                     File..........................................   3-17 I               3.12  Compiling Applications Written in C...........   3-18 =               3.13  Compiling Applications Written in Fortran I                     (Alpha Only)..................................   3-18 I               3.14  CDA Application...............................   3-19 :               3.14.1    CDA-Implementing the Drag-and-DropI                         Feature...................................   3-19 I               3.14.2    CDA Run-Time Services Features............   3-20.I               3.14.2.1    Version Number..........................   3-20oB               3.14.2.2    Changes to the Programming Interface forI                           CDA.....................................   3-20p7               3.14.2.3    Changes to External ReferenceeI                           Processing..............................   3-21pI               3.14.2.4    Message for Style Guide Fallback........   3-22h:               3.14.2.5    Using Logical Names with CONVERTI                           Commands................................   3-22e  I                                                                        ix                    E           3.14.2.6    Restructuring Shareable Images..........   3-23 E           3.15  DECterm Programming...........................   3-24)E           3.15.1    Page-Movement Escape Sequences............   3-24 E           3.15.2    DECCRA Sequence...........................   3-24yE           3.15.3    DECLFKC Sequence..........................   3-25.E           3.15.4    ReGIS Input Cursors.......................   3-25.E           3.16  DECwindows OSF/Motif Toolkit..................   3-25iE           3.16.1    Motif Text Widget Translations............   3-26.E           3.16.2    Upward Compatibility......................   3-26.:           3.16.2.1    Restrictions on Mixing Motif and XUIE                       Widgets.................................   3-27s;           3.16.3    Compile-Time Incompatibilities in MotifeE                     Header Files..............................   3-27.E           3.17  OSF/Motif Example Programs....................   3-28tE           3.17.1    Cut and Paste Example Program.............   3-28GE           3.17.2    DNDDemo Example Program...................   3-28mE           3.17.3    Dogs Example Program......................   3-30BE           3.17.3.1    Dog Widget..............................   3-30.E           3.17.3.2    Square Widget...........................   3-31.E           3.17.4    Helloint Example Program..................   3-32 E           3.17.5    Hellomotif Example Program................   3-33 E           3.17.6    Motifanim Example Program.................   3-33tE           3.17.7    Motifgif and Pict Viewing Programs........   3-34.E           3.17.8    Motifshell Example Program................   3-34SE           3.17.9    Periodic Example Program..................   3-35.E           3.17.10   Textedit Example Program..................   3-35gE           3.17.10.1   Additional Translations.................   3-37iE           3.17.11   View Example Program......................   3-38.E           3.17.12   Xmpiano Example Program...................   3-39dE           3.17.13   Motif Sample Programs.....................   3-41tE           3.17.14   Xmtravel Example Program..................   3-43 E           3.17.15   Resource Files for Example Programs.......   3-43OE           3.17.16   UID Files for Example Programs............   3-44dE           3.18  DECwindows Extensions to Motif................   3-44DE           3.18.1    DXmCSText Input Method Support............   3-44 5           3.18.2    SVN-Horizontal Live Scrolling Not E                     Supported.................................   3-44 E           3.18.3    SVN Horizontal Separator Line.............   3-451E           3.18.4    DXmFormSpaceButtonsEqually Restriction....   3-45.E           3.19  Display Server Extensions.....................   3-45.E           3.19.1    X Image Extension.........................   3-45.E           3.19.2    Client Side Extension Library.............   3-46.           x  2                 >               3.19.3    Shared Memory Extension Support (AlphaI                         Only).....................................   3-47 I               3.19.3.1    How to Use Shared Memory Extension......   3-47.I               3.19.3.2    Using Shared Memory XImages.............   3-48.I               3.19.3.3    Using Shared Memory Pixmaps.............   3-52.I               3.19.4    Using Extension Include Files.............   3-53.I               3.20  Internationalization Enhancements.............   3-54.4               3.20.1    Using the CDA Viewer to ViewI                         Asian-Language Text.......................   3-543I               3.20.1.1    Specifying an Options File..............   3-543I               3.20.1.2    Defining Logical Names..................   3-5535               3.20.2    Converting Files That ContaineI                         Asian-Language Characters.................   3-56.I               3.21  XNL Library Issues............................   3-58bI               3.21.1    xnl_parsedatetime.........................   3-58dI               3.21.2    xnl_langinfo..............................   3-58.I               3.22  Xlib Issues...................................   3-58eI               3.22.1    Command Procedure Builds .PEN Files.......   3-58.I               3.22.2    Parameter/Protocol Datasize Mismatches....   3-59 I               3.22.3    XtAppMainLoop Routine.....................   3-59-?               3.22.4    XSelectAsyncEvent and XSelectAsyncInput I                         Routines .................................   3-60nI               3.22.5    Xlib Internationalization.................   3-60nI               3.22.5.1    Vendor Pluggable Layer..................   3-61e:               3.22.5.2    Compaq Internationalization XlibI                           Implementation..........................   3-62wI               3.22.5.3    Locale in OpenVMS Systems...............   3-62i  &         4  Documentation Release Notes  >               4.1   DECwindows Motif Version 1.2-5 for OpenVMSI                     Documentation.................................    4-1 I               4.1.1     New Desktop Documentation.................    4-3 I               4.2   DECwindows Motif Documentation Corrections....    4-3 I               4.2.1     Getting Started With the New Desktop......    4-3 I               4.2.1.1     File Specification Incorrect............    4-4.A               4.2.2     DECwindows Motif for OpenVMS Applications I                         Guide.....................................    4-4.@               4.2.2.1     Enhancing Information About the FinishI                           Printing Option.........................    4-4.          I                                                                        xi. .  .              E           4.2.3     Using DECwindows Motif for OpenVMS........    4-4.E           4.2.3.1     Using the Drag-and-Drop Feature.........    4-5 E           4.2.3.2     Tear-Off Menus..........................    4-5 5           4.2.3.3     Adding Target Screen Options to.E                       Application Menu Items..................    4-6 E           4.2.3.4     Changing the Startup Environment........    4-6 E           4.2.3.5     Enhancing Startup Performance...........    4-6 E           4.2.3.6     Enhancing Hold-Screen Response Time.....    4-7 9           4.2.4     Managing DECwindows Motif for OpenVMS E                     Systems...................................    4-7 E           4.2.4.1     Global Symbols..........................    4-7 E           4.2.4.2     Security Options........................    4-8 E           4.2.4.3     Displaying a Customized Logo............    4-8 E           4.2.4.4     Enabling and Disabling Access Control...    4-9 9           4.2.5     DECwindows Motif for OpenVMS Guide to.E                     Non-C Bindings............................    4-9.E           4.2.5.1     GET_CHAR_STRUCT Function................   4-10 <           4.2.6     VMS DECwindows Guide to Xlib (Release 4)E                     Programming: VAX Binding..................   4-10.E           4.2.7     DECwindows Extensions to Motif............   4-10.2           4.2.7.1     DXmNlayoutDirection ResourceE                       Constants...............................   4-10.9           4.2.8     DECwindows Motif Guide to Application E                     Programming...............................   4-11 5           4.2.8.1     UIL Source Code for the OpenVMSpE                       DECburger Application...................   4-11 E           4.2.8.2     Help Widget Implementation Code.........   4-11.E           4.2.8.3     Help Widget Implementation-Callbacks....   4-11nE           4.2.8.4     Using UIL to Create the Help Widget.....   4-121<           4.2.9     Overview of DECwindows Motif for OpenVMSE                     Documentation.............................   4-12rE           4.3   OSF/Motif List of Known Problems..............   4-12.  *     A  OSF/Motif Release 1.2 Release Notes  E           A.1   Performance Improvements......................    A-1.E           A.2   Backward Compatibility........................    A-2eE           A.2.1     Visual and Behavioral Compatibility.......    A-2d>           A.3   Changes and New Features for OSF/Motif ReleaseE                 1.2...........................................    A-3AE           A.3.1     General Toolkit Changes...................    A-31E           A.3.1.1     Include File Changes....................    A-3 E           A.3.2     Change in XT Translations.................    A-3          xii  g  K              I               A.3.3     ANSI C Compliance.........................    A-4.I               A.3.4     Display and Screen Specific Data..........    A-4.I               A.3.5     Drag and Drop.............................    A-4.I               A.3.6     Tear-Off Menus............................    A-5.I               A.3.7     Insensitive Visuals.......................    A-5sI               A.3.8     Other Visual Changes......................    A-6bI               A.3.9     Titles for Frames.........................    A-6.I               A.3.10    Audible Warning...........................    A-6 I               A.3.11    Color Enhancements........................    A-7 I               A.3.12    Baseline Alignment........................    A-7 I               A.3.13    Expanded Traversal Set....................    A-7 I               A.3.14    Two-Dimensional Menu Traversal............    A-7 I               A.3.15    Input Focus...............................    A-7 I               A.3.16    Traversal Access Functions................    A-8 I               A.3.17    Virtual Keys..............................    A-8 I               A.3.18    Resource Management.......................    A-9 I               A.3.19    Changes for CUA and Windows Compliance....   A-10 8               A.4   Changes and Enhancements to SpecificI                     Widgets.......................................   A-10 I               A.4.1     XmClipboard...............................   A-10 I               A.4.2     XmCommand.................................   A-11 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-12lI               A.4.7     XmScrolledWindow..........................   A-13DI               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-15dI               A.5.1     Changes to MWM............................   A-15 I               A.5.2     New and Enhanced MWM Resources............   A-15eI               A.5.3     New and Enhanced MWM Functions............   A-16lI               A.5.4     New MWM Action............................   A-17tI               A.6   Changes to the User Interface Language........   A-18.                  I                                                                      xiii     2              	     Indexc         Examples  >           2-1       Error Messages Displayed Due to Low MemoryE                     in Granularity Hints Region...............    2-5   
     Tables  E           1-1       Window Dump to Print File Options.........   1-50   E           1-2       Functional Resources......................   1-64   E           1-3       Visual Resources..........................   1-74i  E           1-4       Font Resources............................   1-75n  E           1-5       Proxy Gateway Resources...................   1-77C  E           2-1       Recommended Quotas for System Tuning......    2-8   E           2-2       Previously Optional Files Now Required....   2-12.  >           2-3       Moving the DIGITAL Logo and Changing LoginE                     Screen Colors ............................   2-17.  >           2-4       Changing Position of the Start Session andE                     Set Password Dialog Boxes.................   2-18.  E           2-5       Logical Names Supported by DECterm........   2-23g  9           3-1       Names of Shareable Libraries Based onrE                     R5........................................    3-6n  9           3-2       Names of Shareable Libraries Based onhE                     OSF/Motif Release 1.2.2...................    3-6   9           3-3       Directories for Previous XUI or Motif E                     Programming Environment...................   3-11.  E           3-4       Drag-and-Drop Widgets.....................   3-19A  E           3-5       New Header File Names.....................   3-21e  E           3-6       Names of Shareable Images.................   3-23   9           3-7       ReGIS Input Cursors-Cursor styles andgE                     Values....................................   3-25f  E           3-8       View Menu Options.........................   3-35t  E           3-9       Textedit Source Files.....................   3-36.  E           3-10      Motif Sample Programs.....................   3-42v  E           3-11      Asian Language Codes for Options Files....   3-55r  5           3-12      Logical Names for Specifying TextAE                     Encoding..................................   3-56V  E           3-13      Languages and Associated Basic Fonts......   3-57o       xivt l  .              B               3-14      Routine Names and Arguments Sent as 16-BitI                         Values....................................   3-59e  4               4-1       DECwindows Motif for OpenVMSI                         Documentation.............................    4-1.                                                                                I                                                                        xva n  u                        I         _________________________________________________________________.  I                                                                   Prefacep      D               The DECwindows Motif Version 1.2-5 for OpenVMS productI               incorporates the Common Desktop Environment (CDE) Motif 1.0YI               Toolkit (OSF/Motif Release 1.2.5) and is based on Release 5lI               of the X Window System Intrinsics. As with DECwindows MotifuI               Version 1.2 and Version 1.2-4 for OpenVMS, DECwindows Motif.E               Version 1.2-5 for OpenVMS continues to provide run-timeMI               support for the XUI user interface and Toolkit. Application.E               development is supported for the CDE Motif 1.0 Toolkit.$  C               On Alpha systems, the New Desktop is derived from the.B               Common Desktop Environment (CDE). The user interfaceB               that was provided in previous versions of DECwindowsE               Motif is now referred to as the DECwindows desktop. The.F               system manager can install either the New Desktop or theD               DECwindows desktop, or both. In addition, the user canC               select which desktop is started during the DECwindows.                startup procedure.  F               In this manual, DECwindows XUI (X User Interface) refersI               to the DECwindows product prior to DECwindows Motif Versiono               1.0.  A               These release notes describe new features, software D               problems, corrections, restrictions, and documentationC               changes that pertain specifically to DECwindows Motif D               Version 1.2-5 for OpenVMS software. They also describe?               software problems, corrections, restrictions, and B               documentation changes from previous DECwindows MotifA               releases that have not been updated in the existing E               documentation for those products. Margin notes indicate H               the first version of the DECwindows Motif product to which(               each release note applies.    I                                                                        xi  a  S                   Intended Audience   E           This manual contains information for system managers, users @           and programmers who use the DECwindows Motif software.       Document Structure  9           This manual contains the following information:w  B           o  Chapter 1 contains general user release notes for all              users.r  A           o  Chapter 2 contains release notes intended for systemi              managers.  :           o  Chapter 3 contains release notes intended for0              application and system programmers.  A           o  Chapter 4 describes additions and corrections to thea              documentation set.   B           o  Appendix A contains a subset of the release notes for%              OSF/Motif Release 1.2.3..       Related Documents   A           For additional information on the Open Systems Software B           Group (OSSG) products and services, access the following)           OpenVMS World Wide Web address:.  (           http://www.openvms.digital.com       Reader's Comments.  7           Compaq welcomes your comments on this manual.e  <           Print or edit the online form SYS$HELP:OPENVMSDOC_4           COMMENTS.TXT and send us your comments by:  0           Internet    openvmsdoc@zko.mts.dec.com  B           Fax         603 884-0120, Attention: OSSG Documentation,                        ZKO3-4/U08  1           Mail        Compaq Computer Corporation3:                       OSSG Documentation Group, ZKO3-4/U08(                       110 Spit Brook Rd.+                       Nashua, NH 03062-2698        xii. 1                 -         How To Order Additional Documentation   ?               Use the following World Wide Web address to order '               additional documentation:.  0               http://www.openvms.digital.com:81/  F               If you need help deciding which documentation best meets:               your needs, call 800-DIGITAL (800-344-4825).           Conventionsr  I               In this manual, any reference to OpenVMS is synonymous withP               Compaq OpenVMS.   G               VMScluster systems are now referred to as OpenVMS Cluster.H               systems. Unless otherwise specified, references to OpenVMSG               Clusters or clusters in this document are synonymous with2               VMSclusters.  D               In this manual, every use of DECwindows and DECwindowsD               Motif refers to DECwindows Motif for OpenVMS software.  E               The following conventions are also 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.   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.              I                                                                      xiii  w  t                8            . . .           Horizontal ellipsis points inA                            examples indicate one of the following.)                            possibilities:   @                            o  Additional optional arguments in a:                               statement have been omitted.  @                            o  The preceding item or items can be9                               repeated one or more times.b  E                            o  Additional parameters, values, or other59                               information can be entered..  @           .                Vertical ellipsis points indicate the@           .                omission of items from a code exampleC           .                or command format; the items are omittede@                            because they are not important to the1                            topic being discussed.-  :           ( )              In command format descriptions,E                            parentheses indicate that you must enclose.C                            the choices in parentheses if you choose.)                            more than one.e  C           [ ]              In command format descriptions, brackets >                            indicate optional elements. You canC                            choose one, none, or all of the options.3B                            (Brackets are not optional, however, in?                            the syntax of a directory name in anf?                            OpenVMS file specification or in the.A                            syntax of a substring specification ine4                            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.           xiv. .  .                =               text style       This text style represents the E                                introduction of a new term or the namenI                                of an argument, an attribute, or a reason.   I                                In the HTML version of this document, thisn@                                convention appears as italic tex.  ?               italic text      Italic text emphasizes importantIH                                information and indicates complete titlesB                                of manuals and variables. VariablesH                                include information that varies in systemC                                messages (Internal error number), inwE                                command lines (/PRODUCER=name), and in.C                                command parameters in text (where dd.E                                represents the predefined code for the.,                                device type).  F               UPPERCASE TEXT   Uppercase text indicates a command, theH                                name of a routine, the name of a file, orG                                the abbreviation for a system privilege..  I                                Monospace type indicates code examples andn;               Monospace type   interactive screen displays.G  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.1  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                                                                        xvm i  i                    I                                                                         1.I         _________________________________________________________________   I                                                General User Release Notes     F               This chapter contains information about DECwindows Motif                for general users.  I         1.1 General User Release Notes Specific to the New Desktop (Alpha.             Only)   F               This section contains release notes for DECwindows Motif<               Version 1.2-5 for OpenVMS and the New Desktop.  ,         1.1.1 dximageview TIF Error Messages  I         V1.2- When using dximageview to view TIF formatted files from the-H         4     CDE$SYSTEM_DEFAULTS:[APPCONFIG.HELP.C.GRAPHICS] directory,  ;               the following warning messages are displayed:.  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.   7         1.1.2 Text Editor Supports Standalone Mode Only-  <         V1.2- The reference page for Text Editor describes aC         4     client/server implementation of the Text Editor. This.  C               release of the Text Editor supports the -"standAlone"s=               option only and is not built as a client/server.               application.  9         1.1.3 Text Editor Does Not Support Spell Checking.  C         V1.2- The Text Editor application, which is part of the NewdG         4     Desktop, is described in Chapter 10 of the Common Desktopt  D               Environment: User's Guide. The spell-checking functionG               described in the section "To Correct Misspelled Words" is.A               not implemented in this version of the Text Editor..  I                                                                       1-1. .  .           General User Release NotesK     1.1 General User Release Notes Specific to the New Desktop (Alpha Only)     B     1.1.4 Tab Size Within the Text Editor Is Not 8 Characters Wide  @     V1.2- The Text Widget upon which the New Desktop Text Editor@     4     is based does not set the size of a tab to exactly the  D           width of 8 characters; it is usually slightly larger. WhenE           displaying text with a combination of spaces and tabs, textA,           may not appear vertically aligned.  /     1.1.5 Some File Names Appear in UNIX Format.  A     V1.2- In the Application Manager Find dialog box and in error >     4     messages reported by the Help Viewer, file names are  B           displayed in UNIX format rather than in standard OpenVMSD           format. For example, SYS$SYSROOT:[SYSMGR]LOGIN.COM appears+           as /sys$sysroot/sysmgr/login.com.   ?     1.1.6 DECwindows Interface for the TPU Editor Does Not Save            Itself  D     V1.2- Users will experience a 1-minute delay for each DECwindowsC     4     Text Processing utility window displayed when exiting the   0           session or when saving a home session.  @           The DECwindows interface for TPU (EVE editor) requiresB           notification if its state needs to be saved, but it doesC           not respond to that notification sent by Session Manager. >           The New Desktop Session Manager waits 1 minute for a=           response before continuing, resulting in the delay..       1.1.7 Front Panel Clock   D     V1.2- The New Desktop Front Panel Clock is an animated icon thatC     4     displays the current system time using an analog display.n  E           The icon has no other function and does not support single-C+           click or double-click operations.r  (     1.1.8 Using MB3 on Front Panel Icons  C     V1.2- The New Desktop Front Panel supports mouse button 3 (MB3) B     4     operations. When the cursor is placed over a Front Panel  C           icon and you press MB3, a subpanel, or menu, appears. The-$           menu items are as follows:  ,           o  Top item-The label of the menu.  ;           o  Second item-The application that starts if youi@              singleclick on the icon. Caution: If the third itemC              is "Delete Subpanel", this change is difficult to undo.*              without reinstalling the kit.       1-2  -         I                                                General User Release Notes I   1.1 General User Release Notes Specific to the New Desktop (Alpha Only)v    I               o  Third item-"Add Subpanel" If a subpanel does not already.-                  exist for the control panel.   5         1.1.9 Selecting Screens on Application Launch   G         V1.2- A new feature allows you to graphically select the screen C         5     on which a new application is displayed when launched   C               from either the Front Panel, the File Manager, or the.B               Application Manager. By default, the new application@               appears on the current screen (that is, the screenC               containing the mouse pointer). The new feature allows C               you to drop an application icon from the File Manager D               or Application Manager onto one of the numbered screenH               controls of the Set Default Screen window. This starts theE               application on the selected screen without changing the                current screen.c  E               The Set Default Screen window is activated as before by4C               selecting the "Set Default Screen" application in the G               Application Manager's Desktop Tools folder. You can start-E               a separate instance of the Set Default Screen window ontD               each screen. The highlighting of the default screen isI               synchronized across all instances of the Set Default Screen                window.   !         1.1.10 Detached Processes   D         V1.2- When you start an application (from the Front Panel orG         4     dtfile), a new detached process is created with a process   E               name constructed from the user name, $CDE, and a three-r'               digit numeric identifier.   I               For example, user SMITH starts an application whose process H               name is SMITH$CDE001. The next assigned process name wouldI               be SMITH$CDE002, unless SMITH$CDE001 has already terminated )               and is available for reuse.M  -         1.1.11 ToolTalk Actions Not Supported   C         V1.2- Creation of ToolTalk Action definitions in the ActionhH         4     Definition files (*.dt) as described in the Common Desktop  E               Environment: Advanced User's and System Administrator'ssC               Guide is not supported in this release. Although sometC               ToolTalk actions exist in the Action Definition filesiH               installed with this product, modification of these actionsI               is not supported and could cause some New Desktop functionsa               to fail.  I                                                                       1-3n                General User Release NotesK     1.1 General User Release Notes Specific to the New Desktop (Alpha Only)n    3     1.1.12 Session Manager Save/Restore Limitations   ;     V1.2- The Session Manager supplied with the New Desktop B     4     supports the WM_SAVE_YOURSELF protocol for the following  E           DECwindows applications: Bookreader, DECterm, and Calendar.rB           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.  @           The New Desktop applications support save/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 noth#              automatically restart.o  E           An example of an existing DECwindows Motif application thati3           supports save/restore is DECwindows Mail.r  9     1.1.13 Limitations of dtfile (New Desktop-Alpha Only)a  ?     V1.2- The dtfile application has the following limitations:n?     4     o  If you specify a folder (directory) name, which isf  E              strictly a logical name, and the logical name translatestC              to a search list, only the first directory encounteredn-              in the search list is displayed.s  @              For example, the SYS$SYSTEM logical represents both>              SYS$SPECIFIC:[SYSEXE] and SYS$COMMON:[SYSEXE]. If=              you present a view of SYS$SYSTEM, only the filesp>              in SYS$SPECIFIC:[SYSEXE] display. This is becauseB              SYS$SPECIFIC:[SYSEXE] precedes SYS$COMMON:[SYSEXE] in              the search list.   >           o  When displaying a directory whose name includes a@              search-listed device, all directories in the searchD              path are displayed. If more than one directory with theA              same name exists in the search path, an icon appearsoB              for each instance of that directory. If more than one       1-4  o  q      I                                                General User Release Notes8I   1.1 General User Release Notes Specific to the New Desktop (Alpha Only)H    G                  file with the same name exists in the search path, theaF                  behavior depends on whether the Show Top Version OnlyG                  filter option has been selected. If selected, only onetH                  icon of the file with the highest version is displayed.E                  If not selected, all versions from all locations areGF                  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.e  =                  For example, suppose the files SYS$SPECIFIC: G                  [SYSMGR]TOOLS.DIR;1 and SYS$COMMON:[SYSMGR]TOOLS.DIR;1.B                  both exist in a system. If a user switches to theD                  directory SYS$SYSROOT:[SYSMGR], two icons representF                  the file TOOLS.DIR. Operations performed on either ofF                  the two icons work identically. New files are createdH                  in the first directory in the search path. In addition,D                  some actions for these icons may not work properly.  >                  To work around this problem, specify explicitE                  directory names when a conflict occurs, for example, >                  SYS$SPECIFIC:[SYSMGR] or SYS$COMMON:[SYSMGR].  1         1.1.14 Login and Pause Screen Text Fieldsx  H         V1.2- The following sections provide information about the Login2         4     Screen and Pause Screen text fields.  I         1.1.14.1 Control Characters Not Recognized When Entering Usernameb  ?               The New Desktop does not support entering control F               characters in the login Username text field. If entered,C               these characters are discarded. This differs from thenF               DECwindows login Username text field which supports such               key sequences as:   D               o  Ctrl/U, Ctrl/J, or F13 (deletes to beginning of the                  line)  G               o  Ctrl/H or F11 (positions to the beginning of the line)   :               o  Ctrl/E (positions at the end of the line)  I               The New Desktop does support Ctrl/U, which when typed while H               entering a password at login or when unpausing the screen,=               erases any characters entered up to that point.V  I                                                                       1-5i s  o           General User Release NotesK     1.1 General User Release Notes Specific to the New Desktop (Alpha Only)b    >     1.1.14.2 Return Key Used to Move Between Login Text Fields  E     V1.2- Because the Username text field and Password text field arerE     4     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     1.1.14.3 First Character Discarded When Entering Pause Screen,              Password3  B     V1.2- If the workstation is paused and the Password dialog boxA     4     is not displayed, the first character typed is ignored.   E           This differs from the DECwindows pause screen, which always '           accepts any characters typed.e  B           When using the New Desktop, use a nontyping key, such asD           Shift, or move the mouse to redisplay the Pause dialog boxB           before entering your password. If you are unsure of whatA           you have already typed, you can use Ctrl/U to erase the            Password text field.  6     1.1.14.4 Text On The Welcome Screen May Not Appear  A     V1.2- If the 100-dpi fonts are not included in the X server'scB     4     font path, the welcome text is not displayed on the blue  C           welcome screen that appears immediately after logging in. E           This may also occur if you are displaying your session on a            remote X server.  8     1.1.15 Use SET DISPLAY/CREATE Within DECterm Windows  ?     V1.2- From a privileged account, if you use the SET DISPLAY B     4     command from within a DECterm window without the /CREATE  D           qualifier, it changes the display used for any application@           created from that point forward. It also redefines theC           display on which the login box appears after logging out.   C           Always use the /CREATE qualifier when setting the display A           from a DECterm if you have not set the display already.        1-6            I                                                General User Release NoteslI   1.1 General User Release Notes Specific to the New Desktop (Alpha Only)m    &         1.1.16 Viewing Reference Pages  E         V1.2- This release of DECwindows contains a new collection of C         4     help files for the New Desktop called reference pagest  D               (also known as man pages). Reference pages are dividedI               into sections and, on OpenVMS, the file extension indicatestH               the section. Sections distributed with the release include               the following:  I               ___________________________________________________________ I               Section_Purpose_____________Extension______________________   4               1       Applications        filename.1  4               3       Libraries/programminfilename.3  4               4       Programming         filename.4  4               5       Include file        filename.5I               ________formats____________________________________________r  >               A version of dthelpview has been set up with theD               appropriate action definition for manpage viewing. TheF               process logical MANPATH has been defined to point to theF               CDE$SYSTEM_DEFAULTS:[MAN] directory that contains all of'               the reference page files.   B               You can use either of the following methods to start5               dthelpview and display reference pages:e                 Method 1  H               To start dthelpview from DECterm and view a reference page                called dtaction.1:  @               1. At the DCL level or in a LOGIN.COM file, define@                  dthelpview as a foreign command by entering the                  following:   #                  $ dthelpview :== - Z                  _"$ sys$sysdevice:[sys0.syscommon.cde$defaults.system.bin]dthelpview.exe"  )               2. At the DCL level, enter:   3                  $ dthelpview -"manPage" dtaction.1e  I                                                                       1-7o M  f           General User Release NotesK     1.1 General User Release Notes Specific to the New Desktop (Alpha Only)                Method 2  C           To start dthelpview from Application Manager and view the +           reference page called dtaction.1:e  '           1. Start Application Manager.   D           2. Double click on the Man Page Viewer icon located in theB              Desktop Apps application group. A dialog box appears.  C           3. Enter the reference page to be viewed and click on OK.g  %     1.1.17 Font Selection Limitationsp  C     V1.2- On the New Desktop, Style Manager contains a control that C     4     displays a dialog box used to select font size. Selecting.  C           a new font size affects only New Desktop applications and A           does not affect existing DECwindows Motif applications.   (     1.1.18 Default Workspace Limitations  =     V1.2- The New Desktop provides a default backdrop for the @     4     four default workspaces. You can change or even select  @           Nobackdrop using the Backdrop control located in Style           Manager.  A           When no backdrop is selected, you cannot drag icons andx@           place them on the backdrop of the desktop. If you dragB           an icon and release it, it snaps back to File Manager or           Application Manager.  E           Icons that were dropped on the background before Nobackdropi5           was selected remain and function correctly.i  8     1.1.19 Alt + Space Key Does Not Post the Window Menu  C     V1.2- The New Desktop maps the key binding Alt+space key to thec@     4     Compose Character function by default. This provides a  @           method for character composition on keyboards which doB           not supply a specific Compose Character key. To use this&           feature, follow these steps:  @           1. Copy CDE$SYSTEM_DEFAULTS:[CONFIG.lang]SYS.DTWMRC to(              DISK$:[LOGIN.DT]DTWMRC.DAT.  =           2. In the Keys DtKeyBindings section, uncomment thet              following line:  7              Alt<Key>space   icon|window   f.post_wmenuo  +           3. Restart the Workspace Manager.c       1-8i s  u      I                                                General User Release NotessI   1.1 General User Release Notes Specific to the New Desktop (Alpha Only)     ;         1.1.20 DECwrite Icon Does Not Open DECwrite Programa  H         V1.2- DECwindows does not include the DECwrite program. However,B         5     DECwindows does include the DECwrite icon on the New  F               Desktop. If the DECwrite product has not been installed,D               clicking on the DECwrite icon results in the following               error messages:t  P               > RCV'D (pid 000000CA): %DCL-W-IVVERB, unrecognized command verb -B                                        check validity and spelling2               -> RCV'D (pid 000000CA):  \DECWRITE\C               -> RCV'D (pid 000000CA):   TESTER       logged out atw%               29-JUL-1998 17:56:44.63e  D               If the DECwrite product is installed and you still getG               this error, ensure that DECwrite is started in SYSTARTUP_                VMS.COM.  F         1.2 DECwindows Support of OpenVMS Extended File Specifications             (EFS)e  E         V1.2- In general, DECwindows Motif supports the Extended FilenC         5     Specifications (EFS) option provided in OpenVMS Alphat  F               Version 7.2. The interface either supports the new ODS-5I               file names or provides an error message indicating that therB               particular component does not support the new names.  &         1.2.1 The File Selection Popup  C         V1.2- The standard file selection popup window used by mostFF         5     DECwindows Motif applications fully supports ODS-5 style  D               file names. The window supports deep directories, caseF               preservation, and extended-length file names. The windowG               supports entry of file names using the extended file namehG               character and displays files using the extended file nameuG               character set using the circumflex character (^). See the D               OpenVMS Guide to Extended File Specifications for moreG               specific information about using deep directories and theh/               extended file name character set.b      I                                                                       1-9n                General User Release NotesH     1.2 DECwindows Support of OpenVMS Extended File Specifications (EFS)    @     1.2.2 The FileView Application in the Traditional DECwindows           Desktop   A     V1.2- With an ODS-5 volume, the FileView application supports.B     5     deep directories, case preservation, and extended-length  A           file names. FileView supports entry of file names using C           the extended file name character and displays files using C           the extended file name character set using the circumflex ?           character (^). See the OpenVMS Guide to Extended FilenB           Specifications for more specific information about usingD           deep directories and the extended file name character set.  D           Any custom FileView command extensions must be modified to           support EFS.  9     1.2.3 The File Manager Application in the New DesktopS  A     V1.2- The FileManager application supports case preservation.o<     5     The FileManager application creates files with the  @           extended file name character set, but does not support&           any operations on its files.  C           The FileManager application supports deep directories andSD           extended-length file names with the following restriction.<           As indicated in the OpenVMS Guide to Extended FileB           Specifications, ODS-5 volumes allow file names up to 236B           8-bit characters in length and deep directory structures@           if the total file specification does not exceed 512 8->           bit characters in length. The current version of theC           File Manager supports extended-length file names and deepcE           directory structures with the additional restriction that aaE           total file specification cannot exceed 235 8-bit characters E           in length. Exceeding this limit causes an error message foro           some menu items.  =     1.2.3.1 File Manager Problems with EFS (New Desktop Only)i  B           o  In File Manager (New Desktop), the "Selected/Move to"D              menu item does not support case preservation. The files<              are moved correctly, but case is not preserved.  =           o  The File Manager currently does not support caseiA              preservation when you create file names that containoC              special characters. For example, "Special^&Characters"i;              will be converted to "SPECIAL^&CHARACTERS.;1".        1-10 -         I                                                General User Release NotesSI      1.2 DECwindows Support of OpenVMS Extended File Specifications (EFS)v    F               o  In File Manager (New Desktop), the "Selected/Copy to"H                  menu item does not support case preservation. The filesA                  are copied correctly, but case is not preserved.   D               o  In File Manager (New Desktop), the "Selected/Put inG                  Trash" menu item does not work on ODS-5 volumes markednE                  for EFS (Extended File Specifications). This appliesrC                  only to folders with extended file names. An erroro?                  message similar to the following is displayed:p  (                  File Manipulation Error  X                  Cannot create "sys$sysroot:[sysmgr.dt.trash]qwertyuiopasdfghjklzxcvbnm-:                    QWERTYUIOPASDFGHJKLZXCVBNM.LONG_NAME;1">                  The most common cause is that you do not have9                  the correct permissions for the involved "                  files or folders.;                  To view permissions, select the object and =                  then select "Change Permissions..." from thes(                  Selected or popup menu.  =                  These files can be deleted at the DCL level.e  I               o  In File Manager (New Desktop), dragging a file or folderlD                  with an extended file name to Trash causes an errorC                  message. On an ODS-2 volume you can drag a file orhD                  folder with a short file name to Trash and still beD                  able to restore it. On an ODS-5 volume you can dragE                  a file or folder with a short name to Trash, but you I                  cannot restore even files with short names from an ODS-5IE                  volume. These files can be deleted at the DCL level.e  E               o  In File Manager (New Desktop), the "File/New Folder"iC                  menu item can handle the creation of a folder whenYG                  the path length exceeds 255 characters, but the folder G                  cannot be displayed (it is hidden). These files can bed)                  viewed at the DCL level.   I               o  In File Manager (New Desktop), the "File/Find/File" menusH                  item cannot find a file with file name that exceeds 235I                  characters if the full file name has been entered in the I                  dialog's form field. To avoid the problem, use wildcards '                  to conduct the search.o    I                                                                      1-11i    t           General User Release NotesH     1.2 DECwindows Support of OpenVMS Extended File Specifications (EFS)    @           o  In File Manager (New Desktop), the "Selected/ChangeD              Permissions" menu item does not work on files with fileC              names that exceed 235 characters. Permission cannot be 3              changed on files with long file names.f  B           o  In File Manager (New Desktop), the "Selected/Copy to"B              menu item causes an error with file names that exceedD              235 characters. The operation produces an error messageA              instructing the user to change the permission on the @              file in order to copy it. However, it does not workE              because permissions cannot be changed on files with long               file names.  E           o  In File Manager (New Desktop), the "Selected/Purge" menu.D              item does not work for long file names on ODS-5 volumesC              marked for EFS (Extended File Specifications). "Short"sE              file names do not present this problem. An error similari+              to the following is displayed:   $              File Manipulation Error  T              Cannot create "sys$sysroot:[sysmgr.dt.trash]qwertyuiopasdfghjklzxcvbnm-6                QWERTYUIOPASDFGHJKLZXCVBNM.LONG_NAME;1":              The most common cause is that you do not have5              the correct permissions for the involvede              files or folders.7              To view permissions, select the object and 9              then select "Change Permissions..." from theU$              Selected or popup menu.  D              These files with long file names can still be purged at              the DCL level.   6           o  In File Manager (New Desktop) the updated@              protection settings are not displayed when invokingA              "Fileview/Command/Protection," although the settings B              have actually been updated. However, the new settings?              can be verified by either issuing a DCL command or 3              invoking "Fileview/Command/Show File."r  #     1.2.4 The Programming Libraries   B     V1.2- The programming libraries fully support deep directories>     5     and extended-length file names. The libraries do not  =           support case preservation or the extended file namet           character set.       1-12           I                                                General User Release NoteslI      1.2 DECwindows Support of OpenVMS Extended File Specifications (EFS)(    E         1.2.5 The Translated Image Support (TIS) Library (Alpha Only)i  E         V1.2- The translated image support (TIS) library has not been %         5     updated to support EFS.i  E         1.3 Alt + Space Key Does Not Post the Window Menu (DECwindowsf             Desktop Only)   I         V1.2- OpenVMS DECwindows Motif maps the key binding Alt+space key I         4     to the Compose Character function by default. This provides   F               a method for character composition on keyboards which doF               not supply a specific Compose Character key. To use this*               feature, follow these steps:  H               1. Copy DECW$SYSTEM_DEFAULTS:DECW$MWM_RC.DAT to DECW$USER_*                  DEFAULTS:DECW$MWM_RC.DAT.  G               2. In the Keys DtKeyBindings section, uncomment the line:g  ;                  Alt<Key>space   icon|window   f.post_wmenu,  ,               3. Restart the Window Manager.           1.4 Using Drag and Dropr  B         V1.2  All DECwindows Motif for OpenVMS applications exceptH               Notepad support the drag-and-drop feature. DECwindows MailF               supports the drag-and-drop feature in all windows exceptF               the main message area, where DECwindows Mail has its ownI               drag-and-drop; you can use MB2 to move messages around witha                the SVN interface.  D               The drag-and-drop feature lets you move or copy screenI               objects; this feature is provided primarily for programmersh@               who choose to incorporate drag-and-drop into theirF               applications. For example, you can move text from a text0               entry area and paste it elsewhere.  8               To drag and drop text into a new location:  @               1. Select the text to be copied or moved with MB1.  H               2. To move the text, press and hold MB2; to copy the text,                  press and hold                   Ctrl/MB2.  2                  A move or copy icon is displayed.  I               3. Drag the icon to the location where you want to drop theU+                  text and release Ctrl/MB2.e  I                                                                      1-13R r  e           General User Release Notes     1.4 Using Drag and Dropo    E              If the object is highlighted as you drag the icon across :              it, you can drop the text into that location.       1.5 Using Tear-Off Menus  C     V1.2- The following applications do not support tear-off menus:      3     o  CDA Viewern             o  Notepad             o  Print Screen   D           Refer to Section 4.2.3.2 for instructions on tearing off a+           menu and closing a tear-off menu.u  8     1.6 Access Control Not Explicitly Enabled by Default  E     V1.0  DECwindows Motif does not enable access control by default.iE           Instead, the product uses access control set by the server. E           The DECwindows X11 display server enables access control at            startup time.t  >           To force the DECwindows Session Manager to enable orB           disable access control explicitly at login time, you can4           define one of the following logical names:  D           $ DEFINE/SYSTEM/EXECUTIVE DECW$LOGIN_ACCESS_CONTROL ENABLE  E           $ DEFINE/SYSTEM/EXECUTIVE DECW$LOGIN_ACCESS_CONTROL DISABLE   @           If the logical name is not defined or if it is definedA           to some other value, such as "SERVER", DECwindows logind6           neither enables nor disables access control.  A           In most cases, it should not be necessary to define thee           logical name.a  (     1.7 Color Customizer Example Program  <     V1.2  The color customizer example program allows you to<           dynamically control the colors of your workstationB           environment. Window, icon, and window manager colors canE           be changed individually or as part of a palette switch. You C           can control mapping between resources and color cells, asvA           well as the size and contents of the palette set. Also, ?           automatic shadowing with the standard Motif shadowings"           algorithms is supported.       1-14 s  e      I                                                General User Release NotesaI                                      1.7 Color Customizer Example Programa              1.7.1 Supported Displays  I         V1.2  The color customizer supports any display using pseudocolorwE               or grayscale visuals. This includes most 4- and 8-planed#               workstation displays.t  $         1.7.2 Supported Applications  ?         V1.2  The color customizer can affect the colors of any F               applications that use the current release of the DIGITALD               X Toolkit Library. Applications from other vendors andD               previous versions of the DIGITAL X Toolkit Library are               unaffected.C  F                 ________________________ Note ________________________  >                 If the color customizer is used to control the@                 colors of applications that have their own color<                 customization dialog boxes (like the SessionD                 Manager, Window Manager, and DECwindows Mail), thoseE                 application-specific color customization dialog boxeseF                 may not reflect the correct current color values whileB                 the customizer is running the application. This isF                 normal; use the customizer instead of the application-A                 specific dialog box to change these color values.D  F                 ______________________________________________________  >         1.7.3 Building the Color Customizer on OpenVMS Systems  G         V1.2  To build the color customizer on OpenVMS systems, perform "               the following steps:  D               1. Copy the files to a private directory. For example:  (                  $ SET DEFAULT SYS$LOGIN1                  $ CREATE/DIRECTORY [.CUSTOMIZER] ,                  $ SET DEFAULT [.CUSTOMIZER]1                  $ COPY DECW$EXAMPLES:CUSTOM.C []t3                  $ COPY DECW$EXAMPLES:CUSTOM.UIL []y8                  $ COPY DECW$EXAMPLES:CUSTOMIMAGE.DAT []8                  $ COPY DECW$EXAMPLES:XSETROOT_CUST.C []=                  $ COPY DECW$EXAMPLES:BUILD_CUSTOMIZER.COM []   B               2. Build the customizer using the following command:  (                  $ @BUILD_CUSTOMIZER.COM  I                                                                      1-15d h  E           General User Release Notes(     1.7 Color Customizer Example Program    D           This command procedure creates the following output files:                CUSTOM.UID               CUSTOM.EXEi              XSETROOT_CUST.EXE  &     1.7.4 Running the Color Customizer  C     V1.2  To run the color customizer, perform the following steps:   A           1. Copy the files CUSTOM.UID and CUSTOM.EXE, which were B              created during the customizer build, to the directoryA              where the customizer will be run. A typical location9C              is the directory SYS$LOGIN or the directory DECW$USER_s              DEFAULTS.  C           2. Copy the files CUSTOM.DAT and DXMDEFAULTS.DAT from theP@              directory DECW$EXAMPLES to the same location as youC              copied the files in step 1. The same typical locations2              apply.o  ;           3. Run the executable file CUSTOM.EXE as follows:o                $ RUN CUSTOMp  C              ________________________ Note ________________________s  >              Only the colors of applications invoked after theA              customizer starts will be affected. For this reason,oC              start the customizer as the first X application during               the login process.e  C              ______________________________________________________i  +     1.7.5 Modifying the DECW$LOGIN.COM File   C     V1.2  As noted in Section 1.7.4, the color customizer should be C           the first X application started during the login process. @           Do this by starting it as a subprocess from within theE           DECW$LOGIN.COM file. Add a command to wait approximately 10 E           seconds between customizer startup and the startup of other            applications.u  D           For example, add the following lines to the DECW$LOGIN.COM           file:i       1-16 r         I                                                General User Release Notes I                                      1.7 Color Customizer Example Program     .               $! Starting the color customizer3               $ DISPLAY = F$LOGICAL("DECW$DISPLAY") F               $ SPAWN/NOWAIT/OUTPUT='DISPLAY' RUN SYS$LOGIN:CUSTOM.EXE               $ WAIT 0:0:10i  A               See Using DECwindows Motif for OpenVMS and ManagingpG               DECwindows Motif for OpenVMS Systems for more informationm)               on the file DECW$LOGIN.COM.s  '         1.7.6 Command Interface Summarya  E         V1.2  A box containing a list of available palettes is in therG               leftmost section of the Color Customizer window. Click one@               the desired palette to see the colors take affect.  C               Below the palettes are two arrays of colored buttons,nD               representing the dynamically allocated color cells forF               normal and shadow colors. To find out what resources areG               affected by a color cell, click and hold the arrow buttono%               next to the color cell.   F                 ________________________ Hint ________________________  D                 As a shortcut, you can click on the screen facsimileA                 in the rightmost corner of the dialog box. If theeF                 portion you click on is colored by one of the resourceF                 values controlled by the customizer, the pop-up window>                 for the appropriate color button is displayed.  F                 ______________________________________________________  G               To modify a single color cell, click on the corresponding D               color button. A colormix widget pops up; as you modifyB               the color, these modifications are reflected in yourD               workstation environment. Use the colormix widget resetI               button to return to the starting color at any time. You can F               also change the color cell you are modifying by clickingF               on a different color button while the colormix widget is               displayed.  E               The automatic shadowing option causes shadow and select I               colors to be automatically updated when their correspondingcI               background colors are changed. The standard Motif shadowingn9               algorithms are used for these calculations.y  I                                                                      1-17p    e           General User Release Notes(     1.7 Color Customizer Example Program    E           Use the File menu to modify, add, and delete color palettesG           as follows:e  ?           o  To modify an existing palette, select the palette,i@              change the colors, and choose Save Palette from the              File menu.   E           o  To add a new palette, select an existing palette, modify C              the colors as necessary, and choose Save Palette As... B              from the File menu. A message box prompts you for the%              name of the new palette.t  ?           o  To delete a palette, select the palette and chooseF/              Delete Palette from the File menu.   E           Changes made through the File menu automatically update them@           CUSTOM.DAT file, which contains the resource defaults.  E           The File menu Exit button causes the customizer applicationsA           to exit. A warning dialog is displayed first. Note thatTB           the color cells allocated by the customizer (and used byB           the currently running applications) will be deallocated.D           After the customizer exits, if the colors of the currently@           running applications are not correct, the applications@           should be restarted to restore normal colors. Usually,>           there is no need to exit the color customizer; it is?           typically kept running at all times, like the Sessione           Manager.  @     1.7.7 Changing the Mapping Between Color Resources and Color           Cellsr  A     V1.2  The file DXMDEFAULTS.DAT allows you to control how manyoB           dynamic color cells are allocated and what resources areC           affected. This file contains resource specifications like            the following:  7           *background:       DXmDynamicWindowBackground 7           *foreground:       DXmDynamicWindowForegrounda6           *topShadowColor:   DXmDynamicWindowTopShadow  E           When the customizer is started, the file DXMDEFAULTS.DAT is)C           written to a property on the root window. Any applicationr>           that is subsequently run and that uses the correct X@           Toolkit Library merges these resources with its normalA           resource database. Resource specifications in this file =           take precedence over specifications with equivalentk9           resource names in other resource default files.n       1-18 w         I                                                General User Release Notes I                                      1.7 Color Customizer Example Programo    A               The resource values within the file DXMDEFAULTS.DAT C               have a special format. For each unique color value iniC               this file that begins with the string "DXmDynamic", apA               color button is created in the color customizer. If E               the string "Shadow" is encountered in a name, the coloriC               button is placed in the shadow button box rather thansB               the normal color button box. If a color value string@               ends with the suffix "Background", it is linked toD               any color buttons with identical prefixes and suffixesB               of "TopShadow", "BottomShadow", or "SelectColor" forE               purposes of automatic shadowing. If a color value nameduI               "DXmDynamicScreenBackground" is encountered, the color cell.H               allocated is used by the customizer to set the root window               background color.   H               You can edit the file DXMDEFAULTS.DAT and define resourcesH               to use the same color cells. You can have separate dynamicG               color cells, for scrollbar widgets or for your DECwindowsSD               Mail application, for example, by adding the following0               lines to the file DXMDEFAULTS.DAT:  A               Mail*background:         DXmDynamicMyMailBackgroundrA               Mail*foreground:         DXmDynamicMyMailForeground @               Mail*topShadowColor:     DXmDynamicMyMailTopShadowC               Mail*bottomShadowColor:  DXmDynamicMyMailBottomShadowt  G               Adding the previous lines to the file DXMDEFAULTS.DAT and F               restarting the customizer causes four new color cells toH               be allocated and four new color buttons to be added to theF               customizer interface. These buttons are assigned defaultE               color values (usually black or white) for each palette.)B               These defaults can then be modified for each palette/               through the customizer interface.t  F                 ________________________ Note ________________________  @                 The text of the DXMDEFAULTS.DAT file is read andE                 parsed by the color customizer. The parsing algorithm.>                 does not allow comments, incorrect spacing, or?                 incorrect resource specifications. If this filex?                 or the CUSTOM.DAT resource file become corrupt,rA                 the customizer cannot start correctly. To resolve @                 the problem, copy the versions of CUSTOM.DAT and    I                                                                      1-19S t  e           General User Release Notes(     1.7 Color Customizer Example Program    B              DXMDEFAULTS.DAT from the DECW$EXAMPLES directory into"              your login directory.  C              ______________________________________________________P  &     1.7.8 DECterm Windows Not Affected  <     V1.2  The color customizer does not affect the colors ofC           DECterm windows. To change the colors of DECterm windows,t@           copy the DECterm resource specifications from the file>           DXMDEFAULTS.DAT and add them to the DECterm resourceE           defaults file DECW$USER_DEFAULTS:DECW$TERMINAL_DEFAULT.DAT.e=           For example, add the following lines to the DECterm_!           resource defaults file:E                .              .              .P             DECW$TERMINAL.main.terminal.background: DXmDynamicTerminalBackgroundP             DECW$TERMINAL.main.terminal.foreground: DXmDynamicTerminalForeground  E           This allows the DECterm window colors to be customized with            the color customizer.a  ?     1.7.9 Changing the Default Value of the Automatic Shadowing            Toggle Button   =     V1.2  The default value of the automatic shadowing togglexC           button is set using the Custom.autoShadow resource in thei%           CUSTOM.DAT file as follows:u  %           Custom.autoShadowing: Falsea  $           The default value is True.  4     1.7.10 Using the Customizer on Multihead Systems  C     V1.2  The color customizer affects only applications started onoB           the same screen as the customizer. On multihead systems,D           you can start a different color customizer for each screen@           and have a different palette in effect on each screen.  >           The color customizer can be configured so that it isA           invoked once and affects all applications regardless of C           where they are started. This mode is invoked by modifying C           the Custom.multiScreen resource in the CUSTOM.DAT file as            follows:  "           Custom.multiScreen: True       1-20    n      I                                                General User Release NotestI                                      1.7 Color Customizer Example Program     )               The default value is False.a  @         1.7.11 Using the XSETROOT_CUST.EXE Demonstration Program  I         V1.2  The XSETROOT_CUST.EXE demonstration program, created during D               the customizer build, is a modified version of the MITC               utility program xsetroot that is used to set a bitmap D               on the root window. The XSETROOT_CUST.EXE program usesG               DXmDynamicScreenBackground and DXmDynamicScreenForegroundaF               as the background and foreground colors of the specifiedC               bitmap. If your DXMDEFAULTS.DAT file contains entries F               for these two dynamic colors, then use the customizer to;               dynamically modify the colors of your bitmap.o                 For example:  @               $ XSETROOT_CUST :== "$SYS$LOGIN:XSETROOT_CUST.EXE"7               $ XSETROOT_CUST -BITMAP your_xbm_file.XBMa  2         1.8 Display PostScript No Longer Supported  D         V1.2- Starting August 1, 1998, Compaq will no longer supportF         5     Adobe Display PostScript software. Compaq is taking this  H               action because Adobe Systems Incorporated is discontinuingF               support for Display PostScript. This action only affectsI               the Adobe Display PostScript software, not the applicationsiD               that make use of the software. For example, BookreaderI               will continue to be supported for all other types of sourcer5               files, except Adobe Display PostScript.p  I               However, for customer convenience, Adobe Display PostScriptrH               software will be supplied on an "as is" unsupported basis.A               Compaq disclaims all warranties made with regard tohF               Adobe Display PostScript software, including all implied8               warranties of merchantability and fitness.  .         1.9 DECwindows Motif Application Notes  F               This section contains information about DECwindows Motif               applications.         I                                                                      1-21                 General User Release Notes*     1.9 DECwindows Motif Application Notes         1.9.1 Bookreader  ;           This section includes problems, restrictions, and 5           enhancements in the Bookreader application.   (     1.9.1.1 Bookreader Printing Improved  >     V1.2- The Bookreader application allows only draft-qualityE     4     printing for books or topics. However, for this release thes  B           Bookreader print function has been improved to eliminateA           such problems as missing lines and words, figures beings9           overwritten by text, and poor leading of lines.   .     1.9.1.2 Multiple-Byte Character Limitation  =     V1.2- In order to print documents that contain multi-bytecD     4     characters (Japanese, Chinese, Korean or Thai), you should  @           use the version of Bookreader that was provided in theE           DECwindows Motif Version 1.2-3 for OpenVMS language varianta           products.t  C     1.9.1.3 Including Comment Characters in the DECW$BOOKSHELF Fileo  A     V1.2- If you include a comment character (! or #) in the lastsB     3     line of the DECW$BOOKSHELF file, Bookreader fails with a  E           reserved operand fault. As a workaround, ensure that you dotB           not add comment characters to the last line of the file.  E           This restriction will be removed in a future version of the_           product.  $     1.9.2 Calendar-Year 2000 Support  E     V1.2- Previous versions of DECW$CALENDAR accepted two-digit yearseE     5     in the interchange format and interpreted the year as beingp  D           in the range 1900-1999. This problem has been corrected byB           interpreting two-digit years as being in the range 1970-           2069.   E           DECW$CALENDAR always uses a four-digit year when writing inUC           the interchange format. Two-digit years can only arise if 3           interfacing Calendar with other programs.        1-22    C      I                                                General User Release Notes_I                                    1.9 DECwindows Motif Application Notesw    #         1.9.3 CDA Run-Time Services_  A         V1.2  This section describes features in the CDA Run-time !               Services component:   ?               o  Pack and Unpack applications are provided. SeeP                   Section 1.9.4.1  H               o  Performance enhancements for viewing CDA and PostScript                  documents.   E               o  Dynamic font support is implemented. Future upgrades H                  to installed fonts are usable by the CDA Viewer and the%                  PostScript back end.C  I               o  The DECwindows CDA Viewer supports DECfonts Version 1.2.t  A               o  CDA support is improved for documents created byl@                  DECwrite that contain links to other documents.  B               You can find additional information about CDA in the                following manuals:  ;               o  DIGITAL CDA Base Services Reference Manualo  C                  Provides reference material for using the CDA dataaB                  structures and access routines to create compound@                  document applications, converters, and viewers.  D               o  Technical Overview of the DIGITAL CDA Base Services  C                  Provides an introduction to CDA, compound documentsD                  processing concepts, and using the DIGITAL CDA Base                  Services.  (         1.9.3.1 CDA Dynamic Font Support  @         V1.2  As well as supporting a static-table for the fontsH               supported by the DECfonts Typeface Collection Version 1.2,H               this version of CDA Run-Time Services includes support forF               dynamic font lookup. This enables the CDA Viewer and theH               PostScript back-end converter to use new fonts as they are&               installed on the system.  ;               Dynamic font support is implemented using theeI               WRITE$FONTS.INI file, which you can maintain using the FonttG               utility provided with either DECwrite or DECpresent. If arF               document contains a font not found in the static tables,G               the CDA Viewer or the PostScript back-end converter tries G               to open the WRITE$FONTS.INI file and search for the font.   I                                                                      1-23T T  =           General User Release Notes*     1.9 DECwindows Motif Application Notes    D           If the font is not found or if the system does not containB           a WRITE$FONTS.INI file, the viewer uses a fallback font.  >           For further information on the Font utility, see the           following documents:  8           o  DECwrite Installation Guide for VMS Systems  :           o  DECpresent Installation Guide for VMS Systems  >           o  DECfonts Typeface Collection and User's Guide for              OpenVMS  (     1.9.3.2 CDA WRITE$FONTS Logical Name  >     V1.2  The default location for the WRITE$FONTS.INI file is>           SYS$LIBRARY, but, if the logical name WRITE$FONTS isE           defined, the CDA Viewer or the PostScript back end uses theoC           logical name definition to search for the WRITE$FONTS.INI            file._  @           Full path support is included, so any of the following            definitions are valid:  E           ___________________________________________________________o           WRITE$FONTS LogicaltE           Name__________________Resulting_File_______________________u  ;           Undefined             SYS$LIBRARY:WRITE$FONTS.INI   ?           DISK:[DIRECTORY]      DISK:[DIRECTORY]WRITE$FONTS.INI   9           SYS$LOGIN:            SYS$LOGIN:WRITE$FONTS.INI   ;           .TMP                  SYS$LIBRARY:WRITE$FONTS.TMPo  E           DISK:[DIRECTORY]FILE__DISK:[DIRECTORY]FILE.INI_____________i       1.9.3.3 CDA Documentst  ?     V1.2  The current version of CDA Run-Time Services includes >           a performance enhancement that decreases the time itB           takes to display the first page of a CDA document. Other@           applications that use the CDA Viewer to view documents?           (for example, DECwindows Mail) also benefit from this            enhancement.  E           The CDA Viewer enables this performance enhancement feature =           by default. You can disable the feature as follows:o  -           $ DEFINE CDA_QUICK_FIRST_PAGE FALSE        1-24 a  r      I                                                General User Release Notes I                                    1.9 DECwindows Motif Application Notes     G               The CDA Viewer might not display some documents correctlyeC               when this feature is enabled. If you encounter such acD               problem, disable the feature and invoke the CDA ViewerF               again. If the problem persists, please submit a SoftwareG               Performance Report along with a copy of the document (andTF               any associated documents). The CDA Pack application (seeF               Section 1.9.4.1) allows you to create a single file thatC               includes a .DDIF or .DTIF document and its associated                files.  )         1.9.4 CDA-Additional Applicationse  D         V1.2  This section contains information about additional CDA               applications.u  ,         1.9.4.1 Pack and Unpack Applications  H         V1.2  CDA Run-Time Services includes two standalone applicationsF               that can be used for transferring CDA documents across aG               network. The CDA Pack application packages a CDA documentoF               along with all of its externally referenced files into aF               single file that can be copied between systems or mailedE               to other users. The CDA Unpack application reads a fileoH               that is packaged by the CDA Pack application and creates aG               copy of the original document file and all its externallyr               referenced files.i  @               These applications allow you to copy CDA documentsC               between systems without copying externally referencedrD               files separately or correcting external file reference2               information after copying documents.  @               To use these applications, add the following lines=               to your LOGIN.COM file (or add the lines to the ,               SYS$MANAGER:SYLOGIN.COM file):  2               $ PACK == "$SYS$SYSTEM:CDA$PACK.EXE"6               $ UNPACK == "$SYS$SYSTEM:CDA$UNPACK.EXE"  G               These lines enable you to use the symbols PACK and UNPACKEG               to invoke the Pack and Unpack applications, respectively.p        I                                                                      1-25  o  i           General User Release Notes*     1.9 DECwindows Motif Application Notes         1.9.4.2 Pack Application  D     V1.2  The CDA Pack application creates a single output file that?           contains the contents of a .DDIF or .DTIF input file. A           The single output file also includes the files that arel6           referenced by the .DDIF or .DTIF input file.  7           The format of the PACK command is as follows:   1           $ PACK input-file-spec output-file-spec   ?           The following sections explain the format of the PACKi           command.             input-file-specr@           Specifies the name of the primary .DDIF or .DTIF input           file..             output-file-spec?           Specifies the name of the output file that is createdtA           by the PACK application. If you do not specify a devicehA           or directory, the output file is created in the currentn           default directory.             Qualifiers:              /[NO]SKIP_MISSINGiD           Controls whether the Pack application continues processingD           if it cannot find one or more of the files that are listed@           as external references in the input file. The names of?           any missing files are sent to SYS$ERROR when the Pack C           application is completed. If you specify /NOSKIP_MISSING,rD           the Pack application does not create an output file if anyE           of the externally referenced files are missing. The defaulth           is /SKIP_MISSING.              /[NO]CONTROLLED_COPY>           Controls whether the output file includes only those@           external references that specify COPY_REFERENCE as theA           value of the ERF_CONTROL item in the input file. If youyC           specify /NOCONTROLLED_COPY, the Pack application includesaC           all referenced files, regardless of the value of the ERF_i:           CONTROL item. The default is /NOCONTROLLED_COPY.         1-26 o  a      I                                                General User Release Notes I                                    1.9 DECwindows Motif Application Notes                    /ALWAYS_ENCODEG               Controls whether an output file is created when there arehE               no external references in the input file, or if none oflG               the externally referenced files are found. The default iseG               not to create an output file in these cases. If an outputeI               file is not created for these reasons, the Pack application_5               returns the CDA_W_NOOUTFIL status code.e                 For example:  *               $ PACK MYFILE.DDIF TEST.PACK  "         1.9.4.3 Unpack Application  F         V1.2  The CDA Unpack application unpacks an input file createdH               by the Pack application. The output files are the .DDIF orH               .DTIF file that is packed by the Pack application, as wellI               as a file for each external reference in the .DDIF or .DTIFaH               file. The Unpack application sends a list of created files               to SYS$ERROR.e  =               The format of the UNPACK command is as follows:m  &               $ UNPACK input-file-spec  E               The following sections explain the format of the UNPACK                command.                 input-file-spec_I               Specifies the name of the input file that is created by thet               Pack application.                  Qualifier:  &               /OUTPUT=output-file-specG               Specifies the file name and location of the files created (               by the Unpack application.  D               If you specify an output file name without a directoryA               name, the Unpack application creates the main .DDIF A               or .DTIF file with the file name you specify in the G               current default directory. It also creates all externallya@               referenced files in the current default directory.    I                                                                      1-27     t           General User Release Notes*     1.9 DECwindows Motif Application Notes    B           If you specify a directory name without a file name, theE           Unpack application creates the main .DDIF or .DTIF file andgE           all externally referenced files in the specified directory.iD           The main .DDIF or .DTIF file has the same name as the file)           packed by the Pack application.   >           If you specify a directory name and a file name, theA           Unpack application creates the main .DDIF or .DTIF fileaC           and all the externally referenced files, in the specifiedyC           directory. The main .DDIF or .DTIF file has the file name            you specify.             For example:             $ UNPACK TEST.PACK7           Output file DISK$:[SMITH]MYFILE.DDIF created. 9           Output file DISK$:[SMITH]FIGURE_1.DDIF created.e  2           $ UNPACK TEST.PACK/OUTPUT=[SMITH.UNPACK]>           Output file DISK$:[SMITH.UNPACK]MYFILE.DDIF created.@           Output file DISK$:[SMITH.UNPACK]FIGURE_1.DDIF created.  ?           $ UNPACK TEST.PACK/OUTPUT=[SMITH.UNPACK]NEW_FILE.DDIF K           Output file DISK$:[SMITH.UNPACK]MYFILE.DDIF renamed NEW_FILE.DDIF @           Output file DISK$:[SMITH.UNPACK]FIGURE_1.DDIF created.  *     1.9.4.4 Pack and Unpack Error Messages  A     V1.2  This section describes messages associated with the CDA1'           Pack and Unpack applications.r  +       FILESPEC, Missing filespec: file-namem             Severity: Informational  D          Explanation: The Pack application cannot locate an externalE          file included as an external reference in the .DDIF or .DTIF E          file or in one of the files referenced in the .DDIF or .DTIFg          file.  +       NOOUTFIL, No output file was created.f            Severity: Warning  ?          Explanation: The Pack application cannot find external D          references in the .DDIF or .DTIF document to be packed, and:          you did not specify the /ALWAYS_ENCODE qualifier.       1-28 m  :      I                                                General User Release Notes I                                    1.9 DECwindows Motif Application Notesi    1          OUTFILE,  Output file created: file-name   #             Severity: Informational                Source: CDA_UNPACK  E             Explanation: The Unpack application created the specifiedeH             file while unpacking a file created by the Pack application.  9         1.9.5 CDA-Hints, Restrictions, and Known Problems   F               This section contains helpful hints, known restrictions,5               and known problems with the CDA Viewer.   &         1.9.5.1 Message for CDA Viewer  I         V1.2  The CDA Viewer issues the following message if it is unablet0               to create the application context:  H          DRMCTXFAIL,  DVR could not create application context, aborting               Level: Error  B             Explanation: The CDA Viewer ends because an attempt toE             create the application context using the Resource Manager C             failed, which is usually caused by insufficient memory..  =             User Action: Reduce the system load and start then             application again.  -         1.9.5.2 CDA Paper Size Button Renamed   I         V1.2  In the CDA Viewer, the name of the Paper Size button in the I               Open dialog box is changed to Display Options. However, thei<               function invoked by the button is not changed.  '         1.9.6 Clock-DECsound Capability   B         V1.2  The Clock application includes an alarm feature thatE               can be used if your system is a TURBOchanel system thatwG               supports DECsound. On systems without sound capabilities,rD               you can select only the keyboard bell. When you chooseH               Alarm from the Options menu, a pop-up window appears. ThisH               pop-up window allows you to set the alarm time, choose theG               sound to be played, and indicate an alarm message. To see E               if your system supports this feature, invoke one of theeI               sounds located in the DECW$EXAMPLES directory (for example,r               BELLS.AUD).t  I                                                                      1-29                 General User Release Notes*     1.9 DECwindows Motif Application Notes         1.9.7 DECsound Application  ;           This section contains information about DECsound.B  "     1.9.7.1 DECsound Prerequisites  =     V1.2- DECsound is supported only on TURBOchannel systems.t@     3     TURBOchannel systems that support DECsound include the             following:  &           o  DEC 3000 Model 400 series  &           o  DEC 3000 Model 500 series  &           o  DEC 3000 Model 700 series  &           o  DEC 3000 Model 900 series  1           o  VAXstation 4000 Model VLC, 60 and 90n       1.9.7.2 DECsound Problemsr  9     V1.1  The following is a known problem with DECsound:h  D           o  The Record operation does not work when you select part              of the waveform.9  C              To correct this problem, do not select any part of theg<              waveform before you click on the Record button.       1.9.8 DECterm Features  =           This section contains information about the DECterm            application.  *     1.9.8.1 New DECterm Default Font Sizes  A     V1.2- In previous releases, the default DECterm font size foroA     4     the "big" and "little" fonts were chosen by point size.   E           This depended on whether 75 or 100 dpi fonts were installedc@           first in the font path. Starting with DECwindows Motif@           Version 1.2-4 for OpenVMS, DECterm chooses its default@           fonts by pixel size. The following table shows the two           behaviors.       1-30           I                                                General User Release NotestI                                    1.9 DECwindows Motif Application Notesp  I               ___________________________________________________________V)                                     PriortI                                     Releases          Since Version 1.2-4a               Default Font Size I               (in_pixels)___________100___75[1]_______100___75___________   >               Big font              25    18          18    18  >               Little font           18    14          14    14I               [1]75_dpi_fonts_or_100_dpi_fonts_on_a_15-inch_monitor______   I               ___________________________________________________________i  G               In addition, on 100-dpi displays DECterm now uses the bigcE               font by default. This results in DECterm using the samenD               font size (18 pixels) on 100-dpi displays as it did inI               prior releases. On displays that are less than 325 mm wide, :               DECterm also now uses a bigger default font.  D               Follow these steps to use the same font as in previous#               releases (14 pixels):o  B               1. From the Options menu, select the Window... item.  4               2. Choose Little Font. Click on Apply.  G               3. If the new default font is too small, click on the Big H                  Font button and change the pixel size in the Other text+                  entry field from 18 to 25..  *         1.9.8.2 DECterm Resource File Name  C         V1.2- In this release, the locale of the display is used toID         4     create the file name of the DECterm resource file. For  H               example, if the locale is set to "ja_JP", then the defaultI               resource file name becomes DECW$TERMINAL_DEFAULT_JA_JP.DAT.t  E               However, DECterm continues to use the old resource file G               name until the user selects Save Options at least once inMG               the particular locale. The default resource file name forsF               DECterm continues to be DECW$TERMINAL_DEFAULT.DAT if the               locale:                  o  Is "C"t  $               o  Starts with "en_US"  "               o  Contains "8859-1"  I                                                                      1-31t a  n           General User Release Notes*     1.9 DECwindows Motif Application Notes         1.9.8.3 Escape Sequences  C     V1.2- The DECterm application supports all ReGIS input cursors:n     3     o  Crosshair             o  Diamond             o  Rubber-band line   "           o  Rubber-band rectangle  C           For a shape other than the diamond cursor when n is equaleE           to 1, define the logical name DECW$TERM_REGIS_CURSOR as one E           of the numbers defined in the SYS$LIBRARY:DECW$CURSOR file.   B     V1.2  The following escape sequences are supported by DECterm:  E           o  All page movement sequences (NP, PP, PPA, PPB, and PPR).e  >           o  One rectangular area operation sequence (DECCRA).  "           o  The DECLFKC sequence.  @           o  The ReGIS command S(C(In)) supports the rubber-band5              rectangle cursor and the diamond cursor.$  @           See Section 3.15.4, ReGIS Input Cursors for additional@           information about escape sequences in DECwindows MotifE           software. See Chapter 3 for details and restrictions on theh!           use of these sequences.e  *     1.9.8.4 Scrolling Through the Keyboard  B     V1.2- You can scroll through the keyboard by pressing the CtrlC     3     key and arrow keys or by pressing the Prev or Next key on              the editing keypad.   -     1.9.8.5 Reporting the DECterm Window Size   C     V1.2- When you enable the Show Feedback option in the WorkspacetA     3     Options dialog box of the Window Manager and you resize   A           a DECterm window, the size of the window is reported inT'           characters instead of pixels.   !     1.9.8.6 Resizing the Terminal   E     V1.2- If you maximize the DECterm window when you enable the Auto9B     3     Resize Terminal window option, the window is expanded to  D           its nearest cell boundary; the window does not necessarilyC           occupy the entire screen. The Restore options continue tod!           function appropriately.D       1-32           I                                                General User Release NotesrI                                    1.9 DECwindows Motif Application Noteso    ;         1.9.8.7 Timeout for Displaying the Copyright Noticee  F         V1.2- If keyboard or mouse activity does not take place for 10D         3     seconds after the copyright notice is displayed on the  F               terminal, the notice disappears from the DECterm screen.  /         1.9.9 DECterm-Restrictions and Problems   I               This section discusses restrictions and problems related to &               the DECterm application.  1         1.9.9.1 Maximum Number of DECterm Windowsn  E         V1.2- A DECterm controller can create a maximum of 23 DECtermTF         4     windows. This occurs because DECterm needs an event flag  G               for each terminal window to use. There are 23 event flags G               that DECterm can use. (Event flag 0 and event flags 24-32s4               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$TERMINALy  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.  0         1.9.9.2 Changing the Auto Repeat Setting  F         V1.2- You cannot change the Auto Repeat setting in the DECtermI         3     Keyboard Options dialog box. Instead, change the setting in   =               the Keyboard dialog box in the Session Manager.   #         1.9.9.3 Positioning DECterm   I         V1.2- If the resource Mwm*clientAutoPlace is set to True, DECterm E         3     windows are not displayed where the DECW$TERMINAL.x andn  G               DECW$TERMINAL.y resources are specified. As a workaround, 9               set this resource to False and restart MWM.e  I                                                                      1-33     e           General User Release Notes*     1.9 DECwindows Motif Application Notes         1.9.9.4 User Font SelectionK  ?     V1.2  DECterm allows you to select available fonts from theoE           Options/Window dialog box. A different font can be selecteduB           to replace the default Big Font, default Little Font, or'           default German Standard Font.   >           In the Options/Window dialog box, you can select the>           default font or enter the name of a font into a text?           field and select that font. When the Big Font, LittlecA           Font, or German Standard Font is selected and the OtheruE           toggle button for the font is selected, DECterm attempts totD           locate and use the font name supplied in the adjacent textD           field. For information on font naming conventions or fonts@           available on your system, consult your system manager.  C              ________________________ Note ________________________d  >              Not all fonts work properly with DECterm. DECterm@              emulates a character-cell terminal, and, therefore,;              expects the fonts to be monospaced (each glyphK>              occupies the same number of pixels). Proportional@              fonts can be chosen, but they produce unpredictable              results.y  @              Furthermore, DECterm fonts are supplied in families@              of 26 related fonts, including variations for bold,B              double-width, double-width/double-height, normal, and>              condensed characters. Also, DECterm fonts include=              special characters, such as the Line Drawing and A              the DIGITAL Technical character sets. A DECterm font @              family is identified by the font naming convention.  ?              Use of fonts that do not have all the related fonteA              family variations, fonts that do not have the neededt=              special characters, or font families that do not B              adhere to the DECterm font family naming conventions,>              may not result in an optimal display or otherwise!              perform as expected.e  C              ______________________________________________________D  C           On OpenVMS systems, Version 6.1 or higher, the VT330 font A           has been made available. The VT330 font is based on thenD           10x20 font used in the VT330 and VT340 terminals. Use thisC           font on a system where they are available by entering the B           following font-name strings in the font-name text field:       1-34           I                                                General User Release Notes I                                    1.9 DECwindows Motif Application Notes     4                   -DEC-VT330-*-*-*--20-*-*-*-c-*-*-*           1.9.9.5 Local Echo  H         V1.2  DECterm supports a local echo mode. In the Options/GeneralG               dialog box, select Local Echo, which causes all character E               sequences generated locally to be echoed on the displaytH               and passed to the remote host. This feature is useful whenF               connected to a host that does not echo typed characters.  "         1.9.9.6 Answerback Message  I         V1.2  A user interface is available to enter answerback messages.fE               This answerback message field is for compatibility withe                DIGITAL terminals.  B               The answerback field is a buffer that contains up toH               thirty characters. The answerback field in earlier DIGITALF               terminals contained a message used to identify itself toH               the host system. For DECterm windows, the answerback fieldH               can be used to store a sequence of characters that you can-               use for any repetitive purpose.y  F               A field is provided in the Options/General dialog box toF               enter answerback text. Click on the answerback field andF               enter your text. To enter control characters, encode theG               control character as a two-digit hex ASCII code, preceded #               by a number sign (#).u  F               For example, when you enter #0D in the answerback field,6               DECterm responds with a carriage return.  I               If two consecutive number sign characters are entered (##),T2               a single number sign is transmitted.  B               If anything other than a valid two-digit hex code orE               another number sign is detected after an initial number ?               sign, the number sign is treated as a normal text E               character. Refer to any ASCII table for a complete listS               of characters.  I               The answerback text can also be concealed. When the Conceal E               Answerback button is enabled, the answerback message isuI               concealed. To deselect the Conceal Answerback button, click E               on the answerback text field, which erases the previousa!               answerback message.   I                                                                      1-35k d  p           General User Release Notes*     1.9 DECwindows Motif Application Notes    %     1.9.9.7 Seven-Bit Printer Supportn  :     V1.2  When the 7-Bit Printer button is selected in the>           Options/Printer dialog box, DECterm modifies printedA           text to be compatible with printers that do not support D           8-bit characters. This includes modifying control sequence@           introducer (CSI) strings to use the format Escape-Left=           Bracket rather than the single 8-bit CSI character.D  C           When the 8-Bit Printer button is selected, DECterm allowsSB           the use of 8-bit characters when printing. This mode canE           cause problems for older printers if they can not interpret            8-bit characters.w             The default is 8-Bit.   .     1.9.9.8 VT330 and VT340 Terminal Emulation  A     V1.0  DECterm incorporates some of the features of the VT330-KC           and VT340-series video terminals, such as ReGIS and SixelfE           graphics. DECterm does not provide complete VT330 and VT340c           terminal emulation.t  6           The following restrictions apply to DECterm:  E           o  User-loadable characters (DRCS), local mode, and controln;              representation mode (CRM) are not implemented.   D           o  The checkerboard character (character 97 in the DIGITAL?              Special Graphic character set) is used as an errort=              character in place of the reverse question mark.c  ?           o  DECterm uses replace mode as the default for SixeltE              drawing on servers with eight planes or less. On serversaD              with more than eight planes, DECterm uses overlay mode;=              replace mode is not functional on those servers.s  ,     1.9.9.9 CREATE/TERMINAL/DETACHED/PROCESS  C     V1.0  The /PROCESS=procnam qualifier does not work when used inoC           conjunction with the /DETACHED qualifier, unless there isSC           already a process running on the system where its processa)           name is equal to the user name.c  @           To work around this problem, use the following command           procedure:       1-36 h  l      I                                                General User Release Notes I                                    1.9 DECwindows Motif Application Notesy    %               $! CREATE_TERM_PROC.COM                $!B               $! Invoke as SPAWN/NOWAIT @CREATE_TERM_PROC procname               $!               $ SET NOON               $!-               $! Set Process name to usernamee               $!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 creationEH               of the process inside the DECterm fails. In this case, theE               DCL command CREATE/TERMINAL returns the following erroru               message:  $               Duplicate process name  0         1.9.9.10 Printing to an Attached Printer  A         V1.1  Printing to a port device requires you to have readeD               and write privileges on that port. You cannot print byI               allocating the device, since the controller requires accessmA               to the device. Instead, set the device to WORLD:RW.   H               For example, to use the printer port on a VAX 3100 system,F               enter the following command from a privileged account or=               include the command in the system startup file:t  4               $ SET PROTECTION=WORLD:RW TTA3:/DEVICE  !         1.9.9.11 DECterm Graphics.  H         V1.1  The following information is specific to DECterm graphics:  I               o  In some cases, a private colormap is created in DECterm.nE                  This private colormap is created when ReGIS or Sixel F                  graphics are displayed in the window and a sufficientE                  number of colors from the default colormap cannot bemF                  allocated. The result is that when the DECterm windowE                  has input focus, the colormap changes for the entire F                  workstation. The default colormap is four colors on a  I                                                                      1-37                 General User Release Notes*     1.9 DECwindows Motif Application Notes    C              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 redrawnnD              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.   @           o  ReGIS addresses the entire window, not just 24 rowsA              and 80 columns, so the aspect ratio between text andsE              graphics might not always be the same as on the VT330 orx              VT340 terminal.  >           o  The following ReGIS features are not implemented:  $              -  Command Display mode                -  Scrollinge                -  Output cursors  #     1.9.9.12 DECterm Resource Usagea  B     V1.1  You cannot create more terminal windows than your system>           resources and quotas allow. If you have insufficient=           resources, a dialog box is displayed with a message >           indicating that no additional DECterm windows can be           created.  E           To reduce the memory requirement of each DECterm window and D           create additional terminal windows, decrease the number ofE           Record Lines Off Top in the Display dialog box and decreasef8           the number of columns for each DECterm window.  D           Once the resource limit is reached, log out of all DECterm@           windows that are running on the host system before you2           increase the number of terminal windows.       1-38           I                                                General User Release Notes5I                                    1.9 DECwindows Motif Application Notes     3         1.9.9.13 Diagnostic Crash File and Messages   F         V1.1  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 DECtermB               application and submit a Software Performance ReportB               (SPR), include a copy of the log file. Under certainI               circumstances, a log file is generated even when no problemoH               is encountered. Therefore, the appearance of a log file asI               an isolated event should not be cause for a problem report.a  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 bepE               generated for each new DECterm created from the Sessione               Manager.  G               DECterm diagnostics can be captured in a file by definingrG               the logical name DECW$TERMINAL_OUTPUT to point to a file.r  %         1.9.9.14 ReGIS Locator Reportn  F         V1.0  When DECterm sends a ReGIS locator report in response toD               the R(P(I)) command, or in multiple input mode and theG               locator position is outside the addressable area, DECtermEF               sends a locator report with the coordinates omitted. For>               example, press the A key to generate the report:  G               A[]<CR>, where <CR> is a carriage return (ASCII code 13).            1.9.10 DECW$CDPLAYER  @         V1.1  The DECW$CDPLAYER application in the DECW$EXAMPLESB               directory requires PHY_IO and DIAGNOSE privileges toC               operate the compact-disc player hardware. Either youry>               process or the image must have these privileges.           1.9.11 DECwindows Mail  I               This section contains information about the DECwindows Mailo               application.  I                                                                      1-39u a  v           General User Release Notes*     1.9 DECwindows Motif Application Notes    .     1.9.11.1 DECwindows Mail Problems with MB3  D     V1.2- If you use MB3 to move a mail message, the DECwindows MailB     5     application can become corrupted and the application can  ?           eventually crash. This problem happens if the primaryo<           selection is not in DECwindows Mail's main window.  D           As a workaround, always use MB1 to select a message before>           moving it. If the display becomes corrupted, restart           DECwindows Mail.  C              ________________________ Note ________________________t  B              The mail messages and mail folders themselves are not6              corrupted; only the display is corrupted.  C              ______________________________________________________   7     1.9.11.2 Pasting Messages from the Directory Window   =     V1.2- In DECwindows Mail, if the user selects one or moreTD     4     messages in the directory window using MB1 and then clicks  B           on MB2 in another window (such as a DECterm window), theA           entire contents of the selected messages is pasted intoiD           the other window. The selected messages are highlighted inD           the directory window, however the text of the selected and?           pasted message is not highlighted in the Read window. *     1.9.11.3 Responses to Keyboard Actions  C     V1.2- Enhancements in the DECwindows Mail application to comply B     3     more closely with OSF/Motif style conventions cause some  A           changes with application responses to keyboard actions.r%           Note the following changes.r  D           If you use the Tab key to advance through text entry boxesC           in the Create/Send window, the current field is no longerIA           highlighted. To select a field, use one of the standard.B           Motif actions, such as double or triple clicking MB1, or.           use the Shift+Alt - >  key sequence.  E           In several dialog boxes, press either the Select key or theRB           space bar to activate a pushbutton through the keyboard.A           Note that the Return key and the Enter key are bound totA           other widgets in the dialog box. Alternatively, you cand9           continue to click MB1 to activate a pushbutton.f       1-40 d  u      I                                                General User Release NotesOI                                    1.9 DECwindows Motif Application Notese    @         1.9.11.4 Using the Color Customizer with DECwindows Mail  E         V1.2  If you use the color customizer sample program providedsG               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 restartrI               DECwindows Mail. See Section 1.7 for more information about #               the color customizer.)  .         1.9.12 DECwindows Motif Window Manager  D               This section contains information about the DECwindows#               Motif Window Manager.d  H         1.9.12.1 Using the Color Customizer with DECwindows Motif Window                  Manager  C         V1.2  If you are using the color customizer provided in theaE               DECW$EXAMPLES directory to control Motif Window ManagersC               colors, the Motif Window Manager customization dialogaC               boxes used to modify those colors may not reflect thefH               correct current color values. This is normal behavior; useF               the color customizer instead of the Motif Window ManagerF               color customization dialog boxes to change these values.G               Alternatively, exit the color customizer and then restart H               Motif Window Manager. See Section 1.7 for more information)               about the color customizer._  #         1.9.12.2 Configuration File_  D         V1.0  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 Charactera8               key) and function key, for example Alt+F7.  I               If any application needs to use these keys, you must eitheraE               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 MWMV9               resource file to point to the new bindings.   I                                                                      1-41                 General User Release Notes*     1.9 DECwindows Motif Application Notes    ;           With the Motif binding, you can no longer use the A           Alt+spacebar or the Compose Character+spacebar to bring ?           up the Window menu because it interferes with Compose @           Character sequences in DECterm. Use Shift+F11 to bring           up the Window menu.e  A           To reenable Alt+space, select the appropriate option inc@           the Workspace Options dialog box and apply the currentC           settings. You can also remove the comment for the default D           button bindings for Alt+space in the DECW$MWM_RC.DAT file.  (     1.9.12.3 DECwindows XUI Applications  A     V1.0  The resource Mwm*useDECMode allows previous versions ofsB           DECwindows XUI applications to behave correctly with theD           Motif Window Manager. In particular, this resource is usedB           to control focus, window placement, multiline icons, and;           the window's initial state (normal or minimized).h  ,     1.9.12.4 Restarting Motif Window Manager  C     V1.0  The file SYS$MANAGER:DECW$MWM.COM is used for informationhA           on how to restart the Window Manager. By default, it isaA           always restarted on all the screens that are available. B           However, if you are not starting the Window Manager from@           the Session Manager, then the Window Manager might notC           have been initially started on all the available screens.mB           You can modify this file to change the way the window is$           restarted for your system.  .     1.9.13 Motif Window Manager-Known Problems  E           This section contains information about known problems with #           the Motif Window Manager.o  ?     1.9.13.1 Customizing Color-Related Resources for Monochromeh              Monitorsl  8     V1.0  The Motif Window Manager does not support fullA           customization of color-related resources for monochromeaD           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 titlelD           background, you must change the Mwm*activeBackgroundPixmapE           resource. Some values include 25_foreground, 50_foreground, 0           75_foreground, and unspecified pixmap.       1-42    i      I                                                General User Release Notes I                                    1.9 DECwindows Motif Application Notes     G               In addition, by default, the title text is created with a H               white background. To use the same color as the rest of the=               title, set the Mwm*cleanText resource to FALSE.f  /         1.9.13.2 Moving the Icon Box Off Screen   D         V1.0  If you move the icon box to the edge of the screen andD               then resize it using the keyboard, you can move it offG               the screen. To retrieve the icon box, press Alt+Tab untilsH               you reach that window and then press Shift Escape (F11) toI               bring up the Window menu for that window. You can then movei.               the window back onto the screen.  5         1.9.13.3 Multihead Systems-Customizing Colorsy  I         V1.0  If you have a multihead system with different monitor types G               (color, monochrome, or gray-scale), you can customize the I               colors only by using the Options dialog box on the monitors E               that match the type of your main monitor (screen 0). To G               customize the other monitors, you must either log in to amI               system with that monitor type or directly edit the resourcer               files.  2         1.9.13.4 Multiline Icon Title Not Centered  C         V1.0  The Window Manager does not center all the lines of an#               multiline icon title..           1.9.14 Notepad  A               This section contains information about the Notepadw               application.  C         1.9.14.1 Notepad Is Linked with the OSF/Motif Release 1.1.3d                  Toolkit  B         V1.2- The Notepad application is linked with the OSF/MotifI         3     Release 1.1.3 Toolkit. Notepad is not modified to link with   I               the OSF/Motif Release 1.2.3 Toolkit, which is provided with I               the DECwindows Motif Version 1.2-5 for OpenVMS product. The1+               following restrictions apply:   I               o  OSF/Motif Release 1.2 drag-and-drop functionality is notkG                  supported. As a workaround, use the standard clipboard H                  operations (Cut, Copy, and Paste) to transfer text into                  Notepad.   H               o  OSF/Motif Release 1.2 tear-off menus are not supported.  I                                                                      1-43                 General User Release Notes*     1.9 DECwindows Motif Application Notes         1.9.15 Paint  ;           This section contains information about the Paintn           application.       1.9.15.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 byi           clicking on it.i  ?     1.9.15.2 Enhancing the Performance of Some Paint Operationsr  ;     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.3  @           When editing images (especially color images), you can?           resize the image area using the Picture Size... entry C           from the Options menu. Resize to the least possible image D           area to significantly reduce the amount of required pixmap           memory.a       1.9.16 Print Screenw  B           This section contains information about the Print Screen           application.  3     1.9.16.1 Print Screen-PostScript Output Problemh  <     V1.2- When using the Print Screen application to produce@     5     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 PostScriptE           printers. To correct this problem, DECwindows Motif VersioneE           1.2-5 for OpenVMS adds support for four new resources whichl3           can be specified in DECW$PRINTSCREEN.DAT:        1-44 .  e      I                                                General User Release NotesaI                                    1.9 DECwindows Motif Application Notes     &               PrintScreen.plxtranslate&               PrintScreen.plytranslate"               PrintScreen.plxscale"               PrintScreen.plyscale  B               These resources control the size and position of the@               PostScript image on the page. The plxtranslate andC               plytranslate resources control the x and y offsets ofoC               the image in inches from the origin. The plxscale andsE               plyscale resources are an x and y scale factor to allowxD               the entire image to be displayed on the page after the               origin is moved.  +         1.9.17 Session Manager and FileView   I               This section contains information about the Session Managers(               and FileView applications.  H         1.9.17.1 Invoking DECchart from the Session Manager Applications                  Menuc  =         V1.2- If you invoke the DECchart application from thegA         3     Session Manager applications menu, your session can   B               fail. As a workaround to this problem, edit the fileG               VUE$LIBRARY:DECCHART$VUE.COM to incorporate the followingr               text:                                     I                                                                      1-45D e  w           General User Release Notes*     1.9 DECwindows Motif Application Notes               $!D           $! Copyright (c) 1989, 1991 Digital Equipment Corporation.!           $! All rights reserved.-           $!F           $! Command procedure to run DECchart from the User Executive           $! in DECwindows           $!&           $  vue$suppress_output_popup           $!1           $! See if we should skip the dialog box            $!5           $    vue$get_symbol vue$show_hidden_dialogs +           $    vue$read show_hidden_dialogsR           $sA           $    if show_hidden_dialogs then goto select_qualifiersp$           $       vue$get_qualifiers           $       goto do_chartt           $            $select_qualifiers:m&           $       vue$popup_qualifiers           $,           $p           $do_chart:           $ $           $ vue$popup_progress_box 8            $ vue$read vue$command           $ @           $ if "''vue$command'" .eqs. "DETACHED_APPLY" then goto           $ select_qualifiersu           $s           $ 'vue$command           $ 7           $ decchart :== $sys$system:decchart$motif.exe "           $ vue$get_next_selection           $ vue$read selection           $ decchart 'selectionn           $a           $ vue$check_verb_loop            $ vue$read loopiA           $ if "''loop'" .eqs. "TRUE" then goto select_qualifierst               1-46    s      I                                                General User Release Notes I                                    1.9 DECwindows Motif Application Notese    H               The only change is to relocate the following line from theA               beginning of the VUE$LIBRARY:DECCHART$VUE.COM file:r  (               $ vue$popup_progress_box 8  H               This statement causes the Progress Box to pop up after the'               qualifiers are processed.   !         1.9.17.2 Security Optionss  G         V1.2  In the Session Manager Security Options dialog box, placeaG               the node name within quotation marks if the name containsr#               any of the following:e  E               o  Reserved characters: space, tab, comma (,) or doubleY#                  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 beginsdH               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 changes               it.   G               Within a quoted string, a double quotation mark should bePG               replaced by two double quotation marks (""). For example,DI               the quoted string "DEC:.zko."my node"" should be changed toi               the following:  '               ("DEC:.zko.""my node""").o  @         1.9.17.3 Using the Color Customizer with Session Manager  C         V1.2  If you are using the color customizer example program H               provided in the directory DECW$EXAMPLES to control SessionE               Manager colors, the Session Manager color customization_F               dialog boxes used to modify those colors may not reflectH               the correct current color values. This is normal behavior;E               use the color customizer instead of the Session Manager F               color customization dialog boxes to change these values.G               Alternatively, exit the color customizer and restart your E               session. See Section 1.7 for more information about thee               color customizer.w  I                                                                      1-47                 General User Release Notes*     1.9 DECwindows Motif Application Notes    :     1.9.17.4 Input Focus Change When Starting Private Logo  E     V1.0  If you are logging into DECwindows and using a private logotD           command file, input focus might revert unexpectedly to the9           Username field when the private logo starts up.   -     1.9.17.5 Session Manager Process-Stopping   ?     V1.0  Stopping the Session Manager process can have seriouse;           consequences for nonprivileged workstation users.d=           DECwindows must be restarted to avoid the followingn           problems:d  D           o  A nonprivileged user cannot start a new Session Manager'              or create a new login box.   @           o  If the session is paused, the Pause cover window isA              deleted and unauthorized users can access windows on               that workstation.  D           o  The workstation can also become unusable if the SessionE              Manager process is terminated by the job controller (for B              example, when the user's access hours, which might be2              from 8 a.m. to 5 p.m., are exceeded).  ?              As a possible solution, restart DECwindows on eachnC              workstation in a batch job that runs during off-hours.i  E           If you stop the Session Manager process, restart DECwindowsoD           (if you have system manager privileges) with the following           command:  -           $ @SYS$MANAGER:DECW$STARTUP RESTARTX  0     1.10 Window Dump to Print File (xpr) Utility  B     V1.2  The Window Dump to Print File utility prints an X Window%           dump using the xpr program.   >           The xpr program receives as input a window dump fileB           produced by the Window Dump utility (xwd) and formats it/           for output on the following printers:z             o  PostScripte  "           o  DIGITAL LN03 or LA100  $           o  IBM PP3812 page printer  0           o  HP LaserJet (or other PCL printers)       1-48    o      I                                                General User Release Notes I                              1.10 Window Dump to Print File (xpr) Utilityu                   o  HP PaintJet  B               To use the xpr program, define xpr as a user-defined               command:  (               $ xpr == "$DECW$UTILS:XPR"  H               You must specify an input file. The xpr program prints theI               largest possible representation of the window on the output G               page. Options allow the user to add headers and trailers,tD               specify margins, adjust the scale and orientation, andC               append multiple window dumps to a single output file.o  /               Use the following command format:   +               $ xpr input_file [options...]                  Options include:  ;                   -append filename  -noff  -output filename                    -compactN                   -device {ln03 | la100 | ps | lw | pp | ljet | pjet | pjetxl}                   -dump2#                   -gamma correction #                   -gray {2 | 3 | 4}T/                   -height inches  -width inchese1                   -header string  -trailer stringe'                   -landscape  -portrait +                   -left inches  -top inchese                   -noposition                    -nosixopte                   -plane n                   -psfig                   -render type                   -report                    -rvn                   -scale scale                   -slide                    -split n-pages  6               Table 1-1 defines the available options.        I                                                                      1-49                 General User Release Notes0     1.10 Window Dump to Print File (xpr) Utility    E           Table_1-1_Window_Dump_to_Print_File_Options________________e  E           Option___________Description_______________________________r  D           -device devtype  Specifies the device on which the file is#                            printed.e  7                            Currently supported devices:   0                            la100  DIGITAL LA100.  /                            ln03   DIGITAL LN03.i  >                            ljet   HP LaserJet series and other@                                   monochrome PCL devices such asC                                   ThinkJet, QuietJet, RuggedWriter, D                                   HP series, and HP-series printers.  ;                            pjet   HP PaintJet (color mode).o  ?                            pjetxl HP PaintJet XL Color Graphicsi7                                   Printer (color mode).a  -                            pp     IBM PP3812.w  5                            ps     PostScript printer.R  @                            lw     LaserWriter is equivalent to -D                                   device ps and is provided only for:                                   backwards compatibility.  5                            The default is PostScript.e  @           -scale scale     Affects the size of the window on the=                            page. The PostScript, LN03, and HPe=                            printers can translate each bit in >                            a window pixel map into a grid of a@                            specified size. For example, each bit@                            might translate into a 3x3 grid. This=                            would be specified by -scale 3. By @                            default, a window is printed with theD                            largest scale that will fit onto the page9                            for the specified orientation.s  D           -height inches   Specifies the maximum height of the page.  C           -width inches    Specifies the maximum width of the page.x  ?           -left inches     Specifies the left margin in inches.s@                            Fractions are allowed. By default the:                            window is centered in the page.  E                                              (continued on next page)5       1-50 _  e      I                                                General User Release Notes I                              1.10 Window Dump to Print File (xpr) Utilitye    I               Table_1-1_(Cont.)_Window_Dump_to_Print_File_Options________   I               Option___________Description_______________________________   G               -top inches      Specifies the top margin for the picture @                                in inches. Fractions are allowed.  F               -header string   Specifies a header string to be printed0                                above the window.  G               -trailer string  Specifies a trailer string to be printed 0                                below the window.  A               -landscape       Forces the window to be printed intF                                landscape mode. By default, a window isG                                printed so that its longest side follows :                                the long side of the paper.  A               -portrait        Forces the window to be printed in D                                portrait mode. By default a window isG                                printed so that its longest side followsn:                                the long side of the paper.  E               -plane number    Specifies which bit plane to use in aneF                                image. The default is to use the entireH                                image and map values into black and white:                                based on color intensities.  A               -gray            Uses a 2x2, 3x3, or 4x4 gray scaletB                                conversion on a color image, ratherH                                than mapping to strictly black and white.G                                This doubles, triples, or quadruples the G                                effective width and height of the image.F  D               -rv              Forces the window to print in reverse%                                video.i  C               -compact         Uses run-length encoding for compactwC                                representation of windows with whiteo&                                pixels.  =               -output          Specifies an output file name.k               filename  H               -append          Specifies a file name previously producedB               filename         by xpr to which the window is to be(                                appended.  I                                                  (continued on next page)   I                                                                      1-51l e  t           General User Release Notes0     1.10 Window Dump to Print File (xpr) Utility    E           Table_1-1_(Cont.)_Window_Dump_to_Print_File_Options________   E           Option___________Description_______________________________   ?           -noff            When specified in conjunction with -gA                            append, the window appears on the samet7                            page as the previous window.o  A           -split n-pages   Allows the user to split a window ontoeE                            several pages. This might be necessary forpB                            very large windows that would otherwiseB                            cause the printer to overload and print9                            the page in an obscure manner.b  C           -psfig           Suppresses translation of the PostScripta=                            picture to the center of the page.o  D           -density dpi     Indicates dot-per-inch density to be used-                            by the HP printer.   C           -cutoff level    Changes the intensity level where colorshB                            are mapped to either black or white forC                            monochrome output on a LaserJet printer. B                            The level is expressed as percentage ofB                            full brightness. Fractions are allowed.  <           -noposition      Causes header, trailer, and image?                            positioning command generation to beo>                            bypassed for LaserJet, PaintJet and0                            PaintJet XL printers.  >           -gamma           Changes the intensity of the colorsB           correction       printed by the PaintJet XL printer. The?                            correction is a floating-point valueiA                            in the range 0.00 to 3.00. Consult the E                            operator's manual to determine the corrects:                            value for the specific printer.  <           -render          Allows the PaintJet XL printer toA           algorithm        render the image with the best qualityh?                            versus performance tradeoff. Consult A                            the operator's manual to determine theG0                            available algorithms.  E                                              (continued on next page)r       1-52 a  a      I                                                General User Release Notes I                              1.10 Window Dump to Print File (xpr) Utilityh    I               Table_1-1_(Cont.)_Window_Dump_to_Print_File_Options________t  I               Option___________Description_______________________________s  C               -slide filename  Allows overhead transparencies to benF                                printed using the PaintJet and PaintJetI               _________________XL_printers.______________________________   =               The program contains the following limitations:d  G               o  Support for PostScript output currently cannot use thes3                  -append, -noff, or -split options..  E               o  The -compact option is only supported for PostScriptoG                  output. It compresses white space but not black space,p?                  so it is not useful for reverse-video windows.n  C               o  For color images, map directly to PostScript imageb                  support.   7               Program limitations with an LN03 printer:w  I               o  The current version of xpr can print most X Windows that >                  are not larger than two-thirds of the screen.  G                  For example, the LN03 prints a large Emacs window, buta>                  fails when trying to print the entire screen.  A               o  The LN03 has memory limitations that cause it to-I                  incorrectly print large or complex windows. The two mostrE                  common errors encountered are "band too complex" andsE                  "page memory exceeded" and are described as follows:t  &                  -  "band too complex"  E                     A window may have a particular six pixel row thathE                     contains too many changes (from black to white tonG                     black). This causes the printer to drop part of the I                     line and possibly drop parts of the page. The printer G                     flashes the number "1" on its front panel when thisdG                     problem occurs. A possible solution to this problem G                     is to increase the scale of the picture or to split 7                     the picture onto two or more pages.u  *                  -  "page memory exceeded"  I                                                                      1-53  u  e           General User Release Notes0     1.10 Window Dump to Print File (xpr) Utility    B                 This occurs if the picture contains too much blackE                 space, or if the picture contains complex half-tones, D                 such as the background color of a display. When thisD                 problem occurs, the printer automatically splits theB                 picture onto two or more pages. The number "5" mayC                 flash on its front panel. As a possible solution toiD                 the problem, it might be necessary to either cut andD                 paste or to rework the application to produce a less                  complex picture.  3           Program limitations with a LA100 printer:2  <           o  The picture is always printed in portrait mode.  "           o  The scale is ignored.  E           o  The scale factor will be different in the horizontal and !              vertical directions.   1           Program limitations with an HP printer:   C           o  If the -density option is not specified, 300 dots-per- A              inch (dpi) is assumed for the ljet device and 90-dpirE              for the pjet device. The LaserJet printer supports 300-,dE              150-, 100-, and 75-dpi. Consult the operator's manual to A              determine the densities supported by other printers.   @           o  If the -scale option is not specified, the image is5              expanded to fit the printable page area.   D           o  The default printable page area is 8x10.5 inches. OtherB              paper sizes can be accommodated using the -height and              -width options.  B           o  Note that a 1024x768 image fits the default printableB              area when processed at 100-dpi with scale=1; the sameB              image can also be printed using 300-dpi with scale=3,?              but it requires more data to be transferred to then              printer.f  D           o  The xpr program may be tailored for use with monochrome@              PCL printers other than the LaserJet. To print on a@              ThinkJet (HP 2225A) printer, invoke xpr as follows:  2              xpr -density 96 -width 6.667 filename  C              To print black-and-white output on a PaintJet printer,o#              invoke xpr as follows:        1-54 r  s      I                                                General User Release NoteshI                              1.10 Window Dump to Print File (xpr) Utilitya    *                  xpr -density 180 filename  C               o  The monochrome intensity of a pixel is computed asrI                  0.30*R + 0.59*G + 0.11*B. If the computed intensity of a1G                  pixel is less than the -cutoff level, it prints white.tI                  This maps light-on-dark display images to black-on-whitevG                  hard copy. The default cutoff intensity is 50% of fullaG                  brightness. For example, specifying -cutoff 87.5 meansoH                  that a pixel will be displayed as black if the computed?                  intensity is less than 85% of full brightness.e  F               o  A LaserJet printer must be configured with sufficientH                  memory to print the image. To print a full page at 300-G                  dpi, approximately 2 MB of printer memory is required.d  E               o  Color images are produced on the PaintJet printer atgF                  90-dpi. The PaintJet is limited to 16 colors from itsI                  330 color palette on each horizontal print line. The xpr H                  program issues a warning message if more than 16 colorsI                  are encountered on a line. Xpr programs the PaintJet forhF                  the first 16 colors encountered on each line and usesG                  the nearest matching programmed value for other colors                   on the line.t  I               o  Specifying the -rv option on the PaintJet printer causestH                  black and white to be interchanged on the output image.-                  No other colors are changed.e  E               o  Multiplane images must be recorded by xwd in ZPixmap C                  format. Single-plane (monochrome) images may be in 3                  either XYPixmap or ZPixmap format.   E               o  Some PCL printers do not recognize image positioningoG                  commands. Output for these printers is not centered on H                  the page, and header and trailer strings may not appear                   where expected.  I               o  The -gamma and -render options are supported only on the &                  PaintJet XL printers.  I               o  The -slide option is not supported on LaserJet printers.   C               o  The -split option is not supported on HP printers.   I               o  The -gray option is not supported on HP or IBM printers.   I                                                                      1-55i x  a           General User Release Notes>     1.11 Keyboard Enhancements for Disabled Users (Alpha Only)    >     1.11 Keyboard Enhancements for Disabled Users (Alpha Only)  A     V1.2  On OpenVMS Alpha systems starting with DECwindows Motif A           Version 1.2 for OpenVMS, the AccessX extension providessE           features to help disabled users interact with workstations.d?           These features make it easier to use the keyboard andi?           mouse. You can interact with workstations by entering D           commands and manipulating menus and dialog boxes. However,E           with AccessX features, performing these input operations is            even easier.  B           A client application is provided to enable and customizeB           the AccessX features. To run this application, enter the           following commands:2  %           $ SET DEFAULT DECW$EXAMPLESh           $ RUN AccessX   E           Online help is available by selecting the Help menu option.e  @           AccessX offers the features described in the following           sections.        1.11.1 Sticky Keys  @           The Sticky Keys feature allows you to perform multikeyA           operations with one hand, one finger, or a mouth stick. @           You can use this feature to enter uppercase letters or@           punctuation characters without having to hold down theB           Shift key while pressing the character key. This featureB           also makes it easier to enter control characters such as           Ctrl/C.        1.11.2 Mouse Keysr  D           The Mouse Keys feature lets you map actions that you wouldA           perform with a mouse to keys on the numeric keyboard ornE           other keys that you specify. With this feature, you can usesE           one finger or a mouth stick to move the cursor to different E           areas of the screen, manipulate menus, and select, cut, and            paste text.              1-56           I                                                General User Release NotesLI                1.11 Keyboard Enhancements for Disabled Users (Alpha Only)d             1.11.3 Toggle Keys  F               The Toggle Keys feature provides audio feedback when theG               Shift Lock (Caps Lock) key is pressed. This feature helps G               users who might have difficulty seeing the keyboard lightxE               indicator for the Shift Lock key or users who are usingnG               a keyboard that does not provide light indicators for any                 keyboard settings.           1.11.4 Repeat Keys  D               The Repeat Keys feature allows you to adjust the auto-I               repeat keyboard mechanism speed or to turn it off entirely. G               With this feature turned on, you can set your keyboard sodI               that holding down a key for a longer than average time doese9               not cause a repeat entry of that character.r           1.11.5 Slow Keys  I               The Slow Keys feature makes the keys less likely to respond E               when brushed accidentally. With this feature turned on,eD               the computer accepts only keystrokes that are held forB               a certain length of time. The computer ignores light9               keystrokes that are held only for a moment.u           1.11.6 Bounce Keys  H               The Bounce Keys feature eliminates the problem of pressingB               a key and then accidentally pressing it again beforeI               moving to another key. You can set this feature to tell thewI               computer not to process a second pressing of a key unless a C               certain length of time elapses between each pressing.            1.11.7 Time Outd  F               The Time Out feature shuts off the AccessX features on aF               workstation after a specified period of time. If you areF               sharing a workstation and have set AccessX features, theH               settings are automatically turned off before the next use.G               To retain the AccessX settings at all times, you can turn_'               off the Time Out feature.         I                                                                      1-57                 General User Release Notes#     1.12 Printing from Applications     #     1.12 Printing from Applicationsr  @     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.  =           As a possible solution, either avoid displaying thedB           DECwindows print dialog, or define a print queue on yourB           system. The print queue does not have to be connected toD           a printer to accept print jobs. Assign a name to the printD           queue that indicates the print queue is not connected to a-           printer, for example, NULL_PRINTER.   <     1.13 Unsupported Translations by the Motif XmText Widget  B     V1.2- By default, the Motif XmText widget does not support theD     3     following translations for Versions 1.1, 1.2, and 1.2-3 of  '           the DECwindows Motif product:o  /              F12:           beginning-of-line()s2              F13:           delete-previous-word())              Ctrl e:        end-of-line() 2              Ctrl j:        delete-previous-word()/              Ctrl h:        beginning-of-line()a,              Ctrl r:        redraw-display()5              Ctrl u:        delete-to-start-of-line()r<              ~Ctrl ~Meta ~Shift Alt<Key>space: self-insert()  E           These translations are preferred by OpenVMS users to ensurew:           consistency with the DCL command line interface.  B           The DECwindows Motif for OpenVMS Session Manager defines?           translations so that they can be used by applications A           that are displayed to an OpenVMS display server. If youtA           display your applications on a different display servereC           (for example, on a PC or DIGITAL UNIX workstation), theser*           translations are not functional.  B           To enable these translations, add the following lines toA           your applications default file (for example, DECW$USER_n9           DEFAULTS:app_name.DAT or to the file DECW$USER_ "           DEFAULTS:XDEFAULTS.DAT):       1-58 e  a      I                                                General User Release Notes I                  1.13 Unsupported Translations by the Motif XmText Widget     3               *XmText.translations:   #override \n\_7                    <Key>F12:     beginning-of-line()\n\u:                    <Key>F13:     delete-previous-word()\n\1                    Ctrl<Key>e:   end-of-line()\n\p:                    Ctrl<Key>j:   delete-previous-word()\n\7                    Ctrl<Key>h:   beginning-of-line()\n\ 4                    Ctrl<Key>r:   redraw-display()\n\=                    Ctrl<Key>u:   delete-to-start-of-line()\n\iD                    ~Ctrl ~Meta ~Shift Alt<Key>space: self-insert()\n  H               You can copy the text for these translations from the file2               DECW$SYSTEM_DEFAULTS:DECW$LOGIN.DAT.  F               Enabling these translations does not affect the standardF               Motif translations, such as Alt-right for end-of-line or)               Ctrl-right for end-of-word.   F                 ________________________ Note ________________________  7                 If you add lines to the file DECW$USER_eD                 DEFAULTS:XDEFAULTS.DAT file, startup performance for6                 all applications is slightly degraded.  F                 ______________________________________________________  A         1.14 Spyglass Enhanced Mosaic Browser No Longer Supportedi  H         V1.2- The Spyglass Enhanced Mosaic browser is no longer providedA         5     with the DECwindows Motif software and is no longer   A               supported. If your system has a previous version of F               DECwindows Motif, the DECwindows Motif Version 1.2-5 forC               OpenVMS installation procedure removes this software.oF               Compaq suggests that you download the Netscape NavigatorE               browser from the DIGITAL OpenVMS Internet Solutions webt-               page at the following location:   D                  http://www.openvms.digital.com/openvms/products/ips  I               Fill out the customer registration form and then follow theh8               instructions for downloading the software.  F                 ________________________ Note ________________________  A                 On OpenVMS 7.2 systems, the Netscape Navigator is.C                 an option when installing the OpenVMS software. Thea@                 Netscape Navigator is not supported on VMS 5.5-2  I                                                                      1-59i w  m           General User Release Notes=     1.14 Spyglass Enhanced Mosaic Browser No Longer Supported_    C              systems. On these systems, you can use the NCSA Mosaic_(              Browser (see next section).  C              ______________________________________________________   -     1.15 NCSA Mosaic Browser (VMS 5.5-2 Only)   C     V1.2- DECwindows Motif for OpenVMS provides the National Center C     3     for Supercomputing Applications (NCSA) Mosaic Version 2.4   C           browser to let you navigate and access information on the            Internet.d  @           The NCSA Mosaic browser is provided as sample, "as is"@           software to introduce you to the Internet and help you@           get started using a World Wide Web viewer. Because theD           NCSA Mosaic browser that ships with this release is only aE           sample implementation, we have placed Mosaic with the other A           sample software in the DECW$UTILS directory. We plan to E           replace this sample NCSA Mosaic browser implementation in a            future release.r  =           The Mosaic browser enables OpenVMS users to search,e>           retrieve, display, store, and forward data using theB           Internet. Mosaic functions in conjunction with the WorldD           Wide Web environment, which is a collection of information           servers.  B           Note that the graphical user interface for Mosaic is notE           compliant with the Motif style guide; therefore, the Mosaicd@           browser does not look the same as the DECwindows Motif-           out-of-the-box (OOTB) applications.h  D           The following information about Mosaic is included in this           section:  5           o  Section 1.15.1, Starting Mosaic Software   1           o  Section 1.15.2, Creating a Home Page   E           o  Section 1.15.3, Configuring Mosaic to Process Multimedia               Files  ;           o  Section 1.15.4, Customizing the Mosaic Browser   ?           o  Section 1.15.5, Restrictions for Using Mosaic froms              Behind a Firewall       1-60 i         I                                                General User Release NotespI                                 1.15 NCSA Mosaic Browser (VMS 5.5-2 Only)     '         1.15.1 Starting Mosaic Softwaree  D         V1.2- The Mosaic browser, which is located in the DECW$UTILSI         3     directory, is installed as part of the product installation   ;               for the DECwindows Motif for OpenVMS product.n  G               To access the verb and start Mosaic, select Menus... from C               the Options Menu in FileView. Mosaic is listed in the E               Item Names list. Add the verb Mosaic to a menu, such as F               the Applications Menu, so that you can invoke Mosaic andG               display the DECwindows Motif for OpenVMS home page. Refer I               to Using DECwindows Motif for OpenVMS for information about $               adding verbs to menus.  F                 ________________________ Note ________________________  ?                 You can display the sample DECwindows Motif for D                 OpenVMS home page without a TCP/IP connection to theA                 network. However, to access information contained C                 in the topics in the Help menu requires that TCP/IPe2                 Services for OpenVMS be installed.  F                 ______________________________________________________  #         1.15.2 Creating a Home Page   C         V1.2- A home page lets you make information about yourself, A         3     your company, your products, and so on available on   E               the Internet. Click on the On HTML... topic in the Help E               menu for information about using HTML (Hypertext MarkupuG               Language) to create a home page. HTML uses markup tags tocH               tell Mosaic how to format text. A Beginner's Guide to HTMLI               is displayed, which provides information about markup tags, H               examples, formatting, creating links, troubleshooting, andE               so on. Note that you can access topics in the Help menuiD               only if your system is connected to the TCP/IP network0               using TCP/IP Services for OpenVMS.  G               As an example of an HTML source, see the DECwindows MotifTE               sample home page. Click on View Source... from the Fileo*               menu to see the HTML source.    I                                                                      1-61p t  o           General User Release Notes-     1.15 NCSA Mosaic Browser (VMS 5.5-2 Only)     9     1.15.3 Configuring Mosaic to Process Multimedia Files   C     V1.2- The Mosaic browser that is included with DECwindows Motif E     4     for OpenVMS provides support for recognizing and processingc  '           the following types of files:              o  GIF             o  Audio             o  MPEGn             o  MIME              o  PostScripth  C           If Mosaic encounters a hyperlink (or an anchor) to any of-D           these file types, it attempts to start an external programE           to display the image or to play the sound. If Mosaic cannot.D           locate an appropriate external viewer, it prompts the userC           to enter a file name where the data file can be stored int4           case the data is needed outside of Mosaic.  E           To determine what external viewer will display the image or 4           play the sound, Mosaic does the following:  D           1. Determines the MIME type of the incoming file according@              to either the file extension or the way the file is.              specified by the document server.  D              If the file extension is used to determine the externalE              viewer, Mosaic uses either a built-in default list or anrC              extension map file that can be configured by the user.a  ?           2. Matches the MIME file type of the incoming file to @              an external viewer according to either the built-inC              default list or a setup that is configured by the user D              and specified in the file DECW$UTILS:XMOSAIC-SETUP.COM.  A           For example, GIF files are mapped to the xv viewer. TheiC           xv viewer is shareware software that is not provided with B           DECwindows Motif. However, the xv viewer is available at?           the following Uniform Resource Locator (URL) address:   H               http://gatekeeper.dec.com/pub/net/infosys/pw/pw-fetch.html  C           The xv mapping is defined in the file DECW$UTILS:XMOSAIC-oE           SETUP.COM, a self-documented command procedure, as follows:   4                   $ XV   :== $DECW$EXAMPLES:PICT.EXE       1-62           I                                                General User Release NotesrI                                 1.15 NCSA Mosaic Browser (VMS 5.5-2 Only)t    F               The executable PICT.EXE is used to display the GIF file.G               Note that PICT.EXE cannot be used to display a JPEG file.e  3               Other mappings include the following:t  I               ___________________________________________________________ I               Image_Type____________Display/Sound_Logical_Name___________   1               audio/*               - > showaudioa  ,               image/xwd             - > xwud  ,               image/x-xwd           - > xwud  ,               image/x-xwindowdump   - > xwud  *               image/*               - > xv  I               application/postscript-_>_ghostview________________________t  C               Mappings in the previous list that are followed by anyC               asterisk (*) are available in some versions of MosaictG               (for example, Version 2.4) that contain native HDF/netCDFe               support.  D               Additional examples of external view setup in the fileD               DECW$UTILS:XMOSAIC-SETUP.COM can include the following               definitions:  J                 $ APLAY         :== mcr decsound -volume 70 -speaker -playJ                 $ SHOWAUDIO     :== mcr decsound -volume 70 -speaker -playG                 $ GHOSTVIEW     :== view/format=ps/interface=decwindows 8                 $ XWUD          :== $decw$utils:xwud.exe  -         1.15.4 Customizing the Mosaic Browser   A         V1.2- You can customize the Mosaic browser by setting any C         4     of the NCSA Mosaic X resources in the file DECW$USER_   "               DEFAULTS:MOSAIC.DAT.  H               The class name for Mosaic for X is Mosaic. The informationD               that follows shows the names and descriptions of the XH               resources. Note that class and resource names are the sameE               except that the first character in the resource name is                capitalized.  1               The following resources are listed:t  %               o  Functional resources   !               o  Visual resources                  o  Font resources   I                                                                      1-63a f  e           General User Release Notes-     1.15 NCSA Mosaic Browser (VMS 5.5-2 Only)     $           o  Proxy gateway resources             Functional Resources  D           Table 1-2 lists the functional resources and descriptions.  E           Table_1-2_Functional_Resources_____________________________h  E           Resource______________Description__________________________f  B           annotationsOnTop:     Indicates whether inlined documentC           Boolean               annotation hyperlinks are prepended <                                 to the document (if true) orB                                 postpended (if false). (Default is'                                 false).   A           autoPlaceWindows:     If set to false, the new DocumentlB           Boolean               View windows are not automaticallyA                                 positioned by the program itself;rB                                 your Window Manager determines the=                                 placement. (Default is true.)   E           catchPriorAndNext:    Controls whether using the keys Priors?           Boolean               and Next (Page Up and Page DownyA                                 on most keyboards) are explicitlyaB                                 caught in the Document View windowE                                 and passed to the vertical scrollbar,rD                                 or whether the normal Motif scrolled?                                 window mechanism is relied uponyB                                 to automatically take this action.3                                 (Default is false.)   @                                 If the Page Up and Page Down key=                                 sequences are not functioningyC                                 appropriately for your environment, D                                 set this resource to true. (Refer to@                                 the information about hot keys.)  D           confirmDeleteAnnotatioConfirms deleted annotations throughC           Boolean               a confirmation dialog box. (Defaultn)                                 is true.)n  E                                              (continued on next page)c         1-64           I                                                General User Release Notes I                                 1.15 NCSA Mosaic Browser (VMS 5.5-2 Only)s    I               Table_1-2_(Cont.)_Functional_Resources_____________________r  I               Resource______________Description__________________________   F               confirmExit: Boolean  Determines whether the NCSA MosaicC                                     browser pops up a dialog box toiD                                     confirm exiting from the programH                                     when the Exit Program menu option is@                                     selected. (Default is true.)  B               defaultAuthorName:    Identifies your full name (forB               string                example, John Q. Public). YourG                                     full name is normally stored in thepD                                     system password file, and MosaicG                                     extracts the name from that file iftE                                     this resource is NULL; otherwise, G                                     the value of this resource is used.s6                                     (Default is NULL.)  C               defaultHeight:        Specifies the default height innF               integer               pixels for a Document View window.5                                     (Default is 680.)   B               defaultHotlistFile:   Specifies a file name to storeE               string                the default hotlist (or a list of:E                                     bookmarks). (Default is ".mosaic-<B                                     hotlist-default". The value ofE                                     the environment variable $HOME isa>                                     prepended to this string.)  I               defaultWidth:         Specifies the default width in pixelsaH               integer               for a Document View window. (Default,                                     is 620.)  I                                                  (continued on next page)                     I                                                                      1-65r l  o           General User Release Notes-     1.15 NCSA Mosaic Browser (VMS 5.5-2 Only),    E           Table_1-2_(Cont.)_Functional_Resources_____________________   E           Resource______________Description__________________________   >           delayImageLoads:      Selects delayed image loading,D           Boolean               which is for users with slow networkC                                 connections. If set to true, Mosaic E                                 substitutes a small icon for inlined->E                                 images and an arrow icon for inlined-dC                                 images that also act as hyperlinks.(C                                 Clicking on an icon tells Mosaic to D                                 load that inlined-image; clicking onD                                 the arrow is equivalent to following9                                 the associated hyperlink.o  E                                 Selecting Load Images in Current fromEA                                 the Mosaic Options menu loads andtB                                 displays all the inlined-images inC                                 the current document. Delayed imagetE                                 loading can also be selected with the_C                                 -dil command-line flag or on a per-DE                                 window basis from the Options menu inm;                                 Mosaic. (Default is false.)e  ?           displayURLsNotTitles: Displays URLs wherever document_@           Boolean               titles are usually displayed, if@                                 set to true. (Default is false.)  B           DocsDirectory:        Overrides the location of the help=           string                documents. (Default is NULL.)   >           documentsMenuSpecfile:Specifies the name of the fileA           string                that holds an optional "Documentsn=                                 Menu Specfile" to allow sitest?                                 to add their own Documents menu @                                 to the Mosaic menu bar. For moreB                                 information, see the documentation=                                 about creating a configurablee;                                 Documents menu. (Default is H                                 "/usr/local/lib/mosaic/documents.menu".)  E                                              (continued on next page)S           1-66 e  a      I                                                General User Release Notes I                                 1.15 NCSA Mosaic Browser (VMS 5.5-2 Only)     I               Table_1-2_(Cont.)_Functional_Resources_____________________m  I               Resource______________Description__________________________w  E               fancySelections:      Cuts and pastes from the Document E               Boolean               View window with fancy selections E                                     enabled in the HTML widget, which B                                     results in underlined headers,H                                     bulleted lists, and so on, if set toH                                     true. Uses normal selection behaviorI                                     if set to false. Note that selections G                                     can be for each window at any time.a7                                     (Default is false.)   H               fullHostname: string  Allows explicit setting of the fullyH                                     qualified host name for systems thatF                                     fail on a call to gethostbyname().F                                     Use the fullHostname resource onlyE                                     if necessary, in conjunction withr8                                     gethostbynameIsEvil.  B               gethostbynameIsEvil:  Set to true if you are runningB               Boolean               your system on a Sun set up soA                                     that when the system attemptsaB                                     to find its own full host nameG                                     through gethostbyname(), the systemeB                                     coredumps. (Default is false.)  F               globalExtensionMap:   Set to the location of the system-B               string                wide extension map config file?                                     of your choice. (Default isaH                                     "/usr/local/lib/mosaic/mime.types".)  E               globalHistoryFile:    Specifies the name of the file to C               string                store the global history of allrF                                     documents accessed from session toH                                     session. (Default is .mosaic-global-I                                     history. The value of the environment G                                     variable $HOME will be prepended to 1                                     this string.)   I                                                  (continued on next page)r      I                                                                      1-67w o  M           General User Release Notes-     1.15 NCSA Mosaic Browser (VMS 5.5-2 Only)c    E           Table_1-2_(Cont.)_Functional_Resources_____________________t  E           Resource______________Description__________________________   E           globalTypeMap:        Specifies the location of the system-a>           string                wide mailcap (type map config)@                                 file of your choice. (Default isA                                 "/usr/local/lib/mosaic/mailcap".)   C           gunzipCommand:        Specifies the command to uncompress B           string                gzip files (that is, files with an@                                 extension of .z.) You can obtain>                                 gunzip from prep.ai.mit.edu inA                                 /pub/gnu. (Default is gunzip -n -tC                                 f, which requires the 1.2.4 version )                                 of gzip.)_  C           hdfMaxImageDimension: Specifies the maximum height and/or @           integer               width of an HDF inlined image in9                                 pixels. (Default is 400.)o  ?           hdfMaxDisplayedDatasetSpecifies the maximum number oftB           integer               displayed data sets while browsingC                                 HDF files. If more than the maximumsC                                 number exist in an HDF file, Mosaici?                                 displays the HDF file in "briefi7                                 mode". (Default is 15.)o  ?           hdfMaxDisplayedAttribuSpecifies the maximum number of.C           integer               displayed attributes while browsingyC                                 HDF files. If more than the maximumnC                                 number exist in an HDF file, MosaicT?                                 displays the HDF file in "briefa7                                 mode." (Default is 10.)   E           hdfPowerUser:         Set to true if most of the supporting D           Boolean               text in an HDF file will be removed.3                                 (Default is false.)n  @           homeDocument: string  Specifies the document to access;                                 at program startup. See thed?                                 information about on specifyingg?                                 your home document. (Default is M                                 http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/ 4                                 NCSAMosaicHome.html)  E                                              (continued on next page)s       1-68 o  a      I                                                General User Release NotesoI                                 1.15 NCSA Mosaic Browser (VMS 5.5-2 Only)h    I               Table_1-2_(Cont.)_Functional_Resources_____________________   I               Resource______________Description__________________________w  F               imageCacheSize:       Specifies the size of the inlined-C               integer               image cache in kilobytes. The -fE                                     ics command-line flag can also be C                                     used. All the images in a given.E                                     document are (temporarily) cachedlI                                     while on that page, regardless of the G                                     imageCacheSize value. Cache flushes G                                     the least recently viewed. (Default -                                     is 2048.)l  E               initialWindowIconic:  Set to true if the first Document H               Boolean               View window opened (when the programG                                     starts) will be iconified. (Default .                                     is false.)  B               maxWaisResponses:     Controls the maximum number ofG               integer               matches Mosaic accesses from a WAISe=                                     server. (Default is 200.)/  G               personalAnnotationDireSpecifies the name of the directoryI>               string                in which to store personalC                                     annotations (as well as the logID                                     file of all personal annotationsC                                     currently in existence). If the F                                     named directory does not exist, itE                                     is created. However, intermediateaB                                     directories, if any are named,@                                     are not created. (Default isE                                     .mosaic-personal-annotations. The_E                                     value of the environment variable C                                     $HOME will be prepended to this ,                                     string.)  A               personalExtensionMap: Specifies the location of the H               string                personal extension map configurationE                                     file of your choice. The value ofiD                                     the environment variable HOME isG                                     prepended. (Default is .mime.types)   I                                                  (continued on next page)   I                                                                      1-69  W  I           General User Release Notes-     1.15 NCSA Mosaic Browser (VMS 5.5-2 Only)     E           Table_1-2_(Cont.)_Functional_Resources_____________________   E           Resource______________Description__________________________   =           personalTypeMap:      Specifies the location of the E           string                personal mailcap file of your choice..E                                 The value of the environment variable >                                 HOME is prepended. (Default is)                                 .mailcap)   A           printCommand: string  Specifies the name of the defaultrB                                 command for the Print menu option.=                                 This command accepts a singlerA                                 argument: the name of the file to E                                 print. Note that this location can be E                                 changed at any time through the Print E                                 option's dialog box. (Default is lpr)e  A           recordCommandLocation:Specifies the location (full path C           string                name) of the command used to recorde?                                 audio annotations (on Sun, SGI,n?                                 and HP platforms). If the namediB                                 command does not exist when Mosaic=                                 is started, audio annotations_<                                 are disabled (the menu entry>                                 becomes insensitive). (DefaultA                                 is "/usr/sbin/recordaiff" on SGI; @                                 "/usr/demo/SOUND/record" on Sun;B                                 "/usr/audio/bin/srecorder" on HP.)  D           recordCommand:        Specifies the command used to recordC           string                audio annotations; this is the fulleC                                 command, using the command named inaB                                 recordCommandLocation as the first@                                 word. (Default is "recordaiff -n@                                 1 -s 8 -r 8000" on SGI; "record">                                 on Sun; "srecorder -au" on HP.B                                 The named command accepts a singleE                                 additional argument: the file name of)D                                 the new audio file. The command alsoE                                 correctly terminates recording when ac0                                 SIGINT is sent.)  E                                              (continued on next page)w       1-70 e  d      I                                                General User Release Notes I                                 1.15 NCSA Mosaic Browser (VMS 5.5-2 Only)     I               Table_1-2_(Cont.)_Functional_Resources_____________________e  I               Resource______________Description__________________________r  G               reloadReloadsImages:  Clears out the Reload option cached(G               Boolean               image data for the current document)H                                     before reloading the document if setG                                     to true; thus causing the images to H                                     also be reloaded. This is useful forH                                     HTML authors who are using Mosaic toH                                     view their work. (Default is false.)  G               sendmailCommand:      Specifies a pointer to the sendmail H               string                binary. It assumes that this programG                                     accepts command-line arguments that_G                                     specify addresses to which messagesoF                                     should be mailed and accepts otherH                                     headers and message text from stdin.E                                     (Default is "/usr/lib/sendmail".)s  I               simpleInterface:      Allows the Mosaic menu bar and bottom H               Boolean               button configuration to be minimizedE                                     considerably. (Default is false).   G               tmpDirectory: string  Specifies the name of the directory E                                     in which to store temporary files G                                     generated by Mosaic. This directory D                                     should contain at least 10 or 20I                                     megabytes, in case you to pull down a F                                     very large data file. Setting thisC                                     resource is equivalent to using F                                     the command-line flag, -tmpdir, orD                                     setting the environment variable+                                     TMPDIR.   F               trackFullURLs:        Enables prototypical smart displayB               Boolean               of "where you're going" duringD                                     mouse tracking, including formatI                                     definition, if set to false. (Default -                                     is true.)   I                                                  (continued on next page)       I                                                                      1-71                 General User Release Notes-     1.15 NCSA Mosaic Browser (VMS 5.5-2 Only)     E           Table_1-2_(Cont.)_Functional_Resources_____________________   E           Resource______________Description__________________________   A           trackPointerMotion:   Sets the mouse pointer so that it-D           Boolean               will not be tracked so that URLs areD                                 visible on the lower status line, if@                                 set to false. (Default is true.)  B           trackVisitedAnchors:  Displays visited anchors (that is,D           Boolean               anchors that point to documents thatC                                 have previously been viewed) with a E                                 different style than anchors that are D                                 not yet visited, if set to true. (OnD                                 slow systems, changing this resourceB                                 to false may substantially improveD                                 the performance of Mosaic.) (Default)                                 is true.)r  B           tweakGopherTypes:     Mosaic interprets Gopher documentsE           Boolean               strictly by the Gopher typing system,dB                                 if set to false. When set to true,@                                 Mosaic uses its own mechanism toB                                 determine the file types of Gopher=                                 documents. (Default is true.)n  E           twirlIncrement:       Indicates the minimum number of bytesh@           integer               that are are transferred between@                                 updates of the twirling transferC                                 icon for normal (FTP, Gopher, HTTP)d=                                 transfers. (Default is 4096.)a  E           twirlingTransferIcon: Set to false to turn off the twirlingoD           Boolean               NCSA logo during document transfers.D                                 Clicking the icon still interrupts a<                                 transfer. (Default is true.)  C           uncompressCommand:    Specifies the command to uncompress @           string                compressed files (that is, filesE                                 with an extension of .Z). (Default is ,                                 uncompress).  E                                              (continued on next page)a         1-72           I                                                General User Release NotessI                                 1.15 NCSA Mosaic Browser (VMS 5.5-2 Only)     I               Table_1-2_(Cont.)_Functional_Resources_____________________   I               Resource______________Description__________________________   D               useDefaultExtensionMapSet to false to keep any defaultH               Boolean               file-extension-to-MIME-type mappingsF                                     from Mosaic. Keeping this resourceF                                     setting to true and overriding theD                                     default as necessary is stronglyC                                     recommended. (Default is true.)h  D               useDefaultTypeMap:    Set to false to keep any default@               Boolean               MIME-type-to-external-viewerH                                     mappings from Mosaic. It is stronglyC                                     recommended that you leave thishF                                     resource set to true; override theE                                     setting as necessary. (Default is.*                                     true.)  I               useGlobalHistory:     Automatically stores a global historyfC               Boolean               of everywhere you visit, if setaE                                     to true. (This history is used tosE                                     shade anchors in different colorsfD                                     based on whether you visited theC                                     corresponding documents, if theuG                                     resource trackVisitedAnchors is seta@                                     to true.) (Default is true.)  E               xtermCommand: string  Specifies the name of the commandlG                                     used to start a terminal window fortG                                     a telnet session. (Default is xtermlE                                     on most platforms; the default issI               ______________________aixterm_-v_on_IBM_AIX_3.x_systems.)__                  Visual Resources  F               Table 1-3 lists the visual resources that are associatedD               with the HTML widget that is used in the Document ViewD               window. Specify these resources in the file DECW$USER_:               DEFAULTS:MOSAIC.DAT in the following format:          I                                                                      1-73e o  (           General User Release Notes-     1.15 NCSA Mosaic Browser (VMS 5.5-2 Only)     %              Mosaic*anchorColor: cyan   E           Table_1-3_Visual_Resources_________________________________   E           Resource______________Description__________________________   D           anchorColor: color    Specifies the color to shade anchorsB                                 whose corresponding documents haveE                                 not previously been visited. (Default *                                 is blue3.)  D           visitedAnchorColor:   Specifies the color to shade anchorsB           color                 whose corresponding documents haveD                                 previously been visited. (Default is,                                 violetred4.)  D           activeAnchorFG:       Specifies the color to shade anchors@           color                 that are in the process of being<                                 activated. (Default is red.)  @           activeAnchorBG:       Specifies the color to shade theB           color                 background of the anchors that areB                                 in the process of being activated.@                                 (Default is grey80, which is theC                                 same color as the background in the )                                 browser.)M  @           anchorUnderlines:     Specifies the number of lines to=           integer               draw underneath the unvisited B                                 anchors (Valid values: 0, 1, 2, 3)/                                 (Default is 1.)   E           visitedAnchorUnderlineSpecifies the number of lines to draw E           integer               underneath the visited anchors. Valid B                                 values: 0, 1, 2, 3 (Default is 1.)  D           dashedAnchorUnderlinesSets drawn lines under the unvisitedB           Boolean               anchors to dashes, if set to true.3                                 (Default is false.)   @           dashedVisitedAnchorUndSetsndrawn lines under unvisitedB           Boolean               anchors to dashes, if set to true.3                                 (Default is false.)l  E                                              (continued on next page)e       1-74           I                                                General User Release NotesoI                                 1.15 NCSA Mosaic Browser (VMS 5.5-2 Only)n    I               Table_1-3_(Cont.)_Visual_Resources_________________________n  I               Resource______________Description__________________________   I               colorsPerInlinedImage:Specifies the number of unique colors G               integer               to allocate for each inlined-image. D                                     (Note that this setting does notH                                     affect the images that are displayedI                                     externally to the NCSA Mosaic browsertI                                     (for example, GIF images passed to an G                                     external viewer).) (Default is 50.)   H               percentVerticalSpace: Specifies the height of the verticalI               integer               space between paragraphs, headers andrG                                     paragraphs, and so on, as expressedmF                                     as a percentage of the normal line<                                     height. (Default is 90.)  G               reverseInlinedBitmapCoSpecifies to reverse foreground and D               Boolean               background colors in inlined XBMH                                     bitmaps, if set to true. (Default is+                                     false.)a  D               verticalScrollOnRight:Specifies that the Document ViewG               Boolean               window places its scroll bar on thevH                                     left side, if set to false. (DefaultI               ______________________is_true.)____________________________                  Font Resources  E               Font resources, which are also associated with the HTMLsG               widget, can be changed dynamically from the Options menu.lG               Table 1-4 lists the font resource names and descriptions.f  I               Table_1-4_Font_Resources___________________________________   I               Resource_______Description_________________________________   G               font: font     Used in normal formatted text. (Default istV                              "-adobe-times-medium-r-normal-*-17-*-*-*-*-*-iso8859-1".)  G               italicFont:    Used in italic formatted text. (Default islV               font           "-adobe-times-medium-i-normal-*-17-*-*-*-*-*-iso8859-1".)  I                                                  (continued on next page)   I                                                                      1-75                 General User Release Notes-     1.15 NCSA Mosaic Browser (VMS 5.5-2 Only)     E           Table_1-4_(Cont.)_Font_Resources___________________________i  E           Resource_______Description_________________________________f  A           boldFont:      Used in bold formatted text. (Default is P           font           "-adobe-times-bold-r-normal-*-17-*-*-*-*-*-iso8859-1".)  C           fixedFont:     Used in fixed (typewriter style) formatted f           font           text. (Default is "-adobe-courier-medium-r-normal-*-17-*-*-*-*-*-iso8859-1".)  =           header1Font:   Used in level 1 headers. (Default is P           font           "-adobe-times-bold-r-normal-*-24-*-*-*-*-*-iso8859-1".)  =           header2Font:   Used in level 2 headers. (Default is P           font           "-adobe-times-bold-r-normal-*-18-*-*-*-*-*-iso8859-1".)  =           header3Font:   Used in level 3 headers. (Default isrP           font           "-adobe-times-bold-r-normal-*-17-*-*-*-*-*-iso8859-1".)  =           header4Font:   Used in level 4 headers. (Default is P           font           "-adobe-times-bold-r-normal-*-14-*-*-*-*-*-iso8859-1".)  =           header5Font:   Used in level 5 headers. (Default isgP           font           "-adobe-times-bold-r-normal-*-12-*-*-*-*-*-iso8859-1".)  =           header6Font:   Used in level 6 headers. (Default is P           font           "-adobe-times-bold-r-normal-*-10-*-*-*-*-*-iso8859-1".)  q           addressFont:   Used in addresses. (Default is "-adobe-times-medium-i-normal-*-17-*-*-*-*-*-iso8859-1".)o           font  B           plainFont:     Used in plaintext regions or preformattedk           font           documents. (Default is "-adobe-courier-medium-r-normal-*-14-*-*-*-*-*-iso8859-1".).  =           listingFont:   Used in listing regions. (Default is T           font           "-adobe-courier-medium-r-normal-*-12-*-*-*-*-*-iso8859-1".)  B           fixedboldFont: Used for bold in fixed (typewriter style)(           font           formatted text.  E           fixeditalicFontUsed for italics in fixed (typewriter style) (           font           formatted text.  >           plainboldFont: Used for bold in plaintext regions or0           font           preformatted documents.  @           plainitalicFontUsed for italic in plaintext regions orE           font___________preformatted_documents._____________________u  !           Proxy Gateway Resources   >           When your proxy gateway has been established by yourE           network or system administrator, you can use its resources.sC           Table 1-5 provides additional details about proxy gatewayu9           support in the NCSA Mosaic Version 2.4 browser.        1-76    m      I                                                General User Release NoteseI                                 1.15 NCSA Mosaic Browser (VMS 5.5-2 Only)a    I               Table_1-5_Proxy_Gateway_Resources__________________________   I               Resource______________Description__________________________   6               ftpProxy: String      Used for ftp URLs.  9               gopherProxy: String   Used for gopher URLs.   7               httpProxy: String     Used for http URLs.   7               newsProxy: String     Used for news URLs.a  7               waisProxy: String     Used for wais URLs.   I               ProxyGateway:_String__Used_for_all_access_methods._________i  C         1.15.5 Restrictions for Using Mosaic from Behind a Firewall   H         V1.2- The following sections present information about using theF         3     ProxyGateway and NoProxy resources with Mosaic to access  D               information on the Internet when security restrictionsG               (that is, a firewall) exist between internal and externalu*               network access at your site.  &         1.15.5.1 ProxyGateway Resource  F               NCSA Mosaic Version 2.4 provided in DECwindows Motif forI               OpenVMS supports the proxy gateway (ProxyGateway) resource.eG               A proxy gateway is a trusted agent that enables Mosaic totI               access network information that is either within or outsiden)               the firewall, but not both.   E               When the Mosaic browser is used from behind a firewall, G               Mosaic can use the proxy gateway to pass network requests C               to the Internet in a URL formatted address. The proxyaD               gateway returns the results to the Mosaic browser. TheB               process of passing and returning network requests isD               transparent to the user. You can view documents on the*               Internet without difficulty.  I               Note, however, that if the proxy gateway is located outsideaD               of your firewall, then information behind the firewallF               (such as home pages, World Wide Web documents, and Notes=               files) cannot be accessed by the proxy gateway.o  I                                                                      1-77n n  u           General User Release Notes-     1.15 NCSA Mosaic Browser (VMS 5.5-2 Only)          1.15.5.2 NoProxy Resourceo  >           If your site requires the ability to access InternetB           information both within and outside the firewall, then aA           version of Mosaic that supports the NoProxy resource is A           required. This resource allows you to specify a list of C           domains that should not be consulted by the proxy gateway C           (that is, access to information in these domains does noth(           go through the proxy gateway).  C           NCSA Mosaic Version 2.4a for OpenVMS supports the NoProxy A           resource and enables access to a proxy gateway. If your A           site operates in a firewall environment and you need to @           access information from both within and outside of theC           firewall, you can copy this pre-release version of Mosaic'!           from the following URL:   5              ftp://gatekeeper.dec.com/pub/DEC/Mosaic/   E           As previously stated, the NoProxy resource restricts access @           for the proxy gateway to a set of domains that are notE           consulted by the proxy gateway. You can specify the NoProxy C           resource, provided that you have NCSA Mosaic Version 2.4a @           for OpenVMS, in the file DECW$USER_DEFAULTS:MOSAIC.DAT,           according to the following format:  F                Mosaic*ProxyGateway:    http://www-proxy.site.org:8080/:                Mosaic*NoProxy:         localhost, site.org  E           ___________________________________________________________ E           Where:________________Description__________________________   D           www-proxy.site.org    Name of the host that runs the proxy&                                 server  @           8080                  Port number through which Mosaic@                                 communicates to the proxy server4                                 through the firewall  =           local host, site.org  List of site names, which are B                                 separated by commas, excluded fromE           ______________________going_through_the_proxy_server_______   >           Refer to the following location (URL) for additional+           information about proxy gateways:   D             http://info.cern.ch/hypertext/WWW/Daemon/user/Guide.html       1-78                         I                                                                         2 I         _________________________________________________________________   I                                              System Manager Release Notes     A               This chapter contains system manager release notes.   1         2.1 Recommended Reboot After Installation   I         V1.2- Although system parameters are correct, it may be necessary H         4     to reboot the system after installing DECwindows Motif for                 OpenVMS.  C               If the DECwindows login box does not appear after younF               install DECwindows Motif and restarting DECwindows MotifE               with the command @SYS$MANAGER:DECW$STARTUP RESTART, you -               will need to reboot the system.u  7         2.2 Log Off Console Before DECwindows Can Startl  I         V1.2- If DECwindows is not started during OpenVMS startup, it caniF         4     be started later by running SYS$MANAGER:DECW$STARTUP.COM  A               from a system account. Perform the following steps:   F               1. Define the logical name DECW$IGNORE_DECWINDOWS with a@                  value of TRUE in SYS$STARTUP:SYSTARTUP_VMS.COM.  #               2. Reboot the system.   H               3. When system startup has completed, press Return and log/                  in to the workstation console.   C               4. After logging in, start DECwindows by invoking the F                  SYS$MANAGER:DECW$STARTUP.COM command procedure, as in'                  the following example:u  ,                  $ @SYS$MANAGER:DECW$STARTUP  F                 ________________________ Note ________________________  E                 Once DECW$STARTUP.COM has completed, you must log out @                 of the console in order for DECwindows to start.  F                 ______________________________________________________  I                                                                       2-1                  System Manager Release NotesA     2.3 Installation Verification Procedure Error in UIL Compiler(    A     2.3 Installation Verification Procedure Error in UIL Compilert  @     V1.2- If you installed a previous version of DECwindows (forB     5     example, V1.2-4) without using the PCSI_INSTALLATION.COM  B           procedure, you might get this error. Enter the followingB           code into a command file and run it. This will check for7           .CLD files. If it finds any, it deletes them:        $ VAX   = 1c     $ Alpha = 2i"     $ ARCH = F$Getsyi("ARCH_TYPE")     $!G     $! See if the user wants the New Desktop to be the default desktop.i     $!3     $ if ARCH .ne. Alpha then goto skip_new_desktop      $ type sys$input  L       The New Desktop is a graphical user interface that is derived from theM       Common Desktop Environment (CDE).  It offers the following features not 8       available with the traditional DECwindows desktop:  P             o Multiple workspaces for greater flexibility in managing windows on               the screen.i  N             o An icon-based File Manager to make it easier to manipulate files0               from the graphical user interface.  L             o Enhanced support for the drag-and-drop feature, which is fullyG               supported in the new File Manager and Application Manageri               applications. >               o New Image Viewer and Icon Editor applications.  Q       Both the New Desktop and the DECwindows desktop provide the same underlying P       X and Motif libraries and the same DECterm, Bookreader, Mail, and Calendar       applications.                        2-2g t         I                                              System Manager Release NoteseI             2.3 Installation Verification Procedure Error in UIL Compiler:    "         $ inquire/nopunct answer -L            "Do you want the New Desktop to be your default desktop ([y]/n)?"0         $ if answer .eqs. "" then answer = "yes"         $ ! O         $ ! Create the decw$default_desktop.com file on the destination device.s         $ !_-         $ dest = "sys$sysdevice:[vms$common]"_2         $ sysmgr_dir = f$search(dest+"SYSMGR.DIR")4         $ sysmgr_node = f$parse(sysmgr_dir,,,"NODE")8         $ sysmgr_device = f$parse(sysmgr_dir,,,"DEVICE")Q         $ sysmgr_directory = f$parse(sysmgr_dir,,,"DIRECTORY") - "]" + ".SYSMGR]".D         $ dname = sysmgr_node + sysmgr_device + sysmgr_directory + -*                 "DECW$DEFAULT_DESKTOP.COM";         $ if f$search(dname) .nes. "" then delete 'dname';*d1         $ open/write/error=dopenerr dfile 'dname'          $ if answereC         $   then write dfile "$ DECW$START_NEW_DESKTOP == ""TRUE""" D         $   else write dfile "$ DECW$START_NEW_DESKTOP == ""FALSE"""         $ endif          $ close dfile >         $ set protection=(sy:rwed,ow:rwed,gr:re,wo:re) 'dname'         $ goto skip_new_desktope         $dopenerr:         $ write sys$output "" =         $ write sys$output "  WARNING: Can't create ''dname'"e         $ write sys$output ""          $skip_new_desktop:
         $!6         $! Update [SYSLIB]DCLTABLES.EXE with new verbs
         $!         $ create_new_dcltable:L         $ IF f$search("SYS$SYSROOT:[SYSLIB]DECW$UILCOMPILER.CLD") .EQS. "" -            THEN GOTO skip_uil ?         $ SET COMMAND/tables=SYS$COMMON:[SYSLIB]DCLTABLES.EXE - 8               /output=SYS$COMMON:[SYSLIB]DCLTABLES.EXE -6               SYS$SYSROOT:[SYSLIB]DECW$UILCOMPILER.CLD         $!$ skip_uil:fW         $ IF f$search("SYS$COMMON:[SYSLIB]ddif$view.cld")  .EQS. "" THEN GOTO skip_view ?         $ SET COMMAND/tables=SYS$COMMON:[SYSLIB]DCLTABLES.EXE -i8               /output=SYS$COMMON:[SYSLIB]DCLTABLES.EXE -.               SYS$COMMON:[SYSLIB]ddif$view.cld
         $!         $skip_view:t    I                                                                       2-3                  System Manager Release NotesA     2.3 Installation Verification Procedure Error in UIL Compiler     R     $ IF f$search("SYS$COMMON:[SYSLIB]pswrap.cld")  .EQS. "" THEN GOTO skip_pswrap;     $ SET COMMAND/tables=SYS$COMMON:[SYSLIB]DCLTABLES.EXE - 4           /output=SYS$COMMON:[SYSLIB]DCLTABLES.EXE -'           SYS$COMMON:[SYSLIB]pswrap.cld      $skip_pswrap:      $!     $! Install the DCLTABLES     $!     $ set noon(     $ INSTALL LIST SYS$LIBRARY:DCLTABLES     $ status = $status1     $ if status .eq. %X10000001 !%SYSTEM-S-NORMAL_
     $ thenI     $   INSTALL REPLACE SYS$LIBRARY:DCLTABLES/OPEN/HEADER_RESIDENT/SHARED      $ endifo     $ set on                                                               2-4            I                                              System Manager Release NotesNI                  2.4 Problem With Delayed DECwindows Startup (Alpha Only)t    @         2.4 Problem With Delayed DECwindows Startup (Alpha Only)  G         V1.2- On OpenVMS Alpha systems, error messages similar to thoser6         4     shown in Example 2-1 are displayed when:  E               o  Shareable address linkage is being used (the defaultc                  setting).  H               o  DECwindows is not started as part of system startup but"                  is started later.  E               These error messages are generated because there is not F               enough memory in the granularity hints region to installD               images resident. The images are installed nonresident,G               without shared address linkage, so DECwindows startup can I               complete. However, the performance and memory advantages of 4               using shared address linkage are lost.  B               The amount of memory in the granularity hints regionD               is determined by the system parameter GH_RSRVPGCNT. InD               DECwindows Motif Version 1.2-3 for OpenVMS and earlierD               versions, this parameter was set to 512, which allowedA               DECwindows to start at any time with shared address D               linkage. However, this also consumed a large amount of               physical memory.  F               To prevent memory from being wasted, OpenVMS temporarilyG               increases the size of the granularity hints region during H               system startup and releases the unused memory once startupI               has completed. Starting with DECwindows Motif Version 1.2-4_E               for OpenVMS DECwindows Motif takes advantage of this byuE               allowing GH_RSRVPGCNT to remain at its default value of-H               zero. DECwindows images can be installed resident and withE               shared address linkage as long as DECwindows is startedd9               during system startup, as it is by default.   A         Example 2-1 Error Messages Displayed Due to Low Memory in ,                     Granularity Hints Region  I                                                  (continued on next page)N          I                                                                       2-5_ _  _            System Manager Release Notes<     2.4 Problem With Delayed DECwindows Startup (Alpha Only)    E     Example 2-1 (Cont.) Error Messages Displayed Due to Low Memory int0                         Granularity Hints Region  S     %INSTALL-I-FAIL, failed to create shared linkage entry for DISK$ALPHASYS:<SYS0. T      -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint re  P     %INSTALL-I-NONRES, installed image non-resident with other specified optionsT      -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint re  A     %RUN-S-PROC_ID, identification of created process is 00000092   A     %RUN-S-PROC_ID, identification of created process is 00000093-  S     %INSTALL-I-FAIL, failed to create shared linkage entry for DISK$ALPHASYS:<SYS0. T      -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint re  P     %INSTALL-I-NONRES, installed image non-resident with other specified optionsT      -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint re  S     %INSTALL-I-FAIL, failed to create shared linkage entry for DISK$ALPHASYS:<SYS0.-.      -SYSTEM-F-PAGOWNVIO, page owner violation3      -SYSTEM-S-NORMAL, normal successful completion 0      -DEBUG-W-NOIOCHAN, no I/O channel available  P     %INSTALL-I-NONRES, installed image non-resident with other specified optionsT      -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint re  S     %INSTALL-I-FAIL, failed to create shared linkage entry for DISK$ALPHASYS:<SYS0.f8      -SYSTEM-F-VA_IN_USE, virtual address already in use3      -SYSTEM-S-NORMAL, normal successful completiong0      -DEBUG-W-NOIOCHAN, no I/O channel available  P     %INSTALL-I-NONRES, installed image non-resident with other specified optionsT      -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint re  S     %INSTALL-I-FAIL, failed to create shared linkage entry for DISK$ALPHASYS:<SYS0.o8      -SYSTEM-F-VA_IN_USE, virtual address already in use3      -SYSTEM-S-NORMAL, normal successful completion 0      -DEBUG-W-NOIOCHAN, no I/O channel available  P     %INSTALL-I-NONRES, installed image non-resident with other specified optionsT      -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint re  S     %INSTALL-I-FAIL, failed to create shared linkage entry for DISK$ALPHASYS:<SYS0.d8      -SYSTEM-F-VA_IN_USE, virtual address already in use3      -SYSTEM-S-NORMAL, normal successful completion 0      -DEBUG-W-NOIOCHAN, no I/O channel available  E                                              (continued on next page)        2-6n l  e      I                                              System Manager Release Notes.I                  2.4 Problem With Delayed DECwindows Startup (Alpha Only)_    I         Example 2-1 (Cont.) Error Messages Displayed Due to Low Memory in_4                             Granularity Hints Region  T         %INSTALL-I-NONRES, installed image non-resident with other specified optionsX          -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint re  W         %INSTALL-I-FAIL, failed to create shared linkage entry for DISK$ALPHASYS:<SYS0. <          -SYSTEM-F-VA_IN_USE, virtual address already in use7          -SYSTEM-S-NORMAL, normal successful completion 4          -DEBUG-W-NOIOCHAN, no I/O channel available  T         %INSTALL-I-NONRES, installed image non-resident with other specified optionsX          -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint re  =         2.5 DECwindows Motif Login Screen-Known Color Probleml  C         V1.2  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.aF               A DECW$LOGIN.DAT file in SYS$COMMON:[DECW$DEFAULTS.USER]F               prevents the "*background:" resource from being defined;6               thus, it will default to the color blue.  F               Compaq provides a copy of the DECW$LOGIN.DAT file in theI               SYS$COMMON:[DECW$DEFAULTS.SYSTEM] directory. Any customizedeF               versions of this file should reside only in SYS$MANAGER.  -         2.6 System Tuning for Non-VGA Devicese  @         V1.2  The DECwindows server requires specific tuning forG               graphics-intensive and 3D applications because of greater G               demand for system resources. You need to make adjustments D               for server quotas on 3D accelerated systems. These areH               minimum values suggested for a system with as little as 64D               MB of physical memory and for running complex clients.  C               Use the AUTHORIZE utility to set the following SYSTEMSF               account quotas to the minimum values shown in Table 2-1.          I                                                                       2-7o o  w            System Manager Release Notes)     2.6 System Tuning for Non-VGA Devicesh    E           Table_2-1_Recommended_Quotas_for_System_Tuning_____________c  E           Parameter______Value_______________________________________x             FILLM          400             ENQLM          1024m             WSDEF          10240             WSQUO          16384             WSEXTENT[1]    20480             PGFLQUO[2]     270000 
           [3]eE           [1]This_value_cannot_exceed_WSMAX._________________________a  >           [2]PAGEFILE.SYS must be of the same or greater size.9           [3]Use for 370000 for ZLX-E and ZLXp-E systems. E           ___________________________________________________________l  7           The server has its own quotas that are set inE;           SYS$COMMON:[SYSMGR]DECW$PRIVATE_SERVER_SETUP.COM.o4           If this file does not exist, copy the file;           SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE toe@           SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM and edit the/           file to include the following values:   E           ___________________________________________________________ E           Quota______________________Value___________________________w  (           DECW$SERVER_FILE_LIMIT     400  )           DECW$SERVER_ENQUEUE_LIMIT  1024   *           DECW$SERVER_WSDEF          10240  *           DECW$SERVER_WSQUOTA        16384  *           DECW$SERVER_WSEXTENT       20480  +           DECW$SERVER_PAGE_FILE[1]   270000gE           [1]Use_for_370000_for_ZLX-E_and_ZLXp-E_systems.____________   E           ___________________________________________________________a  <           If you use larger values, you must also modify theC           corresponding SYSTEM account quotas that you set with the            AUTHORIZE utility.       2-8s h         I                                              System Manager Release Notes I                                     2.6 System Tuning for Non-VGA Devices     /               Tuning for Animation Applications   I               If your application involves lengthy animation sequences ofcH               large models or assemblies, performance may be improved byB               setting the following working set quotas and values:  I               ____________________________________________________________I               Parameter______Value_______________________________________e  "               WSDEF          10240  "               WSQUO          20480  I               WSEXTENT_______32768_______________________________________2                                                              I                                                                       2-9                  System Manager Release Notes)     2.6 System Tuning for Non-VGA Devices     E           You need to set the corresponding server quotas as follows:f  E           ___________________________________________________________ E           Quota______________________Value___________________________o  *           DECW$SERVER_WSDEF          10240  *           DECW$SERVER_WSQUOTA        20480  E           DECW$SERVER_WSEXTENT_______32768___________________________E  C              ________________________ Note ________________________f  A              The parameters should not be tuned upward unless youO5              have at least 128 MB of physical memory.   C              ______________________________________________________   "           Determining Tuning Needs  A           To determine whether you need to set larger parameters,s@           monitor the server process during the heaviest display>           usage. If the working set use approaches the maximum@           WSEXTENT, then you need to adjust the values. However,D           do not set large values unless it is necessary. If you setE           these values too high, performance may be degraded. Optimal >           DECwindows server performance depends on application           demands.  A           Use the SYSGEN utility to issue the SHOW VIRTUALPAGECNT_?           command to determine the current virtual page count a E           process is allowed to have. If it is less than 525000, edit A           the SYS$SYSTEM:MODPARAMS.DAT file and add the followingo           line:   (              MIN_VIRTUALPAGECNT = 525000  >           Note that the minimum value for VIRTUALPAGECNT for aE           working X server needs to be 525000 when a ZLX-E or a ZKXp--@           E graphics card is installed. MIN_VIRTUALPAGECNT couldB           be set as high as the equivalent of your total available.           physical memory and page file space.  E           MIN_WSMAX must be at least as large as the largest WSEXTENT A           value set from among your accounts. Please refer to the B           OpenVMS System Manager's Manual for more information. DoE           not exceed what AUTOGEN gives for WSMAX. See the warning in            the AUTOGEN report.        2-10 a  c      I                                              System Manager Release Notes)I                                     2.6 System Tuning for Non-VGA Devicesn    F               The next time you run AUTOGEN and reboot, the new valuesF               will take effect. VIRTUALPAGECNT should not be less thanH               the sum of your WSEXTENT and PGFLQUO, or the server cannotC               make full use of the quotas. In addition, you need todC               increase the size of the page file to accommodate the G               pagefile quotas of both the server and your clients. Note G               that pagefile quota for the server is derived from systemi               page files.D  G               If, after initial tuning and considerable use, the server E               is failing or is unnecessarily unresponsive, the server B               may have run out of memory or memory may have becomeB               fragmented. A particularly demanding application mayF               require that you give the server even larger PGFLQUO and$               VIRTUALPAGECNT values.  I               If the server error log SYS$MANAGER:DECW$SERVER_0_ERROR.LOGyE               contains the statement xxx: Out of memory, increase the G               pagefile quota for the server. Set this by modifying botheH               system quota PGFLQUO and DECW$PRIVATE_SERVER_SETUP.COM and?               virtual page count via MODPARAMS.DAT and AUTOGEN.n  D               Note that, in multiheaded configurations (for example,G               ZLX-E1 and ZLX-E2), the PGFLQUO and the DECW$SERVER_PAGE_DE               FILE parameters should be increased to meet your systemd               requirements.   3               System Hangs With Some Graphics Cardsf  H         V1.2- On systems with Powerstorm 4d20 or ZLXp-E2 graphics cards,H         5     the operating system may hang or become extremely sluggish  D               if you have a large number of open application windowsF               or if certain CDA documents are opened. To verify that aI               system hang is caused by this problem, use the Watch Errors D               utility in the Desktop Tools drawer of the ApplicationE               Manager. If the system hang is due to this problem, youn%               will see the following:   :               -> RCV'D (pid nnnnnnnn): RCV'D (pid nnnnnnnn\               %SYSTEM-F-EXBUFOBJLM, exceeded systemwide buffer object page limit (MAXBOBMEM):               -> RCV'D (pid nnnnnnnn): RCV'D (pid nnnnnnnn7               SYSTEM logged out at dd-mmm-yyyy hh:mm:ssa    I                                                                      2-11L D  A            System Manager Release Notes)     2.6 System Tuning for Non-VGA Devicesp    >           At the present time, there is no workaround for this@           problem other than using fewer windows (increasing theE           MAXBOBMEM value doesn't fix the problem). If you experienceDE           this problem, you may want to keep a DECterm window free so C           that you can perform a graceful system reboot. Otherwise, 1           you will need to perform a hard reboot.   '     2.7 Previously Optional Files Movedt  D     V1.2- The files listed in Table 2-2 from the optional areas haveC     4     been moved into the required files areas. These files arep  #           now installed by default.S  E     Table_2-2_Previously_Optional_Files_Now_Required_________________E  E     File_Name_________________________________File_Function__________   A     [SYSHLP.EXAMPLES.DECW]ICO.EXE             Programming exampleI3                                               image   ?     [SYSHLP.EXAMPLES.DECW.UTILS]BITMAP.EXE    MIT utility image   ?     [SYSHLP.EXAMPLES.DECW.UTILS]ATOBM.EXE     MIT utility image   ?     [SYSHLP.EXAMPLES.DECW.UTILS]BMTOA.EXE     MIT utility image   ?     [SYSHLP.EXAMPLES.DECW.UTILS]XDPYINFO.EXE  MIT utility image   ?     [SYSHLP.EXAMPLES.DECW.UTILS]XEV.EXE       MIT utility image2  ?     [SYSHLP.EXAMPLES.DECW.UTILS]XLSATOMS.EXE  MIT utility image   ?     [SYSHLP.EXAMPLES.DECW.UTILS]XLSFONTS.EXE  MIT utility image   ?     [SYSHLP.EXAMPLES.DECW.UTILS]XLSWINS.EXE   MIT utility image   ?     [SYSHLP.EXAMPLES.DECW.UTILS]XMAG.EXE      MIT utility image   ?     [SYSHLP.EXAMPLES.DECW.UTILS]XMBIND.EXE    MIT utility image   ?     [SYSHLP.EXAMPLES.DECW.UTILS]XMODMAP.EXE   MIT utility imagea  ?     [SYSHLP.EXAMPLES.DECW.UTILS]XPR.EXE       MIT utility image   ?     [SYSHLP.EXAMPLES.DECW.UTILS]XPROP.EXE     MIT utility imageo  ?     [SYSHLP.EXAMPLES.DECW.UTILS]XRDB.EXE      MIT utility imagei  ?     [SYSHLP.EXAMPLES.DECW.UTILS]XREFRESH.EXE  MIT utility imager  ?     [SYSHLP.EXAMPLES.DECW.UTILS]XSET.EXE      MIT utility imagew  ?     [SYSHLP.EXAMPLES.DECW.UTILS]XSETROOT.EXE  MIT utility imaged  E                                              (continued on next page)s       2-12           I                                              System Manager Release Notes I                                       2.7 Previously Optional Files Movedr    I         Table_2-2_(Cont.)_Previously_Optional_Files_Now_Required_________s  I         File_Name_________________________________File_Function__________s  C         [SYSHLP.EXAMPLES.DECW.UTILS]XWD.EXE       MIT utility imager  C         [SYSHLP.EXAMPLES.DECW.UTILS]XWININFO.EXE  MIT utility imaget  I         [SYSHLP.EXAMPLES.DECW.UTILS]XWUD.EXE______MIT_utility_image______i  C         2.8 Using Shareable Linkages to Install Images (Alpha Only)p  C         V1.2- On OpenVMS Alpha systems, using shareable linkages toeE         4     install images on DECwindows Motif for OpenVMS softwaren  .               offers the following advantages:  B               o  Enhanced startup performance by decreasing image-                   activation time  I               o  Conserved memory usage by decreasing the total of memorye(                  pages used by the image  B               By default, the following images are installed using2               shareable linkages on Alpha systems:  (               o  DECW$XLIBSHR.EXE (Xlib)  4               o  DECW$XTLIBSHRR5.EXE (Xt Intrinsics)  4               o  DECW$XMLIBSHR12.EXE (Motif Toolkit)  >               o  DECW$MRMLIBSHR12.EXE (Motif Resource Manager)  F               o  DECW$DXMLIBSHR12.EXE (DIGITAL Extensions to the Motif                  Toolkit)   @               o  CDE$UNIX_ROUTINES.EXE (UNIX emulation routines)  F               These images are installed using the /SHARE=ADDRESS_DATAG               option. Note that if you accept the default, these images E               cannot be replaced during a restart of DECwindows MotifyG               software. As a result, when you restart DECwindows Motif,rF               the images are not replaced and the following message is               displayed:  U               Shared linkage sections are in use on this system and no images will beSX               reinstalled. If you are restarting DECwindows to reinstall images then you%               must reboot the system.L  I                                                                      2-13a g  u            System Manager Release Notes?     2.8 Using Shareable Linkages to Install Images (Alpha Only)-    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.   A     2.9 Define DECW$UTILS Global Symbol When Moving DECW$EXAMPLESN         Global Symboln  ?     V1.2  DECwindows Motif Version 1.2 for OpenVMS introduced ai>           new symbol, DECW$UTILS. Normally, this symbol points=           to a subdirectory of DECW$EXAMPLES. If you define aS?           DECW$EXAMPLES global symbol in the DECW$PRIVATE_APPS_e=           SETUP.COM command procedure to change the directoryg?           for DECwindows example programs, you must also defineL;           DECW$UTILS to change the directory for utilities.o  E           For example, to redefine both DECW$EXAMPLES and DECW$UTILS,gB           add the following lines to the SYS$MANAGER:DECW$PRIVATE_#           APPS_SETUP.COM procedure:o  8           $ DECW$EXAMPLES == "SYS$SYSROOT:[DECWEXAMPLES];           $ DECW$UTILS == "SYS$SYSROOT:[DECWEXAMPLES.UTILS]E  C              ________________________ Note ________________________a  ;              If the SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COMT4              file does not exist, create it from the?              SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.TEMPLATE file.r  C              ______________________________________________________i  D           Then, restart DECwindows Motif with the following command:  ,           $@SYS$MANAGER:DECW$STARTUP RESTART  7     2.10 FileView Creates Detached Processes by Default   B     V1.1  Applications created by FileView and Session Manager are           detached processes.s  =           The implication is that during application startup,aA           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       2-14           I                                              System Manager Release NotesYI                       2.10 FileView Creates Detached Processes by Default     C               from starting. Examples of such commands are INQUIRE,H4               READ/PROMPT, and SET TERMINAL/INQUIRE.  C               Extensive SYLOGIN.COM or LOGIN.COM command procedures C               slow down application startup. Many of the operationsiE               performed in a SYLOGIN.COM or LOGIN.COM are meaninglessb@               for DECwindows application startup. Therefore, theG               SYLOGIN.COM and LOGIN.COM files should be conditionalizedoB               for DECwindows application startup performance. WhenB               starting a DECwindows application, only a minimum ofD               SYLOGIN.COM and LOGIN.COM commands should be executed.E               Typically, the commands that should be executed are the:H               redefinition of DECW$USER_DEFAULTS (if present), and otherF               logical name definitions if the user will be referencingG               them from within the context of a DECwindows application.tI               The following code segment can be inserted into SYLOGIN.COMeH               and LOGIN.COM immediately following the commands necessary               for DECwindows:o                 $ mode = f$mode() +               $ tt_devname = f$trnlnm("TT")gG               $ session_mgr_login = (mode .eqs. "INTERACTIVE") .and.  -aG                     (f$locate("WSA",tt_devname) .ne. f$len(tt_devname))eM               $ session_detached_process = (mode .eqs. "INTERACTIVE") .and. - G                     (f$locate("MBA",tt_devname) .ne. f$len(tt_devname)) L               $ if session_mgr_login .or. session_detached_process then exit  F               Applications continue to run even if these lines are not;               added to the SYLOGIN.COM and LOGIN.COM files.   5         2.11 Performance Problem with Certain Keymaps   E         V1.2- There is a performance problem when using the Austrian- E         5     German keymap (AUSTRIAN_GERMAN_LK401AG_TW). The problemm  I               can also occur with other keyboard and/or language changes,eI               when the user selects a sequence of keyboard maps/languages C               which force the Mode_switch modifier into the mod4 or C               mod5 entry in the keyboard modifier map. This happens A               in response to the user selecting a keyboard map inuD               the "Keyboard Options" popup that uses the Mode_switch               modifier.m      I                                                                      2-15                  System Manager Release Notes1     2.11 Performance Problem with Certain Keymapss    C           To verify the position of the Mode_switch modifier in theE<           keyboard modifier map, use the following commands:  /           $ XMODMAP :== $DECW$UTILS:XMODMAP.EXE_           $ XMODMAP I           xmodmap:  up to 3 keys per modifier, (keycodes in parentheses):i  5           shift       Shift_R (0xab),  Shift_L (0xae)_&           lock        Caps_Lock (0xb0)&           control     Control_L (0xaf)1           mod1        Alt_L (0xac),  Alt_R (0xb2) (           mod2        Mode_switch (0xb1)&           mod3        Multi_key (0xad)(           mod4        Mode_switch (0x7a)!           mod5        Help (0x7c)T  6           As a workaround, change the modifier mapping7           after selecting the keyboard map by using the )           DECW$UTILS:XMODMAP.EXE utility.s  D           1. Create a file, which when passed to XMODMAP, clears theB              keyboard modifier map and remaps the Mode_switch to a6              lower entry in the keyboard modifier map:                clear shift              clear lock               clear control              clear mod1               clear mod2               clear mod3o              clear mod4               clear mod5m(              add shift = Shift_R Shift_L!              add lock = Caps_Locki$              add control = Control_L#              add mod1 = Alt_R Alt_Lc!              add mod2 = Multi_keyo#              add mod3 = Mode_switcho              add mod5 = Help  C           2. Pass the file to XMODMAP using the following commands:_  2              $ XMODMAP :== $DECW$UTILS:XMODMAP.EXE$              $ XMODMAP XMODMAPRC.DAT       2-16 _  _      I                                              System Manager Release Notes I                                         2.12 Customizing the Login Screen_    )         2.12 Customizing the Login Screen   @         V1.2  To customize the login screen, create a file named>               DECW$LOGIN.DAT in the SYS$MANAGER directory thatE               contains your resource definitions. The custom resource D               definitions from SYS$MANAGER:DECW$LOGIN.DAT are mergedA               with the resource definitions supplied by Compaq in E               SYS$COMMON:[DECW$DEFAULTS.SYSTEM]DECW$LOGIN.DAT to formo#               the new login screen.   E               Keep customized versions of the DECW$LOGIN.DAT resourceSH               file in the SYS$MANAGER directory, and not in DECW$SYSTEM_B               DEFAULTS, to prevent your customized file from beingH               overwritten when upgraded to a newer version of DECwindowsG               Motif for OpenVMS software. In addition, storing the file_H               in the SYS$MANAGER directory prevents the custom file from>               superseding the file that is supplied by Compaq.  C         2.12.1 Customizing the DIGITAL Logo and Login Screen Colors   F         V1.2  You can define the resources in Table 2-3 to control theF               position and colors of the DIGITAL logo and the color of@               the screen background in the Start Session screen.  I               Table 2-3 Moving the DIGITAL Logo and Changing Login ScreenoI               __________Colors___________________________________________   I               Resource__________Description______________________________   ?               rootColor         Color of the screen background.s  E               logoColor         Color of the DIGITAL logo (default isT*                                 burgundy).  G               logoX             x position of the DIGITAL logo (default &                                 is 0).  G               logoY             y position of the DIGITAL logo (default '                                 is 75).s  G               centerLogoX       Boolean; if true (default), the DIGITALtD                                 logo is centered horizontally on theI               __________________screen.__________________________________   A               For example, to position the DIGITAL logo at x=100, B               y=600, add the following resource definitions to the.               SYS$MANAGER:DECW$LOGIN.DAT file:  I                                                                      2-17                  System Manager Release Notes%     2.12 Customizing the Login Screen                decw$login.logoX: 100m           decw$login.logoY: 600 '           decw$login.centerLogoX: falseE  C     2.12.2 Changing Positions of the Start Session and Set PasswordG            Dialog Boxesh  B     V1.2  You can define the resources in Table 2-4 to control the?           position of the Start Session and Set Password dialogo           boxes.  B           Table 2-4 Changing Position of the Start Session and SetE           __________Password_Dialog_Boxes____________________________   E           Resource______________Description__________________________   ?           centerStartSessionX   Boolean; if true (default), thedD                                 Start Session dialog box is centered-                                 horizontally.   ?           centerStartSessionY   Boolean; if true (default), the D                                 Start Session dialog box is centered+                                 vertically.F  ?           centerSetPasswordX    Boolean; if true (default), thetC                                 Set Password dialog box for expired C                                 passwords is centered horizontally.   ?           centerSetPasswordY    Boolean; if true (default), the C                                 Set Password dialog box is centered E           ______________________vertically.__________________________   B           For example, to position the Start Session dialog box atE           x=100, y=600, add the following resource definitions to the *           SYS$MANAGER:DECW$LOGIN.DAT file:  /           decw$login.centerStartSessionX: falses/           decw$login.centerStartSessionY: falsec'           decw$login.HiddenShell.x: 100 '           decw$login.HiddenShell.y: 600,  :           To position the Set Password dialog box at x=30,>           y=100, add the following resource definitions to the*           SYS$MANAGER:DECW$LOGIN.DAT file:       2-18 e         I                                              System Manager Release Notes,I                                         2.12 Customizing the Login Screenf    2               decw$login.centerSetPasswordX: false2               decw$login.centerSetPasswordY: false/               decw$login.SetPasswordShell.x: 30i0               decw$login.SetPasswordShell.y: 100  H         2.12.3 Disabling a Node Name Display in the Start Session Dialog                Box  F         V1.2  To prevent a node name from being displayed in the StartG               Session dialog box, add the following resource definition 5               to the SYS$MANAGER:DECW$LOGIN.DAT file:m  /               decw$login.displayNodeName: falseo  #         2.13 Customized Login Logose  A         V1.1  By default, if there is no DECwindows Motif licensehD               registered for the SYSTEM account, DECwindows does notB               display customized login logos. This is a problem onF               systems with DECwindows Motif personal-use licenses thatH               do not include SYSTEM on the list of authorized DECwindows               users.  E               To display a customized logo without a DECwindows MotifiE               license for SYSTEM, add the following definition to the ;               SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM file:l  +               $ DECW$LOGINLOGOSUB == "TRUE"t  F                 ________________________ Note ________________________  A                 If the file does not exist, copy it from the fileC=                 SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.TEMPLATE.   F                 ______________________________________________________  D               After editing the setup file, restart DECwindows Motif*               using the following command:  1               $ @SYS$MANAGER:DECW$STARTUP RESTART   A               DECwindows Motif login starts the logo process as aSF               subprocess instead of as a detached process. The licenseF               check sees that the logo process is a child of the login:               process and that the X connection is opened.  I                                                                      2-19M S  C            System Manager Release Notes'     2.14 Version Checking Command FilesD    '     2.14 Version Checking Command FilesM  @     V1.0  The DECwindows Motif for OpenVMS kit contains version-C           checking command procedures that layered products can useLB           during their installation procedure. The following threeA           files are placed in the SYS$UPDATE directory during theL7           installation of DECwindows Motif for OpenVMS:S  '           o  DECW$GET_IMAGE_VERSION.COMt  8              A command procedure that extracts the imageE              identification string from an image and places it into ao!              user-defined symbol.                                                                      2-20 e         I                                              System Manager Release NotesrI                                       2.14 Version Checking Command Files_    *               o  DECW$COMPARE_VERSIONS.COM  <                  A command procedure that compares two imageF                  identification strings and assigns a value to a user-<                  defined symbol with these possible results:  0                  -  Facility codes do not match.  -                  -  Identifiers are the same.   >                  -  Second identifier is older than the first.  >                  -  Second identifier is newer then the first.  "               o  DECW$VERSIONS.COM  A                  A command procedure used to display the versions >                  of several components of the DECwindows Motif@                  layered product and the X11 display server. TheE                  DECW$VERSIONS.COM procedure uses the DECW$GET_IMAGE_iI                  VERSION.COM command procedure to obtain the image idents G                  of each file. Use the following command to display theC(                  versions on sys$output:  .                  $ @SYS$UPDATE:DECW$VERSIONS *  I                  ________________________________________________________.I                  Component_____________Description_______________________T  ;                  DECwindows ident      Xlib shareable image   6                  DECwindows server     Server DIX file  7                  DECwindows transport  Transport commonR  ;                  DECwindows Xlib       Xlib shareable imageh  ;                  DECwindows OSF/Motif  OSF/Motif Xm Toolkitn                  Toolkit  :                  DECwindows            DECwindows FileView                  applications   =                  DECwindows            OSF/Motif UIL compiler I                  programming_____________________________________________h  D                  The output from the command procedure shows DW, theC                  version number, and the date the image is created.t                    For example:                      DW V1.2-4960312  I                                                                      2-21                  System Manager Release Notes'     2.14 Version Checking Command Filese    @              is version 1.2-4 and was created on March 12, 1996.  D     2.15 Implications of the Message, "System Menu Bar: Pseudo Mouse          Not Available"N  =     V1.2- "System Menu Bar: Pseudo Mouse not available" is ano>     3     informational message that is included in the user's  E           DECW$USER_DEFAULTS:DECW$SM.LOG file when you run a session.iA           It is not an error message. The message occurs when the B           OpenVMS Session Manager is run remotely to a non-OpenVMSA           server. The OpenVMS server provides pseudomouse mode, atB           mode that allows you to use arrow keys to move the mouse           cursor.   9     2.16 CDA and DECsound Installation Problem (VAX Only)n  C     V1.2- If you install DECwindows Motif Version 1.2-4 for OpenVMS <     4     or later on an OpenVMS VAX system and then install  ?           DECwindows Motif Version 1.2-3 for OpenVMS or earlierVC           using VMSINSTAL, the CDA and DECsound applications do notEC           work. The following error message is displayed when theseO#           applications are started:   H               %SYSTEM-F-SHRIDMISMAT, ident mismatch with shareable image  C           This error is generated because CDA or DECsound is tryingn?           to activate the earlier version of the Motif toolkit.TA           The VMSINSTAL procedure did not replace CDA or DECsound_A           when the earlier version was installed. This is becauseoA           in versions prior to DECwindows Motif Version 1.2-4 forW@           OpenVMS, the VMSINSTAL installation procedure compares?           the versions of CDA and DECsound currently running oni@           the system with the versions being installed, and doesB           not replace CDA or DECsound with older versions of those           components.O  =           To revert to an earlier version of DECwindows Motifm@           and allow CDA applications and DECsound to be run, youB           should first tailor off CDA and DECsound files using theC           SYS$UPDATE:DECW$MOTIF_TAILOR.EXE utility, as described innE           the DECwindows Motif Version 1.2-5 for OpenVMS Installation C           Guide, before installing DECwindows Motif with VMSINSTAL.        2-22    a      I                                              System Manager Release NotessI                     2.16 CDA and DECsound Installation Problem (VAX Only)U    H               This problem is corrected in DECwindows Motif Version 1.2-E               4 for OpenVMS. The new VMSINSTAL installation procedure C               installs CDA and DECsound files regardless of whether F               the versions being installed are older or newer than the/               versions currently on the system.   -         2.17 DECterm System Management Issuesp  D               This section contains information about DECterm system                management issues.  $         2.17.1 DECterm Logical Names  I         V1.1  Table 2-5 describes the logical names that are supported by G               DECterm. If you do not define these logical names in yourfD               LOGIN.COM file, the controller uses the default files.  I         Table_2-5_Logical_Names_Supported_by_DECterm_____________________n  I         Logical_Name______________________Description____________________i  F         DECTERM_DIAG                      Enables diagnostic messages.  F         DECTERM_SHOW_PARSING              Shows characters as they are1                                           parsed.T  I         DECTERM_CHECK_MEMORY              Enables strict memory checking.a  F         FAKE_VM_REAL_FREE_OFF             Must be set to 1 if DECTERM_B                                           CHECK_MEMORY is defined.  I         +DECW$DECTERM_ERROR               Name of error log file; defaulte?                                           is DECTERM_ERROR.LOG.h  I         DECW$DECTERM_OUTPUT               Name of diagnostic output file;e@                                           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 them5                                           controller.c  G         DECW$DECTERM_CTRL_PSWAPM          Sets the PSWAPM quota for thef5                                           controller.e  I         +VAX_specific____________________________________________________p  I                                                  (continued on next page)   I                                                                      2-23y m  n            System Manager Release Notes)     2.17 DECterm System Management Issues     E     Table_2-5_(Cont.)_Logical_Names_Supported_by_DECterm_____________b  E     Logical_Name______________________Description____________________   E     DECW$DECTERM_CTRL_WSEXTENT        Sets the WSEXTENT quota for the 1                                       controller.   D     DECW$DECTERM_CTRL_WSQUOTA         Sets the WSQUOTA quota for the1                                       controller.o  ?     DECW$DECTERM_DISABLE_QUOTA_       Turns off quota checking.      CHECKING  <     DECW$DECTERM_MEM_DIAG             Shows controller quotaE     __________________________________calculations.__________________x  '     2.17.2 Automatic Window Positioningh  ?     V1.1  A resource has been defined to manage repositioning asC           DECterm window when a resize operation forces part of theCC           window off the screen. If a DECterm window is enlarged bykB           using the Options/Window dialog box or by entering a SET@           TERMINAL/PAGE=nn or SET TERMINAL/WIDTH=nn command, theC           controller moves the newly resized DECterm window so that A           it can be viewed in its entirety. If you prefer DECterm D           not to move, add the following line to your DECW$TERMINAL_           DEFAULT.DAT file:   =           DECW$TERMINAL.main.terminal.autoAdjustPosition: off   +     2.17.3 DECterm Window Shrinking Problem   E     V1.2- If the XUI window manager is in use, "Auto Resize Terminal" E     5     is on, and you used the mouse to resize the DECterm window,o  A           the DECterm window shrinks. To workaround this problem,E=           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 rathern?           than character cells. Also, if you maximize a DECterm E           window, it might not properly restore to its previous size.t,           However, it will no longer shrink.       2-24 S  N      I                                              System Manager Release NotesiI                                     2.17 DECterm System Management Issues.    (         2.17.4 Hold Screen Response Time  G         V1.1  If the hold screen key response time is too slow, add thecE               following lines to your DECW$TERMINAL_DEFAULT.DAT file:S  :               DECW$TERMINAL.main.terminal.syncFrequency: 1=               DECW$TERMINAL.main.terminal.batchScrollCount: 1v  C               Using this resource can affect the performance of thetE               DECterm window. The actual impact on performance varieseE               from site to site. You can trade off scrolling speed topF               hold-screen response time. A faster hold-screen responseI               results in a slower scrolling speed. The default values for 9               these resources are 10 and 0, respectively.G  !         2.17.5 Using the Debugger   C         V1.0  To redirect the output from the debugger to a DECterm 2               window, enter the following command:  4               $ CREATE/TERMINAL/NOPROCESS/DEFINE=xxx  B               This command creates a DECterm without an associatedG               process but with a logical name of xxx that points to theoH               terminal. This procedure enables you to direct output to aH               DECterm window other than the window where the applicationE               is currently running. To redirect the output, enter thea!               following commands:   +               $ DEFINE /USER DBG$INPUT xxx:o  ,               $ DEFINE /USER DBG$OUTPUT xxx:  *               $ RUN /DEBUG application.EXE  '         2.17.6 Virtual Terminal Supportl  I         V1.0  To create a process that uses a virtual terminal, enter thel                following command:  )               $ CREATE/TERMINAL/NOPROCESS_  F               Then establish focus to the newly created DECterm, pressH               Return, and log in. Note that the /DEFINE qualifier is not               required.W  I                                                                      2-25                  System Manager Release Notes)     2.17 DECterm System Management IssuesL    7     2.17.7 DTSESSION Logging Problem (New Desktop Only)   =     V1.2- In some cases, DTSESSION continues to log errors to ;     5     its log file until all free disk space is filled.P  @           These errors could occur, for example, if DECW$DISPLAY9           is set to an incorrect value, or if CDE$SYSTEM_ ?           DEFAULTS:[BIN]DTSCREEN.EXE is not properly installed.   D           If the New Desktop's Session Manager (DTSESSION) is unableC           to start the Screen Saver (DTSCREEN), it logs an error to D           the log file device:[user.DT]ERRORLOG. DTSESSION logs thisC           error at a user-settable interval controlled by the Style 4           Manager's "Time Per Background" parameter.  <           To workaround this problem, increase the "Time Per@           Background" parameter to the maximum (120 minutes), orE           exit the New Desktop when you are done with it, rather than            locking the screen.e  #     2.18 Console Window Applicationr  ?     V1.2- DECwindows Motif Version 1.2-3 for OpenVMS introduced C     3     the feature of displaying console messages in the Console   C           Window application. Previous versions of DECwindows MotifY2           displayed the console window by default.  C              ________________________ Note _________________________  <              The new default for displaying console messagesA              starting with the DECwindows Motif Version 1.2-3 for @              OpenVMS release is DISABLE. The default in previousB              versions of DECwindows Motif was ENABLE. These valuesC              are discussed in greater detail later in this section. ?              If the user selects the Alternate Console port forlB              console communications, the DECwindows Console Window@              is disabled and the console broadcasts are enabled.@              Refer to the owner's guide for your workstation for>              information about selecting the Alternate Console              port.  C              ______________________________________________________t  @           Specify how to display messages by defining the globalA           symbol DECW$CONSOLE_SELECTION in the customized startup D           file SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM. Enter one of;           the following values: WINDOW, DISABLE, or ENABLE.s       2-26 r  e      I                                              System Manager Release NotesnI                                           2.18 Console Window Applicationn                   o  WINDOW   @                  Displays console messages in the Console WindowE                  application. This is a new application starting witheI                  the DECwindows Motif Version 1.2-3 for OpenVMS software. G                  If you specify the WINDOW value, the Console Window is H                  displayed in the lower right corner of the login screenH                  by default and continues to be displayed after the user'                  logs in to the system.i  ?                  The Console Window application shares the samecI                  executable file and looks similar to the Message Window.MD                  However, a menu bar is not displayed in the ConsoleI                  Window; it reads its resources from the DECW$CONSOLE.DATEE                  file instead of from the DECW$MESSAGEPANEL.DAT file._I                  Internally, the Console Window is invoked by running the G                  DECW$MESSAGEPANEL.EXE executable with the command line !                  option -console._  F                  To control the initial position of the Console WindowF                  and the classes of OPCOM output that are enabled, youG                  can the define the following global symbol in the filen9                  SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM:   )                     DECW$CONSOLE_GEOMETRY.  D                     This symbol specifies the value of the -geometryE                     option in the DECW$MESSAGEPANEL.EXE command line;.D                     this command is used to start the Console WindowC                     application. The default value is "-0-0", whichrE                     specifies the location of the window in the lowere/                     right corner of the screen.k  F                     To position the window at the lower left corner ofC                     the screen, for example, add the following linefF                     to the command file SYS$MANAGER:DECW$PRIVATE_APPS_                     SETUP.COM:  6                      $ DECW$CONSOLE_GEOMETRY == "+0-0"  "               o  DISABLE (default)  A                  Disables broadcasts to the OPA0: device. Consolet,                  messages are not displayed.                 o  ENABLE   I                                                                      2-27  0  e            System Manager Release Notes#     2.18 Console Window Applications    A              Displays console messages in the console window. TheoD              console window is a six-line display area at the top of$              the workstation screen.  C              ________________________ Note ________________________   >              Although ENABLE was the default value in previous<              releases of DECwindows Motif, it is recommended<              that you do not use this option with DECwindows@              Motif Version 1.2-3 for OpenVMS and later versions.B              Displaying console messages by default in the console?              window can corrupt the contents of the workstatione              display.r  C              ______________________________________________________   @           Refer to Managing DECwindows Motif for OpenVMS SystemsC           for information about defining global symbols in the file 2           SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM.  '     2.19 Window Manager Overlay Support   D     V1.2- The latest version of the Window Manager (MWM) is modified>     3     to support overlays and utilize additional planes of  <           memory, which are available on several 3D graphics@           accelerators: ZLX-M1, ZLX-M2, ZLX- L1, ZLX-E2, ZLX-E3,A           ZLXp-E2, and ZLXp-E3. The Window Manager places bordersnD           and banners for all the windows into these extra planes ofD           memory and thereby reduces the number of expose events for.           your applications that use overlays.  @           Modify your existing applications that use overlays toA           avoid potential problems with the colormap. Set up yourC>           system to share the overlay colormap with the WindowA           Manager, as the hardware supports only one colormap fori           the overlay planes.i  C           To modify your applications to share the overlay colormapeA           with the Window Manager, query the server property namev@           SERVER_OVERLAY_COLORMAPS. When you make the query, theB           server returns the 32-bit value for the overlay Colormap
           ID.          2-28           I                                              System Manager Release Notes.I                                       2.19 Window Manager Overlay Supporta    8               To set up your system to share the overlay>               colormap with the Window Manager, edit the files<               SYS$COMMON:[VUE$LIBRARY.SYSTEM]VUE$MWM.COM andH               SYS$COMMON:[SYSMGR]DECW$MWM.COM. Change the following line               in each file:C  !                $ mwm -multiscreeni  G               Edit this line by adding the -Overlay command-line option                as follows:   ,                $ mwm -multiscreen "-Overlay"  H               Note that if you create and install your own colormap, the,               following problems can result:  I               o  Colors flash on the screen when the colormap is changed.y  I               o  Border and banner colors also change when you change the )                  colors of your colormap.n                 Restrictions  I               The following restrictions apply when you enable the WindowA&               Manager to use overlays:  G               o  The Window Manager supports only single-screen systems G                  and does not function correctly with multiple graphicsA%                  devices (multihead).   H               o  If you select a Matte Size value other than "None" fromH                  the Window Manager options list, the Matte color is notI                  correct; that is, the color does not match the selectione1                  and is occasionally transparent.   E               o  If you select "Show feedback when moving or resizing E                  windows" from the Workspace Options menu, the windoweD                  with the feedback information causes expose events.  D               o  When you move windows by showing the outline of theC                  window, the outline appears to go below the window %                  borders and banners.   G               o  Window borders are occasionally and randomly displayedbF                  in clear or black. If this problem occurs, select theF                  restart option from the Workspace menu to restart the                   Window Manager.  I                                                                      2-29g C  d            System Manager Release Notes'     2.19 Window Manager Overlay Support     E           o  The ZLXp-E2 and ZLXp-E3 3D graphics accelerators are notAE              currently supported when you run the Window Manager withp.              the -Overlay command-line option.                                                                                         2-30 l  C                    I                                                                         3dI         _________________________________________________________________   I                                                  Programmer Release Notesn    =               This chapter contains programmer release notes.s  F         3.1 Programming Release Notes Specific to DECwindows Motif for             OpenVMS Software  C               The release notes in this chapter are cumulative fromoA               DECwindows Motif Version 1.0 and still apply to theuB               DECwindows Motif Version 1.2-5 for OpenVMS software.  9         3.2 DECwindows Motif for OpenVMS Toolkit Versions_  D         V1.2- The DECwindows Motif Version 1.2-5 for OpenVMS releaseF         5     is based on the CDE Motif 1.0 Toolkit (OSF/Motif Release  '               1.2.5) and X11 Release 5.   D         V1.2- The DECwindows Motif Version 1.2-4 for OpenVMS releaseG         4     was based on the CDE Motif 1.0 Toolkit (OSF/Motif Release   '               1.2.5) and X11 Release 5.b  D         V1.2- The DECwindows Motif Version 1.2-3 for OpenVMS releaseD         3     was based on the OSF/Motif Release 1.2.3 Toolkit (with  F               extensions for the Common Desktop Environment (CDE)) and!               X11 Release 5 (R5).D  F         V1.2  The DECwindows Motif Version 1.2 for OpenVMS release wasF               based on the OSF/Motif Release 1.2.2 Toolkit and MIT X11               Release 5 (R5).f  F         V1.1  The DECwindows Motif Version 1.1 for OpenVMS release wasF               based on the OSF/Motif Release 1.1.3 Toolkit and MIT X11               Release 4 (R4).   F         V1.0  The DECwindows Motif Version 1.0 for OpenVMS release wasF               based on the OSF/Motif Release 1.1.1 Toolkit and MIT X11               Release 4 (R4).l  I                                                                       3-1h                Programmer Release Notes-     3.3 Run-Time and Programming Environments_    -     3.3 Run-Time and Programming Environments   A     V1.2- The following run-time and programming environments are B     4     provided with the DECwindows Motif for OpenVMS software:  ?           o  Run-time support is provided for the CDE Motif 1.07A              Toolkit (OSF/Motif Release 1.2.5), OSF/Motif Releasea1              1.1.3 Toolkit, and the XUI Toolkits.o  B           o  Development support is provided for the CDE Motif 1.0              Toolkit only.  D              However, you can choose during installation to save theC              OSF/Motif Release 1.1.3 programming files that existedeA              on your system prior to the DECwindows Motif VersionoE              1.2-4 for OpenVMS product. Refer to the DECwindows MotifgE              Version 1.2-4 for OpenVMS Installation Guide for detailslA              about saving the OSF/Motif Release 1.1.3 programming_              environment.A  ?              -  If you install the software using the VMSINSTALeE                 procedure and choose to save these programming files,e@                 the files are moved to subdirectories and can be)                 accessed for programming.s  @              -  If you install the software using the POLYCENTER@                 Software Installation utility and if programming?                 support for the OSF/Motif Release 1.1.3 Toolkit B                 is present, then you can choose to save the header@                 files and UIL compiler that were used to developB                 OSF/Motif Release 1.1.3 applications. If selected,A                 the installation procedure creates a subdirectorye@                 called [.DECW$113], and the previous programming:                 files are moved into the new subdirectory.  ?              See the DECwindows Motif Version 1.2-4 for OpenVMSw@              Installation Guide for additional information about>              saving the Release 1.1.3 programming environment.  B           o  Application development with the DECwindows Motif for@              OpenVMS product is supported for DEC C++ as well asA              for updated Motif language bindings for Ada, Pascal, D              Fortran, and C. Language bindings for Ada are availableD              in the DEC Ada Version 3.0A for OpenVMS (VAX and Alpha)              layered products.       3-2     4      I                                                  Programmer Release NotessI       3.4 DECW$WML.EXE Looks in Current Directory For DECW$WML_TOKENS.DATt    7         3.4 DECW$WML.EXE Looks in Current Directory For              DECW$WML_TOKENS.DATr  @               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 previousiG               versions of DECwindows Motif, this tokens file was alwaystF               read from SYS$LIBRARY. However, starting with DECwindowsG               Motif Version 1.2-4 for OpenVMS, DECW$WML.EXE first looksfG               for this file in the current directory before looking foroH               it in SYS$LIBRARY. This allows a customized tokens file to               be used.  6         3.5 DECW$COMPARE_VERSIONS Command File Problem  E               The DECW$COMPARE_VERSIONS command file compares versionpB               identifications using two-digit years. Therefore, it@               will not compare version identifiers correctly forF               images generated in the year 2000 and later with versionD               identifiers for images generated before the year 2000.  +         3.6 OSF/Motif Toolkit Compatibilityu  H         V1.2- You cannot code and compile an application with DECwindowsF         3     Motif Versions 1.2 or 1.2-3 include files, transport the  C               resulting object files to a system running DECwindows G               Motif Version 1.1 software, link the object files against/E               DECwindows Motif Version 1.1, and expect the executable G               image (.EXE) to run. Differences in structures defined insI               the .h files cause the offsets to be misaligned and thereby:@               prevent you from creating a meaningful executable.  E         V1.2  The OSF/Motif Release 1.1.3 and Release 1.2.2 Toolkits,u@               on which the DECwindows Motif Versions 1.1 and 1.2F               layered products are based, are not compatible. However,D               applications built against the OSF/Motif Release 1.1.3D               Toolkit will continue to run without modification withE               DECwindows Motif Version 1.2 for OpenVMS; the OSF/MotifNE               Release 1.1.3 Toolkit shareable libraries will continuekF               to be supplied with the DECwindows Motif Version 1.2 forG               OpenVMS layered product and will be available to existing 4               DECwindows applications on the system.    I                                                                       3-3n e              Programmer Release Notes'     3.6 OSF/Motif Toolkit Compatibility     A           Although DECwindows Motif Version 1.1 applications willrD           continue to run without modification with DECwindows Motif?           Version 1.2 for OpenVMS, it is important to note thatnB           only those applications that have been built against theC           OSF/Motif Release 1.2.2 Toolkit can take advantage of newwC           Version 1.2 features, such as drag-and-drop functionalitye           and tear-off menus.l  :           In most cases, simple applications (for example,C           applications that do not contain private toolkit routinesiA           or user-written widgets) can be recompiled and relinkedfD           against the OSF/Motif Release 1.2.2 Toolkit to include theD           new Version 1.2 features. However, previously unidentified@           problems in a DECwindows Motif Version 1.1 applicationA           might be exposed by relinking against the new OSF/Motif ?           Release 1.2.2 Toolkit, and behavior and widget layoutsB           changes in the Release 1.2.2 Toolkit might require other4           modifications to your application as well.  >           More complex applications will probably require moreA           substantial modifications with the new DECwindows Motifw?           Version 1.2 for OpenVMS Toolkit to use the macros anda           functions provided.R  ?           If the code generates errors because of references tofE           display structure fields, define the constant XLIB_ILLEGAL_ 8           ACCESS for X11 R5 compatible structure access.             For example:  5           $ CC/DEFINE=XLIB_ILLEGAL_ACCESS DECBURGER.C        3.6.1 _Xm Routines  C     V1.2  The OSF/Motif Toolkit libraries contain many undocumentedVC           routines, which are prefixed with _Xm. These routines areDA           intended to be used only by the standard Motif widgets. C           OSF reserves the right to modify the API or functionality C           of these routines, or to delete them altogether in future            releases.O  D              _______________________ Caution _______________________  B              Compaq supplies access to the _Xm routines by copying>              them into the shareable image transfer vector forA              the OSF/Motif Release 1.2.2 Toolkit. Compaq does not B              document or support these routines or guarantee their       3-4  i  c      I                                                  Programmer Release Notes I                                       3.6 OSF/Motif Toolkit Compatibilityo    C                 continued existence in future releases. ApplicationsD                 developers who use these routines do so at their own                 risk.e  F                 ______________________________________________________  A         3.6.2 OSF/Motif Release 1.2.2 and X11 Release 5 ShareableE               Libraries   A         V1.2  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.aI               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/MotifXI               Release 1.1.3-based shareable libraries, the Release 1.1.3-sG               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/MotiffB               Release 1.1.3 Toolkit or the OSF/Motif Release 1.2.2B               Toolkit do not have a suffix. These libraries are as               follows:                 o  CDA$ACCESS.EXE   $               o  DECW$D2DXLIBSHR.EXE  $               o  DECW$XEXTLIBSHR.EXE  !               o  DECW$XLIBSHR.EXE   )               o  XDPS$DPSBINDINGSSSHR.EXEm  &               o  XDPS$DPSCLIENTSHR.EXE  #               o  XDPS$DPSLIBSHR.EXE                  o  XIE$SHRLIB.EXE   H               Shareable libraries that are linked with Release 5 (R5) ofF               the Xt Toolkit have a suffix of "R5". Libraries based onH               the XUI Toolkit have no R5 equivalent libraries and shouldI               not be included in a linker options file based on X11 R5 or_H               OSF/Motif Release 1.2.2. Table 3-1 lists these file names.  I                                                                       3-5i w  o           Programmer Release Notes'     3.6 OSF/Motif Toolkit Compatibilityw    C              ________________________ Note ________________________   ;              The DECW$XLIBSHR.EXE file is the MIT Release 5o<              version, not the MIT Release 4 version of Xlib.  C              _______________________________________________________  E           Table_3-1_Names_of_Shareable_Libraries_Based_on_R5_________M  E           Names_of_Files_Based_on_R4__Names_of_Files_Based_on_R5_____   ,           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____________n  ;           Release 5 does not provide an equivalent file forLB           DECW$DWTLIBSHR.EXE or DECW$DWTSHR.EXE. Applications thatB           are built for Release 5 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 onlyyA           with libraries compatible with R5 and OSF/Motif Release 2           1.2.2. Table 3-2 lists these file names.  C           Table 3-2 Names of Shareable Libraries Based on OSF/Motif E           __________Release_1.2.2____________________________________a  E           Names of Files Based on     Names of Files Based on ReleaseaE           Release_1.1.3_______________1.2.2__________________________,  8           DDIF$VIEWSHR.EXE            DDIF$VIEWSHR12.EXE  7           DECW$BKRSHR.EXE             DECW$BKRSHR12.EXEt  :           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  E                                              (continued on next page)        3-6  Y  O      I                                                  Programmer Release NotesWI                                       3.6 OSF/Motif Toolkit Compatibility     E               Table 3-2 (Cont.) Names of Shareable Libraries Based onrI               __________________OSF/Motif_Release_1.2.2__________________m  I               Names of Files Based on     Names of Files Based on Release I               Release_1.1.3_______________1.2.2__________________________   =               DECW$XMLIBSHR.EXE           DECW$XMLIBSHR12.EXEg  ;               DGIT$LIBSHR.EXE             DGIT$LIBSHR12.EXEh  :               IMG$SHRLIB.EXE              IMG$SHRLIB12.EXE  :               LWK$DXMSHR.EXE              LWK$DXMSHR12.EXE  I               XNL$SHR.EXE_________________XNL$SHR12.EXE__________________o  G               There is no DECW$PRINTWGTSHR12.EXE file; the Print Widget 7               is part of the DECW$DXMLIBSHR12.EXE file.y  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/SHAREs,               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:k  *               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                                                                       3-7                 Programmer Release Notes     3.7 Language Bindings          3.7 Language Bindings   ;     V1.2- Fortran, Pascal, C, and C++ language bindings are D     3     provided to support software development for the following              DECwindows components:             o  Xlib (Release 5)              o  Xt (Release 5)e             o  Xm (Release 1.2.3)c              o  Mrm (Release 1.2.3)             o  DXm  .     3.7.1 OSF/Motif Release 1.1.3 Ada Bindings  ?     V1.2  This release of DECwindows Motif does not include AdasA           bindings for either the OSF/Motif Release 1.1.3 Toolkito@           or the OSF/Motif Release 1.2.2 Toolkit. Strongly typedD           bindings for both toolkits are part of the DEC Ada Version            3.0A language product.  @           If DECwindows Motif is installed on OpenVMS DECwindows@           Motif Version 1.1, then the existing OSF/Motif ReleaseD           1.1.3 Ada bindings, located in the DECW$INCLUDE directory,#           are not deleted or moved.2  ;     3.8 OSF/Motif Release 1.1.3 Programming Support and XUIf       V1.2- Restrictions     3     o  Problem:   A              You will encounter problems if you save the previousi@              (Release 1.1.3) programming environment and attempt?              to run an OSF/Motif Release 1.1.3 (Xlib Release 4)tB              program that is created on a DECwindows Motif VersionB              1.2 or Version 1.2-3 system by running the executableB              on a DECwindows Motif Version 1.1 target system. ThatB              is, if you build an application on a DECwindows MotifA              Version 1.2 or Version 1.2-3 for OpenVMS system, the @              image is linked with Xlib Release 5, by default. IfA              you attempt to run that executable on a system whererC              OSF/Motif Release 1.1.3 is installed, the result is anf(              ident mismatch fatal error.       3-8e    R      I                                                  Programmer Release NoteshI                   3.8 OSF/Motif Release 1.1.3 Programming Support and XUIi    A                  In addition, the OSF/Motif Release 1.1.3 and the H                  Release 1.2.2 files produce different output; they haveG                  different structures and are therefore not compatible. H                  Use the appropriate UIL compiler to produce the correct                  UID file.                 o  Resolution:  ?                  1. Rename the DECwindows Motif Version VersiontB                     1.1 executable compiler, DECW$UILMOTIF.EXE, toA                     DECW$UILMOTIF113.EXE and keep the file in theaD                     SYS$COMMON directory. By doing this, the name ofF                     the new Version 1.2-3 compiler, DECW$UILMOTIF.EXE,A                     does not conflict with the previous compiler.   F                  2. Copy the DECW$XLIBSHR.EXE file (Xlib Release 4) to?                     the SYS$COMMON:[SYSEXE.DECW$113] directory.a  I                     The Xlib Release 5 version of Xlib has the same name;wI                     however, a logical name is defined to use the ReleaseeG                     4 version when the programs are linked. The changeseI                     in minor ident of DECW$XLIBSHR.EXE between DECwindows F                     Motif Version 1.1 and DECwindows Motif Version 1.2G                     for OpenVMS caused a loss of backward compatibilityh>                     with DECwindows Motif Version 1.1 systems.  D                  3. If you save the previous programming environmentG                     during installation, create the following two files E                     and copy them to the SYS$COMMON:[SYSEXE.DECW$113]c                     directory:  .                     -  DECW$UILCOMPILER113.CLD  E                        This file enables UIL/OSF Motif and UIL/XUI to I                        function for either XUI or OSF/Motif Release 1.1.3IG                        if you select DECW$UILMOTIF113.EXE for OSF/MotifhE                        Release 1.1.3 or DECW$UILCOMPILER.EXE for XUI.v                I                                                                       3-9+ s  l           Programmer Release Notes;     3.8 OSF/Motif Release 1.1.3 Programming Support and XUIn    .                 -  DECW$DEFINE113_LOGICALS.COM  D                    This file points to the saved header files, whichE                    in turn point to the Xlib Release 4 version of the )                    DECW$XLIBSHR.EXE file.s  B              4. An application must be run on the same version (orD                 higher) of the operating system as the version whereA                 it is linked. For example, an application that isaE                 linked on a VMS Version 5.4-3 system must be run on aa5                 VMS Version 5.4-3 (or higher) system.o  >                 DECwindows Motif Version 1.1 applications thatA                 are compiled for OpenVMS Version 6.1 systems will B                 run only on OpenVMS Version 6.1 systems and not on-                 systems prior to Version 6.1.C  D     V1.2  The X Window and OSF/Motif libraries that are shipped with?           DECwindows Motif Version 1.2 for OpenVMS software arelA           incompatible with those shipped with previous versions. <           Run-time compatibility has been preserved, but the4           programming environment is not compatible.  C           Programming in the XUI or Motif Release 1.1.3 environmenttC           that is provided in previous versions of DECwindows Motif D           is no longer supported in DECwindows Motif Version 1.2 forD           OpenVMS. However, the installation procedure gives you theC           option of saving the programming files that already existaA           on your system. If you choose to save these programming ?           files, they are moved to subdirectories where you can E           access them for programming. Specifically, the installation B           creates a subdirectory called [.DECW$113] in each of the@           directories listed in Table 3-3 and moves the previous*           files into the new subdirectory.  ;           For more information about saving the programminguA           files, see the DECwindows Motif Version 1.2 for OpenVMS            Installation Guide.e                   3-10           I                                                  Programmer Release NotesDI                   3.8 OSF/Motif Release 1.1.3 Programming Support and XUIs    I               Table 3-3 Directories for Previous XUI or Motif ProgrammingOI               __________Environment______________________________________m  I               Directory_____Contents____New_Location_____________________   K               DECW$INCLUDE  C header    SYS$SYSROOT:[DECW$INCLUDE.DECW$113]u!                             filest  E               SYS$SYSTEM    UIL         SYS$SYSROOT:[SYSEXE.DECW$113]d$                             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 logicala8               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 -c8                   SYS$SYSROOT:[DECW$INCLUDE.DECW$113], -/                   SYS$SYSROOT:[DECW$INCLUDE], -a7                   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 inu<               [.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               To use the UIL compiler for XUI or OSF/Motif Release 1.1.3, *               perform the following steps:  %               1. Create a file calledsG                  SYS$SYSROOT:[SYSEXE.DECW$113]DECW$UILCOMPILER.CLD thatL-                  contains the following text:c  I                                                                      3-11A S  E           Programmer Release Notes;     3.8 OSF/Motif Release 1.1.3 Programming Support and XUId    '              define type trace_keywordsf               keyword tokens               keyword symbolsu  )              define type warning_keywords                 keyword nowarnings&               keyword noinformationals  )              define type version_keywordst(               keyword V1, syntax=xui_uil1               keyword V2, syntax=xui_uil, default_/               keyword MOTIF11, syntax=motif_uilc  "              define syntax xui_uil$               image decw$uilcompiler  $              define syntax motif_uil!               image decw$uilmotifo                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_uile  C               qualifier widget_meta_description, label=widget_qual,3;                value(required, noconcatenate, type=$infile)n  $               disallow XUI and MOTIF           3-12           I                                                  Programmer Release Notes I                   3.8 OSF/Motif Release 1.1.3 Programming Support and XUI     I               2. Set the DCL command table to use the XUI UIL compiler as                   follows:e  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                 ______________________________________________________  E         3.9 Adding POSIX for OpenVMS Support to DECwindows TransportsH  <         V1.1  Transports specific to DECwindows require code?               modifications to support POSIX for OpenVMS fork() D               requirements. If you have written a specific transportG               and also plan to implement POSIX for OpenVMS support, you H               must make changes to your transport source code. This note-               describes the required changes.n  "         3.9.1 POSIX fork() Routine  F         V1.1  The POSIX fork() routine creates a copy of the currentlyI               executing process, completely cloning P1 and P0 space. Both H               the original process (the parent) and the new process (the@               child) proceed on identical paths from that point.  >               When using the POSIX fork() routine, data is not!               duplicated because:   H               o  Files that are not opened through the POSIX for OpenVMS8                  file system are not known to the child.  H               o  Channels that are not shareable or opened through POSIX8                  for OpenVMS are not known to the child.  H               o  The AST queue of the parent is not copied to the child.  A               Because of these limitations, the POSIX for OpenVMS D               implementation has placed certain demands on protected@               shareable images, including transports specific to               DECwindows:s  E               o  It is the responsibility of each protected shareableW<                  image to acknowledge that it can be forked.  I                                                                      3-13e n              Programmer Release NotesA     3.9 Adding POSIX for OpenVMS Support to DECwindows Transportsi    A           o  Based on how the child process should function, each.A              protected shareable image must handle any cleanup orSC              duplication of its own data in a routine called a fork.              callback.  C           Specific transports must acknowledge (on the client side)sD           that they can be forked. The SYS$POSIX_FORK_CONTROL systemC           service, described in Section 3.9.2, is provided for thisE           purpose.  @           Specific transports need not perform any cleanup work.  /     3.9.2 SYS$POSIX_FORK_CONTROL System Service   B     V1.1  A new SYS$POSIX_FORK_CONTROL system service was added in
           VMS E           Version 5.5 that registers that a protected shareable imageND           can be forked. It also registers the address and parameter           to a fork callback.   A           The execution of the POSIX fork()  routine fails if the ?           application has been linked with, or has activated, a B           protected shareable image that has not called SYS$POSIX_           FORK_CONTROL.   E           Therefore, in your specific transport's open routine, add a C           call to the SYS$POSIX_FORK_CONTROL system service similar            to the following:B  >           $ POSIX_FORK_CONTROL(CNTRL = POSIX$C_SETUP_CALLBACK,B             WHEN = POSIX$M_CALL_IN_CHILD,HANDLER = posix_fork_cb);  A           In this example, the CNTRL parameter indicates that the B           image is setting up a callback so that it can be forked,B           the WHEN parameter tells when to call the fork callback,A           and the HANDLER parameter gives the address of the fork_           callback..  B           Other parameters that are not used in this example allowE           for a parameter to be passed to the callback routine and toHD           specify the access mode (maximized to that of the caller).  .     3.10 Translated Image Support (Alpha Only)  E           This section discusses restrictions and general informationW)           about translated-image support.        3-14 /  i      I                                                  Programmer Release NoteslI                                3.10 Translated Image Support (Alpha Only)p    ;         3.10.1 Running Translated Images on OpenVMS Systemse  H         V1.2- In versions of OpenVMS Alpha systems prior to Version 1.5,G         3     translation support was provided to address the followingT  G               problems for users who migrated to OpenVMS Alpha systems:Y  :               o  Lack of full-language programming support  @               o  Unavailability of source code for recompilation  A               o  Difficulty recompiling code that depended on VAXS&                  architecture features  F               For programming languages whose OpenVMS VAX versions areD               currently under development, native Alpha versions areB               available in the OpenVMS Alpha Version 6.1 operatingD               system. The translated-image environment is maintainedG               to support language features that are available as of the (               VMS Version 5.5-2 release.  F               Similarly, translation is supported for images whose useE               of system services and run-time library entry points is H               restricted to those images that existed on the VMS Version%               5.5-2 operating system.l  C               If you have installed layered products on your systemeG               since the VMS Version 5.5-2 release, you may need to make C               additional changes if you rebuild an image to supportSB               translation. For instance, for applications that areF               included with DECwindows Motif for OpenVMS VAX software,D               you must build images with the OSF Motif Release 1.1.3H               library or the DECwindows XUI library, instead of with the.               OSF Motif Release 1.2.3 library.  D               The DECwindows Motif Version 1.2-5 for OpenVMS releaseF               includes the same translated-image support file that wasH               provided with the DECwindows Motif Version 1.2 for OpenVMS               Alpha release.  E               DECwindows Motif Version 1.2 for OpenVMS Alpha includes F               support for DECwindows Motif Version 1.1 for OpenVMS VAX0               images on an OpenVMS Alpha system.    I                                                                      3-15n F  t           Programmer Release Notes.     3.10 Translated Image Support (Alpha Only)    D     V1.2  The DECwindows Motif Version 1.2 for OpenVMS Alpha releaseD           does not include support for running translated DECwindowsC           Motif Version 1.2 for OpenVMS VAX images on OpenVMS Alphao           systems.  D           If you want to run an application against DECwindows MotifB           Version 1.2 shareable images on an OpenVMS Alpha system,E           build it (compile and link) on an OpenVMS Alpha system. YoutB           cannot obtain a Version 1.2 translated image by building?           your application against the DECwindows Motif Version @           1.2 shareable images on an OpenVMS VAX system, copyingB           the resulting image file to an OpenVMS Alpha system, and,           translating it (using DECmigrate).  <           If you cannot build your application on an OpenVMSA           Alpha system and need to obtain a translated image withrC           DECmigrate, you should continue to build your applicationaE           against the OSF/Motif Release 1.1.3 programming environmentlB           provided in the DECwindows Motif Version 1.1 for OpenVMSB           VAX product. (Note that you are given the option to saveC           your OSF/Motif Release 1.1.3 programming environment when1A           you upgrade to DECwindows Motif Version 1.2 for OpenVMSrD           VAX.) VAX images built against the OSF/Motif Release 1.1.3C           programming environment can be copied to an OpenVMS Alphan8           system, translated, and executed successfully.  =           You can install translated-image support during the E           DECwindows Motif installation procedure. See the DECwindows @           Motif Version 1.2-4 for OpenVMS Installation Guide for           instructions.g  D           The OSF/Motif Release 1.1.3 shareable images that are usedD           with translated images are different from and incompatible@           with the shareable images used for native images. As a9           result, the following image restrictions apply:   B           o  Do not use both native and translated images that use4              DECwindows Motif software in a process.  =              Either port or translate all the images that useiD              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 aC0              translated image are not supported.       3-16 F  t      I                                                  Programmer Release NoteseI                                3.10 Translated Image Support (Alpha Only)     C               For more information on translated-image support, seefG               the DECmigrate for OpenVMS AXP Systems Translating Images                guide.  B         3.10.2 DECwindows Motif Toolkit Functionality (Alpha Only)  @         V1.1  On OpenVMS Alpha systems, DECwindows Motif ToolkitH               functionality is available with the following restriction:F               for the DECwindows Motif product, C modules are compiledI               using the default MEMBER_ALIGNMENT switch in the C compiler H               to maximize performance. It is recommended that you do not=               use the NOMEMBER_ALIGNMENT compile-time switch.   I               If you intend to port a toolkit application that is written G               in C, see the VAX C Run-Time Library release notes in theM:               OpenVMS Alpha AXP Version 1.0 Release Notes.  =         3.11 Problems Using the DECW$INCLUDE:INTRINSIC.H Fileo  C         V1.2- The DECwindows header file, DECW$INCLUDE:INTRINSIC.H,oC         5     redefines the globalref macro to be extern when usingo  G               the DEC C compiler, even when the /STANDARD=VAXC compilerrH               switch is specified. This could have a wide impact on user               applications.e  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-writteneG               applications use the same extern model that was used when 9               the DECwindows shared images were compiled.E  A               To workaround this problem, rather than having yourlA               application use globalref and globaldef for its ownrB               variables, use the following preprocessor directive:  0               #pragma extern_model strict_refdef  F               This workaround has the advantage of being strictly ANSIB               compliant. This pragma directive is described in theI               "Preprocessor Directives" chapter of the DEC C User's Guidei)               for OpenVMS Systems manual.       I                                                                      3-17     g           Programmer Release Notes,     3.12 Compiling Applications Written in C    ,     3.12 Compiling Applications Written in C  B     V1.0  During the VAX C layered-product installation procedure,@           you have the option of extracting the VAX C definition>           files (.h files) or leaving the .h files in the textC           library. If you extract the definition files, you can use_7           #include control lines of the following form:              #include <filename.h>_  >           The DECwindows header files assume that the .h files?           were extracted. They contain #include <module_name.h> E           notation for the included files. The DECwindows programmingR3           documentation also makes this assumption.o  C           VAX C should, therefore, be installed using the option toE&           extract the library modules.  E           If you have already installed VAX C and you did not extract_E           the .h files, the DECwindows sample C programs do not work.[E           To correct this problem, reinstall VAX C and extract the .h            files.  B           With DEC C, the 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  ?     3.13 Compiling Applications Written in Fortran (Alpha Only)D  B     V1.1  On OpenVMS Alpha systems, some of the include files usedD           for writing DECwindows Motif applications in Fortran, suchC           as the DECW$MOTIF.FOR file, contain structure definitions E           that cause memory layout changes, depending on the compilerc           switches used.  *           You can do one of the following:  B           o  Use the CDEC$ OPTIONS in the source code so that your@              Fortran programs work correctly with the DECwindows&              Motif run-time libraries:  A              -  Before you include DECwindows Motif files in yourr5                 program, add the following statement:f  4                 CDEC$ OPTIONS /ALIGN=RECORDS=NATURAL       3-18 m         I                                                  Programmer Release Notes I               3.13 Compiling Applications Written in Fortran (Alpha Only)     F                  -  Following the INCLUDE statement, add the following                     statement:  %                     CDEC$ END OPTIONSD                        For example:  8                     CDEC$ OPTIONS /ALIGN=RECORDS=NATURAL,                     INCLUDE "DECW$MOTIF.FOR"%                     CDEC$ END OPTIONS   I               o  Use the Fortran compiler switch, /ALIGN=RECORDS=NATURAL,f0                  when you compile your programs.           3.14 CDA Application  I               This section contains programming information about the CDAa               application.  9         3.14.1 CDA-Implementing the Drag-and-Drop Featured  D         V1.2  The drag-and-drop feature, which lets you move or copyH               information between widgets, is implemented in the widgets"               listed in Table 3-4.  I               Table_3-4_Drag-and-Drop_Widgets____________________________u  I               Widget____________Drag_Operation____Drop_Operation_________   ?               XmText            copy and move     copy and moveo  ?               XmTextField       copy and move     copy and movea  $               XmLabel           copy  $               XmPushButton      copy  $               XmToggleButton    copy  I               XmList____________copy_____________________________________,  G               For information about how to include additional drag-and- F               drop functionality in applications and for an example ofH               a drag-and-drop program, see the Open Software Foundation:@               OSF/Motif Programmer's Guide, Revision 1.2 manual.  I                                                                      3-19a d  u           Programmer Release Notes     3.14 CDA Application    )     3.14.2 CDA Run-Time Services Features,  A     V1.2  This section describes new programming features in this,E           version of the CDA Run-Time Services. See Chapter 1 for new_           user features.       3.14.2.1 Version Numberq  <     V1.2- DECwindows Motif for OpenVMS software incorporatesB     4     additional problem resolutions that were not provided in  =           the general release of the CDA Version 1.8 product.   B           CDA Version 1.6 was part of the DECwindows Motif VersionE           1.1 for OpenVMS release. Starting with the DECwindows Motif D           Version 1.2 for OpenVMS release, DECwindows Motif providedD           the CDA Run-Time Services component of CDA Version 1.8. AsD           of the DECwindows Motif Version 1.2-4 for OpenVMS release,5           DECwindows Motif incorporates Version 1.8A.   9     3.14.2.2 Changes to the Programming Interface for CDA   ?     V1.2  This section describes the changes to the programming >           interface for this version of CDA Run-Time Services.  E           This version provides a new set of header files that define B           CDA constants, types, and routines using portable namingE           conventions. By using these new naming conventions, you can C           use a wider variety of C compilers to minimize the amount ;           of system-specific code in your CDA applications.   B           The names of the new set of header files are the same as?           the names of the previous set of header files, except.B           that the dollar sign ($)  has been removed. For example,B           the cda$msg.h include file is now called cdamsg.h. Other?           examples include the following: The DDIF$K_DSC_MAJOR_lE           VERSION symbol is now declared as DDIF_K_DSC_MAJOR_VERSION,oA           and the CDA$_NORMAL status value is now defined as CDA_g           NORMAL.o  C           The previous set of header files is also included in this E           version, but these files will no longer be updated. Changes B           introduced since the release of DECwindows Motif VersionC           1.1 (for example, the new definitions for audio support), C           are available only in the new set of header files. To useqD           the new CDA features, change the file names in your source           code.t       3-20           I                                                  Programmer Release Notes I                                                      3.14 CDA Application     B               The new set of header files supplements the previousF               set of header files. If you want to write ANSI-compliantG               applications using CDA definitions and CDA Toolkit calls, H               use the new set of header files. However, you can continueH               to use the header files that define symbols containing theH               dollar sign ($) provided you choose a non-ANSI compilation               mode.d  @               By using the previous set of header files, you canC               successfully build existing source code that uses thea*               previous naming conventions.  @               See Table 3-5 for a list of new header file names.  I               Table_3-5_New_Header_File_Names____________________________   I               Previous_Name____New_Name__________________________________p  '               cda$def.h        cdadef.hS  '               cda$msg.h        cdamsg.h_  (               ddif$def.h       ddifdef.h  (               dtif$def.h       dtifdef.h  '               cda$ptp.h        cdaptp.h   '               cda$typ.h        cdatyp.he  '               dvr$msg.h        dvrmsg.h   )               dvr$cc_def.h     dvrccdef.hP  )               dvr$cc_ptp.h     dvrccptp.h   (               dvr$decw_def.h   dvrwdef.h  I               dvr$decw_ptp.h___dvrwptp.h__________________________________  9         3.14.2.3 Changes to External Reference Processinge  I         V1.2  CDA Run-Time Services supports relative file specificationsCC               for external references. Relative references are also F               supported: that is, a reference where the directory pathE               is not fully specified but is relative to the directoryi*               path of the parent document.  I                                                                      3-21                 Programmer Release Notes     3.14 CDA Application    -     3.14.2.4 Message for Style Guide Fallbackf  E     V1.2  The following message is displayed when a local style guideo           cannot be found:  B       STYGDEFBK, Fallback to nonlocale-specific style guide: file-
          specp            Level: Informationalt  E          Explanation: Since the locale-specific style guide cannot be D          found, the nonlocale-specific version of the style guide is          used.  6     3.14.2.5 Using Logical Names with CONVERT Commands  A     V1.2  During a document conversion, if a logical name is usedoB           to specify the directory of the primary document and theA           document file extension is omitted, external referencesM=           that contain relative file specifications cause thes           conversion to fail.   E           This failure occurs because the back-end converter examines B           the converter processing options, although the front-end?           converter opens the input file. Because the converter A           software cannot predict what default file extension the C           front-end converter might apply, it uses the OpenVMS file E           services to resolve the logical name and to find the actualgD           file specification so that the directory can be parsed and1           extended with a relative specification.   D           The conversion fails only when the external reference uses)           a format such as the following:n             sys$login:mydoco  ?           In this case, the reference will not be resolved. TheM@           reference is resolved in all other cases. For example:             sys$login:mydoc.doc            disk$:[smith]mydoc            disk$:[smith]mydoc.doc           3-22    e      I                                                  Programmer Release NotesrI                                                      3.14 CDA Applicationo    /         3.14.2.6 Restructuring Shareable Images   C         V1.2  The CDA Viewer includes two shareable images to allow H               installation on systems where DECwindows is not installed.  C               In DECwindows Motif Version 1.2 for OpenVMS software,rC               shareable images that use the X services are renamed.OA               Table 3-6 lists the shareable images in the various )               versions of the CDA Viewer.   I               Table_3-6_Names_of_Shareable_Images________________________n                 CDAlI               Version_____Image_Name_______Description___________________s  @               Version     CDA$ACCESS       CDA Run-Time Services;               1.6                          shareable image.o  B                           DDIF$VIEWSHR     Callable viewer widget.  @               Version     CDA$ACCESS       CDA Run-Time Services;               1.7                          shareable image.   G                           DDIF$VIEWSHR     The DDIF$DECW_VIEWSHR widgetaF                           DDIF$DECW_       is a callable viewer widgetH                           VIEWSHR          that uses the LIB$FIND_IMAGE_G                           DDIF$CC_VIEWSHR  SYMBOL routine to invoke the H                                            DDIF$DECW_VIEWSHR (DECwindowsI                                            interface) and DDIF$CC_VIEWSHRtE                                            (character-cell interface) 3                                            widgets.l  @               Version     CDA$ACCESS       CDA Run-Time Services;               1.8                          shareable image.i               Version                1.8A  G                           DDIF$VIEWSHR12   The DDIF$VIEWSHR12 widget isiH                                            a callable viewer widget thatH                                            uses LIB$FIND_IMAGE_SYMBOL toI                                            invoke the DDIF$DECW_VIEWSHR12 E                                            (DECwindows interface) andgF                                            DDIF$CC_VIEWSHR (character-I               _____________________________cell_interface)_widgets.______c  I               By using the LIB$FIND_IMAGE_SYMBOL routine to reference theaI               entry points to the DDIF$DECW_VIEWSHR, DDIF$DECW_VIEWSHR12, H               and DDIF$CC_VIEWSHR images, an application can dynamically  I                                                                      3-23o    n           Programmer Release Notes     3.14 CDA Application    B           determine whether it can execute in a given environment.B           The DDIF$VIEW.EXE application now replaces this routine.  @           The previous DDIF$VIEWSHR.EXE shareable image is still>           included to maintain compatibility with applicationsD           linked against it. However, new applications (and previousB           applications that take advantage of new features) should'           use the new shareable images.        3.15 DECterm Programming  9           This section contains information about DECtermn           programming.  )     3.15.1 Page-Movement Escape Sequencesi  :     V1.2  The following page-movement escape sequences are!           implemented in DECterm:i  1               NP       <CSI> Pn U       Next Page 5               PP       <CSI> Pn V       Previous Pagea>               PPA      <CSI> Pn P       Page Position Absolute>               PPB      <CSI> Pn R       Page Position Backward>               PPR      <CSI> Pn Q       Page Position Relative  <           Note that "Pn" is the number of pages to move; theA           exception is PPA, where "Pn" is the actual page number.y  C              ________________________ Note ________________________   A              DECterm does not support cursor coupling; the cursorg=              is always bound to the current (displayed) page.i  C              ______________________________________________________s       3.15.2 DECCRA Sequence  =     V1.2  DECterm supports the DECCRA (Copy Rectangular Area)e@           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 copyr/           from one off-screen page to another).            3-24 c  i      I                                                  Programmer Release NotestI                                                  3.15 DECterm Programmingt             3.15.3 DECLFKC Sequenceh  F         V1.2  Since DECterm does not have a user interface to redefineA               the F5 (Break) key, the DECLFKC (Local Function KeyeH               Control) sequence redefines the F5 key when "0" (all keys)<               is used to select which key is to be modified.  "         3.15.4 ReGIS Input Cursors  G         V1.2- DECterm supports the following input cursors: cross-hair, F         3     rubber-band line, diamond, and rubber-band rectangle. To  F               select input cursors use the S(C(In)) command. Table 3-7$               shows the values of n.  I               Table_3-7_ReGIS_Input_Cursors-Cursor_styles_and_Values_____o  I               Cursor_Style__________Variable_n___________________________s  +               Cross-hair            Omitted   %               Cross-hair (default)  0a  %               Diamond               1   %               Cross-hair            2   %               Rubber-band line      3e  %               Rubber-band           4aI               rectangle__________________________________________________a  F                 ________________________ Note ________________________  C                 If a shape other than the diamond cursor is desired =                 when n is equal to 1, define the logical nameaB                 DECW$DECTERM_REGIS_CURSOR to be one of the numbers>                 defined in the SYS$LIBRARY:DECW$CURSOR.H file.  F                 ______________________________________________________  )         3.16 DECwindows OSF/Motif Toolkite  <               This section contains information about notes,H               restrictions, and corrections for the DECwindows OSF/Motif               Toolkit.  I                                                                      3-25a s              Programmer Release Notes%     3.16 DECwindows OSF/Motif Toolkitu    )     3.16.1 Motif Text Widget Translationsa  C     V1.0  To implement virtual bindings, it is necessary for CompaqaB           to modify the default XmText and XmTextField translationD           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 virtuald:           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.s       3.16.2 Upward Compatibility   =     V1.0  The combination of DECW$DWTLIBSHR, DECW$DWTSHR, and >           DECW$XTSHR shareable images is intended to be binaryB           and upwardly compatible with the previous DECW$DWTLIBSHR?           shareable image. A possible exception is applicationsaB           that dynamically activate the image DECW$DWTLIBSHR using?           LIB$FIND_IMAGE_SYMBOL. The problem with dynamic image$A           activation is that the semantics of the Intrinsics haveeD           changed in places between the X Toolkit Intrinsics Release=           3 to the MIT X11 Release 4 Intrinsics. A previously =           linked XUI application calls through entries in the ?           XUI transfer vector that use the X Toolkit Intrinsics A           Release 3 semantics of the Intrinsics. However, as soonc?           as that application relinks (or dynamically activatesd?           DECW$DWTLIBSHR), it uses the MIT X Toolkit IntrinsicsN0           Release 4 semantics of the Intrinsics.  ?           Applications that dynamically activate DECW$DWTLIBSHR D           should be changed to link directly against DECW$DWTLIBSHR.D           DECW$DWTLIBSHR is now a small, thin-layer, shareable imageB           that dynamically activates automatically the majority ofB           the toolkit code only when necessary. There is no reason>           for applications to continue to dynamically activate           DECW$DWTLIBSHR."  <           In addition, Compaq cannot guarantee binary upward;           compatibility in the future for applications that <           dynamically activate the toolkit shareable images.<           DECwindows toolkits (XUI and Motif) are based uponD           standards that Compaq does not control. When the standardsE           make an incompatible change, Compaq will change the toolkitr       3-26 t  ,      I                                                  Programmer Release NotesmI                                         3.16 DECwindows OSF/Motif Toolkita    C               to follow it. However, the intent is to add code that A               allows existing executable images to run unchanged.   =         3.16.2.1 Restrictions on Mixing Motif and XUI Widgets   E         V1.0  Mixing Motif and XUI widgets is restricted. The problem F               results from the fact that both XUI and Motif have theirA               own Vendor Shell widget class. If an application is_D               linked against XUI and not Motif, the XUI Vendor ShellE               widget class is used in order to maintain compatibilityrF               with DECwindows XUI. If an application is linked againstG               Motif, the Motif Vendor Shell widget class is used. MotifSE               widgets require the Motif Vendor Shell; XUI widgets are H               compatible with the Motif Vendor Shell. The problem occursG               when an XUI-only application dynamically activates (usingnG               LIB$FIND_IMAGE_SYMBOL) a shareable image that uses Motif.iH               The toolkit makes the decision to use the XUI Vendor ShellF               when the toolkit is initialized and the Motif widgets inD               the dynamically activated shareable image do not work.  D               The workaround is to add the application image name toE               the DECW$USE_XM_VENDOR_SHELL logical name. This logical E               name contains a comma-separated list of image names for.E               which the toolkit is to use the Motif Vendor Shell. TheeH               value of DECW$USE_XM_VENDOR_SHELL logical name defaults toG               NOTES$MAIN. To add additional image names to this logicalC(               name, enter the following:  =               $ DEFINE DECW$USE_XM_VENDOR_SHELL "NOTES$MAIN,- +               _$ yourimage1,yourimage2,..."f  @               Note that DECW$USE_XM_VENDOR_SHELL does not affectF               applications that use Motif since they are already using%               the Motif Vendor Shell.   C         3.16.3 Compile-Time Incompatibilities in Motif Header Files   I         V1.2- Several macro definitions are removed from the Motif header E         3     files in the OSF/Motif programming support. The changese  0               affect the following header files:  #               o  DECW$INCLUDE:XMP.H   7                  The following definitions are removed:s  9                  -  #define XmLONGBITS sizeof(Cardinal)*8e  9                  -  #define XmHALFLONGBITS (XmLONGBITS/2)v  I                                                                      3-27. h              Programmer Release Notes%     3.16 DECwindows OSF/Motif Toolkit     C              These macros are replaced in the same header file withn!              the following macro:o                -  XmOFFSETBITS  <              Update the code to call the XmOFFSETBITS macro.  !           o  DECW$INCLUDE:TEXTP.Ht  3              The following definitions are removed:   )              -  #define MAXINT 2147483647s9                 /* Biggest number that can fit in long */i  &              -  #define NODELTA MAXINT  D              The definition of MAXINT is operating-system dependent.B              Include this definition in applications in one of the              following ways:  :              -  Include the appropriate system-header file  #              -  Define the constant   #     3.17 OSF/Motif Example Programsc  ?           This section describes example programs from the Openh;           Softare Foundation (OSF) that are included in the <           DECwindows Motif Version 1.2 for OpenVMS software.  (     3.17.1 Cut and Paste Example Program  C     V1.2  This example demonstrates the use of the Motif Clipboard. @           You can cut and paste application-defined data formats$           using the XmClipboard API.  C           Run two cut/paste clients and transfer graph values using )           the pull-down and pop-up menus.,  "     3.17.2 DNDDemo Example Program  E     V1.2  This example illustrates a typical use of the drag-and-dropo           feature.  B           When the example starts, it does not have any valid dropC           sites. It starts with different color rectangles that act D           as drag sources for dragging the colors around. Create the            drop sites as follows:  ?           o  Move the pointer into the drawing area (with white               background).i       3-28           I                                                  Programmer Release Notes I                                           3.17 OSF/Motif Example Programss    I               o  Press MB1 and drag. You see the "rubber-banding" effect.h  ?               o  Release MB1 after dragging a desired distance.   B                  A black rectangle appears. You can create as many(                  rectangles as you like.  E               The rectangles inside the drawing area that you createdtF               act as valid drop sites for colors. You can test this byE               initiating the drag from the yellow color rectangle andhG               dragging over to one of the rectangles inside the drawingi%               area and releasing MB2.h  C               To initiate a drag, move the pointer over to the drag @               source, press BTransfer (which is MB2 by default),D               and start to drag. Notice that the cursor changes to aH               painter's palette in the same color as the color rectangle/               from which the drag is initiated.   ;               While you are dragging, notice the following:-  B               o  When dragging over the root window, the drag icon8                  consists of only the painter's palette.  I               o  When dragging over parts of the drawing area where thereuF                  are no rectangles, the drag icon changes to include aF                  "DO NOT ENTER!" sign on top of the painter's palette.  D               o  When dragging over any of the rectangles inside theH                  drawing area, the "DO NOT ENTER!" sign is replaced with#                  a painter's brush.   E               To perform a drop, release MB2. If you release MB2 withaC               the pointer over any part of the drawing area outsideiD               of the rectangles, or anywhere on the root window, theB               drag icon snaps back to the point of drag initiationE               and disappears. This is an indication that the drop youlH               attempted failed. If you release MB2 with the pointer overE               any of the rectangles inside the drawing area, the dragrF               icon disappears into the background; this indicates thatE               the drop was a success. The rectangle on which the drop F               was attempted, becomes filled in with the color that was               dragged.  I               The rectangles inside the drawing area act as drag sources.sF               Initiate the drag with the pointer on any rectangle, andC               the cursor changes to a rectangle (either of the same C               size or a smaller size depending on the X cursor size   I                                                                      3-29     3           Programmer Release Notes#     3.17 OSF/Motif Example Programs     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           If you want to copy the rectangle to a new position, useE           the appropriate modifier key while dragging, or at the timemA           you attempt the drop (Ctrl is the modifier key for copy C           in the current implementation). When you drag a rectangle_E           with no modifier key pressed or with the Shift key pressed,DB           the solid rectangle from where the drag was initiated isB           replaced by a hollow rectangle with dotted-line borders.E           It continues this way for the duration of the drag or untilC@           you press the Ctrl key, which changes the operation to@           Copy. At that time it regains its original solid form.  C              ________________________ Note ________________________D  @              During dragging you can cancel the drag by pressingC              the Cancel key (F11). Also, you can press the Help key C              to get information about whether the drop will succeedI*              and possible drop operations.  C              ______________________________________________________        3.17.3 Dogs Example Program   D     V1.1  This example uses the dog and square widgets. It shows howE           to incorporate new widgets into the UIL source by using the             user-defined function.  ;           The dogs example program allows you to change the B           DogNwagTime and SquareNmakeSquare resources dynamically.  B           If you have a system with sound generation features, youC           might want to change the bark callback to something other            than XBell().d       3.17.3.1 Dog Widget   D     V1.1  The dog widget (DogWidget) demonstrates how to subclassify@           a primitive widget that remains binary compatible withB           future versions of Motif. It uses XmResolvePartOffsets()6           and associated macros and implements all the>           recommendations in the XmResolvePartOffsets manpage.       3-30 s  _      I                                                  Programmer Release NotesaI                                           3.17 OSF/Motif Example Programs     F               The dog widget is a subclass of XmPrimitive. It can barkE               and wag its tail. If you want more advanced tricks, you3I               must subclassify it, or replace up.bm, down.bm, and bark.bm )               with more advanced bitmaps.u  9               The dog widget has the following resources:c  C               o  DogNwagTime: Time in milliseconds between each wag.  G               o  DogNbarkTime: Time in milliseconds the bark graphic isw                  displayed  E               o  DogNbarkCallback: Callback called by the bark actionl  <               The dog widget has the following translations:  4               o  osfActivate/Return/Space/MB1 = Bark  !               o  W/MB2 = Wag taila  0               o  S/Shift-MB2 = Stop wagging tail                 o  osfHelp = Helpp           3.17.3.2 Square Widget  ?         V1.1  The square widget (SquareWidget) demonstrates howD=               to subclassify a constraint widget that remains >               binary compatible with future versions of Motif.>               It uses XmResolveAllPartOffsets() and associatedB               macros and implements all the recommendations in the.               XmResolveAllPartOffsets manpage.  A               The square Widget is a subclass of XmBulletinBoard. D               It forces its children to be square using a constraint               resource._  G               The square widget has the resource SquareNmajorDimension.uB               This resource determines which dimension is used forB               the new size of the child. Values are SquareWIDTH or               SquareHEIGHT._  ;               The square widget has the constraint resourcesE               SquareNmakeSquare. This resource determines whether theaI               child is forced to be square or set to its preferred shape.u  I                                                                      3-31     n           Programmer Release Notes#     3.17 OSF/Motif Example Programs4    #     3.17.4 Helloint Example Program   D     V1.2  This example is a simple UIL/Xm program with a label and a           push button.  D           With this version, you can choose a Kanji, Hebrew, French,+           or English interface at run time.r  <           The program uses the file LOCALSTRINGS.UID for all<           language-specific interfaces. To change languages,@           copy one of the LOCALSTRINGS_*.UID files to DECW$USER_?           DEFAULTS:LOCALSTRINGS.UID. Then, use the logical nameCA           LANG or the xnlLanguage resource to set the locale. SetsC           the LOCALSTRINGS suffix and the locale name to one of thea           following:  E           ___________________________________________________________ E           Locale______Interface_Type__________________________________             Japan       Kanjis             Hebrew      Hebrew             French      French  E           English_____Standard_English_______________________________   D           To define the xnlLanguage resource, add the following line*           to your DECW$XDEFAULTS.DAT file:             *xnlLanguage:locale   A           The following fonts are needed for the helloint example            program:  E           ____________________________________________________________E           Locale____Font_Name________________________________________o  D           French    -adobe-helvetica-medium-r-normal-12-120-75-75-p-                      67-iso8859-1  E           English   -adobe-times-medium-r-normal-14-100-100-100-p-74-                      iso8859-1B  B           Hebrew    -Misc-Fixed-Medium-R-Normal-13-120-75-75-C-80-                     ISO8859-8   &           Japan     -*-JISX0208.1983-1  E           __________-*-JISX0201.1976-0_______________________________   B           If you do not have these fonts installed on your system,A           either change the UIL files to reference other fonts or        3-32           I                                                  Programmer Release NotesiI                                           3.17 OSF/Motif Example Programsi    H               install the *.DECW$BDF fonts provided in the DECW$EXAMPLESB               directory. See Managing DECwindows Motif for OpenVMSC               Systems for instructions on how to install new fonts.   )         3.17.5 Hellomotif Example Programt  H         V1.2  This example is a simple UIL/Xm program with a label and a               push button.  (         3.17.6 Motifanim Example Program  H         V1.1  The motifanim program demonstrates the following OSF/Motif               features:d  E               o  Declaration of icon/bitmap using UIL for portabilityT                  across visuals   >               o  Exchange of value between UIL and C using Mrm  -               o  Use of the Motif form widgeta  I               o  Background procedure running while the client process isi:                  waiting for input (Xt intrinsics feature)  D               This example lets you animate a set of pixmaps in an XI               window. The pixmaps are not fixed by motifanim but are reada1               at startup from existing UID files.i  E               The syntax of all the animation.uid files can add a newlF               set of pixmaps to be animated using motifanim. Some tree7               examples of animation data files include:r                    dog.uil                  plane.uil  G               The default animation is dog. To run the example with thes;               other animations, use the following commands:   )               $ SET DEFAULT DECW$EXAMPLEST7               $ motifanim := "$DECW$EXAMPLES:motifanim" %               $ motifanim -anim plane   I               The files motiflogo.uil, motifanim.uil, and motifanim.c are 1               the core components of the program.L  I                                                                      3-33                 Programmer Release Notes#     3.17 OSF/Motif Example Programs     -     3.17.7 Motifgif and Pict Viewing Programsn  0     V1.2  The following .gif files are provided:  ?           o  TOUCAN.GIF, which is a picture of a tropical bird.C  D           o  CHALLENGER.GIF, which is a picture of the space shuttle              Challenger.  A     V1.1  The motifgif and pict programs work together to display A           a .gif formatted picture. The motifgif program displaystC           a .gif file within Motif constructs. The motifgif programa8           looks for .gif files in the current directory.  @           The motifgif program has three significant components:             o  motifgifs  B              The source and executable code in this directory is aA              Motif program driving the display of a .gif picture.              o  pict   B              The program called by motifgif that displays a bitmapE              of a .gif picture file. This program used to be xgif but /              has since been converted to Motif.d  5           The following problems exist with motifgif:b  .           o  Resizing a picture does not work.  C           o  The -d option is not used when calling pict, so remotea@              displays must set the DISPLAY environment variable.  %     3.17.8 Motifshell Example Programt  @     V1.2  The motifshell program is an example of an environment?           created using Motif. The purpose of the example is toc@           show how Motif may be used as a standalone environment7           for dispatching other programs and utilities.   C           The motifshell program is written in C code. There are non           UIL references.a  C              ________________________ Note ________________________e  C              Displaying a file listing or process status takes some B              time. These operations are accomplished by spawning aB              DCL command, capturing the output in a file, and then              reading the file.       3-34    k      I                                                  Programmer Release NotesDI                                           3.17 OSF/Motif Example Programse    ?                 The default font is proportionally spaced. SometC                 listings are more readable if a fixed space font isMF                 used, such as Courier. Use the Font option to select a                 different font.o  F                 ______________________________________________________  '         3.17.9 Periodic Example Program   H         V1.2  The periodic example is a demonstration of the displayableG               widgets in Motif. The program displays Motif widgets in ao$               periodic chart format.  (         3.17.10 Textedit Example Program  F         V1.2  The textedit program is a primitive text editor based onE               the Motif XmText widget that makes use of its XmNsource E               resource to allow multiple views of the same underlying                text.e  8               Table 3-8 describes the View menu options.  I               Table_3-8_View_Menu_Options________________________________   I               Option_______Description___________________________________n  F               Split Pane   Adds a new independently scrollable view of$                            the text.  5               Remove Pane  Removes a designated pane.i  I               One_Pane_____Removes_all_panes_except_the_designated_pane._a  E               The designated pane is determined in the following way:-  G               o  If using an explicit focus policy, it is the last viewr!                  which had focus.T  E               o  If using a pointer focus policy, it is the last view 0                  with which the user interacted.  A               The designated pane is also the one whose clipboard F               contents are pasted when Paste is selected from the Edit               Menu.   I               The textedit sources are separated into independent layers.lE               Textedit contains the source files listed in Table 3-9.i  I                                                                      3-35r c              Programmer Release Notes#     3.17 OSF/Motif Example Programs     E           Table_3-9_Textedit_Source_Files____________________________M             FileE           Name_____Description_______________________________________   C           tfile.c  The code to read, write, and remove files. Hides C                    any operating system or filesystem dependencies.   E           app.c    Uses tfile.c to provide all the code to manipulatenD                    files and their related buffers. This is toolkit-                    dependent.o  ;           tk.c     Isolates dependencies on the Xm Toolkit.   >                    The first half of the file provides utility:                    routines and a toolkit-independent (butC                    application-specific) interface that can be usedoA                    by the toolkit-independent dialog layer of thet                    application.v  >                    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 the B                    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 code *                    is toolkit-independent.  ?           textedit.Initializes the application and instantiatese@                    widget hierarchies. The code hides the use ofE           _________UIL_and_Mrm_from_the_rest_of_the_application._____M  C              ________________________ Note ________________________d  7              Moving and removing files is not currentlyy              implemented.n  C              ______________________________________________________n           3-36 e  m      I                                                  Programmer Release Notes I                                           3.17 OSF/Motif Example Programs     )         3.17.10.1 Additional Translationsd  E         V1.2  Users familiar with emacs may want to add the following =               translations to their DECW$XDEFAULTS.DAT files:   U               *XmText.translations:     Mod1<Btn3Down>: scroll-cursor-vertically()\n\ ?                 Mod1<Btn3Motion>: scroll-cursor-vertically()\n\ 1                Ctrl<key>a: beginning-of-line()\n\g2                Ctrl<key>b: backward-character()\n\5                Ctrl<key>d: delete-next-character()\n\a+                Ctrl<key>e: end-of-line()\n\m1                Ctrl<key>f: forward-character()\n\ $                Ctrl<key>g: beep()\n\9                Ctrl<key>h: delete-previous-character()\n\,+                Ctrl<key>i: cut-primary()\n\ 2                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\e)                Ctrl<key>n: next-line()\n\a2                Ctrl<key>o: newline-and-backup()\n\-                Ctrl<key>p: previous-line()\n\w)                Ctrl<key>v: next-page()\n\o-                Ctrl<key>w: cut-clipboard()\n\ /                Ctrl<key>y: paste-clipboard()\n\.2                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\ -                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\e4                Mod1<key>less: beginning-of-file()\n\1                Mod1<key>]: forward-paragraph()\n\w/                Mod1<key>[: backward-paragraph()             I                                                                      3-37t p  h           Programmer Release Notes#     3.17 OSF/Motif Example Programse          3.17.11 View Example Program  B     V1.2  The view program is similar to the DCL command TYPE/PAGEB           using Motif with internationalization support. It allows1           you to view files in several languages.o  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:_  *           $ SET DEFAULT DECW$USER_DEFAULTS,           $ @DECW$EXAMPLES:FILEVIEW language  A           This command file copies the .UID and .DAT files to theu?           current directory. It sets the appropriate locale andh4           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 can1"           create secondary shells.  E           Each top-level shell is a parent of a Main Window, the workI)           area of which is a PanedWindow.n  1           The menu bar has the following entries:l  E           o  File-opening and closing files, creating new shells, andr              exiting  :           o  View-controlling the panes in the pane window             File Menut  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.              o  Open New Shellm  D              Creates a secondary shell similar to the primary shell.=              Files can be viewed in each shell independently.              o  Close  @              This entry only exists on the secondary windows. It>              destroys the top-level shell and closes the file.       3-38    r      I                                                  Programmer Release NotesrI                                           3.17 OSF/Motif Example Programsn                   o  Exiti  G                  This entry only exists on the primary shell; it closesg(                  the file and the shell.                 View Menut  ;               The view menu contains the following options:e                 o  New Pane   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 searches G                  the string. If the string is found, it is displayed in G                  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.   '         3.17.12 Xmpiano Example Programo  F         V1.2  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.t  D               At the bottom of the window is a set of notes that mayG               be used on the staff. Selecting one of these note buttonsiG               changes the active note accordingly. The selected note is 5               also displayed as the new mouse cursor.   E               Though the note selection is limited, it is possible toqH               play sharps as well as naturals. The program interface hasE               not been written to play flats. The staff automatically F               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 buttoniF               on a staff that is visible. The following menu items are               displayed:  I                                                                      3-39  g              Programmer Release Notes#     3.17 OSF/Motif Example Programsf               o  Add Voice  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 menu_=              bar relate to the staff that is being displayed.              o  Remove Voice   ?              Removes the staff as well as the connection to the_=              corresponding display. There is no undo for thisn@              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 Voice_  B              Plays the voice of the staff in which the right mouseE              was pressed. If the voice is the same as the local host,nB              the keys on the keyboard that correspond to the notesE              appear as though they are being pressed as the notes arelC              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 can_E              slow down the application significantly on many servers.              o  Play Allf  =              Plays all voices at the same time on each of thei               specified displays.             o  Save Voice   7              Saves the corresponding voice to a file. AeD              FileSelectionDialog is displayed to prompt for the name@              of the file in which to save the voice. The display1              connection information is not saved.t             o  Load Voices  <              Loads (appends) a previously saved voice to the!              corresponding staff.              o  Quitm  '              Exits the example program.i       3-40 X  r      I                                                  Programmer Release NotesEI                                           3.17 OSF/Motif Example Programso    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.a  H               To set the color of the notes, change the foreground colorG               of the application. To do this, use the -fg option on the (               command line. For example:  2               $ xmpiano :== $DECW$EXAMPLES:xmpiano                $ xmpiano -fg blue  %         3.17.13 Motif Sample Programsw  D         V1.2  Table 3-10 lists sample programs showing various Motif$               Toolkit functionality.                                                            I                                                                      3-41m r              Programmer Release Notes#     3.17 OSF/Motif Example Programs     E           Table_3-10_Motif_Sample_Programs___________________________o  E           File_Name_____Description__________________________________s  &           xmdialogs.c   dialog sampler  $           xmfonts.c     font browser  #           xmeditor.c    text editort  $           xmlist.c      list example  8           xmprotocol.c  window manager protocols example  1           xmter.c       shape & animation examplem  /           xmform.c      form attachment example   ;           xmforc.c      form attachment + rowcolumn example   <           xmmap.c       drawingarea + scrolledwindow example  1           xmgetres.c    resource fetching examplem  E           xmapdef.c_____app_defined_scrolled_window_example__________U  =           The following notes apply to these sample programs:C  A           1. The xmfonts program defaults to displaying the fontsCC              whose name length are less than 10 characters. On somet@              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 Manager .              to remove the window decorations.  ?           3. The xmform program displays a string made of MotifrD              widgets embedded in a Form. Use the following commands:  /              $ xmform :== $DECW$EXAMPLES:xmform.              $ 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,m$              xmform returns "MOTIF".       3-42    n      I                                                  Programmer Release Notes I                                           3.17 OSF/Motif Example Programs     A               4. The xmgetres program is an example of how to use_G                  XmGetSecondaryResourceData. Use the following commandst$                  to invoke xmgetres:  7                  $ xmgetres :== $DECW$EXAMPLES:xmgetres '                  $ xmgetres WidgetClassi  H                  The variable WidgetClass is optional. If WidgetClass isH                  omitted, it defaults to a class named "Widget". You canG                  also use the class "All", which displays the resources H                  for all the Xt and the Motif widgets. See the OSF/MotifF                  Programmer's Reference manual for a list of available                   widget classes.  (         3.17.14 Xmtravel Example Program  C         V1.2  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 well =               as be compliant with the OSF/Motif Style Guide.e  G               The program is just an example, many of the functions areE@               either not implemented or use predefined settings.  3         3.17.15 Resource Files for Example Programsw  I         V1.2  Many of the example programs have associated resource filespC               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 filese1               associated with them is as follows:   I               ___________________________________________________________eI               Example_Program_______Resource_File________________________e  5               DECW$CDPLAYER.EXE     DECW$CDPLAYER.DAT   0               FILEVIEW.EXE          FILEVIEW.DAT  0               PERIODIC.EXE          PERIODIC.DAT  1               MOTIFANM.EXE          MOTIFANIM.DAT   /               XMAPDEF.EXE           XMDEMOS.DATh  /               XMDIALOGS.EXE         XMDEMOS.DATp  /               XMEDITOR.EXE          XMDEMOS.DAT   I                                                                      3-43                 Programmer Release Notes#     3.17 OSF/Motif Example Programs   E           ___________________________________________________________ E           Example_Program_______Resource_File________________________r  +           XMFONTS.EXE           XMDEMOS.DAT   +           XMFORC.EXE            XMDEMOS.DAT   +           XMFORM.EXE            XMDEMOS.DAT_  +           XMGETRES.EXE          XMDEMOS.DATe  +           XMLIST.EXE            XMDEMOS.DAT_  +           XMMAP.EXE             XMDEMOS.DAT,  +           XMPROTOCOL.EXE        XMDEMOS.DAT   +           XMTER.EXE             XMDEMOS.DATn  E           XMTRAVEL.EXE__________XMTRAVEL.DAT_________________________p  D           If a resource file is not found, the example programs run,>           but some of the display attributes may be incorrect.  *     3.17.16 UID Files for Example Programs  D     V1.2  The UID files used by the example programs must be locatedD           in either the current directory or your DECW$USER_DEFAULTSD           directory. If they are not found, the application fails toC           start. The UID files can be copied from the DECW$EXAMPLESa           directory.  '     3.18 DECwindows Extensions to Motifa  C           This section contains information about the extensions toe           the Motif Toolkit.  )     3.18.1 DXmCSText Input Method Support   ?     V1.2  X11 R5 input method support is added to the DXmCSText >           widget. Specify input methods using the vendor shell@           XmNinputMethod resource. However, to maintain backward<           compatibility, the existing input method resources;           DXmNinputMethod and DXmNinputMethodType are still            available.  6     3.18.2 SVN-Horizontal Live Scrolling Not Supported  ;     V1.0  Horizontal live scrolling is not supported in thee4           Structured Visual Navigation (SVN) widget.       3-44 .  e      I                                                  Programmer Release NotescI                                       3.18 DECwindows Extensions to Motif_    ,         3.18.3 SVN Horizontal Separator Line  H         V1.1  When displaying an application that uses the SVN widget onH               a Sun system running OpenWindows Version 2, the horizontalF               separator line of the SVN widget is not always displayedG               due to a problem with the OpenWindows server. The problemr8               does not exist with OpenWindows Version 3.  5         3.18.4 DXmFormSpaceButtonsEqually Restriction   F         V1.1  The convenience routine DXmFormSpaceButtonsEqually sizesD               and spaces all widgets or gadgets equally if they haveE               a subclass of XmLabel or XmLabelGadget. The results areeB               undefined if a widget or gadget is not a subclass of'               XmLabel or XmLabelGadget.c  &         3.19 Display Server Extensions  H               This section contains information about the display server               extensions.d            3.19.1 X Image Extension  E         V1.1  Starting with DECwindows Motif Version 1.1 for OpenVMS,)D               DECwindows Motif supports the X Image Extension (XIE).H               XIE allows image display processing using resources on theF               server side of the X client-server model. XIE eliminatesH               the need to transmit image data repeatedly from the clientE               to the server and also allows data to be transmitted ina9               compressed form, reducing the network load.n  D               DECwindows Motif includes the XIE client side sharableI               library (XIE$SHRLIB.EXE) and C language header files. These H               allow applications to communicate with any X11 server that)               supports the XIE extension.<  D               An XIE program uses a structure called the XIEImage toB               describe image data on the client side. This generalE               mechanism describes data that the destination server isoD               incapable of processing. Consult the documentation forF               the server system for information on what data types andE               sizes are supported. Unless the documentation specifiesoC               different limits, the server is capable of processing F               unsigned byte (UdpK_DTypeBU), unaligned bit field (UdpK_F               DTypeVU), and aligned bit field (UdpK_DTypeV) data, withD               a maximum depth of 8 bits per pixel per component. TheF               XIE client library supports these data types, as well as  I                                                                      3-45a T  /           Programmer Release Notes"     3.19 Display Server Extensions    D           unsigned word (UdpK_DTypeWU), and a depth of up to 16 bits"           per pixel per component.  >           The XIE protocol and programming interface are beingC           standardized within the X Consortium for R6, and programslE           that use XIE will probably have to be modified. You can use @           the Image Display Services (IDS) component of DECimage?           Application Services for VMS as an alternative to thelB           XIE library interface. IDS provides a higher level model@           of image display and automatically uses XIE when it is$           available and appropriate.  D           XIE is documented in the DECimage Application Services for>           VMS X Image Extension Programmer's Reference Manual.  (     3.19.2 Client Side Extension Library  A     V1.1  Starting with DECwindows Motif Version 1.1 for OpenVMS,nB           Xlib added a client side library that allows VMS clients@           to issue Shape, XInput, Multibuffer, and shared memoryD           extension requests to servers that provide these features.=           (For example, the DECwindows X11 display server fort@           OpenVMS VAX does not support the Shape extension while=           the DECwindows X11 display server for OpenVMS Alpha A           system does support Shape.) The name of this library is            DECW$XEXTLIBSHR.EXE.  6           You must modify the linking file options for7           client applications that issue Shape, XInput,a:           Multibuffer, or shared memory extension requests;           to link to the Xlib extensions shareable image in A           SYS$LIBRARY:DECW$XEXTLIBSHR.EXE. Add the following linew&           to your linker options file:  +           SYS$LIBRARY:DECW$XEXTLIBSHR/SHARE   @           For more information on Shape, XInput, and Multibuffer?           extensions, see the following text files in SYS$HELP:.                DECW$SHAPE.TXT               DECW$XINPUT.TXT!              DECW$MULTIBUFFER.TXTi           3-46 s  l      I                                                  Programmer Release NotestI                                            3.19 Display Server Extensions     ;         3.19.3 Shared Memory Extension Support (Alpha Only)p  G         V1.2  On OpenVMS Alpha systems, shared memory extension supporteF               provides the capability to share memory XImages. This isF               a version of the XImage interface where the actual imageF               data is stored in a shared-memory segment. Consequently,B               the image does not need to be moved through the XlibC               interprocess communication channel. For large images,dF               use of this extension can result in dramatic performance               increases.  H               Support for shared memory pixmaps is also provided. SharedF               memory pixmaps are two-dimensional arrays of pixels in aG               format specified by the X server, where the image data is E               stored in the shared memory segment. Through the use ofdI               shared memory pixmaps, you can change the contents of theses6               pixmaps without using any Xlib routines.  F               These routines are included in the client side extensionE               library. See Section 3.19.2 for details on linking this                library.  3         3.19.3.1 How to Use Shared Memory Extensiont  I               Code that uses the shared memory extension must include thei%               following header files:i  -               # include "DECW$INCLUDE:Xlib.h" ,               # include "DECW$INCLUDE:shm.h"-               # include "DECW$INCLUDE:XShm.h"T  C               Any code that uses the shared memory extension should D               first check that the server provides the extension. InI               some cases, such as running over the network, the extension                does not work.  E               To check if the shared memory extension is available ong>               your system, call one of the following routines:  1               Status XShmQueryExtension (display) %                      Display *displays  F               Status XShmQueryVersion (display, major, minor, pixmaps)&                      Display *display;(                      int *major, *minor;"                      Bool *pixmaps  I                                                                      3-47e                Programmer Release Notes"     3.19 Display Server Extensions    9           The following table lists each argument and itsg           description.  E           ___________________________________________________________cE           Argument____Description____________________________________t  *           display     The current display.  =                       If the shared memory extension is used, >                       the return value from either function isB                       True. Otherwise, your program operates using.                       conventional Xlib calls.  ;           major       Major version number of the extensionaC                       implementation. Returned by XShmQueryVersion.p  ;           minor       Minor version number of the extensionpC                       implementation. Returned by XShmQueryVersion.   E           pixmaps_____True,_if_shared_memory_pixmaps.________________h  (     3.19.3.2 Using Shared Memory XImages  C           The following sequence shows the process for creating ando&           using shared memory XImages:  7           1. Create the shared memory XImage structure.a  D           2. Create a shared memory segment to store the image data.  .           3. Attach the shared memory segment.  ?           4. Inform the server about the shared memory segment.i  *           5. Use the shared memory XImage.  C           The following sections explain each step in this process:   :           Step 1-Creating a Shared Memory XImage Structure  C           To create a shared memory XImage, use the XShmCreateImaget2           routine, which has the following format:  H           XImage *XShmCreateImage (display, visual, depth, format, data,-                       shminfo, width, height) "                  Display *display;                   Visual *visual;3                  unsigned int depth, width, height;                   int format;                  char *data;*                  XShmSegmentInfo *shminfo;       3-48 t  r      I                                                  Programmer Release NotescI                                            3.19 Display Server Extensionss    I               Most of the arguments are the same as for XCreateImage (See G               the X Window System for a description of the XCreateImageeE               routine.) Note that there are no offset, bitmap_pad, orlG               bytes_per_line arguments. These quantities are set by thenF               server, and your code needs to abide by them. Unless youH               have already allocated the shared memory segment (see step8               2), you pass in NULL for the data pointer.  F               The argument shminfo is a pointer to a structure of typeB               XShmSegmentInfo. Allocate one of these structures soD               that it has a lifetime at least as long as that of theG               shared memory XImage. There is no need to initialize thise;               structure before the call to XShmCreateImage.m  G               If successful, an XImage structure is returned, which youp/               can use for the subsequent steps.   7               Step 2-Creating the Shared Memory Segmentt  D               Create the shared memory segment after the creation ofD               the XImage because the XImage returns information that4               indicates how much memory to allocate.  A               The following example illustrates how to create thee               segment:  2               shminfo.shmid = shmget (IPC_PRIVATE,M                       image->bytes_per_line * image->height, IPC_CREAT|0777);m  E               This example assumes that you called your shared memory H               XImage structure. A return value of 0 indicates the sharedI               memory allocation has failed. Use the bytes_per_line field,mI               not the width you used to create the XImage, as they may bew               different.  F               Note that the shared memory ID returned by the system isG               stored in the shminfo structure. The server needs that IDs.               to attach itself to the segment.  8               Step 3-Attaching the Shared Memory Segment  H               Attach the shared memory segment to your process as in the                following example:  J               shminfo.shmaddr = image->data = shmat (shminfo.shmid, 0, 0);  H               The address returned by shmat is stored in both the XImage2               structure and the shminfo structure.  I                                                                      3-49  t              Programmer Release Notes"     3.19 Display Server Extensions    A           To finish supplying arguments in the shminfo structure, @           decide how you want the server to attach to the shared?           memory segment, and set the shminfo.readOnly field asM           follows:  #           shminfo.readOnly = False;r  C           If you set the structure to True, the server cannot writeu7           to this segment, and XShmGetImage calls fail.   C              ________________________ Note ________________________t  <              The shared memory segment routines are provided@              with DECwindows Motif. Using global sections, these@              routines emulate the shared memory routines on UNIX              systems.   C              ______________________________________________________r  E           Step 4-Informing the Server About the Shared Memory Segmento  D           Tell the server to attach to your shared memory segment as#           in the following example:v  /           Status XShmAttach (display, shminfo);a  ?           If successful, a nonzero status is returned, and youri"           XImage is ready for use.  /           Step 5-Using the Shared Memory XImagec  A           To write a shared memory XImage into an X drawable, useFE           the XShmPutImage routine. The XShmPutImage routine uses thea           following format:   <           XShmPutImage (display, d, gc, image, src_x, src_y,I                                dest_x, dest_y, width, height, send_event)o"                  Display *display;                  Drawable d;                  GC gc;d                  XImage *image; 2                  int src_x, src_y, dest_x, dest_y;,                  unsigned int width, height;!                  Bool send_event;e  B           The interface is identical to the XPutImage routine (seeD           the X Window System), except for one additional parameter,>           send_event. If this parameter is passed as True, theB           server generates a completion event when the image write       3-50 g  _      I                                                  Programmer Release Notes I                                            3.19 Display Server Extensions     F               is complete. This allows your program to know when it isI               safe to begin manipulating the shared memory segment again.A  F               The completion event is of the type XShmCompletionEvent,*               which is defined as follows:  #                    typedef struct { ;                        inttype;              /* of event */aN                        unsigned long serial; /* # of last request processed */X                        Bool send_event;      /* true if came from a SendEvent request */R                        Display *display;     /* Display the event was read from */F                        Drawable drawable;    /* drawable of request */=                        int major_code;       /* ShmReqCode */ @                        int minor_code;       /* X_ShmPutImage */Q                        ShmSeg shmseg;        /* the ShmSeg used in the request */ N                        unsigned long offset; /* the offset into ShmSeg used */)                    } XShmCompletionEvent;   C               To determine the event type value that is used at runuH               time, use the XShmGetEventBase routine as in the following               example:  S                    int CompletionType = XShmGetEventBase (display) + ShmCompletion;t  F                 ________________________ Note ________________________  B                 If you modify the shared memory segment before theC                 arrival of the completion event, the results may be.                 inconsistent.o  F                 ______________________________________________________  E               To read image data into a shared memory XImage, use thetD               XShmGetImage routine, which uses the following format:  G               Status XShmGetImage (display, d, image, x, y, plane_mask) &                      Display *display;                       Drawable d;#                      XImage *image;e                      int x, y;.                      unsigned long plane_mask;  =               The following table lists each argument and itst               description.  I                                                                      3-51a a  n           Programmer Release Notes"     3.19 Display Server Extensions  E           ___________________________________________________________ E           Argument____Description____________________________________H  .           display     The display of interest.  *           d           The source drawable.  -           image       The destination XImage.o  :           x           X-offset within the source drawable.  :           y           Y-offset within the source drawable.  E           plane_mask__The_planes_that_are_to_be_read.________________t  ?           To destroy a shared memory XImage, first instruct thetD           server to detach from it, then destroy the segment itself.C           The following example illustrates how to destroy a shared            memory XImage:  (           XShmDetach (display, shminfo);            XDestroyImage (image);"           shmdt (shminfo.shmaddr);.           shmctl (shminfo.shmid, IPC_RMID, 0);  (     3.19.3.3 Using Shared Memory Pixmaps  @           Unlike X images, for which any image format is usable,C           the shared memory extension supports only a single format.D           for the data stored in a shared memory pixmap (XYPixmap orB           ZPixmap). This format is independent of the depth of theE           image and independent of the screen. (For 1-bit pixmaps theo            format is irrelevant.)  @           The XShmPixmapFormat routine returns the shared memoryD           pixmap format for the server. The XShmPixmapFormat routine#           has the following format:   (           int XShmPixmapFormat (display)"                  Display *display;  D           Your application can only use shared memory pixmaps in theD           format returned by the XShmPixmapFormat routine (includingB           bits-per-pixel). To create a shared memory pixmap do the           following:  A           o  Create a shared memory segment and shminfo structure @              exactly the same way as is listed for shared memoryD              XImages steps 1 through 4 (see Section 3.19.3.2). While@              it is not necessary to create an XImage first (step@              1), doing so incurs little overhead and provides an5              appropriate bytes_per_line value to use.a       3-52           I                                                  Programmer Release NotesiI                                            3.19 Display Server Extensionsd    A               o  Call the XShmCreatePixmap routine, which has the)"                  following format:  K                  Pixmap XShmCreatePixmap (display, d, data, shminfo, width,T9                                           height, depth);p)                         Display *display; #                         Drawable d; #                         char *data;m1                         XShmSegmentInfo *shminfo;s:                         unsigned int width, height, depth;  I                  The arguments are the same as for XCreatePixmap (see thecG                  X Window System) except for two additional parameters, D                  data and shminfo. The data parameter is the pointerD                  to the shared memory segment and is the same as theI                  shminfo.shmaddr field. The shminfo parameter is the same +                  as the previous structure.   C                  If successful, a pixmap is returned, which you canyE                  manipulate. You can manipulate its contents directlyiI                  through the shared memory segment. Shared memory pixmapsrI                  are destroyed with the XFreePixmap routine, although you9I                  should detach and destroy the shared memory segment (seef-                  step 4 in Section 3.19.3.2).d  ,         3.19.4 Using Extension Include Files  D         V1.2  To ensure that programs that contain extension includeG               files compile properly, add the logical name DECW$INCLUDE 5               to the C include directory search list.   D               To add the logical name for VAX C, enter the following               command:  -               $ DEFINE C$INCLUDE DECW$INCLUDEd  D               To add the logical name for DEC C, enter the following               command:  5               $ DEFINE DECC$USER_INCLUDE DECW$INCLUDEe          I                                                                      3-53x s              Programmer Release Notes*     3.20 Internationalization Enhancements    *     3.20 Internationalization Enhancements  ?     V1.2- Additional internationalization support enables users$?     3     to view and convert files that contain Asian-languageo             characters.i  ?           This section provides the following information aboutE9           internationalization support for the CDA ViewerP           application:  @           o  Section 3.20.1, Using the CDA Viewer to View Asian-              Language Text  A           o  Section 3.20.2, Converting Files That Contain Asian-                Language Characters  ;     3.20.1 Using the CDA Viewer to View Asian-Language Texty  C     V1.2- You can use the CDA Viewer in two ways to view text filesu(     3     that contain Asian characters:  C           o  Specify an options file to the CDA Viewer application.m  B           o  Define logical names at the DCL command level or in a              LOGIN.COM file.  @           Refer to the DECwindows Motif for OpenVMS Applications;           Guide for information about using the CDA Viewer.o  '     3.20.1.1 Specifying an Options File   B     V1.2- Specify an options file by including a one-line entry in+     3     the file in the following format:i  0           TEXT TEXT_ENCODING text_encoding_value              o  TEXT is the format.  <           o  TEXT_ENCODING is the option you specify to CDA.  B           o  text_encoding_value is the value of the codeset. (See.              Table 3-11 for a list of values.)  E           Table 3-11 shows the languages, codesets, and text-encodingm           values.n       3-54 .         I                                                  Programmer Release Notes I                                    3.20 Internationalization Enhancements     I               Table_3-11_Asian_Language_Codes_for_Options_Files__________   I               Language_________Codeset__________Text_Encoding_Value______   9               Japanese         DEC Kanji        DEC_KANJIL  9               Japanese         Super DEC Kanji  SDECKANJI   9               Traditional      DEC Hanyu        DEC_HANYU                Chineses  9               Simplified       DEC Hanzi        DEC_HANZIt               Chinesee  I               Korean___________DEC_Korean_______DEC_HANGUL_______________h  E               The following table shows examples of one-line entries.h  I               ___________________________________________________________nI               Options_File_____________One-Line_Entry____________________s  G               HANYU.CDA$OPTIONS        TEXT   TEXT_ENCODING   DEC_HANYUQ  G               HANZI.CDA$OPTIONS        TEXT   TEXT_ENCODING   DEC_HANZI*  I               HANGUL.CDA$OPTIONS_______TEXT___TEXT_ENCODING___DEC_HANGUL_   C               To view the EXAMPLES_CUSTOMERS.TXT file that contains F               Japanese text in DEC Kanji, use your editor to create anF               options file called KANJI.CDA$OPTIONS. Add the following)               one-line entry to the file:   *               TEXT TEXT_ENCODING DEC_KANJI  F               When you access the file through the Options File dialogI               box with the CDA Viewer, the EXAMPLES_CUSTOMERS.TXT file is D               viewable in the DEC Kanji codeset (Japanese language).  '         3.20.1.2 Defining Logical Namest  @         V1.2- The second option to enable viewing files in AsianF         3     languages is to specify the text file and encoding value  ,               by defining two logical names:  "               o  DDIF$READ_TEXT_GL  "               o  DDIF$READ_TEXT_GR  H               Table 3-12 shows the logical names and associated encoding               values.u  I                                                                      3-55x s  _           Programmer Release Notes*     3.20 Internationalization Enhancements    E           Table_3-12_Logical_Names_for_Specifying_Text_Encoding______m  E           DDIF$READ_TEXT_GL_____DDIF$READ_TEXT_GR_____Encoding_Value_a  9           LATIN1                MCS                   MCSi  A           LATIN1                LATIN1                ISO Latin-1   @           LATIN1                KATAKANA              ASCII-Kana  ?           LATIN1                KANJI                 DEC Kanjit  ?           ROMAN                 MCS                   Roman-MCSn  ;           ROMAN                 LATIN1                Romanr  A           ROMAN                 KANJI                 Roman-Kanjih  @           ROMAN                 KATAKANA              Roman-Kana  ?           LATIN1                HANZI                 DEC Hanzid  @           LATIN1                HANGUL                DEC Hangul  E           LATIN1________________HANYU_________________DEC_Hanyu______   E           You can define the logical names on the DCL command line orX.           in your LOGIN.COM file. For example:  +           $ DEFINE DDIF$READ_TEXT_GL LATIN1 *           $ DEFINE DDIF$READ_TEXT_GR KANJI  B           Note that this example defines the text encoding for DEC!           Kanji (see Table 3-12).r  B     3.20.2 Converting Files That Contain Asian-Language Characters  @     V1.2- You can convert an Asian-language text file to anotherA     3     format by specifying an options file or by defining thee  B           logical names DDIF$READ_TEXT_GL and DDIF$READ_TEXT_GR as=           discussed in Section 3.20.1.1 and Section 3.20.1.2.   C           The format for converting a document from TEXT to another            format is as follows:e  S           $ CONVERT/DOCUMENT/OPTION=language.CDA$OPTIONS filename.TXT/FORMAT=TEXT -e;           _$ filename.output_extension/FORMAT=output_formatu  E           For example, to convert a traditional Chinese language textt@           file to a DDIF file, enter the following command line:  7           $ CONVERT/DOCUMENT/OPTION=HANYU.CDA$OPTIONS -CL           _$ GUIDELINES_PERSONNEL.TXT/FORMAT=TEXT  GUIDELINES_PERSONNEL.DDIF  :           Note that this command line does not include the6           /FORMAT=DDIF qualifier; DDIF is the default.       3-56           I                                                  Programmer Release NotesbI                                    3.20 Internationalization Enhancementsh    B               The output file, GUIDELINES_PERSONNEL.DDIF, contains               language data.  H               You can also create Asian language PostScript files from aI               DDIF, DTIF, or text (ASCII) file. For example, to convert a G               DDIF file to PostScript (.PS) format, enter the following                command:  D               $ CONVERT/DOCUMENT filename.DDIF filename.PS/FORMAT=PS  F                 ________________________ Note ________________________  F                 Convert only DDIF and DTIF files that contain language9                 data to Asian language PostScript format.   F                 ______________________________________________________  C               When you print an Asian language PostScript file on a I               PostScript printer, ensure that the required language fontshE               are available on the printer. Otherwise, the PostScriptlF               file defaults to a basic set of fonts. If these fonts doG               not exist, the PostScript file defaults to Courier fonts.oG               Table 3-13 shows the languages and their associated basic.               fonts.  I               Table_3-13_Languages_and_Associated_Basic_Fonts____________r  I               Language______________Basic_Fonts__________________________f  G               Japanese              Ryumin-Light-EUC-H or Ryumin-Light-y+                                     Hankaku   I               Hanyu                 Sung-Light-CNS11643, Sung-Light-DTSCSl  )               Hangul                Munjo   I               Hanzi_________________XiSong-GB2312-80_____________________   F                 ________________________ Note ________________________  <                 Vertical writing is not supported by the CDAF                 converters. All vertical text is printed horizontally.  F                 ______________________________________________________  I                                                                      3-57_ _  _           Programmer Release Notes     3.21 XNL Library IssuesI         3.21 XNL Library Issuesr  B           This section contains information about the XNL library.       3.21.1 xnl_parsedatetime  A     V1.2- xnl_parsedatetime (and its VAX binding, XNL$PARSE_DATE_hB     5     TIME) accepts two-digit or four-digit years in the input  B           argument XmString s (which is the date-time string to beA           parsed). Valid years in the two-digit format are in themA           range 70 to 99, which mean the years from 1970 to 1999.hD           Values from 00 to 69 are invalid. Year 2000 and later must0           be specified in the four-digit format.       3.21.2 xnl_langinfo   B     V1.2- xnl_langinfo (and its VAX binding, XNL$LANGINFO) returnsA     5     a string for date-time formatting when D_FMT or D_T_FMT   B           is specified in the item argument. In the locales listedE           below, this function returns a formatting string containing C           %y. This formatting string should be used carefully aftertC           the year 2000, as %y indicates the two-digit year format.x             o  es_ES Spanish  !           o  fr_BE French Belgiuma              o  fr_CA French Canada             o  iw_IL Hebrewl             o  no_NO Norwegian       3.22 Xlib Issues  7           This section contains information about Xlib.m  .     3.22.1 Command Procedure Builds .PEN Files  ?     V1.0  To allow Pascal programs to inherit environment filesc;           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.       3-58 y         I                                                  Programmer Release NotesfI                                                          3.22 Xlib Issues     5         3.22.2 Parameter/Protocol Datasize Mismatches   G         V1.0  Several Xlib routines accept longword parameters that are I               not sent in their entirety in the X Protocol message to the G               server. In each case, the Xlib routine sends out only theiI               least significant 16 bits of the parameter value. This is asI               constraint of the field size within the X Protocol message.sG               Table 3-14 lists routine names and the longword arguments}2               that are sent only as 16-bit values.  C               Table 3-14 Routine Names and Arguments Sent as 16-Bit I               ___________Values__________________________________________   I               Routine_Name_______________________Routine_Arguments_______n  @               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,heightS  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,angle2i  I               XFillRectangle/FILL_RECTANGLE______x,y,width,height________   $         3.22.3 XtAppMainLoop Routine  C         V1.2- Previously, if a program entered its event loop, (forsH         5     example, by calling XtAppMainLoop) without having opened a  H               display or specified a timer or event flag for the programH               to wait for (by calling XtAppAddTimeout or XtAppAddInput),B               Xlib terminated the program with the following error               message:  ?                       X Toolkit Error: Error in XMultiplexInput   I                                                                      3-59k h  l           Programmer Release Notes     3.22 Xlib Issues    C           Starting with DECwindows Motif Version 1.2-5 for OpenVMS, B           if there is nothing to wait for, Xlib stalls waiting for<           input instead of terminating with an error status.  :           To allow Xlib to process events at a later time,=           applications should provide some means of regainingr>           control, such as specifying an event flag by calling           XtAppAddInput.  ;     3.22.4 XSelectAsyncEvent and XSelectAsyncInput Routiness  >     V1.1  The XSelectAsyncEvent and XSelectAsyncInput routines9           allocate memory for the storage of AST deliveryoB           information. This memory is freed in the following ways:  @           o  If you close a display (XCloseDisplay), all the ASTE              delivery information associated with all windows on that               display is freed.  >           o  If you destroy a window (XDestroyWindow), the AST;              delivery information for that window is freed.m  E           The AST delivery information for subwindows is not freed byy           XDestroyWindow.r  @           If you want to turn off AST notification for all event;           types within a given window and also free the AST ?           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 thef-           ast_routine argument equal to zero.t  $     3.22.5 Xlib Internationalization  D     V1.2  The X Window System Version 11, Release 5 (X11 R5) definesC           a number of services to support writing internationalized ?           X applications. Internationalization of X is based on A           the concept of a locale. A locale defines the localizedeD           behavior of a program at run time. Locales affect Xlib by:  6           o  Encoding and processing input method text  /           o  Encoding resource files and valuesf  .           o  Encoding and imaging text strings  E           o  Encoding and decoding for interclient text communication        3-60    g      I                                                  Programmer Release Notes I                                                          3.22 Xlib Issues     C               The X Window System defines a general methodology andeC               a set of application programming interfaces (APIs) torC               standardize programming in X. Standards have not beenoE               established for implementing these internationalizationaD               features. Currently, the X11 R5 distribution makes twoI               sample implementations of Xlib internationalization support F               available: Xsi and Ximp. In addition, Compaq provides anD               implementation called Xi18n. You can select which I18NH               implementation you want. All three implementations provideI               the same functionality through the same set of public APIs, H               but their underlying processing differs. These differences6               are described in the following sections.  '         3.22.5.1 Vendor Pluggable Layer   C         V1.2  Compaq provides a general mechanism called the vendor >               pluggable layer, which allows you to choose yourA               own internationalization implementations. DifferentDB               implementations can be built as standalone shareable?               libraries and can be selected through the logicall                DECW$XVENDORLAYER.  D               If this logical is not defined, the mechanism searchesG               for an internationalization implementation library in the                following order:  )                  DECW$XI18NLIBSHR (Xi18n) %                  DECW$XSILIBSHR (Xsi) '                  DECW$XIMPLIBSHR (Ximp)   E               If a shareable library is not found, the default is the F               Xi18n implementations that are already linked with Xlib.  H               The following functions act as interfaces between Xlib andH               the internationalization implementation shareable library:                    XDefaultStringm"                  XwcFreeStringList*                  XwcTextListToTextProperty*                  XmbTextListToTextProperty*                  XwcTextPropertyToTextList*                  XmbTextPropertyToTextList"                  _XrmInitParseInfo"                  _XlcDefaultLoader  I                                                                      3-61     1           Programmer Release Notes     3.22 Xlib Issues    B           When creating the Xsi or the Ximp shareable library, youC           need to know the names of the interfaces because they are @           defined within Xlib. Compaq recommends that you renameB           the functions during compilation by adding the following           compilation flags:             /define=(-2               "XDefaultString"="_XDefaultString",-8               "XwcFreeStringList"="_XwcFreeStringList",-H               "XwcTextListToTextProperty"="_XwcTextListToTextProperty",-H               "XmbTextListToTextProperty"="_XmbTextListToTextProperty",-H               "XwcTextPropertyToTextList"="_XwcTextPropertyToTextList",-H               "XmbTextPropertyToTextList"="_XmbTextPropertyToTextList",-8               "_XrmInitParseInfo"="__XrmInitParseInfo",-7               "_XlcDefaultLoader"="__XlcDefaultLoader")m  <     3.22.5.2 Compaq Internationalization Xlib Implementation  E     V1.2  The Compaq implementation (Xi18n) provides enhanced support C           and a stable internationalization environment. The Compaq B           implementation (Xi18n) provides the following advantages?           over the Xsi or Ximp environments provided with the Xn           distribution:   E           o  Most European locales and Asian locales are supported bye>              the DECwindows Motif for OpenVMS version of Xlib.  A           o  New locales can easily be supported without changing D              Xlib. New locales can be added by plugging in a locale-D              specific shareable library and a corresponding X locale+              database file for that locale.   ?           o  Encoding of input processing can be different from_B              output encodings. The output methods create a defaultC              font set and use available font resources installed in D              the X server. The code conversion is transparent to the              user.  &     3.22.5.3 Locale in OpenVMS Systems  <     V1.2- DECwindows Motif for OpenVMS software is dependent=     4     on a locale environment that conforms to the ANSI CC  B           specification. In OpenVMS versions prior to Version 6.2,?           the DEC C Run-Time Library's implementation of localelD           support is very limited, so Xlib provides its own internalE           locale environment. In OpenVMS Version 6.2 and higher, Xlib D           uses the locale environment provided by the DEC C Run-Time           Library.       3-62 e  A      I                                                  Programmer Release NotespI                                                          3.22 Xlib Issues2    E               The locale support provided in DECwindows Motif VersioneG               1.2-4 for OpenVMS has been modified to make it compatiblenD               with the locale support in the DEC C Run-Time Library.G               This corrects a problem that was introduced in DECwindowslH               Motif Version 1.2 for OpenVMS and that is described in the0               OpenVMS Version 6.2 Release Notes.  E               If you write internationalized applications using thesenD               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 before !                  <X11/Xlocale.h>.   I               o  For Motif applications, <X11/Xlocale.h> is automaticallyA                  included.  9               o  Turn on the following compilation flags:A  E                  /define=(X_LOCALE,X_WCHAR,_WCHAR_T_,XLIB_XPG4_FUNCS)                                                   I                                                                      3-63A                         I                                                                         4 I         _________________________________________________________________   I                                               Documentation Release Notes_    C               The release notes in this chapter are cumulative from E               DECwindows Motif Version 1.0 and still apply to Version F               1.2-5. This chapter describes the following information:  H               o  Section 4.1, DECwindows Motif Version 1.2-5 for OpenVMS                  Documentation  H               o  Section 4.2, DECwindows Motif Documentation Corrections  >               o  Section 4.3, OSF/Motif List of Known Problems  D         4.1 DECwindows Motif Version 1.2-5 for OpenVMS Documentation  ?         V1.2- This chapter contains updates to DECwindows MotifDE         5     documentation. Note that some of the documents have notn  A               been reissued for this release of DECwindows Motif.n  I               Table_4-1_DECwindows_Motif_for_OpenVMS_Documentation_______   B                                                           SoftwareI               Title_______________________________________Version________   G               DECwindows Motif Version 1.2-5 for OpenVMS  Version 1.2-5                Release Notesr  G               DECwindows Motif Version 1.2-5 for OpenVMS  Version 1.2-5D                Installation Guide  G               Getting Started With the New Desktop        Version 1.2-4t  H               DECwindows Motif for OpenVMS Applications   Version 1.2[1]               Guide.  I               [1]Updates_to_these_documents,_if_any,_are_noted_in_this___P  +               chapter of the Release Notes.   I                                                  (continued on next page)u  I                                                                       4-1                 Documentation Release Notesa@     4.1 DECwindows Motif Version 1.2-5 for OpenVMS Documentation    8           Table 4-1 (Cont.) DECwindows Motif for OpenVMSE           __________________Documentation____________________________:  >                                                       SoftwareE           Title_______________________________________Version_________  D           DECwindows Motif for OpenVMS Guide to       Version 1.2[1]           Non-C Bindings  D           Using DECwindows Motif for OpenVMS          Version 1.1[1]           (Digital Press)_  D           DECwindows Motif for OpenVMS Quick          Version 1.2[1]           Reference Card  D           Managing DECwindows Motif for OpenVMS       Version 1.2[1]           Systemsi  D           Overview of DECwindows Motif for OpenVMS    Version 1.2[1]           Documentationo  A           DECwindows Extensions to Motif              Version 1.2d  A           DECwindows Companion to the OSF/Motif       Version 1.2g           Style Guide   A           DECwindows Motif Guide to Application       Version 1.2d           Programming_  D           VMS DECwindows Device Driver Manual         Version 1.0[1]  D           VMS DECwindows Transport Manual             Version 1.0[1]  D           Porting XUI Applications to Motif           Version 1.0[1]  D           VMS DECwindows Guide to Xlib (Release 4)    Version 1.0[1]$           Programming: MIT C Binding  D           VMS DECwindows Guide to Xlib (Release 4)    Version 1.0[1]"           Programming: VAX Binding  D           VMS DECwindows Display PostScript System    Version 1.0[1]            Programming Supplement  ?           X Window System (Digital Press)             Release 5tC                                                       Third Edition_  ?           X Window System Toolkit (Digital Press)     Release 4   ?           X and Motif Quick Reference Guide (Digital  Release 5e           Press)  E           [1]Updates_to_these_documents,_if_any,_are_noted_in_this___c  '           chapter of the Release Notes.r  E                                              (continued on next page)i       4-2i    $      I                                               Documentation Release Notes I              4.1 DECwindows Motif Version 1.2-5 for OpenVMS Documentation     <               Table 4-1 (Cont.) DECwindows Motif for OpenVMSI               __________________Documentation____________________________a  B                                                           SoftwareI               Title_______________________________________Version________2  E               OSF/Motif Style Guide (Prentice-Hall)       Release 1.2t  E               OSF/Motif Programmer's Guide (Prentice-     Release 1.2i               Hall)m  E               OSF/Motif Programmer's Reference            Release 1.2aI               (Prentice-Hall)____________________________________________e  '         4.1.1 New Desktop Documentation,  I               DECwindows Motif also provides the following Common Desktop F               Environment (CDE) manuals in support of the New Desktop:  9               o  Common Desktop Environment: User's Guide   G               o  Common Desktop Environment: Advanced User's and System &                  Administrator's Guide  E               o  Common Desktop Environment: Help System Author's andm#                  Programmer's Guidet  B               o  Common Desktop Environment: Programmer's Overview  ?               o  Common Desktop Environment: Programmer's GuideF  <               o  Common Desktop Environment: Style Guide and(                  Certification Checklist  A               o  Common Desktop Environment: Internationalization #                  Programmer's Guideo  5               o  Common Desktop Environment: Glossary   6         4.2 DECwindows Motif Documentation Corrections  C               This section contains corrections and enhancements tob6               existing DECwindows Motif documentation.  2         4.2.1 Getting Started With the New Desktop  D               This section contains documentation corrections to the:               Getting Started With the New Desktop manual.  I                                                                       4-3t                Documentation Release Notesl2     4.2 DECwindows Motif Documentation Corrections    (     4.2.1.1 File Specification Incorrect  A     V1.2- A file specification for a command procedure in Getting C     5     Started With the New Desktop (part number AA-QUW1A-TE) is_  E           incorrect. The file specification appears in Section 3.4.9,i"           paragraph 5, as follows:  ?           "Optional DECwindows applications, such as DECwindows >           Notes, may not provide any information and therefore?           are not restarted. For such cases, there is a commandg=           procedure called disk$:[user.DT]SESSIONETC.COM thatx>           you can use to start any applications that cannot beA           restarted automatically. This procedure is analogous toiD           the DECW$LOGIN.COM procedure in the traditional DECwindows           environment."W  ,           The correct file specification is:  0           disk$:[user.DT.SESSIONS]SESSIONETC.COM  9     4.2.2 DECwindows Motif for OpenVMS Applications GuideL  @           This section contains documentation corrections to theA           DECwindows Motif for OpenVMS Applications Guide manual.g  B     4.2.2.1 Enhancing Information About the Finish Printing Option  B     V1.2- The section called "Printing Information" in the chapterB     3     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.  ,     4.2.3 Using DECwindows Motif for OpenVMS  =           This section contains documentation corrections and @           enhancements to the Using DECwindows Motif for OpenVMS           manual.          4-4            I                                               Documentation Release Notes I                            4.2 DECwindows Motif Documentation Correctionsr    /         4.2.3.1 Using the Drag-and-Drop FeatureX  D         V1.2  The drag-and-drop feature lets you move or copy screenF               objects. For example, you can move text from buttons and!               paste it elsewhere.t  8               To drag and drop text into a new location:  @               1. Select the text to be copied or moved with MB1.  6               2. To move the text, press and hold MB2;1                  to copy the text, press and holdy                  Ctrl/MB2.  -                  A move or copy icon appears.s  I               3. Drag the icon to the location where you want to drop the &                  text and release MB2.  I                  If the object is highlighted as you drag the icon across >                  it, you can drop the text into that location.  D               Drag-and-drop is provided primarily for programmers to>               incorporate the feature into their applications.  G               The DECwindows Motif Version 1.2 for OpenVMS applicationsoF               support the drag-and-drop feature, with the exception ofD               Notepad. DECwindows Mail supports drag-and-drop in allI               windows except the main message area, where DECwindows MailfH               has its own drag-and-drop feature; you can use MB2 to move5               messages around with the SVN interface.            4.2.3.2 Tear-Off Menus  F         V1.2- The DECwindows Mail application supports tear-off menus.E         V1.2  The DECwindows Motif applications allow you to tear offh  D               pull-down and popup menus. Tear-off menus let you keepH               frequently used menus displayed without repeatedly pulling+               them down or popping them up.   !               To tear off a menu:l  3               1. Display a pull-down or popup menu.   A                  If the menu is a tear-off menu, a dotted line iso2                  displayed at the top of the menu.  3               2. Click on the dotted line with MB1.   H                  The menu remains active until it is closed or until the.                  parent application is closed.  I                                                                       4-5a    I           Documentation Release Notesa2     4.2 DECwindows Motif Documentation Corrections    #           To close a tear-off menu:a  B           1. Click on the Window menu button in the tear-off menu.  (           2. Choose the Close menu item.  C           The following applications do not support tear-off menus::             o  CDA Viewer              o  DECwindows Mail             o  Notepad             o  Print Screen1  B     4.2.3.3 Adding Target Screen Options to Application Menu Items  B     V1.2  The example "Adding Target Screen Options to Application>           Menu Items" in Using DECwindows Motif for OpenVMS is=           incorrect. To correct the problem, remove the firsto+           occurrence of the following line:g             $ select_qualifiers:  ,     4.2.3.4 Changing the Startup Environment  C     V1.2  The example "Changing Your Logo" is incorrect. To correct E           the problem, 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/LOGX  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   )     4.2.3.5 Enhancing Startup Performance   ?     V1.1  Extensive SYLOGIN.COM or LOGIN.COM command proceduresR?           slow down application startup. Many of the operationseA           performed in a SYLOGIN.COM or LOGIN.COM are meaninglessa<           for DECwindows application startup. Therefore, theC           SYLOGIN.COM and LOGIN.COM files should be conditionalizeda>           for DECwindows application startup performance. WhenE           starting a DECwindows application, a minimum of SYLOGIN.COMt4           and LOGIN.COM commands should be executed.       4-6            I                                               Documentation Release Notes I                            4.2 DECwindows Motif Documentation Corrections     E               Typically, the commands that should be executed are the1H               redefinition of DECW$USER_DEFAULTS (if present), and otherF               logical name definitions if the user will be referencingG               them from within the context of a DECwindows application. I               The following code segment can be inserted into SYLOGIN.COMiH               and LOGIN.COM immediately following the commands necessary               for DECwindows:                  $ mode = f$mode()"+               $ tt_devname = f$trnlnm("TT")eG               $ session_mgr_login = (mode .eqs. "INTERACTIVE") .and.  -TG                     (f$locate("WSA",tt_devname) .ne. f$len(tt_devname))TM               $ session_detached_process = (mode .eqs. "INTERACTIVE") .and. -xG                     (f$locate("MBA",tt_devname) .ne. f$len(tt_devname))xL               $ if session_mgr_login .or. session_detached_process then exit  F               Applications continue to run even if these lines are not;               added to the SYLOGIN.COM and LOGIN.COM files.i  3         4.2.3.6 Enhancing Hold-Screen Response Time   G         V1.1  If the Hold Screen key response time is too slow, add themE               following lines to your DECW$TERMINAL_DEFAULT.DAT file:t  :               DECW$TERMINAL.main.terminal.syncFrequency: 1=               DECW$TERMINAL.main.terminal.batchScrollCount: 1c  C               Using this resource can affect the performance of theeE               DECterm window. The actual impact on performance variesoE               from site to site. You can trade off scrolling speed tonF               hold-screen response time. A faster hold-screen responseI               results in a slower scrolling speed. The default values ford9               these resources are 10 and 0, respectively.   ;         4.2.4 Managing DECwindows Motif for OpenVMS Systems   B               This section contains documentation enhancements andF               corrections to the Managing DECwindows Motif for OpenVMS               Systems manual.          4.2.4.1 Global Symbols  F         V1.2- The following additional global symbols are available in7         3     the DECwindows Motif for OpenVMS product:c  '               o  DECW$CONSOLE_SELECTIONs  D                  Specifies how to display operator-messages options.  &               o  DECW$CONSOLE_GEOMETRY  I                                                                       4-7i 6  a           Documentation Release Notesc2     4.2 DECwindows Motif Documentation Corrections    ?              Specifies the value of the -geometry option in the 0              DECW$MESSAGEPANEL.EXE command line.  =           For information about using these symbols, refer toIC           Section 2.18 in these Release Notes. Refer to the chapteroE           "Using DECwindows" in Managing DECwindows Motif for OpenVMS :           Systems for the complete list of global symbols.       4.2.4.2 Security Options  C     V1.2  In the Session Manager Security Options dialog box, place C           the node name within quotation marks if the name contains            any of the following:   A           o  Reserved characters: space, tab, comma (,) or doublea              quotation mark (")              o  Double colon (::)  @           o  A colon (:) as the final character in the node name  C           Session Manager automatically adds quotation marks to theuC           node name if they are needed, unless the node name begins D           with a double quotation mark. If the node name begins withC           a double quotation mark, Session Manager assumes that theiC           user has already quoted the node name and does not changeI
           it.   C           Within a quoted string, a double quotation mark should be D           replaced by two double quotation marks (" "). For example,E           the quoted string "DEC:.zko."my node"" should be changed to            the following:  #           ("DEC:.zko.""my node""")._  (     4.2.4.3 Displaying a Customized Logo  =     V1.1  By default, if there is no DECwindows Motif license @           registered for the SYSTEM account, DECwindows does not>           display customized login logos. This is a problem onB           systems with DECwindows Motif personal-use licenses thatD           do not include SYSTEM on the list of authorized DECwindows           users.  A           To display a customized logo without a DECwindows MotifwA           license for SYSTEM, add the following definition to the47           SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM file:n       4-8V i  1      I                                               Documentation Release NotesDI                            4.2 DECwindows Motif Documentation Correctionsn    +               $ DECW$LOGINLOGOSUB == "TRUE"h  F                 ________________________ Note ________________________  >                 If the SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM:                 file does not exist, copy it from the file=                 SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.TEMPLATE.   F                 ______________________________________________________  D               After editing the setup file, restart DECwindows Motif*               using the following command:  1               $ @SYS$MANAGER:DECW$STARTUP RESTARTi  A               DECwindows Motif login starts the logo process as aMF               subprocess instead of as a detached process. The licenseF               check sees that the logo process is a child of the login:               process and that the X connection is opened.  5         4.2.4.4 Enabling and Disabling Access Controln  I         V1.0  DECwindows Motif does not enable access control by default. H               Instead, it uses the access control set by the server. TheE               DECwindows X11 display server enables access control at                startup time.f  B               To force the DECwindows Session Manager to enable orF               disable access control explicitly at login time, you can8               define one of the following logical names:  H               $ DEFINE/SYSTEM/EXECUTIVE DECW$LOGIN_ACCESS_CONTROL ENABLE  I               $ DEFINE/SYSTEM/EXECUTIVE DECW$LOGIN_ACCESS_CONTROL DISABLEf  E               If the logical name is not defined, or if it is defined E               to some other value, such as "SERVER", DECwindows login :               neither enables nor disables access control.  E               In most cases, it should not be necessary to define the                logical name.   B         4.2.5 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.t  I                                                                       4-9w o  D           Documentation Release Notes[2     4.2 DECwindows Motif Documentation Corrections    $     4.2.5.1 GET_CHAR_STRUCT Function  E     V1.2- The access related to the char_struct argument for the XLIBwA     3     GET_CHAR_STRUCT function is incorrectly documented. Thea  "           correct access is write.  C     4.2.6 VMS DECwindows Guide to Xlib (Release 4) Programming: VAXa           Binding   B     V1.2  Example 1-1 in the VMS DECwindows Guide to Xlib (ReleaseB           4) Programming: VAX Binding is incorrect. To correct the@           problem, change the following two lines in the section'           "Create the WINDOW_1 window":   >           WINDOW_1X = (X$WIDTH_OF_SCREEN(DPY) - WINDOW_1W) / 2?           WINDOW_1Y = (X$HEIGHT_OF_SCREEN(DPY) - WINDOW_1H) / 2e  -           The example should read as follows:s  A           WINDOW_1X = (X$WIDTH_OF_SCREEN(SCREEN) - WINDOW_1W) / 2eB           WINDOW_1Y = (X$HEIGHT_OF_SCREEN(SCREEN) - WINDOW_1H) / 2  B           Example 3-1 in the VMS DECwindows Guide to Xlib (ReleaseB           4) Programming: VAX Binding is incorrect. To correct the2           problem, change the following two lines:  I           WINDOW_1X = (X$DISPLAY_WIDTH_OF_SCREEN(SCREEN) - WINDOW_1W) / 2 J           WINDOW_1Y = (X$DISPLAY_HEIGHT_OF_SCREEN(SCREEN) - WINDOW_1H) / 2  -           The example should read as follows:   F           WINDOW_1X = (X$DISPLAY_WIDTH_OF_SCREEN(DPY) - WINDOW_1W) / 2G           WINDOW_1Y = (X$DISPLAY_HEIGHT_OF_SCREEN(DPY) - WINDOW_1H) / 2l  (     4.2.7 DECwindows Extensions to Motif  :           This section lists documentation corrections and=           enhancements for the DECwindows Extensions to Motif            document.   2     4.2.7.1 DXmNlayoutDirection Resource Constants  B     V1.2- The section on DXmNlayoutDirection Resource in Chapter 2(     3     lists the following constants:              o  DXmLAYOUT_LEFT_DOWN             o  DXmLAYOUT_LEFT_UP  !           o  DXmLAYOUT_RIGHT_DOWN              o  DXmLAYOUT_RIGHT_UPo       4-10 u         I                                               Documentation Release Notes I                            4.2 DECwindows Motif Documentation Correctionso    A               Note that the following constants are not currently =               available for the DXmNlayoutDirection resource:r  "               o  DXmLAYOUT_LEFT_UP  #               o  DXmLAYOUT_RIGHT_UP   C               The introduction to Table 2-1 is incorrect. Table 2-1 G               describes the effect of the constants DXmLAYOUT_LEFT_DOWNn8               and DXmLAYOUT_RIGHT_DOWN on the functions.  B         V1.2  In Section 2.2 of the DECwindows Extensions to MotifG               manual, the description of DXmChildren indicates that thesE               routine can be used to learn the length of widget_list.g  G               The documentation is incorrect. The sentence should read,NI               "You can use the DXmNumChildren routine to learn the length :               of the widget list returned by DXmChildren."  ?         4.2.8 DECwindows Motif Guide to Application Programming   >               This section lists documentation corrections andH               enhancements for the DECwindows Motif Guide to Application!               Programming manual.   E         4.2.8.1 UIL Source Code for the OpenVMS DECburger Applicatione  A         V1.2- The introduction to the section in Chapter 4 calledoC         3     "Creating the Help Widget with UIL", which introducesa  E               Example 4-6, "UIL Help Widget Implementation," does notcE               clearly state that the complete UIL source code for thetH               OpenVMS DECburger application is included in DECW$EXAMPLES!               on OpenVMS systems.[  /         4.2.8.2 Help Widget Implementation Code   H         V1.2- In the title of Example 4-7, "Help Widget Implementation-CH         3     Language Module", DECBURGER.C should be added to the title                 as follows:   ;               "Help Widget Implementation-C Language Modulea               (DECburger.C)"  4         4.2.8.3 Help Widget Implementation-Callbacks  >         V1.2- The title of Example 4-8 should read as follows:@         3     "Help Widget Implementation-Callbacks (DECburger.C                 continued)"d  I                                                                      4-11i                Documentation Release Notesf2     4.2 DECwindows Motif Documentation Corrections    /     4.2.8.4 Using UIL to Create the Help Widget   C     V1.2- The title of Section 4.10, "Using the Toolkit Help WidgetoE     3     Creation Routine," does not accurately reflect the contentsn  ?           of this section. The title should read, "Using UIL to "           Create the Help Widget".  B           The introductory paragraph to Example 4-9 in the sectionD           called "Using the Toolkit Help Widget Creation Routine" isA           incomplete. The information should state the following:u  D           "The code in Example 4-9 is included in DECburger.C but isE           commented and will not be compiled when the example programC           is built."  @           The implementation in this example is not complete; it;           requires some sections from Examples 4-7 and 4-8.   D           To summarize, the documentation should state the following           information:  A           o  Examples 4-6 and 4-7 are UIL code (DECburger.UIL(D))o;              that, when combined, create the DECburger.EXE.p  5           o  Example 4-8 is C code for DECburger.EXE.x  9           o  Example 4-9 is C code for a Toolkit example.e  @     4.2.9 Overview of DECwindows Motif for OpenVMS Documentation  ;     V1.2  Table 2-2 in the Overview of DECwindows Motif for >           OpenVMS Documentation Version 1.2 indicates that the?           DECwindows Motif Version 1.2 for OpenVMS InstallationyC           Guide is included in the User Kit. This is incorrect. Thei<           installation guide is included with the media kit.  (     4.3 OSF/Motif List of Known Problems  B           Included in the DECwindows Motif for OpenVMS software isA           an OSF file that contains the OSF/Motif known problems. E           During the installation this file is copied from the kit to 2           SYS$HELP:DECW$MOTIF_OSF_BUGLIST_V12.TXT.         4-12    i                    I                                                                         AdI         _________________________________________________________________e  I                                       OSF/Motif Release 1.2 Release Notesn    G               The release notes in this document are based on Chapter 3MH               of the OSF/Motif Release Notes for Release 1.2 and includeB               a few other notes relevant to programmers developingH               OSF/Motif applications. Most of the notes describe changesI               made for OSF/Motif Release 1.2. The first two notes discussDE               performance improvements and information about backward                compatibility.  I               These Release Notes support the OSF/Motif software providediG               with the DECwindows Motif for OpenVMS software, DEC OSF/1iC               software, the eXcursion Software Development Kit, ando)               ULTRIX Worksystem Software.   G               For the OSF/Motif Release 1.2.3 update, approximately 425t%               problems were resolved.M  $         A.1 Performance Improvements  H               The Open Software Foundation set as its goal for OSF/MotifI               Release 1.2 to improve performance where possible and, at a G               minimum, to not allow it to degrade below the performance '               of OSF/Motif Release 1.1.i  :               Performance testing was done in three areas:  -               o  Aspects obvious to end users   !               o  Data space usageh                 o  Memory leakagei  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 a H               Scrolled Text region that contains a large amount of test.  I                                                                       A-1S G  E      '     OSF/Motif Release 1.2 Release NotesS      A.1 Performance Improvements    @           Data space usage has improved throughout the OSF/MotifC           Toolkit, particularly for the Text widget. In some cases,.>           data space usage has been reduced by as much as 40%.D           Also, the memory used for the text in a Text widget is nowC           correctly reduced when that text is replaced by a smaller            amount of text.u  C           Memory leakage has been reduced to a minimum for multipleIC           creates and destroys of all Toolkit widgets. Although the A           Motif tests showed small memory leaks, the OSF believes ?           that this amount of memory is required as part of ther9           startup overhead and is not a true memory leak.,  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 behavioralo           compatibility.  -     A.2.1 Visual and Behavioral Compatibilityg  ;           The OSF ran automated tests that compared currentpC           visuals with those recorded using OSF/Motif Release 1.1.4iE           libraries. Once all differences between the Release 1.2 and E           Release 1.1.4 versions were accounted for, the visuals wereoB           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 anlA           application is now honored by the Toolkit. In OSF/Motifl>           Release 1.1, applications set the initial size for aA           manager widget, but did not, in fact, use that size. InE?           Release 1.2, Motif now uses that size setting and thes0           initial layout is changed accordingly.       A-2     E      I                                       OSF/Motif Release 1.2 Release NotesoI                    A.3 Changes and New Features for OSF/Motif Release 1.2p    >         A.3 Changes and New Features for OSF/Motif Release 1.2  G               This section summarizes changes and new features that therI               OSF has made to OSF/Motif Release 1.2. Detailed information A               about these modifications is contained in the MotiftD               reference pages and the Motif Release 1.2 revisions of               following books:  &               o  OSF/Motif Style Guide  -               o  OSF/Motif Programmer's Guidei  F               The following sections discuss the OSF/Motif Release 1.2               enhancements.   %         A.3.1 General Toolkit Changes   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 Releasec.               1.1 are obsolete in Release 1.2:                    ExtObject.h                  Traversal.h                  VaSimple.hC                  VendorE.h                  VendorEP.ht  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 Translationsf  H               As a result of fixing a problem in the XT translation codeC               (Patch 25 for X11 R5), the translations in Xt are now F               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. Othero;               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 thath*               file to the xmodmap utility.  I                                                                       A-3i m         '     OSF/Motif Release 1.2 Release Noteso:     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 definitionsiE           allow the application to use modifiers with the arrow keys.t             !p           ! Always force:            !   KP_2 = Down            !   KP_8 = Upw           !   KP_4 = Lefte           !   KP_6 = Right           keycode 120 = Down           keycode 76  = Up           keycode 98  = Left           keycode 100 = RightD       A.3.3 ANSI C Compliancee  C           All references to caddr_t have been changed to XtPointer.AA           This change affects all callback routines and any other C           routines that reference caddr_t. The OSF made this changeeC           so that OSF/Motif Release 1.2 would be compliant with ther           ANSI C specification.W  *     A.3.4 Display and Screen Specific Data  E           Motif now has an XmDisplay object that supports per-displayfD           data and resources. An XmScreen object has been added that1           supports per-screen data and resources.        A.3.5 Drag and DropP  C           OSF/Motif Release 1.2 supports the drag and drop metaphor_C           for data interchange. The drag-and-drop specification haseD           been fully implemented. See the Release 1.2 version of theB           OSF/Motif Programmer's Guide for information on the drag           and drop interface.h  C              ________________________ Note ________________________   A              If you want to use Btn2 to have pop-up menus pop up,iB              drag and drop will not function properly. You need to5              disable drag and drop in such instances.g  C              ______________________________________________________s       A-4y f  t      I                                       OSF/Motif Release 1.2 Release Notes I                    A.3 Changes and New Features for OSF/Motif Release 1.2              A.3.6 Tear-Off Menus  C               With tear-off menus, the user can retain menus on the C               display area for subsequent selections. Each tearable G               menupane is a tear-off button. When the mouse drag buttonSG               is pressed on the tear-off button, the pane tears off andSH               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-nG               off menu's windowpane follows the standard window manageru               policy.d  I               Tear-off behavior is enabled by setting the XmNtearOffModelrI               resource to XmTEAR_OFF_ENABLED. (The default is XmTEAR_OFF_u               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.e  G               The converter is not automatically installed because many H               applications use map or cascading callbacks to dynamicallyG               set the sensitivity of items within their menus. However,lG               if a tear-off menu is mapped, the sensitivity of its menuiB               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 ineE               operations being enabled at unexpected times. If a user1D               activates one of these menu items, the application can<               crash or the persistent data can be corrupted.  !         A.3.7 Insensitive Visuals   A               Motif provides visual indications to show whether a C               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:s                    XmArrowButton                  XmListE                  XmScrollBar                  XmTextL  I                                                                       A-5  M  f      '     OSF/Motif Release 1.2 Release Notesc:     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-dimensional               beveled look.  A           o  Minor changes have been made to the color generation =              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.l  C           o  Motif now adds a location cursor to surround all itemsLC              in a List whenever a List widget has the focus and then2              current keyboard item is not visible.  C           o  There are minor layout differences because of fixes in !              geometry management.O       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-6b e  p      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 Enhancements   B               The following three resources have been added to theC               XmScreen widget so that users can specify the defaulttE               background color and thresholds for shadow calculation:   "                  XmNlightThreshold!                  XmNdarkThresholdt'                  XmNforegroundThresholdn  I               Motif has added the XmChangeColor function that changes thetA               background and other colors for a specified widget.p  !         A.3.12 Baseline Alignment   G               Motif has added two functions for baseline alignment. ThecF               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 SetM  C               In OSF/Motif Release 1.2, you can use more widgets to G               support traversal using the keyboard. For example, insideeG               a tab group, users can now use the arrow keys to traversecF               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 tabi               group.  -         A.3.14 Two-Dimensional Menu Traversalo  G               With OSF/Motif Release 1.2, the left, right, up, and downlI               traversal arrows now navigate within a menupane. The up andeF               down arrow keys wrap between columns. The right and leftE               arrow keys post the previous or next menupane when theyoE               are pressed in the rightmost and leftmost column of thet%               menupane, respectively.            A.3.15 Input Focus  A               OSF/Motif Release 1.2 has added the XmNinitialFocustD               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                                                                       A-7h t         '     OSF/Motif Release 1.2 Release NotesV:     A.3 Changes and New Features for OSF/Motif Release 1.2    %     A.3.16 Traversal Access Functionsl  E           OSF/Motif Release 1.2 has added the following new functions @           to support better interaction with keyboard traversal:                XmGetFocusWidgetO              XmGetTabGroup              XmGetVisibility              XmIsTraversable              XmIsVisible  C           The XmTrackingLocate function has been modified to do the            following:  7           o  Field all events, not just a button press.   5           o  Return on any keystroke or button press._  0           o  Be called for nonsensitive widgets.  C           In addition, the XmTrackingEvent function has been added. C           This function is similar to XmTrackingLocate, except thatp.           it returns a pointer to the X event.       A.3.17 Virtual Keysc  E           OSF/Motif Release 1.2 has added the XmTranslateKey function D           that allows applications to override the default XtKeyProc'           to handle Motif virtual keys.a  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 youiC           get a warning message on application startup. Specify the 6           following information in the XKeysymDB file:  #           osfPageLeft     :1004FF40   #           osfPageUp       :1004FF41.  #           osfPageDown     :1004FF42   #           osfPageRight    :1004FF43   ?           To comply with the OSF/Motif Style Guide, the defaultn>           binding for osfMenu has been changed from <key>F4 to           Shift<key>F10.       A-8  ,         I                                       OSF/Motif Release 1.2 Release Notes I                    A.3 Changes and New Features for OSF/Motif Release 1.2a    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 warning1G               messages, add the hp prefix as follows to the appropriated                lines in the file:  3               osfDelete :         <key>hpDeleteChar   3               osfInsert :         <key>hpInsertChar   3               osfPrimaryPaste :   <key>hpInsertLinee  3               osfQuickPaste :     <key>hpDeleteLine   G               OSF/Motif Release 1.2 has a new client, xmbind, that setsiD               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 xmbindeE               if MWM is not used or if you need to change the virtual .               bindings without restarting MWM.  A               Virtual bindings can now be specified by individual A               vendors. If there is no .motifbind file in the homeeE               directory, you can use the xmbind.alias file to providedI               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'                  XmRepTypeGetRegisteredt                  XmRepTypeGetIdB%                  XmRepTypeGetNameListh#                  XmRepTypeGetRecorde  C               These functions are useful for developers who want tosG               define new resource converters that use an enumerated set.               of values.  I                                                                       A-9i R  a      '     OSF/Motif Release 1.2 Release Notesi:     A.3 Changes and New Features for OSF/Motif Release 1.2    1     A.3.19 Changes for CUA and Windows Compliance   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.a  E           If your application has a default button associated with anaA           XmBulletinBoard, pressing Return (except in a multiline ?           XmText), Ctrl/Return, or the key bound to osfActivatehA           while the focus is in the XmBulletinBoard now activatest           the default button.   4     A.4 Changes and Enhancements to Specific Widgets  A           This section summarizes the changes to specific widgets 2           that were made in OSF/Motif Release 1.2.       A.4.1 XmClipboarde  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 (charaD           *) to XtPointer, int to long, and (int *) to (long *). The@           related functions affected by these modifications are:             o  XmClipboardCopy  "           o  XmClipboardCopyByName  $           o  XmClipboardInquireCount  %           o  XmClipboardInquireFormatf  &           o  XmClipboardRegisterFormat              o  XmClipboardRetrieve  !           o  XmClipboardStartCopyd  &           o  XmClipboardWithdrawFormat       A-10 S  o      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_V5               AREA as a value for the child argument.m           A.4.3 XmList  G               To enhance its capabilities for managing lists, OSF/Motif ?               Release 1.2 includes the following new functions:T  )               o  XmListAddItemsUnselectedf  &               o  XmListDeletePositions  $               o  XmListGetKbdItemPos  $               o  XmListIsPosSelected  "               o  XmListPosToBounds  -               o  XmListReplaceItemsUnselected   0               o  XmListReplaceItemsPosUnselected  '               o  XmListReplacePositionsf  $               o  XmListSetKbdItemPos  )               o  XmListUpdateSelectedListy                 o  XmListYToPosh  ;               The XmList widget includes a new translation:                  o  <Copy>s  7                  Copies the selection to the clipboard.   +               XmList includes a new action:   -               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. TheiC                 name will be corrected in a later release of Motif.h  F                 ______________________________________________________  I                                                                      A-11  o  e      '     OSF/Motif Release 1.2 Release Notes 4     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.h  <           In OSF/Motif Release 1.2, if the selectedItems and=           selectedItemCount resources for a list are set in agB           resource file, the location cursor appears over the last@           item in the selectedItems list, not the first selected           item.s       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.a  D           A new dialog type, XmDIALOG_TEMPLATE, creates a MessageBoxB           that contains only a Separator. The application provides           additional children.  =           XmCreateTemplateDialog creates an XmDIALOG_TEMPLATEo,           XmMessageBox inside a DialogShell.       A.4.5 XmRowColumn and Menusp  4           OSF/Motif Release 1.2 adds a new resource,@           XmNentryVerticalAlignment, that specifies the vertical           alignment style.  ?           Another resource, XmNunpostBehavior has been added to A           the XmScreen object. This resource can be set to enablei?           external button events to be replayed after a menu is            unposted.b       A.4.6 XmScrollBari  >           In OSF/Motif Release 1.2, XmScrollBar includes a new           translation:             o  <Cancel>   -              Cancels the current slider drag.            A-12           I                                       OSF/Motif Release 1.2 Release Notes I                          A.4 Changes and Enhancements to Specific Widgetse             A.4.7 XmScrolledWindow  G               OSF/Motif Release 1.2 adds the function, XmScrollVisible,eA               that scrolls an automatic scrolled window to make as>               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, 6               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 the %               XmNdialogType resource.a  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           A.4.9 XmText  I               OSF/Motif Release 1.2 has added two functions to XmText foroI               making update changes to the widget: XmTextDisableRedisplayc(               and XmTextEnableRedisplay.  A               Two other functions facilitate string manipulation:g6               XmTextFindString and XmTextGetSubstring.  D               In Release 1.2, the destination cursor now follows theA               insert cursor and is no longer independently drawn.   5               XmText includes three new translations:                  o  <Backspace>  8                  Deletes any non-null primary selection.                 o  <Delete>p  8                  Deletes any non-null primary selection.                 o  <LeaveWindow>  I                                                                      A-13b v         '     OSF/Motif Release 1.2 Release Notesi4     A.4 Changes and Enhancements to Specific Widgets    C              Continues a selection action by scrolling after a timeL              delay.   *           XmText includes two new actions:  '           o  scroll-cursor-vertically()e  A              Scrolls the cursor vertically based on a y position.f              o  toggle-overstrike()  :              Switches between insert and overstrike modes.  C              ________________________ Note ________________________   <              There is a potential problem in both XmText and@              XmTextField with rendering strings in fonts or font=              sets that contain characters whose ascenders cant?              rise above the font ascent. If the text containing =              these characters is highlighted, any overlappingt?              descenders in the previous line may be overwrittenh5              by the ascenders in the succeeding line.t  C              ______________________________________________________o       A.4.10 XmTextField  A           OSF/Motif Release 1.2, the XmTextField widget has a new E           resource, XmNfocusCallback, that specifies the callbacks toe8           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.h  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 W  i      I                                       OSF/Motif Release 1.2 Release Notes I                          A.4 Changes and Enhancements to Specific Widgetsn    3         A.4.11 XmToggleButton, XmToggleButtonGadget   E               In OSF/Motif Release 1.2, setting XmNfillOnSelect to be I               true when XmNindicatorOn is false now causes the backgroundsG               of a set XmToggleButton to be filled with XmNselectColor.e  I               The default value for XmNfillOnSelect is dynamic so that itw2               matches the state of XmNindicatorOn.  -         A.5 Motif Window Manager Enhancementsh  C               This section highlights the enhancements to the Motifl#               Window Manager (MWM).h           A.5.1 Changes to MWM  >               OSF/Motif Release 1.2 incorporates the following"               enhancements to MWM:  1               o  An internationalized .mwmrc filer  2               o  Internationalized dialog messages  -               o  A built-in default root menuo  G               o  Support for the <Return> continuation character (\) ini                   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 box   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 thet2               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                                                                      A-15  h  n      '     OSF/Motif Release 1.2 Release Noteso)     A.5 Motif Window Manager Enhancements                o  frameBorderWidthl  C              Now bases its default value on the size and resolution               of the screen.              o  iconPlacement  A              Now takes the addition value, tight, which specifies A              automatic icon placement with no gaps between icons.e             o  maximumClientSize  =              Can now take the values vertical and horizontal.p             o  moveOpaquee  ?              Controls whether an image of the window or just an ,              outline of the window is moved.             o  resizeBorderWidth  C              Now bases its default value on the size and resolutionM              of the screen..             o  usePPositionl  >              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 within C              the application stacking order, but retains the parentu>              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..             o  f.minimize   9              Can now be used from an icon in an icon box.o             o  f.raise       A-16 t  v      I                                       OSF/Motif Release 1.2 Release Notes I                                     A.5 Motif Window Manager Enhancements     E                  Includes a within argument to move the window within G                  the application stacking order, but retains the parentwB                  window below the children rule. The function alsoB                  includes a freeFamily argument to move the windowE                  absolutely without regard to its local family stack.0G                  Both modifiers move the window within the local family 9                  stack, but do not move the family stack.e                 o  f.raise_lower  E                  Includes a within argument to move the window within1G                  the application stacking order, but retains the parentoB                  window below the children rule. The function alsoB                  includes a freeFamily argument to move the windowE                  absolutely without regard to its local family stack.eG                  Both modifiers move the window within the local familyl9                  stack, but do not move the family stack.                  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.e                 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:a                 o  <Alt> <Esc>  F                  This key combination behaves similarly to f.next_key,G                  except that the window is always raised, regardless off-                  the value of focusAutoRaise.,  I                                                                      A-17t s  e      '     OSF/Motif Release 1.2 Release Notes .     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 Usera#           Interface Language (UIL):   B           o  There is a new command flag, -s, that enables the use@              of setlocale and the creation of localized Compound              Strings.   C              ________________________ Note ________________________B  @              There is a serious problem in parsing double quotedC              strings with the -s flag. If you need to use this flag A              for parsing double quoted strings, you must obtain a                patch from the OSF.  C              ______________________________________________________   C           o  New UIL syntax now supports font sets and font tables.i  @           o  New UIL syntax now supports wide character strings.  B           o  Support has been added for using widget references as              callback tags.e  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.B  >           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. Thisa3                 function replaces MrmOpenHierarchy.t  %              -  MrmFetchBitmapLiteral   C                 This function fetches a bitmap literal with a depthm                 of 1.        A-18 s  h                            F      _________________________________________________________________  F                                                                  Index      F      A______________________________   C______________________________  *      Access control,  1-14             CDAB        enabling and disabling, 4-9       applications,  1-23, 1-25A      AccessX support                        dynamic font support,d3        keyboard enhancements, 1-56             1-23 A      Ada bindings                           installation problem,e3        Release 1.1.3, 3-8                      2-22 :      Animation applications,  2-9           packing,  1-26<      Answerback message                     unpacking,  1-27D        DECterm, 1-35                        WRITE$FONT logical name,3      Applications                              1-24iF        compiling Fortran, 3-18           changes to external reference<        for DECwindows Motif, 1-21           processing, 3-21:      Auto Repeat setting                 converters,  3-56B        changing in DECterm, 1-33         converting Asian-language  <      B______________________________        text files, 3-56F      Backdrop                            defining logical names,  3-55B        default, 1-8                      Display Options...,  1-296      Bindings support                    drag-and-drop?        languages, 3-8                       implementing,  3-19XF      Bookreader                          internationalization support,0        draft-quality printing, 1-22         3-54D        multiple-byte character           logical names with convert,0          printing,  1-22                    3-227        using comments in the             message,  1-29 D          DECW$BOOKSHELF file,  1-22      packing and unpacking error:                                             messages, 1-28A                                          paper size button,  1-29 4                                          programmingA                                             external referencing,p3                                                3-21_D                                             interface changes,  3-20  F                                                                Index-1 M  f              C     CDA                                Compose character, 1-8, 1-13tE       programming (cont'd)             Compound Document Architecture_  /          logical names with convert     See CDA 3             , 3-22                     Console portS8          release notes,  3-19           selecting,  2-265          restructuring of shareable    Console Windows?             images, 3-23                console messages,  2-26e?          style guide message,  3-22     controlling the initial 9       restructuring of shareable           position, 2-27tA          images, 3-23                   defining a global symbol,i/       specifying an options file,          2-27cD          3-54                           displaying console messages,/       style guide message,  3-22           2-26 D       Version 1.8A enhancements,           DISABLE (default),  2-26,2          3-20                                 2-278     C header files,  3-18                  ENABLE,  2-278     Clock                                  values,  2-268       DECsound for Clock,  1-29            WINDOW,  2-267     Color Customizer,  1-14             invoking,  2-27e?       auto shadowing toggle button,     selecting the AlternateT=          1-20                              Console port, 2-26m7       building,  1-15                  Copyright noticed?       command summary,  1-17            displaying in a DECtermc7       DECterms unaffected,  1-20           window, 1-33 !       mapping color resources andoF          color cells, 1-18             D______________________________/       modifying DECW$LOGIN.COM,        Debuggers?          1-16                           using in DECterm,  2-25.B       running,  1-16                   DEC CDA Base Services, 3-20;       supported                        DECchart application A          applications,  1-15            invoking from the Session 8          displays,  1-15                   Manager, 1-45/       using on multiheaded systems,    DECsound C          1-20                           installation problem,  2-22 4       xsetroot_cust demo,  1-21         notes,  1-30<     Command files                       prerequisites,  1-30;       for checking version,  2-20       restrictions,  1-30 .     Compatibility                      DECtermA       shareable images,  3-26           answerback message,  1-35,E     Compiling applications              automatic window positioning,   /       See also Applications                2-24 @       Fortran,  3-18                    changing the Auto Repeat  8                                            setting, 1-33>                                         DECCRA sequence,  3-24       Index-2e e  o              E         DECterm (cont'd)                  DECW$INCLUDE:TEXTP.H header 1          DECLFKC sequences,  3-25            fileMD          diagnostic crash file,  1-39       definition changes, 3-28H          diagnostic crash messages,       DECW$INCLUDE:XMP.H header file  A             1-39                            See also Header filesa9          displaying the copyright           changes, 3-27 ?             notice,  1-33                   removed definitionsoC          escape sequences,  1-32               XmHALFLONGBITS, 3-27 ?          finish printing option,  4-4          XmLONGBITS, 3-27b8          font sizes,  1-30                DECW$LOGIN.DATI          graphics,  1-37                    customizing the login screen, 2          hold-screen response time,           2-174             2-25, 4-7                     DECW$UTILS@          local echo,  1-35                  global symbols, 2-144          logicals,  2-23                  DECwindowsE          page-movement sequences,           delayed startup on Alpha,d1             3-24                              2-5RH          positioning,  1-33               DECwindows Extensions to Motif3          /PROCESS problem,  1-36             , 3-44 F          programming issues,  3-24        DECwindows OSF/Motif Toolkit7          ReGIS input cursors,  3-25         See Toolkit ?          ReGIS locator report,  1-39      DECwindows transportst?          reporting window size,  1-32       POSIX support, 3-13oB          resizing the terminal,  1-32     Detached processes,  1-3C          resource file name,  1-31        Development support,  3-2 6          resource usage,  1-38            Dialog boxesA          screen print services,  1-37       changing the positionmA          scrolling through the                 Set Password, 2-18nB             keyboard,  1-32                    Start Session, 2-188          seven-bit printer support,       Display serverD             1-36                            shared memory extension,2          system management,  2-23             3-47G          terminal emulator,  1-36           shared memory pixmaps, 3-52aG          user font selection,  1-34         shared memory XImages, 3-48iD          using the debugger,  2-25          supporting AccessX, 1-56B          virtual terminal support,        Documentation titles and5             2-25                             versionstI         DECW$CDPLAYER                       DECwindows Motif for OpenVMS,v1          required privileges,  1-39           4-1c7         DECW$CONSOLE_GEOMETRY             Drag-and-drop_B          global symbol,  4-7                using, 1-13, 3-19, 4-50         DECW$CONSOLE_SELECTION            dtFile<          global symbol,  4-7                limitations, 1-4  I                                                                   Index-3                    =     DXmCSText widget                   Finish printing option 5       input method support,  3-44       DECterm,  4-4h<     DXmFormSpaceButtonsEqually         Font limitations, 1-85        routine                         Font resourcese2       sizing and spacing widgets,       See Mosaic.          3-45                          FortranE     DXmLAYOUT_LEFT_DOWN constant        compiling applications,  3-18s;       DXmNlayoutDirection resource,    Functional resources 2          4-10                           See Mosaic     DXmLAYOUT_LEFT_UP constant(       DXmNlayoutDirection resource,    GF          4-10                          _______________________________?     DXmLAYOUT_RIGHT_DOWN constant      GET_CHAR_STRUCT functionl5       DXmNlayoutDirection resource,     access,  4-10n5          4-10                          Global symbolsaC     DXmLAYOUT_RIGHT_UP constant         DECW$CONSOLE_GEOMETRY,  4-7 D       DXmNlayoutDirection resource,     DECW$CONSOLE_SELECTION,  4-7  
          4-10hF     DXmNlayoutDirection resource       H______________________________  3       constants,  4-10                 Header filesc  C                                         DECW$INCLUDE:TEXTP.H,  3-28.A     E______________________________     DECW$INCLUDE:XMP.H,  3-27t7     EFS                                 languages,  3-8 @       See Extended File                Hold-screen response time7          Specifications                 enhancing,  4-7A0     Escape sequences                   Home page  7       DECterm,  1-32                    See also Mosaic 7     Extended File Specifications        creating,  1-61a  (        (EFS)                           IF       FileManager support,  1-10       _______________________________4       file selection popup,  1-9       Input cursors9       FileView support,  1-10           cross-hair,  3-25p6       programming library support,      diamond,  3-25?          1-12                           rubber-band line,  3-25tD       Support overview,  1-9            rubber-band rectangle,  3-258       translated image support,         selecting,  3-25;          1-13                          Internationalizationn?                                         converting files,  3-54.=     F______________________________     locale support,  3-60e<     Files                               viewing files,  3-54/       previously optional,  2-12       Internetz  7     FileView                            See also Mosaics=       application startup,  2-14        browsing,  1-59, 1-60          private logos,  1-48       Index-4                    0                                           Mosaic7         K______________________________     configuringl9         Key bindings, 1-8, 1-13                processingdC         Keyboard                                  Audio files, 1-62eA          enhancements for disabled                GIF files, 1-62fB             users,  1-56                          MIME files, 1-62B          scrolling in DECterm,  1-32              MPEG files, 1-62H                                                   multimedia files, 1-62H         L                                         PostScript files, 1-62F         _______________________________     creating a home page, 1-61C         Local echo                          determining an external ;          DECterm,  1-35                       viewer,  1-62 ?         Locale support, 3-62                external view setup =         Logical names                          examples, 1-63.?          defining in the CDA Viewer,        file location, 1-61.:             3-55                            firewall, 1-77@         Login logos                         font resources, 1-75F          customizing,  2-19, 4-8            functional resources, 1-64:         Login screen                        mappings, 1-63<          changing colors,  2-17             NoProxy resourceA          customizing,  2-17                    restrictions, 1-78 E             DECW$LOGIN.DAT,  2-17           providing as the Internete<         Logos                                 browser,  1-60D          modifying the DIGITAL logo,        proxy gateway resources,2             2-17                              1-76  >                                             restrictions, 1-77G         M______________________________     setting Mosaic X resources,   2         Mail                                  1-63:          color customizer,  1-41            starting, 1-61H          keyboard actions,  1-40               an external program, 1-62B             activating pushbuttons in       supporting the NoProxy=                dialog boxes,  1-40            resource,  1-78mG             highlighting selections,        supporting the ProxyGateway =                1-40                           resource,  1-77wB          pasting messages,  1-40            visual resources, 1-73?         Messages                          Motif and XUI widgets 8          System Menu Bar: Pseudo Mouse      mixing, 3-27>             not available,  2-22          Motif Window ManagerI         MIT X11                             centering lines for multilinet@          Release 3 Intrinsics                 icon titles,  1-43B             messages,  3-26                 color customizer, 1-41D          Release 4 Intrinsics               configuration file, 1-417             messages,  3-26                 customizingvB                                                colors on multihead?                                                  systems,  1-43   I                                                                   Index-5                    8     Motif Window Manager (cont'd)      OSF/Motif Toolkit9       moving the icon box off the       examples (cont'd)   6          screen, 1-43                      pict,  3-346       restarting,  1-42                    PICT,  3-34E       running earlier versions of          resource files for example <          DECwindows, 1-42                     programs, 3-43?       supporting customization for         Square widget,  3-31a:          monochrome monitors, 1-42         textedit,  3-35@     MWM                                    uid files for example<       See Motif Window Manager                programs, 3-446                                            view,  3-389     N                                      xmpiano,  3-39e:     _______________________________        xmtravel,  3-43=     New Desktop                         known problems,  4-12 6       detached processes,  1-3         Overlay support?       font selection,  1-8              See also Window Managere0       Front Panel,  1-2                 colormap=       reference pages,  1-7                avoiding potentiala<       release notes for general               problems, 2-28E          user, 1-1 to 1-8               modifying applications,  2-28lA       saving and restoring              sharing overlay colormaps C          applications, 1-4                 with the Window Manager,_/       ToolTalk support,  1-3               2-28      Node name displayb(       disabling,  2-19                 PF     Notepad                            _______________________________,       linking with the Release         PaintC          1.1.3 Toolkit, 1-43            creating private colormaps,_/                                            1-44 D     O______________________________     enhancing performance duringA     Options file                           basic operations, 1-44 9       specifying,  3-54                Parameter datasizee9     OSF/Motif Toolkit                   mismatches,  3-59s9       examples,  3-28                  Pascal programming 9          cutpaste,  3-28                .PEN files,  3-58d0          dnddemo,  3-28                PEN filesC          Dogs,  3-30                    using with Pascal programs,o/             widget,  3-30                  3-58e4          helloint,  3-32               POSIX supportD          hellomotif,  3-33              DECwindows transports,  3-13E          MOTIFANIM,  3-33               SYS$POSIX_FORK_CONTROL system 8          MOTIFGIF,  3-34                   service, 3-14E          motif samples,  3-41           using the POSIX fork routine,t/          motifshell,  3-34                 3-13c            periodic,  3-35       Index-6n p  e              B         Printing                          Session Manager (cont'd):          Bookreader,  1-22                  known problemsB         Print Screen                           private logos, 1-48B          problems with PostScript           security options, 1-47D             output,  1-44                   stopping a process, 1-48A         Process                           Set Password dialog box_G          creating with virtual              changing the position, 2-18lC             terminal support,  2-25       Seven-bit printer supports9         Programming environments, 3-2       DECterm, 1-36 :         Programming support and XUI,      Shareable images?           3-8                               compatibility, 3-26lF         Proxy gateway resources             upward compatibility, 3-26<          See Mosaic                       Shareable linkagesC         Pushbuttons                         installing images, 2-13 7          DECwindows Mail                  Shared memory G             activating in dialog boxes      creating and using XImages,g2                ,  1-40                        3-48C                                             extension support, 3-47 9         R                                   pixmaps, 3-52 B         _______________________________   Spyglass Enhanced MosaicE         Rebooting after installation,       no longer supported, 1-59d7           2-1                             Start Session B         Reference pages                     blue login screen, 2-7B          viewing,  1-7                    Start Session dialog boxG         ReGIS input cursors                 changing the position, 2-18a  F          See also Input cursors           Structured Visual Navigation  3         Resources                           See SVNw@          See also Mosaic                  SVN (Structured Visual8          font,  1-75                         Navigation)F          functional,  1-64                  horizontal separator line,2          proxy gateway,  1-76                 3-458          setting in Mosaic,  1-63           widget, 3-44G          visual,  1-73                    SYS$POSIX_FORK_CONTROL system 4         Run-time support, 3-2                service7                                             registering2H         S______________________________        addresses and parameters,5         Save/restore protocol, 1-4               3-14 I         Security options, 4-8                  protected shareable images 8          Session Manager,  1-47                  ,  3-140         Server                            SystemC          tuning,  2-7                       recommended quotas, 2-7 G         Session Manager                     tuning non-VGA devices, 2-7 9          color customizer,  1-47          System menu barn:          DECchart application,  1-45        messages, 2-22  I                                                                   Index-7n a                 1                                        Transports <     T______________________________     POSIX support,  3-13       Tear-off menusF       using,  4-5                      U______________________________  0     Terminal                           UIL files5       resizing,  1-32                   parsing,  3-3,6     Toolkit                            UIL source code<       compatibility,  3-3               documentation,  4-11          naming in OSF/MotifF             Release 1.2.2 and X11      V______________________________E             R5 Shareable Libraries,    Version checking command files 0             3-5                          ,  2-20?          using _Xm routines,  3-4      Virtual terminal support A       compiling C modules using the     creating a process,  2-25 7          MEMBER_ALIGNMENT switch,      Visual resources 2          3-17                           See Mosaic#       description of Release 1.2.3,o(          A-1                           WF       extensions                       _______________________________.          DXmCSText widget,  3-44       Widgets>       mixing Motif and XUI Widgets,     See also Motif and XUI8          3-27                              widgets, 3-27@       modifying XmText and              sizing and spacing usingE          XmTextField translation           DXmFormSpaceButtonsEqually 1          manager syntax, 3-26              , 3-45 :       OSF/Motif Release 1.2.3,  3-1    Window Dump utilityA       OSF/Motif Release 1.2.4,  3-1     dump to print file (xpr), /       OSF/Motif Release 1.2.5,  3-1        1-48o5       release 1.1.3 applications       Window Managerr>          abort, 1-58                    overlay support,  2-282       saving programming               Window sizeD          environments, 3-8              reporting for DECterm,  1-326     Toolkit shareable images           Workspaces, 1-8         See Shareable imagesF     Translated image support           X______________________________  >       Extended File Specifications     X Image extension, 3-45+          (EFS), 1-13                   Xlib A     Translated-image support,  3-14     Compaq international Xlibe?       running on OpenVMS systems,          implementation, 3-62 2          3-15                           extensionsE     Translations                           client side library,  3-46 C       unsupported with XmText           Internationalization,  3-60 5          Widget, 1-58                   locale,  3-62 0                                         routines       Index-8     y              E         Xlib                                unsupported translations,e2          routines (cont'd)                    1-585             files for Pascal programs,    XNL libraryoC                3-58                         xnl_parsedatetime, 3-58 B             parameter datasize,  3-59       xnl_xnl_langinfo, 3-586             XSelectAsyncEvent,  3-60      xnl_langinfoA             XSelectAsyncInput,  3-60        year 200 issues, 3-58 ;             XtAppMainLoop,  3-59          xnl_parsedatetime B          vendor pluggable layer,  3-61      year 2000 issues, 3-58C         XmNinputMethod resource           XSelectAsyncEvent routinenC          using the shell to specify         allocating memory, 3-60 C             input methods,  3-44          XSelectAsyncInput routine C         XmText Widget                       allocating memory, 3-60gF                                           XtAppMainLoop routine,  3-59                                                              I                                                                   Index-91