     1                     Compaq DECwindows for OpenVMS F                     __________________________________________________  !                     Release Notes                        April 2001  @                     This manual describes new features, software<                     problems, corrections, restrictions, and@                     documentation changes that pertain to Compaq@                     DECwindows Motif for OpenVMS, Version 1.2-6.            H                     Revision/Update Information:  This manual supersedes@                                                   the DECwindowsE                                                   Motif Version 1.2-5 E                                                   for OpenVMS Release 8                                                   Notes.  G                     Operating System:             OpenVMS Alpha Version G                                                   6.2, 7.1-2, 7.2-1, or 5                                                   7.3 E                                                   OpenVMS VAX Version ;                                                   6.2, 7.1, =                                                   7.2, or 7.3 C                                                   VMS Version 5.5-2   I                     Software Version:             Compaq DECwindows Motif D                                                   for OpenVMS Alpha,?                                                   Version 1.2-6 C                                                   Compaq DECwindows H                                                   Motif for OpenVMS VAX,?                                                   Version 1.2-6                         /                     Compaq Computer Corporation "                     Houston, Texas                 J           ________________________________________________________________           April 2001  ,            2001 Compaq Computer Corporation  A           COMPAQ, VAX, VMS, the Compaq logo, and the DIGITAL logo 9           Registered in U.S. Patent and Trademark Office.   A           Motif, OSF/1, and UNIX are registered trademarks of The            Open Group.   =           All other product names mentioned herein may be the A           trademarks or registered trademarks of their respective            companies.  C           Confidential computer software. Valid license from Compaq D           or authorized sublicensor required for possession, use, orD           copying. Consistent with FAR 12.211 and 12.212, CommercialA           Computer Software, Computer Software Documentation, and A           Technical Data for Commercial Items are licensed to the E           U.S. Government under vendor's standard commercial license.   ?           Compaq shall not be liable for technical or editorial /           errors or omissions contained herein.   B           The information in this publication is subject to changeA           without notice and is provided "AS IS" WITHOUT WARRANTY @           OF ANY KIND. THE ENTIRE RISK ARISING OUT OF THE USE OFB           THIS INFORMATION REMAINS WITH THE RECIPIENT. IN NO EVENT?           SHALL COMPAQ BE LIABLE FOR ANY DIRECT, CONSEQUENTIAL, D           INCIDENTAL, SPECIAL, PUNITIVE, OR OTHER DAMAGES WHATSOEVERE           (INCLUDING WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS =           PROFITS, BUSINESS INTERRUPTION, OR LOSS OF BUSINESS >           INFORMATION), EVEN IF COMPAQ HAS BEEN ADVISED OF THE@           POSSIBILITY OF SUCH DAMAGES. THE FOREGOING SHALL APPLY?           REGARDLESS OF THE NEGLIGENCE OR OTHER FAULT OF EITHER B           PARTY AND REGARDLESS OF WHETHER SUCH LIABILITY SOUNDS INB           CONTRACT, NEGLIGENCE, TORT, OR ANY OTHER THEORY OF LEGALA           LIABILITY, AND NOTWITHSTANDING ANY FAILURE OF ESSENTIAL (           PURPOSE OF ANY LIMITED REMEDY.  D           The limited warranties for Compaq products are exclusivelyD           set forth in the documentation accompanying such products.>           Nothing herein should be construed as constituting a)           further or additional warranty.   E                                                                ZK6470   B           The Compaq OpenVMS documentation set is available on CD-           ROM.                                 C   _________________________________________________________________   C                                                            Contents       C   Preface...................................................     xv      1  Introduction   C         1.1   Features of This Release......................    1-1      2  General User Release Notes   C         2.1   General DECwindows Motif Environment..........    2-1 C         2.1.1     Changes and Enhancements..................    2-1 C         2.1.1.1     Enhanced Web Browser Support............    2-1 C         2.1.1.2     Color Customizer Example Program........    2-3 C         2.1.1.2.1    Supported Displays.....................    2-3 C         2.1.1.2.2    Supported Applications.................    2-4 5         2.1.1.2.3    Building the Color Customizer on C                      OpenVMS Systems........................    2-4 C         2.1.1.2.4    Running the Color Customizer...........    2-5 C         2.1.1.2.5    Modifying the DECW$LOGIN.COM File......    2-5 C         2.1.1.2.6    Command Interface Summary .............    2-6 7         2.1.1.2.7    Changing the Mapping Between Color C                      Resources and Color Cells..............    2-7 C         2.1.1.2.8    DECterm Windows Not Affected...........    2-9 6         2.1.1.2.9    Changing the Default Value of theC                      Automatic Shadowing Toggle Button......    2-9 6         2.1.1.2.10   Using the Customizer on MultiheadC                      Systems................................    2-9 0         2.1.1.2.11   Using the XSETROOT_CUST.EXEC                      Demonstration Program..................   2-10 3         2.1.1.3     Window Dump to Print File (xpr) C                     Utility.................................   2-10 <         2.1.1.4     Keyboard Enhancements for Disabled UsersC                     (Alpha Only)............................   2-18 C         2.1.1.4.1    Sticky Keys............................   2-18   C                                                                 iii                    E           2.1.1.4.2    Mouse Keys.............................   2-18 E           2.1.1.4.3    Toggle Keys............................   2-18 E           2.1.1.4.4    Repeat Keys............................   2-19 E           2.1.1.4.5    Slow Keys..............................   2-19 E           2.1.1.4.6    Bounce Keys............................   2-19 E           2.1.1.4.7    Time Out...............................   2-19 E           2.1.1.5     Drag and Drop Support...................   2-19 E           2.1.2     Problems and Restrictions.................   2-20 6           2.1.2.1     Support Discontinued for DisplayE                       PostScript..............................   2-20 ;           2.1.2.2     Unsupported Translations by the Motif E                       XmText Widget...........................   2-20 E           2.1.2.3     Limited Supported for Tear-Off Menus....   2-22 7           2.1.2.4     Printing from Applications Linked E                       Against OSF/Motif Release 1.1.3.........   2-22 >           2.1.2.5     Access Control Not Explicitly Enabled byE                       Default.................................   2-22 E           2.2   New Desktop Environment (Alpha Only)..........   2-23 E           2.2.1     Changes and Enhancements..................   2-23 E           2.2.1.1     Screen Saver and Screen Lock Support....   2-23 4           2.2.1.2     Full List of Language VariantsE                       Displayed...............................   2-24 =           2.2.1.3     File/Shred Menu Item Handles Multilevel E                       Directories.............................   2-24 :           2.2.1.4     Display Icon Files from the Find SetE                       Dialog Box..............................   2-24 6           2.2.1.5     Selecting Screens on ApplicationE                       Launch..................................   2-25 3           2.2.1.6     Front Panel Icons Support MB3 E                       Operations..............................   2-25 E           2.2.1.7     Detached Processes......................   2-26 E           2.2.1.8     Viewing Reference Pages.................   2-26 E           2.2.2     Corrections...............................   2-27 9           2.2.2.1     Session Manager Exits Properly When <                       Saving a Session From an NonprivilegedE                       Account.................................   2-27 =           2.2.2.2     File Manager Allows Access to Files and E                       Directories That Use ACLs...............   2-28 7           2.2.2.3     Screen Lock Functions Properly on E                       Multihead Systems ......................   2-28 :           2.2.2.4     Can Set Default Display on MultiheadE                       Systems.................................   2-28            iv                   =               2.2.2.5     Can Remove the Calendar Icon From a I                           Subpanel................................   2-28 I               2.2.2.6     Can Switch Between Workspaces...........   2-29 =               2.2.2.7     Login Screen Positioned Properly in I                           640x480 Display Mode....................   2-29 =               2.2.2.8     Invalid Characters in a Username or I                           Password No Longer Halt Login...........   2-29 I               2.2.2.9     Welcome Message Updated.................   2-29 I               2.2.3     Problems and Restrictions.................   2-29 =               2.2.3.1     Desktop Applications Disappear When I                           Setting a Home Session..................   2-30 >               2.2.3.2     DECwrite Icon Does Not Open DECwriteI                           Program.................................   2-30 I               2.2.3.3     Viewing TIF Files with dximageview......   2-30 >               2.2.3.4     Text Editor Supports Standalone ModeI                           Only....................................   2-31 <               2.2.3.5     Text Editor Does Not Support SpellI                           Checking................................   2-31 >               2.2.3.6     Text Editor Tab Width is Larger ThanI                           Eight Characters........................   2-31 I               2.2.3.7     File Names Displayed in UNIX Format.....   2-31 @               2.2.3.8     Delay When Exiting a Session with OpenI                           TPU Windows.............................   2-31 I               2.2.3.9     Front Panel Clock is an Icon Only.......   2-32 I               2.2.3.10    ToolTalk Actions Not Supported..........   2-32 6               2.2.3.11    Session Manager Save/RestoreI                           Limitations.............................   2-32 I               2.2.3.12    File Manager Limitations................   2-33 ;               2.2.3.13    Login and Pause Screen Text Field I                           Restrictions............................   2-34 A               2.2.3.13.1   Control Characters Not Recognized When I                            Entering Username......................   2-34 @               2.2.3.13.2   Return Key Used to Move Between LoginI                            Text Fields............................   2-34 B               2.2.3.13.3   First Character Discarded When EnteringI                            Pause Screen Password..................   2-34 <               2.2.3.13.4   Text on the Welcome Screen is NotI                            Displayed..............................   2-35 =               2.2.3.14    Using SET DISPLAY/CREATE in DECterm I                           Windows.................................   2-35 I               2.2.3.15    Font Selection Limitations..............   2-35 I               2.2.3.16    Default Workspace Limitations...........   2-35       I                                                                         v                    >           2.2.3.17    Alt + Space Key Does Not Post the WindowE                       Menu ...................................   2-36 E           2.3   Traditional DECwindows Desktop Environment....   2-36 E           2.3.1     Problems and Restrictions.................   2-36 >           2.3.1.1     Alt + Space Key Does Not Post the WindowE                       Menu....................................   2-36 E           2.4   Bookreader....................................   2-37 E           2.4.1     Changes and Enhancements..................   2-37 E           2.4.1.1     Bookreader Printing Improved............   2-37 E           2.4.2     Corrections...............................   2-37 =           2.4.2.1     Last Login State Properly Restored (New E                       Desktop Only)...........................   2-37 <           2.4.2.2     Can Open DECW$BOOK Files Directly fromE                       FileView (Alpha Only)...................   2-37 ;           2.4.2.3     Can Specify DECW$BOOKSHELF Files with E                       Blank Lines.............................   2-38 E           2.4.3     Problems and Restrictions.................   2-38 4           2.4.3.1     Support for Display PostScriptE                       Removed.................................   2-38 9           2.4.3.2     Including Comment Characters in the E                       DECW$BOOKSHELF File.....................   2-38 E           2.5   CDA...........................................   2-38 E           2.5.1     Changes and Enhancements..................   2-39 E           2.5.1.1     Dynamic Font Support....................   2-39 E           2.5.1.2     WRITE$FONTS Logical Name................   2-39 E           2.5.1.3     Enhanced Display Performance............   2-40 E           2.5.1.4     Pack and Unpack Applications............   2-40 E           2.5.1.4.1    Pack Application Syntax................   2-41 E           2.5.1.4.2    Unpack Application Syntax..............   2-42 E           2.5.1.4.3    Error Messages.........................   2-43 E           2.5.1.5     Paper Size Button Renamed...............   2-44 E           2.5.1.6     New CDA Viewer Error Message............   2-44 E           2.5.2     Problems and Restrictions.................   2-44 4           2.5.2.1     Support for Display PostScriptE                       Removed.................................   2-44 E           2.6   Clock.........................................   2-45 E           2.6.1     Changes and Enhancements..................   2-45 E           2.6.1.1     DECsound Alarm Capability...............   2-45 E           2.6.2     Corrections...............................   2-45 7           2.6.2.1     DECW$CLOCK.EXE Process Increments E                       Correctly...............................   2-45 E           2.7   DECterm.......................................   2-45            vi                   I               2.7.1     Changes and Enhancements..................   2-46 I               2.7.1.1     Improved Batch Scrolling................   2-46 I               2.7.1.2     New Default Font Sizes..................   2-46 I               2.7.1.3     DECterm Resource File Name..............   2-47 I               2.7.1.4     Escape Sequences........................   2-47 I               2.7.1.5     Scrolling Through the Keyboard..........   2-48 I               2.7.1.6     Reporting the DECterm Window Size.......   2-48 I               2.7.1.7     Resizing the Terminal...................   2-48 >               2.7.1.8     Timeout for Displaying the CopyrightI                           Notice..................................   2-48 I               2.7.2     Corrections...............................   2-48 I               2.7.2.1     Can Specify Non-Standard Font Sets......   2-49 >               2.7.2.2     Device Output Files Used by MultipleI                           DECterm Windows Updated Correctly.......   2-49 <               2.7.2.3     Print Operations That Exceed QuotaI                           Generate a Warning Message..............   2-49 B               2.7.2.4     Button and Menubar Background Colors SetI                           Properly (New Desktop Only).............   2-50hI               2.7.3     Problems and Restrictions.................   2-50eI               2.7.3.1     Maximum Number of DECterm Windows.......   2-50.I               2.7.3.2     Changing the Auto Repeat Setting........   2-50xI               2.7.3.3     Positioning DECterm Windows.............   2-51lI               2.7.3.4     User Font Selection.....................   2-51 I               2.7.3.5     Local Echo..............................   2-52 I               2.7.3.6     Answerback Message......................   2-52.I               2.7.3.7     Seven-Bit Printer Support...............   2-53 I               2.7.3.8     Printing to an Attached Printer.........   2-53lI               2.7.3.9     DECterm Graphics........................   2-54.I               2.7.3.10    DECterm Resource Usage..................   2-54.I               2.7.3.11    Diagnostic Crash File and Messages......   2-55nI               2.7.3.12    VT330 and VT340 Terminal Emulation......   2-55wI               2.7.3.13    CREATE/TERMINAL/DETACHED/PROCESS........   2-56 I               2.7.3.14    ReGIS Locator Report....................   2-57oI               2.8   DECW$CDPLAYER.................................   2-58sI               2.8.1     Problems and Restrictions.................   2-58.I               2.8.1.1     Required Privileges.....................   2-58.I               2.9   DECwindows Mail...............................   2-58.I               2.9.1     Corrections...............................   2-58r;               2.9.1.1     Can Drag Messages Between Folders.@                           While Text is Selected in an Alternate          I                                                                       vii. 2                 E                       Window..................................   2-58 9           2.9.1.2     Can Send Multiple Messages from the E                       DECnotes Interface......................   2-59 ;           2.9.1.3     Can Pick Inbox on Receipt of New Mail E                       (Alpha Only)............................   2-593>           2.9.1.4     Window Color Options Displayed CorrectlyE                       (New Desktop Only)......................   2-59 E           2.9.2     Problems and Restrictions.................   2-59.1           2.9.2.1     Support Removed for DisplayiE                       PostScript..............................   2-59.9           2.9.2.2     Pasting Messages from the DirectorynE                       Window..................................   2-60 E           2.9.2.3     Responses to Keyboard Actions...........   2-6015           2.9.2.4     Using the Color Customizer with E                       DECwindows Mail.........................   2-60.E           2.10  Extended File Specification (EFS) Support.....   2-61 E           2.10.1    Changes and Enhancements..................   2-61 E           2.10.1.1    File Selection Popup Window.............   2-61.>           2.10.1.2    FileView Application (DECwindows DesktopE                       Only)...................................   2-61 ;           2.10.1.3    File Manager Application (New Desktop E                       Only)...................................   2-62 E           2.10.1.4    The Programming Libraries...............   2-62 E           2.10.2    Corrections...............................   2-62 ;           2.10.2.1    File Manager Corrections for EFS (New E                       Desktop Only)...........................   2-62 E           2.10.3    Problems and Restrictions.................   2-63 9           2.10.3.1    File Manager Problems with EFS (New E                       Desktop Only)...........................   2-63.<           2.10.3.2    Translated Image Support (TIS) LibraryE                       (Alpha Only)............................   2-64 E           2.11  Notepad.......................................   2-65.E           2.11.1    Problems and Restrictions.................   2-65 :           2.11.1.1    Notepad Is Linked with the OSF/MotifE                       Release 1.1.3 Toolkit...................   2-65 E           2.12  Paint.........................................   2-65 E           2.12.1    Problems and Restrictions.................   2-65 E           2.12.1.1    Private Colormaps.......................   2-65o4           2.12.1.2    Slow Performance of Some PaintE                       Operations..............................   2-66 E           2.13  Print Screen..................................   2-66 E           2.13.1    Problems and Restrictions.................   2-66 E           2.13.1.1    PostScript Output Problem...............   2-66          viii k                 I               2.14  Session Manager and FileView .................   2-67DI               2.14.1    Corrections...............................   2-67.=               2.14.1.1    Can Create DECterm Windows from thes;                           Qualifiers Dialog Box (DECwindows.I                           Desktop Only)...........................   2-67.I               2.14.2    Problems and Restrictions.................   2-67 <               2.14.2.1    Invoking DECchart from the SessionI                           Manager Applications Menu...............   2-68 I               2.14.2.2    Security Options........................   2-69DA               2.14.2.3    Using the Color Customizer with Session.I                           Manager.................................   2-70 B               2.14.2.4    Input Focus Change When Starting PrivateI                           Logo....................................   2-70 I               2.14.2.5    Stopping a Session Manager Process......   2-70 I               2.15  Window Manager................................   2-71cI               2.15.1    Changes and Enhancements..................   2-71 I               2.15.1.1    DECwindows XUI Applications.............   2-71aI               2.15.2    Problems and Restrictions.................   2-71o9               2.15.2.1    Using the Color Customizer with I                           DECwindows Motif Window Manager.........   2-71aI               2.15.2.2    Configuration File......................   2-72 I               2.15.2.3    Restarting Motif Window Manager.........   2-72.A               2.15.2.4    Customizing Color-Related Resources for.I                           Monochrome Monitors.....................   2-72.I               2.15.2.5    Moving the Icon Box Off Screen..........   2-73.9               2.15.2.6    Customizing Colors on Multihead.I                           Systems.................................   2-73eI               2.15.2.7    Multiline Icon Title Not Centered ......   2-73   '         3  System Manager Release Notes.  I               3.1   Installation and Upgrade Information..........    3-1 I               3.1.1     Changes and Enhancements..................    3-1 I               3.1.1.1     DMA Disabled by Default (Alpha Only)....    3-1 ?               3.1.1.2     DECW$GETPARAMS.COM Modified to Accept I                           Large GBLPAGES Values (Alpha Only)......    3-1 I               3.1.1.3     Previously Optional Files Moved.........    3-2 =               3.1.1.4     Using Shareable Linkages to Install.I                           Images (Alpha Only).....................    3-3.@               3.1.1.5     Version Checking Available for CommandI                           Files...................................    3-4p        I                                                                        ix                    E           3.1.2     Problems and Restrictions.................    3-5.6           3.1.2.1     Check System Parameters Prior toE                       Upgrade.................................    3-5 6           3.1.2.2     Upgrade Problem After InstallingE                       Required PCSI ECO.......................    3-6_E           3.1.2.3     Reboot Recommended After Installation...    3-7e9           3.1.2.4     Installation Verification Procedure E                       Error in UIL Compiler...................    3-7eE           3.2   System Startup Information....................    3-9hE           3.2.1     Changes and Enhancements..................   3-10O:           3.2.1.1     Starting DECwindows Independently ofE                       OpenVMS.................................   3-10 E           3.2.2     Problems and Restrictions.................   3-10 =           3.2.2.1     Problem With Delayed DECwindows Startup E                       (Alpha Only)............................   3-10 7           3.2.2.2     Color Problem in DECwindows Login E                       Screen..................................   3-13 E           3.3   System and Environment Tuning Information.....   3-13 E           3.3.1     Changes and Enhancements..................   3-13 <           3.3.1.1     Displaying an Expanded Welcome MessageE                       (New Desktop Only)......................   3-13 ;           3.3.1.2     Setting the File Manager Refresh Rate E                       (New Desktop Only)......................   3-14eE           3.3.1.3     System Tuning for Non-VGA Devices.......   3-14 :           3.3.1.4     Define DECW$UTILS Global Symbol WhenE                       Moving DECW$EXAMPLES Global Symbol......   3-17 E           3.3.1.5     Customizing the Login Screen............   3-18 <           3.3.1.5.1    Customizing the Compaq Logo and LoginE                        Screen Colors..........................   3-18 >           3.3.1.5.2    Changing Positions of the Start SessionE                        and Set Password Dialog Boxes..........   3-19_;           3.3.1.5.3    Disabling a Node Name Display in the E                        Start Session Dialog Box...............   3-20 E           3.3.1.6     Displaying Customized Login Logos.......   3-20eE           3.3.2     Problems and Restrictions.................   3-201E           3.3.2.1     System Hangs With Some Graphics Cards...   3-21 6           3.3.2.2     Performance Problem with CertainE                       Keymaps.................................   3-21vE           3.4   Console Window................................   3-22aE           3.4.1     Changes and Enhancements..................   3-23fE           3.4.1.1     Displaying Console Messages.............   3-23nE           3.5   DECterm.......................................   3-25c           xn                   I               3.5.1     Changes and Enhancements..................   3-25 I               3.5.1.1     Supported DECterm Logical Names.........   3-25bI               3.5.1.2     Automatic Window Positioning............   3-26eI               3.5.1.3     Improving Hold Screen Response Time.....   3-27hI               3.5.1.4     Using the Debugger......................   3-27 I               3.5.1.5     Virtual Terminal Support................   3-27HI               3.5.2     Problems and Restrictions.................   3-28PI               3.5.2.1     DECterm Window Shrinking Problem........   3-28,I               3.6   Session Manager and FileView..................   3-28TI               3.6.1     Changes and Enhancements..................   3-28N>               3.6.1.1     Implications of the Message, "SystemI                           Menu Bar: Pseudo Mouse Not Available"...   3-28GI               3.6.1.2     Detached Processes Created by Default...   3-29EI               3.6.2     Problems and Restrictions.................   3-30 @               3.6.2.1     DTSESSION Logging Problem (New DesktopI                           Only)...................................   3-30 I               3.7   Window Manager................................   3-30aI               3.7.1     Changes and Enhancements..................   3-30aI               3.7.1.1     Overlay Support.........................   3-30i  #         4  Programmer Release Notesa  I               4.1   OSF/Motif Toolkit Support.....................    4-1 8               4.2   Run-Time and Programming EnvironmentI                     Support.......................................    4-2 I               4.2.1     Changes and Enhancements..................    4-3 I               4.2.1.1     Available Language Bindings.............    4-3f>               4.2.1.2     Running Translated Images on OpenVMSI                           Systems.................................    4-4.I               4.2.2     Problems and Restrictions.................    4-6a8               4.2.2.1     Support for Display PostScriptI                           Removed.................................    4-6.5               4.2.2.1.1    Impact on DECwindows Motif I                            Applications...........................    4-7 I               4.2.2.1.2    Impact on Java Applications............    4-8.A               4.2.2.2     Using Multithreading and Upcalls (Alpha.I                           Only)...................................    4-8S,               4.2.2.3     Problems Using theI                           DECW$INCLUDE:INTRINSIC.H File...........    4-8.A               4.2.2.4     DECW$WML.EXE Looks in Current Directory.I                           For DECW$WML_TOKENS.DAT.................    4-9.<               4.2.2.5     DECW$COMPARE_VERSIONS Command FileI                           Limitation..............................    4-9e    I                                                                        xie l  a              E           4.2.2.6     Use of _Xm Routines.....................    4-9 7           4.2.2.7     Compiling Applications Written in E                       Fortran (Alpha Only)....................   4-10 E           4.2.2.8     Compiling Applications Written in C.....   4-10aE           4.3   CDA...........................................   4-11 E           4.3.1     Changes and Enhancements..................   4-11.E           4.3.1.1     Drag-and-Drop Feature Available.........   4-11lE           4.3.1.2     Changes to the Programming Interface....   4-12 3           4.3.1.3     Changes to External Reference.E                       Processing..............................   4-13 E           4.3.1.4     Message for Style Guide Fallback........   4-14u6           4.3.1.5     Using Logical Names with CONVERTE                       Commands................................   4-14 E           4.3.1.6     Restructuring Shareable Images..........   4-15 E           4.4   DECterm.......................................   4-17 E           4.4.1     Changes and Enhancements..................   4-17 E           4.4.1.1     ReGIS Input Cursors.....................   4-17 E           4.4.1.2     Page-Movement Escape Sequences..........   4-18 E           4.4.1.3     DECCRA Sequence.........................   4-18 E           4.4.1.4     DECLFKC Sequence........................   4-18tE           4.4.2     Corrections...............................   4-18u=           4.4.2.1     CREATE/TERM/WAIT SHOW PROCESS No LongertE                       Disrupts SYS$INPUT......................   4-19eE           4.5   DECTPU for DECwindows Motif...................   4-19iE           4.5.1     Problems and Restrictions.................   4-19eE           4.5.1.1     Small Display Monitors and DECTPU.......   4-19EE           4.6   DECwindows Extensions to Motif................   4-20.E           4.6.1     Changes and Enhancements..................   4-20l2           4.6.1.1     SVN Widget Supports ExtendedE                       Selection...............................   4-20SE           4.6.1.2     DXmCSText Input Method Support..........   4-20sE           4.6.2     Problems and Restrictions.................   4-20.0           4.6.2.1     DXmFormSpaceButtonsEquallyE                       Restriction.............................   4-20.<           4.6.2.2     SVN Widget Does Not Support HorizontalE                       Live Scrolling..........................   4-21.E           4.6.3     Corrections...............................   4-21p7           4.6.3.1     Calling DXmSvnDeleteEntries aftereE                       DXmSvnAddEntries........................   4-21 E           4.7   Display Server Extensions.....................   4-21p               xiin .  .              I               4.7.1     Changes and Enhancements..................   4-215@               4.7.1.1     Shared Memory Extension Support (AlphaI                           Only)...................................   4-21.I               4.7.1.1.1    How to Use Shared Memory Extension.....   4-22.I               4.7.1.1.2    Using Shared Memory XImages............   4-23.I               4.7.1.1.3    Using Shared Memory Pixmaps............   4-27.I               4.7.1.2     Specifying Extension Include Files......   4-28.I               4.7.1.3     X Image Extension Support...............   4-28.7               4.7.1.4     Client Side Extension LibrarytI                           Available...............................   4-29.I               4.8   Internationalization..........................   4-30UI               4.8.1     Changes and Enhancements..................   4-30F6               4.8.1.1     Using the CDA Viewer to ViewI                           Asian-Language Text.....................   4-30 I               4.8.1.1.1    Specifying an Options File.............   4-30 I               4.8.1.1.2    Defining Logical Names.................   4-31W7               4.8.1.2     Converting Files That Contain I                           Asian-Language Characters...............   4-32 I               4.9   XNL Library...................................   4-34 I               4.9.1     Changes and Enhancements..................   4-34 I               4.9.1.1     xnl_parsedatetime.......................   4-34 I               4.9.1.2     xnl_langinfo............................   4-34 I               4.10  Xlib..........................................   4-34 I               4.10.1    Changes and Enhancements..................   4-35 I               4.10.1.1    X11 Environment Variable Parsing........   4-35 I               4.10.1.2    UIDPATH Environment Variable............   4-35 0               4.10.1.3    New Default Format forI                           XtResolvePathname.......................   4-36 I               4.10.1.4    XtAppMainLoop Routine...................   4-36.I               4.10.1.5    Locale Support in OpenVMS Systems.......   4-36wI               4.10.1.6    Xlib Internationalization...............   4-37aI               4.10.1.6.1   Vendor Pluggable Layer.................   4-38o;               4.10.1.6.2   Compaq Internationalization Xlib.I                            Implementation.........................   4-39 A               4.10.1.7    XSelectAsyncEvent and XSelectAsyncInput.I                           Routines ...............................   4-39.I               4.10.1.8    Command Procedure Builds .PEN Files.....   4-40 I               4.10.2    Corrections...............................   4-40.I               4.10.2.1    UNIX Filename Emulation (Alpha Only)....   4-401;               4.10.2.2    XmTextField Widget Switches Focus I                           Correctly...............................   4-40 =               4.10.2.3    XrmoptionStickyArg Produces Correct I                           Results.................................   4-400    I                                                                      xiii. .  .              E           4.10.2.4    PAllHints Macro Corrected...............   4-41.E           4.10.3    Problems and Restrictions.................   4-41.4           4.10.3.1    XtOpenDisplay Routine and CaseE                       Sensitivity.............................   4-41.1           4.10.3.2    Parameter/Protocol DatasizeeE                       Mismatches..............................   4-41e  "     5  Documentation Release Notes  E           5.1   Getting Started With the New Desktop..........    5-1 E           5.1.1     File Specification Incorrect..............    5-1 9           5.2   DECwindows Motif for OpenVMS Applications E                 Guide.........................................    5-1 :           5.2.1     Enhancing Information About the FinishE                     Printing Option...........................    5-2 E           5.3   Using DECwindows Motif for OpenVMS............    5-3 E           5.3.1     Using the Drag-and-Drop Feature...........    5-3 E           5.3.2     Using Tear-Off Menus......................    5-3 3           5.3.3     Adding Target Screen Options to.E                     Application Menu Items....................    5-4 E           5.3.4     Changing the Startup Environment..........    5-4 E           5.3.5     Enhancing Startup Performance.............    5-5 E           5.3.6     Enhancing Hold-Screen Response Time.......    5-5 5           5.4   Managing DECwindows Motif for OpenVMS.E                 Systems.......................................    5-6sE           5.4.1     Global Symbols............................    5-61E           5.4.2     Security Options..........................    5-6.E           5.4.3     Displaying a Customized Logo..............    5-7 E           5.4.4     Enabling and Disabling Access Control.....    5-8 ;           5.5   DECwindows Motif for OpenVMS Guide to Non-C2E                 Bindings......................................    5-8.E           5.5.1     GET_CHAR_STRUCT Function..................    5-8 8           5.6   VMS DECwindows Guide to Xlib (Release 4)E                 Programming: VAX Binding......................    5-8 E           5.7   DECwindows Extensions to Motif................    5-9 E           5.7.1     DXmNlayoutDirection Resource Constants....    5-9 5           5.8   DECwindows Motif Guide to ApplicationPE                 Programming...................................   5-10.=           5.8.1     UIL Source Code for the OpenVMS DECburgerrE                     Application...............................   5-10.E           5.8.2     Help Widget Implementation Code...........   5-10mE           5.8.3     Help Widget Implementation-Callbacks......   5-10IE           5.8.4     Using UIL to Create the Help Widget.......   5-11d         xiv. .  .              .         A  OSF/Motif Release 1.2 Release Notes  I               A.1   Performance Improvements......................    A-1.I               A.2   Backward Compatibility........................    A-2.I               A.2.1     Visual and Behavioral Compatibility.......    A-2.B               A.3   Changes and New Features for OSF/Motif ReleaseI                     1.2...........................................    A-3.I               A.3.1     General Toolkit Changes...................    A-3.I               A.3.1.1     Include File Changes....................    A-3 I               A.3.2     Change in XT Translations.................    A-3 I               A.3.3     ANSI C Compliance.........................    A-4 I               A.3.4     Display and Screen Specific Data..........    A-4nI               A.3.5     Drag and Drop.............................    A-4 I               A.3.6     Tear-Off Menus............................    A-5iI               A.3.7     Insensitive Visuals.......................    A-5GI               A.3.8     Other Visual Changes......................    A-6VI               A.3.9     Titles for Frames.........................    A-6oI               A.3.10    Audible Warning...........................    A-6 I               A.3.11    Color Enhancements........................    A-7.I               A.3.12    Baseline Alignment........................    A-7fI               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-7RI               A.3.16    Traversal Access Functions................    A-8rI               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-11tI               A.4.4     XmMessageBox..............................   A-12.I               A.4.5     XmRowColumn and Menus.....................   A-12nI               A.4.6     XmScrollBar...............................   A-12iI               A.4.7     XmScrolledWindow..........................   A-13.I               A.4.8     XmSelectionBox, XmFileSelectionBox........   A-13 I               A.4.9     XmText....................................   A-13 I               A.4.10    XmTextField...............................   A-14.I               A.4.11    XmToggleButton, XmToggleButtonGadget......   A-15 I               A.5   Motif Window Manager Enhancements.............   A-15tI               A.5.1     Changes to MWM............................   A-15iI               A.5.2     New and Enhanced MWM Resources............   A-15.I               A.5.3     New and Enhanced MWM Functions............   A-16e  I                                                                        xv                    E           A.5.4     New MWM Action............................   A-17 E           A.6   Changes to the User Interface Language........   A-18   $     B  OSF/Motif Toolkit Information  9           B.1   OSF/Motif Release 1.2.2 and X11 Release 5.E                 Shareable Libraries...........................    B-1n;           B.2   OSF/Motif Release 1.1.3 Programming Support.E                 and XUI.......................................    B-4 E           B.3   DECwindows OSF/Motif Toolkit..................    B-9 :           B.3.1     Callable OSF/Motif UIL Compiler (AlphaE                     Only).....................................    B-9.E           B.3.2     Motif Text Widget Translations............    B-9dE           B.3.3     Upward Compatibility......................   B-10 :           B.3.3.1     Restrictions on Mixing Motif and XUIE                       Widgets.................................   B-11.;           B.3.4     Compile-Time Incompatibilities in Motif.E                     Header Files..............................   B-11.E           B.4   OSF/Motif Example Programs....................   B-12.E           B.4.1     Cut and Paste Example Program.............   B-12.E           B.4.2     DNDDemo Example Program...................   B-12 E           B.4.3     Dogs Example Program......................   B-14 E           B.4.3.1     Dog Widget..............................   B-15 E           B.4.3.2     Square Widget...........................   B-15 E           B.4.4     Helloint Example Program..................   B-162E           B.4.5     Hellomotif Example Program................   B-17 E           B.4.6     Motifanim Example Program.................   B-17.E           B.4.7     Motifgif and Pict Viewing Programs........   B-18.E           B.4.8     Motifshell Example Program................   B-19.E           B.4.9     Periodic Example Program..................   B-19.E           B.4.10    Textedit Example Program..................   B-19eE           B.4.10.1    Additional Translations.................   B-21aE           B.4.11    View Example Program......................   B-22dE           B.4.12    Xmpiano Example Program...................   B-24nE           B.4.13    Motif Sample Programs.....................   B-27 E           B.4.14    Xmtravel Example Program..................   B-28.E           B.4.15    Resource Files for Example Programs.......   B-28.E           B.4.16    UID Files for Example Programs............   B-29cE           B.5   OSF/Motif List of Known Problems..............   B-29p                 xvi. .                 9         C  Using the NCSA Mosaic Browser (VMS 5.5-2 Only)/  I               C.1   Starting Mosaic Software......................    C-2iI               C.2   Creating a Home Page..........................    C-3.<               C.3   Configuring Mosaic to Process MultimediaI                     Files.........................................    C-3iI               C.4   Customizing the Mosaic Browser................    C-5n?               C.5   Restrictions for Using Mosaic from Behind amI                     Firewall......................................   C-19sI               C.5.1     ProxyGateway Resource.....................   C-19rI               C.5.2     NoProxy Resource..........................   C-20.  
         Index              Examples  B               3-1       Error Messages Displayed Due to Low MemoryI                         in Granularity Hints Region...............   3-11I           Tables  B               1-1       Directory of Changes for Compaq DECwindowsI                         Motif for OpenVMS, Version 1.2-6..........    1-1.  I               2-1       Supported Web Browsers....................    2-1   I               2-2       Window Dump to Print File Options.........   2-12   I               3-1       Previously Optional Files Now Required....    3-2   I               3-2       Recommended Quotas for System Tuning......   3-14.  A               3-3       Moving the Compaq Logo and Changing Login I                         Screen Colors ............................   3-18   B               3-4       Changing Position of the Start Session andI                         Set Password Dialog Boxes.................   3-19   I               3-5       Logical Names Supported by DECterm........   3-25   I               4-1       Drag-and-Drop Widgets.....................   4-11o  I               4-2       New Header File Names.....................   4-13.  I               4-3       Names of Shareable Images.................   4-15a  =               4-4       ReGIS Input Cursors-Cursor styles anddI                         Values....................................   4-17t  I               4-5       Asian Language Codes for Options Files....   4-31a  9               4-6       Logical Names for Specifying Text.I                         Encoding..................................   4-32a  I                                                                      xvii                    E           4-7       Languages and Associated Basic Fonts......   4-33e  >           4-8       Routine Names and Arguments Sent as 16-BitE                     Values....................................   4-41   9           B-1       Names of Shareable Libraries Based on E                     R5........................................    B-2   9           B-2       Names of Shareable Libraries Based on E                     OSF/Motif Release 1.2.2...................    B-2   9           B-3       Directories for Previous XUI or Motif.E                     Programming Environment...................    B-7.  E           B-4       View Menu Options.........................   B-20t  E           B-5       Textedit Source Files.....................   B-20   E           B-6       Motif Sample Programs.....................   B-27   E           C-1       Functional Resources......................    C-6   E           C-2       Visual Resources..........................   C-16   E           C-3       Font Resources............................   C-17   E           C-4       Proxy Gateway Resources...................   C-19                                     	     xviii                              I         _________________________________________________________________h  I                                                                   Preface.      G               These release notes describe features, software problems, G               corrections, restrictions, and documentation changes that I               pertain to the Compaq DECwindows Motif for OpenVMS, Version                1.2-6 software..  :               The notes in this manual are cumulative fromH               DECwindows Motif Version 1.0 and indicate any undocumentedI               items that still pertain to the Compaq DECwindows Motif for H               OpenVMS, Version 1.2-6 software. Margin notes indicate theI               first version of the DECwindows Motif product to which eachn#               release note applies..           Intended Audience.  E               This manual is intended for system managers, users, andnF               programmers who work with the DECwindows Motif software.           Document Structure  3               This manual is structured as follows:S  E               o  Chapter 1 highlights the features, enhancements, andgB                  changes that comprise Compaq DECwindows Motif for(                  OpenVMS, Version 1.2-6.  F               o  Chapter 2 contains general user release notes for all                  users.   E               o  Chapter 3 contains release notes intended for systemi                  managers.  >               o  Chapter 4 contains release notes intended for4                  application and system programmers.  E               o  Chapter 5 describes additions and corrections to the #                  documentation set.   I                                                                        xv     .              B           o  Appendix A contains a subset of the release notes for#              OSF/Motif Release 1.2..  A           o  Appendix B contains release notes for the DECwindowsi              OSF/Motif Toolkit.a  @           o  Appendix C contains information on starting, using,A              and customizing the NCSA Mosaic browser on VMS 5.5-2               systems.n       Related Documents.  C           For additional information on the OpenVMS System Software.B           Group (OSSG) products and services, access the following)           OpenVMS World Wide Web address:   '           http://www.openvms.compaq.com.       Reader's Comments   C           Compaq welcomes your comments on this manual. Please send 8           comments to either of the following addresses:  +           Internet    openvmsdoc@compaq.como  1           Mail        Compaq Computer Corporation0:                       OSSG Documentation Group, ZKO3-4/U08(                       110 Spit Brook Rd.+                       Nashua, NH 03062-2698   )     How To Order Additional Documentation   ;           Use the following World Wide Web address to orderw#           additional documentation:r  -           http://www.openvms.compaq.com:8000/        Conventionsn  C           In this manual, references to OpenVMS are synonymous with .           the Compaq OpenVMS Operating System.  E           Unless otherwise specified, references to OpenVMS Clusters, B           VMSclusters, or clusters in this document are synonymous'           with Compaq OpenVMS Clusters..       xvi.    3              F               All uses of DECwindows and DECwindows Motif refer to theI               Compaq DECwindows Motif for OpenVMS software. Additionally, H               all uses of DECwindows XUI (X User Interface) refer to theG               DECwindows product prior to DECwindows Motif Version 1.0.   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.r  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, this4E                                convention appears as brackets, rathert*                                than a box.  <                . . .           Horizontal ellipsis points inE                                examples indicate one of the following -                                possibilities:.  D                                o  Additional optional arguments in a>                                   statement have been omitted.  D                                o  The preceding item or items can be=                                   repeated one or more times.e  I                                o  Additional parameters, values, or other.=                                   information can be entered.t  D               .                Vertical ellipsis points indicate theD               .                omission of items from a code exampleG               .                or command format; the items are omitted.D                                because they are not important to the5                                topic being discussed.o  >               ( )              In command format descriptions,I                                parentheses indicate that you must enclose.G                                the choices in parentheses if you choose.-                                more than one.s  I                                                                      xviig c                   C           [ ]              In command format descriptions, brackets >                            indicate optional elements. You canC                            choose one, none, or all of the options. B                            (Brackets are not optional, however, in?                            the syntax of a directory name in an-?                            OpenVMS file specification or in the.A                            syntax of a substring specification ins4                            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, bracesm?                            indicate required elements; you musto<                            choose one of the options listed.  9           text style       This text style represents the A                            introduction of a new term or the name.E                            of an argument, an attribute, or a reason..  E                            In the HTML version of this document, this.=                            convention appears as italic text.r  ;           italic text      Italic text emphasizes important.D                            information and indicates complete titles>                            of manuals and variables. VariablesD                            include information that varies in system?                            messages (Internal error number), in A                            command lines (/PRODUCER=name), and in ?                            command parameters in text (where dd A                            represents the predefined code for the.(                            device type).  B           UPPERCASE TEXT   Uppercase text indicates a command, theD                            name of a routine, the name of a file, orC                            the abbreviation for a system privilege.             	     xviiif F  e                I                                Monospace type indicates code examples and.;               Monospace type   interactive screen displays.s  G                                In the C programming language, monospacetD                                type in text identifies the following?                                elements: keywords, the names ofwH                                independently compiled external functions?                                and files, syntax summaries, and E                                references to variables or identifiers 8                                introduced in an example.  F               -                A hyphen at the end of a command formatF                                description, command line, or code lineF                                indicates that the command or statement?                                continues on the following line..  D               numbers          All numbers in text are assumed to beI                                decimal unless otherwise noted. Nondecimal.H                                radixes-binary, octal, or hexadecimal-are4                                explicitly indicated.                                                I                                                                       xix     .                    I                                                                         1dI         _________________________________________________________________x  I                                                              Introduction.    C               This chapter summarizes the features and enhancements.F               included in Compaq DECwindows Motif for OpenVMS, VersionF               1.2-6 and provides information regarding the recommended=               migration paths and the current support policy..  $         1.1 Features of This Release  E               Compaq DECwindows Motif for OpenVMS, Version 1.2-6 is a.G               maintenance release that delivers a full range of changessA               and enhancements to your desktop. From faster batch E               scrolling to support for the Common Desktop Environment G               (CDE) screen saver and lock extensions, these changes arenE               intended to provide you with a more efficient, flexibleTG               DECwindows Motif environment that is further in line witheH               the current OSF/Motif, MIT X11 Release 5 (X11 R5), and CDE               standards.  E               Table 1-1 lists the specific changes, enhancements, and.I               corrections implemented in this release of DECwindows Motiff:               and the section in which they are described.  H               Table 1-1 Directory of Changes for Compaq DECwindows MotifI               __________for_OpenVMS,_Version_1.2-6_______________________l  I               Title________________________________Section_______________.                 Global Changes  B               Enhanced Web Browser Support         Section 2.1.1.1  !               New Desktop Changes.  I                                                  (continued on next page)       I                                                                       1-1.    /           Introduction      1.1 Features of This Release    ;           Table 1-1 (Cont.) Directory of Changes for Compaq A                             DECwindows Motif for OpenVMS, Version1E           __________________1.2-6____________________________________1  E           Title________________________________Section_______________   >           Screen Saver and Screen Lock         Section 2.2.1.1           Support.  >           Full List of Language Variants       Section 2.2.1.2           Displayedt  >           File/Shred Menu Item Handles         Section 2.2.1.3            Multilevel Directories  >           Display Icon Files from the Find     Section 2.2.1.4           Set Dialog Box  >           Session Manager Exits Properly       Section 2.2.2.1'           When Saving a Session From ano           Nonprivileged Account   >           File Manager Allows Access to Files  Section 2.2.2.2'           and Directories That Use ACLss  >           Screen Lock Functions Properly on    Section 2.2.2.3           Multihead Systems.  >           Can Set Default Display on           Section 2.2.2.4           Multihead Systems.  >           Can Remove the Calendar Icon From a  Section 2.2.2.5           Subpanel  >           Can Switch Between Workspaces        Section 2.2.2.6  >           Login Screen Positioned Properly in  Section 2.2.2.7           640x480 Display Mode  >           Welcome Message Updated              Section 2.2.2.9  &           DECwindows Motif Application           Changes   >           Bookreader: Last Login State         Section 2.4.2.1(           Properly Restored (New Desktop           Only).  E                                              (continued on next page).       1-2. .         I                                                              Introduction I                                              1.1 Features of This Release     ?               Table 1-1 (Cont.) Directory of Changes for Compaq E                                 DECwindows Motif for OpenVMS, Version I               __________________1.2-6____________________________________   I               Title________________________________Section_______________.  B               Bookreader: Can Open DECW$BOOK       Section 2.4.2.21               Files Directly from FileView (Alpha                Only)s  B               Bookreader: Can Specify              Section 2.4.2.3-               DECW$BOOKSHELF Files with Blanks               Lines   B               Clock: DECW$CLOCK.EXE Process        Section 2.6.2.1"               Increments Correctly  B               DECterm: Improved Batch Scrolling    Section 2.7.1.1  B               DECterm: Can Specify Non-Standard    Section 2.7.2.1               Font Sets.  B               DECterm: Device Output Files Used    Section 2.7.2.21               by Multiple DECterm Windows Updatedn               Correctlyi  B               DECterm: Print Operations That       Section 2.7.2.3-               Exceed Quota Generate a Warningn               Message.  B               DECterm: Button and Menubar          Section 2.7.2.4,               Background Colors Set Properly                (New Desktop Only)  B               DECterm: CREATE/TERM/WAIT SHOW       Section 4.4.2.1(               PROCESS No Longer Disrupts               SYS$INPUTi  B               DECwindows Mail: Can Drag Messages   Section 2.9.1.1+               Between Folders While Text is -               Selected in an Alternate Windowe  B               DECwindows Mail: Can Send Multiple   Section 2.9.1.2(               Messages from the DECnotes               Interface.  B               DECwindows Mail: Can Pick Inbox on   Section 2.9.1.3.               Receipt of New Mail (Alpha Only)  I                                                  (continued on next page)   I                                                                       1-3                 Introduction      1.1 Features of This Release    ;           Table 1-1 (Cont.) Directory of Changes for Compaq.A                             DECwindows Motif for OpenVMS, VersiontE           __________________1.2-6____________________________________.  E           Title________________________________Section_______________   >           DECwindows Mail: Window Color        Section 2.9.1.4*           Options Displayed Correctly (New           Desktop Only)   ?           Session Manager/FileView: Can        Section 2.14.1.1 )           Create DECterm Windows from thev+           Qualifiers Dialog Box (DECwindowsa           Desktop Only).  ,           DECwindows Extensions to Motif and           Xlib Changes  >           SVN Widget Supports Extended         Section 4.6.1.1           Selection   ?           X11 Environment Variable Parsing     Section 4.10.1.1.  ?           UIDPATH Environment Variable         Section 4.10.1.2.  ?           New Default Format for               Section 4.10.1.3.           XtResolvePathname   ?           UNIX Filename Emulation (Alpha       Section 4.10.2.1            Only)   ?           XmTextField Widget Switches Focus    Section 4.10.2.2            Correctly   ?           XrmoptionStickyArg Produces Correct  Section 4.10.2.3_           Results_  ?           PAllHints Macro Corrected            Section 4.10.2.4   <           Callable OSF/Motif UIL Compiler      Section B.3.1           (Alpha Only)  )           Installation and Tuning Changes   >           DMA Disabled by Default (Alpha       Section 3.1.1.1           Only)t  E                                              (continued on next page).       1-4e           I                                                              IntroductionsI                                              1.1 Features of This Releases    ?               Table 1-1 (Cont.) Directory of Changes for CompaqME                                 DECwindows Motif for OpenVMS, VersionsI               __________________1.2-6____________________________________e  I               Title________________________________Section_______________   B               DECW$GETPARAMS.COM Modified to       Section 3.1.1.21               Accept Large GBLPAGES Values (Alpha                Only)u  B               Displaying an Expanded Welcome       Section 3.3.1.1(               Message (New Desktop Only)  B               Setting the File Manager Refresh     Section 3.3.1.2I               Rate_(New_Desktop_Only)____________________________________                                                             I                                                                       1-5e n  d                    I                                                                         2 I         _________________________________________________________________   I                                                General User Release Notes     F               This chapter contains information about DECwindows Motif                for general users.  0         2.1 General DECwindows Motif Environment  E               This section contains release notes that pertain to the F               general DECwindows Motif user environment. This includesI               common changes, corrections, and restrictions that apply tooI               both the New Desktop and the traditional DECwindows desktop                environments.e  &         2.1.1 Changes and Enhancements  @               The following notes describe important changes and?               enhancements made to the general DECwindows Motif                environment.  ,         2.1.1.1 Enhanced Web Browser Support                 V1.2-6  F               Compaq DECwindows Motif for OpenVMS, Version 1.2-6 usersD               have several web browser alternatives depending on theC               version of the OpenVMS operating system that they areo;               running. Table 2-1 shows the current options.n  I               Table_2-1_Supported_Web_Browsers___________________________   :               OpenVMS                     OpenVMS PlatformI               Version       _____________________________________________ I               ______________VAX_________________Alpha____________________s  1               5.5-2         NCSA Mosaic 4.2     -n  I                                                  (continued on next page)q  I                                                                       2-1s    n           General User Release Notes,     2.1 General DECwindows Motif Environment    E           Table_2-1_(Cont.)_Supported_Web_Browsers___________________   7           OpenVMS                      OpenVMS PlatformeE           Version       _____________________________________________ E           ______________VAX_________________Alpha____________________a  C           6.2           Netscape Navigator  Netscape Navigator GoldM0                         Gold 3.03           3.03  C           7.1, 7.1-2,   Netscape Navigator  Netscape Navigator Gold 0           7.2, 7.2-1,   Gold 3.03           3.03E           and_7.3___________________________Mozilla__________________   E           The following sections provide additional details regarding @           the individual web browsers and their current level of           support.             Mozillao  E           The OpenVMS development team has ported the Mozilla browsereC           to the OpenVMS Alpha platform. The latest version of thismB           browser, which is based on Netscape 6, is available from0           the following Compaq OpenVMS web page:  R           http://www.openvms.compaq.com/openvms/products/ips/register_mozilla.html  B           This page contains installation and running instructions@           for Mozilla, as well as information about hardware andD           software prerequisites, system parameters, account quotas,            and problem reporting.             Netscape Navigator  A           Netscape Navigator Gold Version 3.03 is the current web @           browser for most versions and platforms of the OpenVMSA           software. However, support for this browser is expected C           to end one year after the official release of the Mozillad           browser.  @           Compaq will continue to provide the Netscape NavigatorC           Gold software on an "as is," unsupported basis for use oniE           OpenVMS VAX systems and on those OpenVMS Alpha systems that C           do not support the Mozilla browser. See Table 2-1 for the D           current list of web browsers supported on OpenVMS systems.  B           You can obtain the Netscape Navigator Gold software from0           the following Compaq OpenVMS web page:  E           http://www.openvms.compaq.com/openvms/internetnetworks.html        2-2s n  s      I                                                General User Release Notes I                                  2.1 General DECwindows Motif Environment                    NCSA Mosaic   D               Compaq provides the National Center for SupercomputingG               Applications (NCSA) Mosaic Version 2.4 browser on an "as-pC               is, unsupported basis for systems running VMS Version,F               5.5-2. The software for the Mosaic browser is located inF               the DECW$UTILS directory and is installed as part of the4               DECwindows Motif product installation.  A               For detailed information about starting, using, andbB               customizing the NCSA Mosaic browser, see Appendix C.  &               Spyglass Enhanced Mosaic  H               The Spyglass Enhanced Mosaic browser is no longer providedA               with the DECwindows Motif software and is no longer I               supported. Note that starting with DECwindows Motif Version C               1.2-5, the product installation procedure removes thei0               Spyglass Enhanced Mosaic software.  I               If you are currently using this browser and plan to upgradetE               your system to DECwindows Motif Version 1.2-5 or later,h@               refer to Table 2-1 to select an alternate browser.  0         2.1.1.2 Color Customizer Example Program                 V1.2  @               The color customizer example program allows you to@               dynamically control the colors of your workstationF               environment. Window, icon, and window manager colors canI               be changed individually or as part of a palette switch. You G               can control mapping between resources and color cells, as E               well as the size and contents of the palette set. Also, C               automatic shadowing with the standard Motif shadowing &               algorithms is supported.  A               2.1.1.2.1 Supported Displays   The color customizer A               supports any display using pseudocolor or grayscale.D               visuals. This includes most 4- and 8-plane workstation               displays.e        I                                                                       2-3                 General User Release Notes,     2.1 General DECwindows Motif Environment    E           2.1.1.2.2 Supported Applications   The color customizer can D           affect the colors of any applications that use the current@           release of the DIGITAL X Toolkit Library. ApplicationsC           from other vendors and previous versions of the DIGITAL Xn)           Toolkit Library are unaffected.   C              ________________________ Note ________________________   ;              If the color customizer is used to control the =              colors of applications that have their own color 9              customization dialog boxes (like the SessioniA              Manager, Window Manager, and DECwindows Mail), those B              application-specific color customization dialog boxesC              may not reflect the correct current color values whilei?              the customizer is running the application. This issC              normal; use the customizer instead of the application-i>              specific dialog box to change these color values.  C              ______________________________________________________o  D           2.1.1.2.3 Building the Color Customizer on OpenVMS SystemsD            To build the color customizer on OpenVMS systems, perform           the following steps:  @           1. Copy the files to a private directory. For example:  $              $ SET DEFAULT SYS$LOGIN-              $ CREATE/DIRECTORY [.CUSTOMIZER] (              $ SET DEFAULT [.CUSTOMIZER]-              $ COPY DECW$EXAMPLES:CUSTOM.C []_/              $ COPY DECW$EXAMPLES:CUSTOM.UIL [] 4              $ COPY DECW$EXAMPLES:CUSTOMIMAGE.DAT []4              $ COPY DECW$EXAMPLES:XSETROOT_CUST.C []9              $ COPY DECW$EXAMPLES:BUILD_CUSTOMIZER.COM []C  >           2. Build the customizer using the following command:  $              $ @BUILD_CUSTOMIZER.COM  D           This command procedure creates the following output files:                CUSTOM.UIDl              CUSTOM.EXEp              XSETROOT_CUST.EXE       2-42 i  .      I                                                General User Release Notes I                                  2.1 General DECwindows Motif Environment     G               2.1.1.2.4 Running the Color Customizer   To run the color 6               customizer, perform the following steps:  E               1. Copy the files CUSTOM.UID and CUSTOM.EXE, which were F                  created during the customizer build, to the directoryE                  where the customizer will be run. A typical location G                  is the directory SYS$LOGIN or the directory DECW$USER_a                  DEFAULTS.  G               2. Copy the files CUSTOM.DAT and DXMDEFAULTS.DAT from the D                  directory DECW$EXAMPLES to the same location as youG                  copied the files in step 1. The same typical locations                   apply.,  ?               3. Run the executable file CUSTOM.EXE as follows:_                    $ RUN CUSTOM_  F                 ________________________ Note ________________________  A                 Only the colors of applications invoked after theoD                 customizer starts will be affected. For this reason,F                 start the customizer as the first X application during"                 the login process.  F                 ______________________________________________________  D               2.1.1.2.5 Modifying the DECW$LOGIN.COM File   As notedF               in Section 2.1.1.2.4, the color customizer should be theC               first X application started during the login process._D               Do this by starting it as a subprocess from within theI               DECW$LOGIN.COM file. Add a command to wait approximately 10 I               seconds between customizer startup and the startup of othere               applications.n  H               For example, add the following lines to the DECW$LOGIN.COM               file:n  .               $! Starting the color customizer3               $ DISPLAY = F$LOGICAL("DECW$DISPLAY")rF               $ SPAWN/NOWAIT/OUTPUT='DISPLAY' RUN SYS$LOGIN:CUSTOM.EXE               $ WAIT 0:0:10n  A               See Using DECwindows Motif for OpenVMS and Managing G               DECwindows Motif for OpenVMS Systems for more informationn)               on the file DECW$LOGIN.COM.   I                                                                       2-52 2              General User Release Notes,     2.1 General DECwindows Motif Environment    C           2.1.1.2.6 Command Interface Summary    A box containing a B           list of available palettes is in the leftmost section ofC           the Color Customizer window. Click on the desired palettec(           to see the colors take affect.  ?           Below the palettes are two arrays of colored buttons, @           representing the dynamically allocated color cells forB           normal and shadow colors. To find out what resources areC           affected by a color cell, click and hold the arrow button !           next to the color cell.   C              ________________________ Hint ________________________   A              As a shortcut, you can click on the screen facsimile >              in the rightmost corner of the dialog box. If theC              portion you click on is colored by one of the resourcesC              values controlled by the customizer, the pop-up window_;              for the appropriate color button is displayed._  C              ______________________________________________________O  C           To modify a single color cell, click on the correspondingl@           color button. A colormix widget pops up; as you modify>           the color, these modifications are reflected in your@           workstation environment. Use the colormix widget resetE           button to return to the starting color at any time. You caneB           also change the color cell you are modifying by clickingB           on a different color button while the colormix widget is           displayed.  A           The automatic shadowing option causes shadow and selectcE           colors to be automatically updated when their corresponding E           background colors are changed. The standard Motif shadowing 5           algorithms are used for these calculations.   E           Use the File menu to modify, add, and delete color palettesu           as follows:7  ?           o  To modify an existing palette, select the palette,N@              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.o       2-6n n  u      I                                                General User Release Notes I                                  2.1 General DECwindows Motif Environment9    C               o  To delete a palette, select the palette and choose 3                  Delete Palette from the File menu.e  I               Changes made through the File menu automatically update the-D               CUSTOM.DAT file, which contains the resource defaults.  I               The File menu Exit button causes the customizer application E               to exit. A warning dialog is displayed first. Note that_F               the color cells allocated by the customizer (and used byF               the currently running applications) will be deallocated.H               After the customizer exits, if the colors of the currentlyD               running applications are not correct, the applicationsD               should be restarted to restore normal colors. Usually,B               there is no need to exit the color customizer; it isC               typically kept running at all times, like the Sessiond               Manager.  D               2.1.1.2.7 Changing the Mapping Between Color ResourcesE               and Color Cells  The file DXMDEFAULTS.DAT allows you toiD               control how many dynamic color cells are allocated andF               what resources are affected. This file contains resource0               specifications like the following:  ;               *background:       DXmDynamicWindowBackground ;               *foreground:       DXmDynamicWindowForegroundc:               *topShadowColor:   DXmDynamicWindowTopShadow  I               When the customizer is started, the file DXMDEFAULTS.DAT is G               written to a property on the root window. Any applicationbB               that is subsequently run and that uses the correct XD               Toolkit Library merges these resources with its normalE               resource database. Resource specifications in this file A               take precedence over specifications with equivalent =               resource names in other resource default files.   A               The resource values within the file DXMDEFAULTS.DAT C               have a special format. For each unique color value inCC               this file that begins with the string "DXmDynamic", a A               color button is created in the color customizer. If_E               the string "Shadow" is encountered in a name, the color_C               button is placed in the shadow button box rather than B               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 named_  I                                                                       2-7                 General User Release Notes,     2.1 General DECwindows Motif Environment    E           "DXmDynamicScreenBackground" is encountered, the color cell D           allocated is used by the customizer to set the root window           background color._  D           You can edit the file DXMDEFAULTS.DAT and define resourcesD           to use the same color cells. You can have separate dynamicC           color cells, for scrollbar widgets or for your DECwindows @           Mail application, for example, by adding the following,           lines to the file DXMDEFAULTS.DAT:  =           Mail*background:         DXmDynamicMyMailBackground =           Mail*foreground:         DXmDynamicMyMailForegroundc<           Mail*topShadowColor:     DXmDynamicMyMailTopShadow?           Mail*bottomShadowColor:  DXmDynamicMyMailBottomShadow   C           Adding the previous lines to the file DXMDEFAULTS.DAT and B           restarting the customizer causes four new color cells toD           be allocated and four new color buttons to be added to theB           customizer interface. These buttons are assigned defaultA           color values (usually black or white) for each palette.e>           These defaults can then be modified for each palette+           through the customizer interface.S  C              ________________________ Note ________________________s  =              The text of the DXMDEFAULTS.DAT file is read andrB              parsed by the color customizer. The parsing algorithm;              does not allow comments, incorrect spacing, or_<              incorrect resource specifications. If this file<              or the CUSTOM.DAT resource file become corrupt,>              the customizer cannot start correctly. To resolve=              the problem, copy the versions of CUSTOM.DAT and B              DXMDEFAULTS.DAT from the DECW$EXAMPLES directory into"              your login directory.  C              ______________________________________________________                        2-8u r  _      I                                                General User Release NotesSI                                  2.1 General DECwindows Motif Environment_    @               2.1.1.2.8 DECterm Windows Not Affected   The colorG               customizer does not affect the colors of DECterm windows.rG               To change the colors of DECterm windows, copy the DECterm,G               resource specifications from the file DXMDEFAULTS.DAT and2G               add them to the DECterm resource defaults file DECW$USER__F               DEFAULTS:DECW$TERMINAL_DEFAULT.DAT. For example, add theD               following lines to the DECterm resource defaults file:                    .                  .                  .T                 DECW$TERMINAL.main.terminal.background: DXmDynamicTerminalBackgroundT                 DECW$TERMINAL.main.terminal.foreground: DXmDynamicTerminalForeground  I               This allows the DECterm window colors to be customized withq#               the color customizer./  C               2.1.1.2.9 Changing the Default Value of the Automatic ?               Shadowing Toggle Button  The default value of the @               automatic shadowing toggle button is set using theB               Custom.autoShadow resource in the CUSTOM.DAT file as               follows:  )               Custom.autoShadowing: False   (               The default value is True.  H               2.1.1.2.10 Using the Customizer on Multihead Systems   TheG               color customizer affects only applications started on thepF               same screen as the customizer. On multihead systems, youH               can start a different color customizer for each screen and@               have a different palette in effect on each screen.  B               The color customizer can be configured so that it isE               invoked once and affects all applications regardless of G               where they are started. This mode is invoked by modifyingoG               the Custom.multiScreen resource in the CUSTOM.DAT file asd               follows:  &               Custom.multiScreen: True  )               The default value is False.n      I                                                                       2-9                 General User Release Notes,     2.1 General DECwindows Motif Environment    >           2.1.1.2.11 Using the XSETROOT_CUST.EXE Demonstration@           Program   The XSETROOT_CUST.EXE demonstration program,<           created during the customizer build, is a modified=           version of the MIT utility program xsetroot that isu@           used to set a bitmap on the root window. The XSETROOT_>           CUST.EXE program uses DXmDynamicScreenBackground andE           DXmDynamicScreenForeground as the background and foregroundtA           colors of the specified bitmap. If your DXMDEFAULTS.DATtB           file contains entries for these two dynamic colors, thenE           use the customizer to dynamically modify the colors of your            bitmap.h             For example:  <           $ XSETROOT_CUST :== "$SYS$LOGIN:XSETROOT_CUST.EXE"3           $ XSETROOT_CUST -BITMAP your_xbm_file.XBMh  3     2.1.1.3 Window Dump to Print File (xpr) Utility              V1.2  B           The Window Dump to Print File utility prints an X Window%           dump using the xpr program.y  >           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:t             o  PostScript.  "           o  DIGITAL LN03 or LA100  $           o  IBM PP3812 page printer  0           o  HP LaserJet (or other PCL printers)             o  HP PaintJet  >           To use the xpr program, define xpr as a user-defined           command:  $           $ xpr == "$DECW$UTILS:XPR"  D           You must specify an input file. The xpr program prints theE           largest possible representation of the window on the output C           page. Options allow the user to add headers and trailers, @           specify margins, adjust the scale and orientation, and?           append multiple window dumps to a single output file.e       2-10 e  l      I                                                General User Release Notes.I                                  2.1 General DECwindows Motif Environment     /               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}                   -dumpe#                   -gamma correctionG#                   -gray {2 | 3 | 4} /                   -height inches  -width inchess1                   -header string  -trailer stringn'                   -landscape  -portrait_+                   -left inches  -top inches                    -nopositionz                   -nosixopt                    -plane n                   -psfig                   -render type                   -reporte                   -rvn                   -scale scale                   -slide                    -split n-pages  6               Table 2-2 defines the available options.                                  I                                                                      2-11                 General User Release Notes,     2.1 General DECwindows Motif Environment    E           Table_2-2_Window_Dump_to_Print_File_Options_________________  E           Option___________Description_______________________________r  D           -device devtype  Specifies the device on which the file is#                            printed.   7                            Currently supported devices:p  0                            la100  DIGITAL LA100.  /                            ln03   DIGITAL LN03.   >                            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).   ?                            pjetxl HP PaintJet XL Color Graphics 7                                   Printer (color mode).u  -                            pp     IBM PP3812.   5                            ps     PostScript printer.X  @                            lw     LaserWriter is equivalent to -D                                   device ps and is provided only for:                                   backwards compatibility.  5                            The default is PostScript.T  @           -scale scale     Affects the size of the window on the=                            page. The PostScript, LN03, and HPX=                            printers can translate each bit inb>                            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. ByD@                            default, a window is printed with theD                            largest scale that will fit onto the page9                            for the specified orientation.   D           -height inches   Specifies the maximum height of the page.  C           -width inches    Specifies the maximum width of the page._  ?           -left inches     Specifies the left margin in inches.n@                            Fractions are allowed. By default the:                            window is centered in the page.  E                                              (continued on next page)        2-12    _      I                                                General User Release NotesoI                                  2.1 General DECwindows Motif Environment2    I               Table_2-2_(Cont.)_Window_Dump_to_Print_File_Options________e  I               Option___________Description_______________________________o  G               -top inches      Specifies the top margin for the picturea@                                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 printedu0                                below the window.  A               -landscape       Forces the window to be printed inOF                                landscape mode. By default, a window isG                                printed so that its longest side followsf:                                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 follows.:                                the long side of the paper.  E               -plane number    Specifies which bit plane to use in an F                                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 scaleoB                                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.   D               -rv              Forces the window to print in reverse%                                video.r  C               -compact         Uses run-length encoding for compactwC                                representation of windows with white &                                pixels.  =               -output          Specifies an output file name.l               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)n  I                                                                      2-13l i              General User Release Notes,     2.1 General DECwindows Motif Environment    E           Table_2-2_(Cont.)_Window_Dump_to_Print_File_Options________   E           Option___________Description_______________________________   ?           -noff            When specified in conjunction with - A                            append, the window appears on the same 7                            page as the previous window.t  A           -split n-pages   Allows the user to split a window ontolE                            several pages. This might be necessary forSB                            very large windows that would otherwiseB                            cause the printer to overload and print9                            the page in an obscure manner.   C           -psfig           Suppresses translation of the PostScript =                            picture to the center of the page.   D           -density dpi     Indicates dot-per-inch density to be used-                            by the HP printer.i  C           -cutoff level    Changes the intensity level where colorseB                            are mapped to either black or white forC                            monochrome output on a LaserJet printer.mB                            The level is expressed as percentage ofB                            full brightness. Fractions are allowed.  <           -noposition      Causes header, trailer, and image?                            positioning command generation to be >                            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 valueaA                            in the range 0.00 to 3.00. Consult therE                            operator's manual to determine the correctl:                            value for the specific printer.  <           -render          Allows the PaintJet XL printer toA           algorithm        render the image with the best quality ?                            versus performance tradeoff. Consult A                            the operator's manual to determine thee0                            available algorithms.  E                                              (continued on next page)        2-14 n         I                                                General User Release NotesoI                                  2.1 General DECwindows Motif EnvironmentA    I               Table_2-2_(Cont.)_Window_Dump_to_Print_File_Options________c  I               Option___________Description_______________________________   C               -slide filename  Allows overhead transparencies to be F                                printed using the PaintJet and PaintJetI               _________________XL_printers.______________________________   =               The program contains the following limitations:   G               o  Support for PostScript output currently cannot use thea3                  -append, -noff, or -split options.   E               o  The -compact option is only supported for PostScript G                  output. It compresses white space but not black space, ?                  so it is not useful for reverse-video windows.   C               o  For color images, map directly to PostScript image                   support.   7               Program limitations with an LN03 printer:u  I               o  The current version of xpr can print most X Windows thatt>                  are not larger than two-thirds of the screen.  G                  For example, the LN03 prints a large Emacs window, butn>                  fails when trying to print the entire screen.  A               o  The LN03 has memory limitations that cause it tosI                  incorrectly print large or complex windows. The two most E                  common errors encountered are "band too complex" and E                  "page memory exceeded" and are described as follows:   &                  -  "band too complex"  E                     A window may have a particular six pixel row thatmE                     contains too many changes (from black to white torG                     black). This causes the printer to drop part of theoI                     line and possibly drop parts of the page. The printer.G                     flashes the number "1" on its front panel when this G                     problem occurs. A possible solution to this problemaG                     is to increase the scale of the picture or to splita7                     the picture onto two or more pages.i  *                  -  "page memory exceeded"  I                                                                      2-15                 General User Release Notes,     2.1 General DECwindows Motif Environment    B                 This occurs if the picture contains too much blackE                 space, or if the picture contains complex half-tones,tD                 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 togD                 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:s  <           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 andu!              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-dpi E              for the pjet device. The LaserJet printer supports 300-, E              150-, 100-, and 75-dpi. Consult the operator's manual totA              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.T  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 thec              printer.   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, #              invoke xpr as follows:T       2-16           I                                                General User Release Notes I                                  2.1 General DECwindows Motif Environment     *                  xpr -density 180 filename  C               o  The monochrome intensity of a pixel is computed aseI                  0.30*R + 0.59*G + 0.11*B. If the computed intensity of arG                  pixel is less than the -cutoff level, it prints white.dI                  This maps light-on-dark display images to black-on-whitemG                  hard copy. The default cutoff intensity is 50% of fullcG                  brightness. For example, specifying -cutoff 87.5 means H                  that a pixel will be displayed as black if the computed?                  intensity is less than 85% of full brightness.   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.e  E               o  Color images are produced on the PaintJet printer atRF                  90-dpi. The PaintJet is limited to 16 colors from itsI                  330 color palette on each horizontal print line. The xproH                  program issues a warning message if more than 16 colorsI                  are encountered on a line. Xpr programs the PaintJet forUF                  the first 16 colors encountered on each line and usesG                  the nearest matching programmed value for other colorsh                  on the line.D  I               o  Specifying the -rv option on the PaintJet printer causeshH                  black and white to be interchanged on the output image.-                  No other colors are changed.   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 positioning G                  commands. Output for these printers is not centered onuH                  the page, and header and trailer strings may not appear                   where expected.  I               o  The -gamma and -render options are supported only on theG&                  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                                                                      2-17  a  s           General User Release Notes,     2.1 General DECwindows Motif Environment    A     2.1.1.4 Keyboard Enhancements for Disabled Users (Alpha Only)j             V1.2  A           On OpenVMS Alpha systems starting with DECwindows MotifoA           Version 1.2 for OpenVMS, the AccessX extension provides E           features to help disabled users interact with workstations. ?           These features make it easier to use the keyboard and ?           mouse. You can interact with workstations by enteringuD           commands and manipulating menus and dialog boxes. However,E           with AccessX features, performing these input operations ism           even easier.  B           A client application is provided to enable and customizeB           the AccessX features. To run this application, enter the           following commands:   %           $ SET DEFAULT DECW$EXAMPLESs           $ RUN AccessXe  E           Online help is available by selecting the Help menu option.   @           AccessX offers the features described in the following           sections.   @           2.1.1.4.1 Sticky Keys   The Sticky Keys feature allows?           you to perform multikey operations with one hand, one E           finger, or a mouth stick. You can use this feature to enteriD           uppercase letters or punctuation characters without havingA           to hold down the Shift key while pressing the character A           key. This feature also makes it easier to enter control $           characters such as Ctrl/C.  D           2.1.1.4.2 Mouse Keys   The Mouse Keys feature lets you mapD           actions that you would perform with a mouse to keys on theD           numeric keyboard or other keys that you specify. With thisB           feature, you can use one finger or a mouth stick to moveA           the cursor to different areas of the screen, manipulatee1           menus, and select, cut, and paste text.   B           2.1.1.4.3 Toggle Keys   The Toggle Keys feature provides?           audio feedback when the Shift Lock (Caps Lock) key isdE           pressed. This feature helps users who might have difficultysD           seeing the keyboard light indicator for the Shift Lock keyA           or users who are using a keyboard that does not provider5           light indicators for any keyboard settings.l       2-18           I                                                General User Release Notes I                                  2.1 General DECwindows Motif Environment     H               2.1.1.4.4 Repeat Keys   The Repeat Keys feature allows youF               to adjust the auto-repeat keyboard mechanism speed or toH               turn it off entirely. With this feature turned on, you canG               set your keyboard so that holding down a key for a longereE               than average time does not cause a repeat entry of that                character.  H               2.1.1.4.5 Slow Keys   The Slow Keys feature makes the keysI               less likely to respond when brushed accidentally. With thisaE               feature turned on, the computer accepts only keystrokesdF               that are held for a certain length of time. The computerG               ignores light keystrokes that are held only for a moment.-  H               2.1.1.4.6 Bounce Keys   The Bounce Keys feature eliminatesA               the problem of pressing a key and then accidentally E               pressing it again before moving to another key. You can D               set this feature to tell the computer not to process aF               second pressing of a key unless a certain length of time,               elapses between each pressing.  E               2.1.1.4.7 Time Out   The Time Out feature shuts off thefH               AccessX features on a workstation after a specified periodD               of time. If you are sharing a workstation and have setI               AccessX features, the settings are automatically turned offnH               before the next use. To retain the AccessX settings at all;               times, you can turn off the Time Out feature..  %         2.1.1.5 Drag and Drop Support_                 V1.2  F               All DECwindows Motif applications except Notepad supportE               the drag-and-drop feature. DECwindows Mail supports the B               drag-and-drop feature in all windows except the mainG               message area, where DECwindows Mail has its own drag-and- H               drop; you can use MB2 to move messages around with the SVN               interface.  D               The drag-and-drop feature lets you move or copy screenI               objects; this feature is provided primarily for programmers @               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.  G               Refer to Section 5.3.1 for instructions on using drag and                drop.   I                                                                      2-19p t  s           General User Release Notes,     2.1 General DECwindows Motif Environment    #     2.1.2 Problems and Restrictions   =           The following notes describe the known problems and E           restrictions that currently exist in the general DECwindows            Motif environment.  7     2.1.2.1 Support Discontinued for Display PostScript   B           Starting August 1, 1998, Compaq discontinued support forD           Adobe Display PostScript software. Compaq took this actionD           because Adobe Systems Incorporated discontinued its former1           ongoing support for Display PostScript.   ?           This action has had a varying degree of impact on the >           behavior of those DECwindows Motif applications thatB           used the Adobe Display PostScript software. For example,B           starting with DECwindows Motif Version 1.2-6, Bookreader>           can no longer display graphics in PostScript format.  =           For information about the effects of this action on E           specific DECwindows applications, see the following release            notes:  (           o  Bookreader, Section 2.4.3.1  !           o  CDA, Section 2.5.2.1r  -           o  DECwindows mail, Section 2.9.2.1w  @           To learn about the possible impact to user-written andD           third-party applications designed for the DECwindows Motif+           environment, see Section 4.2.2.1.   ?     2.1.2.2 Unsupported Translations by the Motif XmText Widgets             V1.2-3  B           By default, the Motif XmText widget does not support theD           following translations for Versions 1.1, 1.2, and 1.2-3 of'           the DECwindows Motif product:_  /              F12:           beginning-of-line()f2              F13:           delete-previous-word())              Ctrl e:        end-of-line() 2              Ctrl j:        delete-previous-word()/              Ctrl h:        beginning-of-line()r,              Ctrl r:        redraw-display()5              Ctrl u:        delete-to-start-of-line() <              ~Ctrl ~Meta ~Shift Alt<Key>space: self-insert()       2-20           I                                                General User Release NotespI                                  2.1 General DECwindows Motif Environmentt    I               These translations are preferred by OpenVMS users to ensure >               consistency with the DCL command line interface.  G               The DECwindows Motif Session Manager defines translations ?               so that they can be used by applications that are I               displayed to an OpenVMS display server. If you display your I               applications on a different display server (for example, on H               a PC or Compaq Tru64 UNIX workstation), these translations!               are not functional.o  F               To enable these translations, add the following lines toE               your applications default file (for example, DECW$USER_ =               DEFAULTS:app_name.DAT or to the file DECW$USER_ &               DEFAULTS:XDEFAULTS.DAT):  3               *XmText.translations:   #override \n\h7                    <Key>F12:     beginning-of-line()\n\J:                    <Key>F13:     delete-previous-word()\n\1                    Ctrl<Key>e:   end-of-line()\n\ :                    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\oD                    ~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_ D                 DEFAULTS:XDEFAULTS.DAT file, startup performance for6                 all applications is slightly degraded.  F                 ______________________________________________________            I                                                                      2-21                 General User Release Notes,     2.1 General DECwindows Motif Environment    0     2.1.2.3 Limited Supported for Tear-Off Menus             V1.2-3  C           The following applications do not support tear-off menus:e             o  CDA Viewers             o  Notepad             o  Print Screenp  B           Refer to Section 5.3.2 for instructions on tearing off a+           menu and closing a tear-off menu.s  ?     2.1.2.4 Printing from Applications Linked Against OSF/MotifF             Release 1.1.3l             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")g           are also affected.  =           As a possible solution, either avoid displaying thetB           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.p  <     2.1.2.5 Access Control Not Explicitly Enabled by Default             V1.0  E           DECwindows Motif does not enable access control by default. E           Instead, the product uses access control set by the server. E           The DECwindows X11 display server enables access control at            startup time.   >           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        2-22 l  e      I                                                General User Release NotescI                                  2.1 General DECwindows Motif Environmente    D               If the logical name is not defined or if it is definedE               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 theo               logical name.i  0         2.2 New Desktop Environment (Alpha Only)  H               Compaq DECwindows Motif for OpenVMS, Version 1.2-6 productI               incorporates the Common Desktop Environment (CDE) Motif 1.0iG               Toolkit (OSF/Motif Release 1.2.5) and is based on ReleaseiC               5 of the X Window System Intrinsics. As with previous D               releases, Compaq DECwindows Motif for OpenVMS, VersionE               1.2-6 continues to provide run-time support for the XUI D               user interface and Toolkit. Application development is6               supported for the CDE Motif 1.0 Toolkit.  C               On Alpha systems, the New Desktop is derived from theJG               Common Desktop Environment (CDE). The user interface thattC               was provided in previous versions of DECwindows MotiftB               is referred to as the DECwindows desktop. The systemE               manager can choose to install either the New Desktop or D               the DECwindows desktop, or both. In addition, the userG               can select which desktop is started during the DECwindowsa                startup procedure.  I               This section contains release notes that pertain to the New "               Desktop environment.  &         2.2.1 Changes and Enhancements  H               The following notes describe changes and enhancements made-               to the New Desktop environment.   4         2.2.1.1 Screen Saver and Screen Lock Support                 V1.2-6  G               New Desktop now supports the Screen Saver Extension (MIT- B               SCREEN-SAVER), which is available systems running onB               OpenVMS Alpha Version 7.1 or greater. This extensionB               enables you to use the following features, which areA               available from the Style Manager Screen dialog box:   G               o  Screen saver-Prevents screen burn-in by displaying one G                  or more screen savers after a specific timeout period.   I                                                                      2-23f p  l           General User Release Notes,     2.2 New Desktop Environment (Alpha Only)    B              You can set both the timeout period and the amount of:              time each screen saver is displayed onscreen.  @              Sample screen savers are available from CDE$SYSTEM_A              DEFAULTS:[EXAMPLES.DTSCREEN]. To learn how to createeD              additional screen savers and make them available to theE              Style Manager, see Getting Started With the New Desktop.i  D           o  Screen lock-Secures your current New Desktop session(s)@              by locking the Front Panel after a specific timeout?              period. Once locked, a user must enter the accountd@              password of the home session password to unlock the              desktop.r  C           For more information on using the screen saver and screeniC           lock components of the Style Manager, see the online helpl,           for the Style Manager application.  4     2.2.1.2 Full List of Language Variants Displayed             V1.2-6  =           The Login Screen has been modified to recognize alle>           available language variants. Now when you select theE           Language item from the Options menu, all available languagefC           variants are listed and ready for selection. This enablesSA           you to login and create a localized New Desktop session @           that displays the Front Panel, desktop, and menu items?           according to the options associated with the selectedM           variant.  ?     2.2.1.3 File/Shred Menu Item Handles Multilevel Directoriesl             V1.2-6  >           The File Manager now allows you to delete items thatD           contain one or more subdirectories. Once dragged or placedB           into the Trash Can using the Select/Put In Trash option,B           you can select File/Shred to quickly dispose of the itemC           and its contents, including any underlying subdirectories            and files.  ;     2.2.1.4 Display Icon Files from the Find Set Dialog Boxe             V1.2-6  B           When defining or editing an application icon with CreateE           Action application, you can now view and select from a listsC           of available icon files in the associated Find Set dialog            box.       2-24           I                                                General User Release NotessI                                  2.2 New Desktop Environment (Alpha Only).    7         2.2.1.5 Selecting Screens on Application Launch                  V1.2-5  B               You can graphically select the screen on which a newD               application is displayed when launched from either theH               Front Panel, the File Manager, or the Application Manager.D               By default, the new application appears on the currentH               screen (that is, the screen containing the mouse pointer).E               The feature allows you to drop an application icon fromaE               the File Manager or Application Manager onto one of the H               numbered screen controls of the Set Default Screen window.H               This starts the application on the selected screen without*               changing the current screen.  E               The Set Default Screen window is activated as before byaC               selecting the "Set Default Screen" application in thesG               Application Manager's Desktop Tools folder. You can start E               a separate instance of the Set Default Screen window on D               each screen. The highlighting of the default screen isI               synchronized across all instances of the Set Default Screene               window.a  8         2.2.1.6 Front Panel Icons Support MB3 Operations                 V1.2-4  G               The New Desktop Front Panel supports mouse button 3 (MB3) F               operations. When the cursor is placed over a Front PanelE               icon and you press MB3, a subpanel or menu appears. Thep(               menu items are as follows:  0               o  Top item-The label of the menu.  F               o  Second item-The application that starts if you single#                  click on the icon.n  B               o  Third item-Add or delete a subpanel, depending onI                  whether a subpanel already exists for the control panel.r  G                 _______________________ Caution _______________________d  F                 If the third item is "Delete Subpanel", this change isB                 difficult to reverse without reinstalling the kit.  F                 ______________________________________________________  I                                                                      2-25                 General User Release Notes,     2.2 New Desktop Environment (Alpha Only)         2.2.1.7 Detached Processes             V1.2-4  @           When you start an application (from the Front Panel orC           dtfile), a new detached process is created with a processiA           name constructed from the user name, $CDE, and a three-r#           digit numeric identifier.e  E           For example, user SMITH starts an application whose processhD           name is SMITH$CDE001. The next assigned process name wouldE           be SMITH$CDE002, unless SMITH$CDE001 has already terminated %           and is available for reuse.l  #     2.2.1.8 Viewing Reference Pages              V1.2-4  D           DECwindows contains a collection of help files for the NewB           Desktop called reference pages (also known as manpages).D           Reference pages are divided into sections and, on OpenVMS,<           the file extension indicates the section. Sections=           distributed with the release include the following:h  E           ___________________________________________________________rE           Section_Purpose_____________Extension______________________   0           1       Applications        filename.1  0           3       Libraries/programminfilename.3  0           4       Programming         filename.4  0           5       Include file        filename.5E           ________formats____________________________________________   :           A version of dthelpview has been set up with the@           appropriate action definition for manpage viewing. TheB           process logical MANPATH has been defined to point to theB           CDE$SYSTEM_DEFAULTS:[MAN] directory that contains all of#           the reference page files.r  >           You can use either of the following methods to start1           dthelpview and display reference pages:        2-26 h  r      I                                                General User Release NoteseI                                  2.2 New Desktop Environment (Alpha Only)w                   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 :== -oZ                  _"$ sys$sysdevice:[sys0.syscommon.cde$defaults.system.bin]dthelpview.exe"  )               2. At the DCL level, enter:   3                  $ dthelpview -"manPage" dtaction.1g                 Method 2  G               To start dthelpview from Application Manager and view the /               reference page called dtaction.1:N  +               1. Start Application Manager.e  H               2. Double click on the Man Page Viewer icon located in theF                  Desktop Apps application group. A dialog box appears.  G               3. Enter the reference page to be viewed and click on OK..           2.2.2 CorrectionsD  I               The following notes describe the resolution of any problemssE               specific to the New Desktop environment that previouslyi<               resulted in an error or required a workaround.  I         2.2.2.1 Session Manager Exits Properly When Saving a Session From (                 an Nonprivileged Account                 V1.2-6  H               Starting and exiting a New Desktop session from an accountF               that does not have rename privileges to the files in theD               SYS$LOGIN:[.DT] directory no longer causes the SessionC               Manager to hang. This problem has been corrected; thebD               Session Manager exits the session properly and returns&               you to the Login Screen.  I                                                                      2-27A e  o           General User Release Notes,     2.2 New Desktop Environment (Alpha Only)    D     2.2.2.2 File Manager Allows Access to Files and Directories That             Use ACLs             V1.2-6  9           Previously, the File Manager application deniednB           nonprivileged users access to files and directories even?           though access was granted through access control listoC           (ACL). This problem has been corrected; dtfile allows the.B           user to access the file or directory as specified by the           related ACL entry.  ?     2.2.2.3 Screen Lock Functions Properly on Multihead Systems              V1.2-6  D           When running New Desktop on a multihead system, using lockE           screen with the Use Backgrounds For Lock option enabled waseC           not behaving properly. It was possible to lock the screen C           from a remote system and then display an application over D           the background on the locked workstation. This problem has           been corrected.   8     2.2.2.4 Can Set Default Display on Multihead Systems             V1.2-6  >           Previously, the following problems occurred when the>           default display was set to a value other than 0 on a           multihead system:E  E           o  File Manager (DTFILE.EXE) continued to display on screena              0.d  7           o  xrdb -q returned values only for screen 0.p  E           These problems have been fixed; all applications and return ?           values either appear on or are related to the correcto           display device.t  8     2.2.2.5 Can Remove the Calendar Icon From a Subpanel             V1.2-6  @           Previously, removing the Calendar icon from a subpanel>           caused the Window Manager to crash. This problem hasA           been corrected; you can safely delete the icon from any            application subpanel.        2-28 X  x      I                                                General User Release NotesiI                                  2.2 New Desktop Environment (Alpha Only)     -         2.2.2.6 Can Switch Between Workspaces                  V1.2-6  B               Previously, changing workspaces resulted in a systemF               crash as soon as the user clicked on a window in the newE               workspace to bring it into focus. This problem has been G               corrected; you can toggle between two or more workspaces.   H         2.2.2.7 Login Screen Positioned Properly in 640x480 Display Mode                 V1.2-6  D               The Login Screen has been recentered so that it allowsE               ample space for both operator message and login text onoH               Compaq Alpha systems that use the screen resolution of 640E               x 480 (such as those containing Cirrus graphics cards).   F         2.2.2.8 Invalid Characters in a Username or Password No Longer                 Halt Login                 V1.2-6  G               Entering one or more invalid characters (such as a space)_H               in either the Username or Password text field of the LoginE               Screen no longer halts the login process by causing the D               Login Screen to disapper. This problem has been fixed.G               If any invalid characters are detected, a warning message G               is displayed that prompts you to correct the username andf.               password text before proceeding.  '         2.2.2.9 Welcome Message Updated                  V1.2-6  E               Previously, the welcome message in the Login Screen didaG               not display a host name when the DECnet network transport E               was not configured. This problem has been corrected. IfpF               TCP/IP is the network transport, the TCP/IP host name isF               displayed. If neither transport is configured, a default;               message of "Welcome to OpenVMS" is displayed.i  '         2.2.3 Problems and Restrictionsb  =               The following notes describe known problems andpB               restrictions that currently exist in the New Desktop               environment.  I                                                                      2-29  r              General User Release Notes,     2.2 New Desktop Environment (Alpha Only)    >     2.2.3.1 Desktop Applications Disappear When Setting a Home             Sessioni             V1.2-6  C           In the Style Manager, selecting Startup and then Set Home.D           Session can cause applications that you previously startedE           using the Application Manager to disappear. This can happen >           if you start these applications with the Application?           Manager and then close the Application Manager beforee$           setting your home session.  B           The workaround is to keep the Application Manager window           open.   8     2.2.3.2 DECwrite Icon Does Not Open DECwrite Program             V1.2-5  D           DECwindows does not include the DECwrite program. However,>           DECwindows does include the DECwrite icon on the NewB           Desktop. If the DECwrite product has not been installed,@           clicking on the DECwrite icon results in the following           error messages:   L           > RCV'D (pid 000000CA): %DCL-W-IVVERB, unrecognized command verb ->                                    check validity and spelling.           -> RCV'D (pid 000000CA):  \DECWRITE\?           -> RCV'D (pid 000000CA):   TESTER       logged out at !           29-JUL-1998 17:56:44.63u  @           If the DECwrite product is installed and you still getC           this error, ensure that DECwrite is started in SYSTARTUP_p           VMS.COM.  .     2.2.3.3 Viewing TIF Files with dximageview             V1.2-4  E           When using dximageview to view TIF formatted files from thefD           CDE$SYSTEM_DEFAULTS:[APPCONFIG.HELP.C.GRAPHICS] directory,7           the following warning messages are displayed:e  K           TIFFOpen: Warning, unknown field with tag 34209 (0x85a1) ignored.nL           TIFFOpen: XResolution: Rational with zero denominator (num = 200).  ;           Note this error only occurs with the TIF files ino@           CDE$SYSTEM_DEFAULTS:[APPCONFIG.HELP.C.GRAPHICS]; it isB           only a warning. The file is still displayed correctly by           the image viewer.r       2-30           I                                                General User Release NotesfI                                  2.2 New Desktop Environment (Alpha Only)h    9         2.2.3.4 Text Editor Supports Standalone Mode OnlyE                 V1.2-4  <               The reference page for Text Editor describes aC               client/server implementation of the Text Editor. This C               release of the Text Editor supports the -"standAlone"h=               option only and is not built as a client/servern               application.  ;         2.2.3.5 Text Editor Does Not Support Spell Checking                  V1.2-4  C               The Text Editor application, which is part of the New G               Desktop, is described in Chapter 10 of the Common DesktoppD               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.e  E         2.2.3.6 Text Editor Tab Width is Larger Than Eight Charactersn                 V1.2-4  G               The Text Widget upon which the New Desktop Text Editor is G               based does not set the size of a tab to exactly the width E               of eight (8) characters; it is usually slightly larger. I               When displaying text with a combination of spaces and tabs,n5               text may not appear vertically aligned.t  3         2.2.3.7 File Names Displayed in UNIX Formatm                 V1.2-4  E               In the Application Manager Find dialog box and in errormB               messages reported by the Help Viewer, file names areF               displayed in UNIX format rather than in standard OpenVMSH               format. For example, SYS$SYSROOT:[SYSMGR]LOGIN.COM appears/               as /sys$sysroot/sysmgr/login.com.   B         2.2.3.8 Delay When Exiting a Session with Open TPU Windows                 V1.2-4  ?               Users will experience a one-minute delay for eachdG               DECwindows Text Processing utility (TPU) window displayed E               when exiting the session or when saving a home session.s  I                                                                      2-31i h  l           General User Release Notes,     2.2 New Desktop Environment (Alpha Only)    @           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.o@           The New Desktop Session Manager waits one minute for a=           response before continuing, resulting in the delay.d  -     2.2.3.9 Front Panel Clock is an Icon Only              V1.2-4  D           The New Desktop Front Panel Clock is an animated icon thatC           displays the current system time using an analog display.eE           The icon has no other function and does not support single- +           click or double-click operations.d  +     2.2.3.10 ToolTalk Actions Not Supported              V1.2-4  ?           Creation of ToolTalk Action definitions in the ActionuD           Definition files (*.dt) as described in the Common DesktopA           Environment: Advanced User's and System Administrator'si@           Guide is not supported. Although some ToolTalk actionsB           exist in the Action Definition files installed with thisE           product, modification of these actions is not supported and 9           could cause some New Desktop functions to fail.s  5     2.2.3.11 Session Manager Save/Restore Limitationsd             V1.2-4  ;           The Session Manager supplied with the New Desktop B           supports the WM_SAVE_YOURSELF protocol for the followingE           DECwindows applications: Bookreader, DECterm, and Calendar..B           Applications that have been written to take advantage of           this protocol can:  <           o  Save their state when the user exits a session.  @           o  Restore a state when the user starts a new session.  @           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.       2-32 i  t      I                                                General User Release Notes I                                  2.2 New Desktop Environment (Alpha Only)     E               o  Applications that do not support save/restore do notr'                  automatically restart.t  I               An example of an existing DECwindows Motif application that 7               supports save/restore is DECwindows Mail.s  )         2.2.3.12 File Manager Limitations                  V1.2-4  I               The File Manager application has the following limitations:2  C               o  If you specify a folder (directory) name, which is I                  strictly a logical name, and the logical name translatesnG                  to a search list, only the first directory encounteredp1                  in the search list is displayed.   D                  For example, the SYS$SYSTEM logical represents bothB                  SYS$SPECIFIC:[SYSEXE] and SYS$COMMON:[SYSEXE]. IfA                  you present a view of SYS$SYSTEM, only the filesnB                  in SYS$SPECIFIC:[SYSEXE] display. This is becauseF                  SYS$SPECIFIC:[SYSEXE] precedes SYS$COMMON:[SYSEXE] in!                  the search list.   B               o  When displaying a directory whose name includes aD                  search-listed device, all directories in the searchH                  path are displayed. If more than one directory with theE                  same name exists in the search path, an icon appears F                  for each instance of that directory. If more than oneG                  file with the same name exists in the search path, the2F                  behavior depends on whether the Show Top Version OnlyG                  filter option has been selected. If selected, only one H                  icon of the file with the highest version is displayed.E                  If not selected, all versions from all locations areaF                  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.1  =                  For example, suppose the files SYS$SPECIFIC:fG                  [SYSMGR]TOOLS.DIR;1 and SYS$COMMON:[SYSMGR]TOOLS.DIR;1gB                  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.  I                                                                      2-33                 General User Release Notes,     2.2 New Desktop Environment (Alpha Only)    :              To work around this problem, specify explicitA              directory names when a conflict occurs, for example,o:              SYS$SPECIFIC:[SYSMGR] or SYS$COMMON:[SYSMGR].  ;     2.2.3.13 Login and Pause Screen Text Field RestrictionsT             V1.2-4  D           The following sections provide information about the Login.           Screen and Pause Screen text fields.  D           2.2.3.13.1 Control Characters Not Recognized When Entering>           Username   The New Desktop does not support enteringA           control characters in the login Username text field. IftD           entered, these characters are discarded. This differs fromA           the DECwindows login Username text field which supports             such key sequences as:  @           o  Ctrl/U, Ctrl/J, or F13 (deletes to beginning of the              line)  C           o  Ctrl/H or F11 (positions to the beginning of the line)   6           o  Ctrl/E (positions at the end of the line)  E           The New Desktop does support Ctrl/U, which when typed while D           entering a password at login or when unpausing the screen,9           erases any characters entered up to that point.   ?           2.2.3.13.2 Return Key Used to Move Between Login Text D           Fields   Because the Username text field and Password textD           field are different dialog boxes in the New Desktop, pressB           the Return key to move the cursor from the Username text@           field to the Password text field. The Tab key does notE           move the cursor to the next text field; rather, this actiono#           highlights the OK button.w  B           2.2.3.13.3 First Character Discarded When Entering Pause@           Screen Password   If the workstation is paused and theC           Password dialog box is not displayed, the first charactereB           typed is ignored. This differs from the DECwindows pause<           screen, which always accepts any characters typed.  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.       2-34 e  o      I                                                General User Release Notes I                                  2.2 New Desktop Environment (Alpha Only)     I               2.2.3.13.4 Text on the Welcome Screen is Not Displayed   If G               the 100-dpi fonts are not included in the X server's font I               path, the welcome text is not displayed on the blue welcomegH               screen that appears immediately after logging in. This mayI               also occur if you are displaying your session on a remote Xl               server..  <         2.2.3.14 Using SET DISPLAY/CREATE in DECterm Windows                 V1.2-4  C               From a privileged account, if you use the SET DISPLAY.F               command from within a DECterm window without the /CREATEH               qualifier, it changes the display used for any applicationD               created from that point forward. It also redefines theG               display on which the login box appears after logging out.e  G               Always use the /CREATE qualifier when setting the display E               from a DECterm if you have not set the display already.   +         2.2.3.15 Font Selection Limitationse                 V1.2-4  G               On the New Desktop, Style Manager contains a control thateG               displays a dialog box used to select font size. SelectingtG               a new font size affects only New Desktop applications andFE               does not affect existing DECwindows Motif applications.   .         2.2.3.16 Default Workspace Limitations                 V1.2-4  A               The New Desktop provides a default backdrop for theeD               four default workspaces. You can change or even selectD               Nobackdrop using the Backdrop control located in Style               Manager.  E               When no backdrop is selected, you cannot drag icons andtD               place them on the backdrop of the desktop. If you dragF               an icon and release it, it snaps back to File Manager or"               Application Manager.  I               Icons that were dropped on the background before Nobackdrop 9               was selected remain and function correctly.h  I                                                                      2-35  2              General User Release Notes,     2.2 New Desktop Environment (Alpha Only)    :     2.2.3.17 Alt + Space Key Does Not Post the Window Menu             V1.2-4  C           The New Desktop maps the key binding Alt+space key to they@           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 ther              following line:  7              Alt<Key>space   icon|window   f.post_wmenuo  +           3. Restart the Workspace Manager.   2     2.3 Traditional DECwindows Desktop Environment  A           This section contains release notes that pertain to theo:           traditional DECwindows Desktop environment only.  #     2.3.1 Problems and Restrictionsn  9           The following notes describe known problems andh>           restrictions that currently exist in the traditional)           DECwindows Desktop environment.d  9     2.3.1.1 Alt + Space Key Does Not Post the Window Menu              V1.2-4  @           DECwindows Motif maps the key binding Alt+space key toB           the Compose Character function by default. This providesB           a method for character composition on keyboards which doB           not supply a specific Compose Character key. To use this&           feature, follow these steps:  D           1. Copy DECW$SYSTEM_DEFAULTS:DECW$MWM_RC.DAT to DECW$USER_&              DEFAULTS:DECW$MWM_RC.DAT.  C           2. In the Keys DtKeyBindings section, uncomment the line:V  7              Alt<Key>space   icon|window   f.post_wmenun  (           3. Restart the Window Manager.       2-36 l         I                                                General User Release Notes I                                                            2.4 Bookreader              2.4 Bookreader  C               This section contains release notes pertaining to the %               Bookreader application.p  &         2.4.1 Changes and Enhancements  H               The following notes describe changes and enhancements made,               to the Bookreader application.  ,         2.4.1.1 Bookreader Printing Improved                 V1.2-4  B               The Bookreader application allows only draft-qualityI               printing for books or topics. However, the Bookreader printnF               function has been improved to eliminate such problems asI               missing lines and words, figures being overwritten by text,i(               and poor leading of lines.           2.4.2 Correctionsi  E               The following notes describe the resolution of problemsh@               that previously resulted in an error or required a               workaround.   E         2.4.2.1 Last Login State Properly Restored (New Desktop Only)                  V1.2-6  C               Each time you start a New Desktop session, Bookreader F               remembers and properly restores its application state asE               it existed during your most recent New Desktop session. G               Previously, the application state and its position on the:2               desktop was only partially restored.  F         2.4.2.2 Can Open DECW$BOOK Files Directly from FileView (Alpha                 Only)s                 V1.2-6  I               Highlighting a Bookreader filename (.DECW$BOOK) in FileView I               and then starting Bookreader from the Applications menu nowi4               opens and displays the specified book.  G               Previously, only the main Bookreader window was displayedlD               containing the default library. Note that this problem9               existed on the OpenVMS Alpha platform only.   I                                                                      2-37  o  t           General User Release Notes     2.4 Bookreader    =     2.4.2.3 Can Specify DECW$BOOKSHELF Files with Blank Linesy             V1.2-6  A           Bookreader allows you to select and open DECW$BOOKSHELF <           files that contain either a blank line or that are=           not terminated by a front slash (\). The parsing of D           DECW$BOOKSHELF files has been improved so that this action3           no longer results in an access violation.   #     2.4.3 Problems and Restrictions   E           The following notes describe problems and restrictions thati:           currently pertain to the Bookreader application.  2     2.4.3.1 Support for Display PostScript Removed             V1.2-6  @           With the removal of the support for Display PostScriptB           from the current version of DECwindows Motif, Bookreader>           no longer supports the display of PostScript artwork?           in online manuals. When Bookreader detects PostScript1@           artwork, it displays a full-size figure window with anB           large "X" overlayed with an error message box containing            the following message:  2           Unable to display PostScript(R) graphic..           This feature is no longer available.  !           There is no workaround.r  C     2.4.3.2 Including Comment Characters in the DECW$BOOKSHELF Filet             V1.2-3  A           If you include a comment character (! or #) in the lastcB           line of the DECW$BOOKSHELF file, Bookreader fails with aE           reserved operand fault. As a workaround, ensure that you dooB           not add comment characters to the last line of the file.       2.5 CDA              V1.2  A           This section contains release notes that pertain to the D           Compound Document Architecture (CDA) Run-Time Services and4           CDA Viewer components of DECwindows Motif.       2-38           I                                                General User Release NotesoI                                                                   2.5 CDAr    &         2.5.1 Changes and Enhancements  C               The following notes describe changes and enhancements4B               made to the the CDA Run-Time Services and CDA Viewer               application.  $         2.5.1.1 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 forI               dynamic font lookup. This enables the CDA Viewer to use newu8               fonts as they are installed on the system.  ;               Dynamic font support is implemented using the I               WRITE$FONTS.INI file, which you can maintain using the FontiG               utility provided with either DECwrite or DECpresent. If adF               document contains a font not found in the static tables,G               the CDA Viewer tries to open the WRITE$FONTS.INI file and E               search for the font. If the font is not found or if the H               system does not contain a WRITE$FONTS.INI file, the viewer#               uses a fallback font.d  (         2.5.1.2 WRITE$FONTS Logical Name                 V1.2  B               The default location for the WRITE$FONTS.INI file isB               SYS$LIBRARY, but, if the logical name WRITE$FONTS isF               defined, the CDA Viewer uses the logical name definition5               to search for the WRITE$FONTS.INI file.k  D               Full path support is included, so any of the following$               definitions are valid:  I               ___________________________________________________________p!               WRITE$FONTS Logical1I               Name__________________Resulting_File_______________________   ?               Undefined             SYS$LIBRARY:WRITE$FONTS.INIr  C               DISK:[DIRECTORY]      DISK:[DIRECTORY]WRITE$FONTS.INIs  =               SYS$LOGIN:            SYS$LOGIN:WRITE$FONTS.INIl  ?               .TMP                  SYS$LIBRARY:WRITE$FONTS.TMPs  I               DISK:[DIRECTORY]FILE__DISK:[DIRECTORY]FILE.INI_____________.  I                                                                      2-39                 General User Release Notes     2.5 CDA     (     2.5.1.3 Enhanced Display Performance             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 thisi           enhancement.  E           The CDA Viewer enables this performance enhancement feature =           by default. You can disable the feature as follows:   -           $ DEFINE CDA_QUICK_FIRST_PAGE FALSE   C           The CDA Viewer might not display some documents correctly ?           when this feature is enabled. If you encounter such ap@           problem, disable the feature and invoke the CDA Viewer           again.  (     2.5.1.4 Pack and Unpack Applications             V1.2  D           CDA Run-Time Services includes two standalone applicationsB           that can be used for transferring CDA documents across aC           network. The CDA Pack application packages a CDA documentlB           along with all of its externally referenced files into aB           single file that can be copied between systems or mailedA           to other users. The CDA Unpack application reads a fileaD           that is packaged by the CDA Pack application and creates aC           copy of the original document file and all its externallye           referenced files.   <           These applications allow you to copy CDA documents?           between systems without copying externally referencedY@           files separately or correcting external file reference.           information after copying documents.  <           To use these applications, add the following lines9           to your LOGIN.COM file (or add the lines to the (           SYS$MANAGER:SYLOGIN.COM file):  .           $ PACK == "$SYS$SYSTEM:CDA$PACK.EXE"2           $ UNPACK == "$SYS$SYSTEM:CDA$UNPACK.EXE"  C           These lines enable you to use the symbols PACK and UNPACKaC           to invoke the Pack and Unpack applications, respectively.        2-40 S         I                                                General User Release NotesoI                                                                   2.5 CDAp    >               2.5.1.4.1 Pack Application Syntax   The CDA PackD               application creates a single output file that containsE               the contents of a .DDIF or .DTIF input file. The singlenH               output file also includes the files that are referenced by,               the .DDIF or .DTIF input file.  ;               The format of the PACK command is as follows:e  5               $ PACK input-file-spec output-file-specd  C               The following sections explain the format of the PACKe               command.                 input-file-specSD               Specifies the name of the primary .DDIF or .DTIF input               file.e                 output-file-specC               Specifies the name of the output file that is created E               by the PACK application. If you do not specify a device E               or directory, the output file is created in the current                 default directory.                 Qualifiers:3                 /[NO]SKIP_MISSINGRH               Controls whether the Pack application continues processingH               if it cannot find one or more of the files that are listedD               as external references in the input file. The names ofC               any missing files are sent to SYS$ERROR when the PackeG               application is completed. If you specify /NOSKIP_MISSING, H               the Pack application does not create an output file if anyI               of the externally referenced files are missing. The defaultd               is /SKIP_MISSING.e  "               /[NO]CONTROLLED_COPYB               Controls whether the output file includes only thoseD               external references that specify COPY_REFERENCE as theE               value of the ERF_CONTROL item in the input file. If youtG               specify /NOCONTROLLED_COPY, the Pack application includes1G               all referenced files, regardless of the value of the ERF_ >               CONTROL item. The default is /NOCONTROLLED_COPY.      I                                                                      2-41o C  /           General User Release Notes     2.5 CDAs               /ALWAYS_ENCODEC           Controls whether an output file is created when there areiA           no external references in the input file, or if none ofTC           the externally referenced files are found. The default is C           not to create an output file in these cases. If an outputpE           file is not created for these reasons, the Pack applicationt1           returns the CDA_W_NOOUTFIL status code.a             For example:  &           $ PACK MYFILE.DDIF TEST.PACK  >           2.5.1.4.2 Unpack Application Syntax   The CDA Unpack?           application unpacks an input file created by the Pack C           application. The output files are the .DDIF or .DTIF file C           that is packed by the Pack application, as well as a file A           for each external reference in the .DDIF or .DTIF file. A           The Unpack application sends a list of created files toh           SYS$ERROR.  9           The format of the UNPACK command is as follows:e  "           $ UNPACK input-file-spec  A           The following sections explain the format of the UNPACKt           command.             input-file-spectE           Specifies the name of the input file that is created by the            Pack application.              Qualifier:  "           /OUTPUT=output-file-specC           Specifies the file name and location of the files created $           by the Unpack application.  @           If you specify an output file name without a directory=           name, the Unpack application creates the main .DDIF =           or .DTIF file with the file name you specify in the C           current default directory. It also creates all externally <           referenced files in the current default directory.           2-42           I                                                General User Release Notes I                                                                   2.5 CDAE    F               If you specify a directory name without a file name, theI               Unpack application creates the main .DDIF or .DTIF file andaI               all externally referenced files in the specified directory. H               The main .DDIF or .DTIF file has the same name as the file-               packed by the Pack application.r  B               If you specify a directory name and a file name, theE               Unpack application creates the main .DDIF or .DTIF fileiG               and all the externally referenced files, in the specifiedaG               directory. The main .DDIF or .DTIF file has the file namet               you specify.                 For example:                  $ UNPACK TEST.PACK;               Output file DISK$:[SMITH]MYFILE.DDIF created. =               Output file DISK$:[SMITH]FIGURE_1.DDIF created.t  6               $ UNPACK TEST.PACK/OUTPUT=[SMITH.UNPACK]B               Output file DISK$:[SMITH.UNPACK]MYFILE.DDIF created.D               Output file DISK$:[SMITH.UNPACK]FIGURE_1.DDIF created.  C               $ UNPACK TEST.PACK/OUTPUT=[SMITH.UNPACK]NEW_FILE.DDIF O               Output file DISK$:[SMITH.UNPACK]MYFILE.DDIF renamed NEW_FILE.DDIF D               Output file DISK$:[SMITH.UNPACK]FIGURE_1.DDIF created.  H               2.5.1.4.3 Error Messages   This section describes messagesC               associated with the CDA Pack and Unpack applications.b  /          FILESPEC,  Missing filespec: file-namee  #             Severity: Informational   G             Explanation: The Pack application cannot locate an external H             file included as an external reference in the .DDIF or .DTIFH             file or in one of the files referenced in the .DDIF or .DTIF             file.   /          NOOUTFIL,  No output file was created.n               Severity: Warning   B             Explanation: The Pack application cannot find externalG             references in the .DDIF or .DTIF document to be packed, andp=             you did not specify the /ALWAYS_ENCODE qualifier.t  I                                                                      2-43g S  W           General User Release Notes     2.5 CDA     -       OUTFILE, Output file created: file-nameo             Severity: Informational            Source: CDA_UNPACKa  B          Explanation: The Unpack application created the specifiedE          file while unpacking a file created by the Pack application.   %     2.5.1.5 Paper Size Button Renamed              V1.2  E           In the CDA Viewer, the name of the Paper Size button in the.B           Open dialog box was changed to Display Options. However,=           the function invoked by the button was not changed.x  (     2.5.1.6 New CDA Viewer Error Message             V1.2  E           The CDA Viewer issues the following message if it is unable ,           to create the application context:  D       DRMCTXFAIL, DVR could not create application context, aborting            Level: Errorv  ?          Explanation: The CDA Viewer ends because an attempt tocB          create the application context using the Resource Manager@          failed, which is usually caused by insufficient memory.  :          User Action: Reduce the system load and start the          application again.   #     2.5.2 Problems and Restrictionss  9           The following notes describe known problems and ?           restrictions that currently exist with either the CDAa:           Run-Time Services or the CDA Viewer application.  2     2.5.2.1 Support for Display PostScript Removed             V1.2-6  @           With the removal of the support for Display PostScriptE           from the current version of DECwindows Motif, CDA no longeriC           supports the display of PostScript source. The PostScripthE           option has been removed from the CDA Viewer. If you attemptaE           to view a PostScript file from the character cell interface.@           CDA viewer, the viewer displays the following message:  7           %CDA-E-UNSUPFMT, unsupported document format.n  !           There is no workaround.i       2-44    i      I                                                General User Release NoteslI                                                                 2.6 Clocki             2.6 Clocki  I               This section contains release notes pertaining to the Clock                application.  &         2.6.1 Changes and Enhancements  H               The following notes describe changes and enhancements made'               to the Clock application.L  )         2.6.1.1 DECsound Alarm Capabilityy                 V1.2  I               The Clock application includes an alarm feature that can be G               used if your system supports DECsound. On systems without H               sound capabilities, you can select only the keyboard bell.C               When you choose Alarm from the Options menu, a pop-up F               window appears. This pop-up window allows you to set theH               alarm time, choose the sound to be played, and indicate anI               alarm message. To see if your system supports this feature,aC               invoke one of the sounds located in the DECW$EXAMPLESd1               directory (for example, BELLS.AUD).p           2.6.2 Correctionsd  E               The following notes describe the resolution of problemsiG               with the Clock application that previously resulted in ano-               error or required a workaround.a  ;         2.6.2.1 DECW$CLOCK.EXE Process Increments Correctly                  V1.2-6  H               The Clock application now consistently increments hour andE               minute values correctly. Previously, the DECW$CLOCK.EXE F               process generated two timer queue entries (XtTimeout) atD               the end of each 61-minute period to increment both theE               minute and hour values. Due to scheduling issues, these B               duplicate entries sometimes resulted in a time loss.E               The expiration value for XtTimeout has been adjusted tos%               eliminate this problem.l           2.7 DECtermo  A               This section contains information about the DECtermr               application.  I                                                                      2-45  h  e           General User Release Notes     2.7 DECterm     "     2.7.1 Changes and Enhancements  9           The following notes describe recent changes ando7           enhancements made to the DECterm application.o  $     2.7.1.1 Improved Batch Scrolling             V1.2-6  =           The overall performance of batch scrolling has been ?           improved allowing you to moving through long files orsD           multiscreen output quicker and easier. Now when you changeC           the value of the Batch Scroll Lines option in the DisplayuB           Options dialog box, the resulting display performance is           visibly quicker.  "     2.7.1.2 New Default Font Sizes             V1.2-4  A           In previous releases, the default DECterm font size foraA           the "big" and "little" fonts were chosen by point size.rE           This depended on whether 75 or 100 dpi fonts were installedf@           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.  E           ___________________________________________________________ %                                 Prior E                                 Releases          Since Version 1.2-4            Default Font Size E           (in_pixels)___________100___75[1]_______100___75___________c  :           Big font              25    18          18    18  :           Little font           18    14          14    14E           [1]75_dpi_fonts_or_100_dpi_fonts_on_a_15-inch_monitor______   E           ___________________________________________________________p  C           In addition, on 100-dpi displays DECterm now uses the bighA           font by default. This results in DECterm using the same @           font size (18 pixels) on 100-dpi displays as it did inE           prior releases. On displays that are less than 325 mm wide, 6           DECterm also now uses a bigger default font.  @           Follow these steps to use the same font as in previous           releases (14 pixels):w  >           1. From the Options menu, select the Window... item.       2-46 n  f      I                                                General User Release NotesFI                                                               2.7 DECtermo    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.I  *         2.7.1.3 DECterm Resource File Name                 V1.2-4  C               In this release, the locale of the display is used toiD               create the file name of the DECterm resource file. ForH               example, if the locale is set to "ja_JP", then the defaultI               resource file name becomes DECW$TERMINAL_DEFAULT_JA_JP.DAT._  E               However, DECterm continues to use the old resource file G               name until the user selects Save Options at least once in G               the particular locale. The default resource file name for F               DECterm continues to be DECW$TERMINAL_DEFAULT.DAT if the               locale:                  o  Is "C"N  $               o  Starts with "en_US"  "               o  Contains "8859-1"            2.7.1.4 Escape Sequences                 V1.2-3  G               The DECterm application supports all ReGIS input cursors:                  o  Crosshair                 o  Diamond  !               o  Rubber-band linec  &               o  Rubber-band rectangle  G               For a shape other than the diamond cursor when n is equal I               to 1, define the logical name DECW$TERM_REGIS_CURSOR as onedI               of the numbers defined in the SYS$LIBRARY:DECW$CURSOR file.                  V1.2  F               The following escape sequences are supported by DECterm:  I               o  All page movement sequences (NP, PP, PPA, PPB, and PPR).r  B               o  One rectangular area operation sequence (DECCRA).  &               o  The DECLFKC sequence.  I                                                                      2-47m o  e           General User Release Notes     2.7 DECterm     @           o  The ReGIS command S(C(In)) supports the rubber-band5              rectangle cursor and the diamond cursor.a  A           See Section 4.4.1.1, ReGIS Input Cursors for additionale@           information about escape sequences in DECwindows MotifE           software. See Chapter 4 for details and restrictions on thee!           use of these sequences.A  *     2.7.1.5 Scrolling Through the Keyboard             V1.2-3  B           You can scroll through the keyboard by pressing the CtrlC           key and arrow keys or by pressing the Prev or Next key ons           the editing keypad.k  -     2.7.1.6 Reporting the DECterm Window Size              V1.2-3  C           When you enable the Show Feedback option in the WorkspacelA           Options dialog box of the Window Manager and you resizesA           a DECterm window, the size of the window is reported in '           characters instead of pixels.e  !     2.7.1.7 Resizing the Terminalo             V1.2-3  E           If you maximize the DECterm window when you enable the AutonB           Resize Terminal window option, the window is expanded toD           its nearest cell boundary; the window does not necessarilyC           occupy the entire screen. The Restore options continue to !           function appropriately.t  7     2.7.1.8 Timeout for Displaying the Copyright Notice              V1.2-3  B           If keyboard or mouse activity does not take place for 10@           seconds after the copyright notice is displayed on theB           terminal, the notice disappears from the DECterm screen.       2.7.2 Corrections.  A           The following notes describe the resolution of problemsrE           with the DECterm application that previously resulted in an )           error or required a workaround.        2-48 p  f      I                                                General User Release NotesTI                                                               2.7 DECterms    2         2.7.2.1 Can Specify Non-Standard Font Sets                 V1.2-6  E               In the Window Options dialog box, you can now specify anI               subset of the standard font set listed for Big Font, Littleh-               Font, and Standard German Font.i  E               For example, select Little Font and click Other. In theoC               text entry box, replace the standard size and displaytF               options with alternate values from the current font set,               as follows:   (               o  Original specification:  <                  -bitstream-terminal-*-*-*--18-*-*-*-*-*-*-*  (               o  Modified specification:  A                  -bitstream-terminal-*-r-narrow--36-*-*-*-*-*-*-*r  D               For additional information about specifying fonts, seeB               Section 2.7.3.4. For information regarding the fontsD               available on your system, contact your system manager.  D         2.7.2.2 Device Output Files Used by Multiple DECterm Windows!                 Updated Correctlyf                 V1.2-6  B               Redirecting the printer or window output of multipleB               DECterm windows to the same device file now producesI               separate versions of the file-one for each DECterm session.xG               Previously, when performing an OPEN/READ INPUT command on G               this device file, an error occured, and after closing the G               file, only one version was created for all open sessions.e  E         2.7.2.3 Print Operations That Exceed Quota Generate a Warning                  MessageO                 V1.2-6  E               DECterm print operations that exceed the available disk ;               quota now generate following warning message:   8               write to printer failed, write returned -1  I                                                                      2-49  u  i           General User Release Notes     2.7 DECterm     B     2.7.2.4 Button and Menubar Background Colors Set Properly (New             Desktop Only)u             V1.2-6  E           The colors of the DECterm cascade buttons and menubar items A           are now consistent with other desktop applications when C           you use the Style Manager to activate the More Colors fora           Desktop option.k  #     2.7.3 Problems and Restrictionst  =           The following notes describe the known problems ande<           restrictions that currently exist with the DECterm           application.  -     2.7.3.1 Maximum Number of DECterm Windowse             V1.2-4  A           A DECterm controller can create a maximum of 23 DECtermdB           windows. This occurs because DECterm needs an event flagC           for each terminal window to use. There are 23 event flags C           that DECterm can use. (Event flag 0 and event flags 24-32 0           are not available for DECterm to use.)  A           If you need more than 23 DECterm windows, then you must D           create a new controller. To create a new controller, enter            the following command:             $ MCR DECW$TERMINALo  B           Note that the window from which this command is executedD           cannot be used for anything else because this command doesC           not return until the last DECterm window is closed. AfterF@           starting the controller with this method, the user can@           create another 23 DECterm windows with the DCL command           CREATE/TERMINAL.  ,     2.7.3.2 Changing the Auto Repeat Setting             V1.2-3  B           You cannot change the Auto Repeat setting in the DECtermE           Keyboard Options dialog box. Instead, change the setting in 9           the Keyboard dialog box in the Session Manager.,       2-50           I                                                General User Release NotesxI                                                               2.7 DECterma    +         2.7.3.3 Positioning DECterm Windowsi                 V1.2-3  I               If the resource Mwm*clientAutoPlace is set to True, DECtermnE               windows are not displayed where the DECW$TERMINAL.x andDG               DECW$TERMINAL.y resources are specified. As a workaround,,9               set this resource to False and restart MWM.   #         2.7.3.4 User Font Selection                  V1.2  C               DECterm allows you to select available fonts from the I               Options/Window dialog box. A different font can be selectedtF               to replace the default Big Font, default Little Font, or+               default German Standard Font.u  B               In the Options/Window dialog box, you can select theB               default font or enter the name of a font into a textC               field and select that font. When the Big Font, Little E               Font, or German Standard Font is selected and the Other I               toggle button for the font is selected, DECterm attempts to H               locate and use the font name supplied in the adjacent textH               field. For information on font naming conventions or fontsD               available on your system, consult your system manager.  F                 ________________________ Note ________________________  A                 Not all fonts work properly with DECterm. DECterm C                 emulates a character-cell terminal, and, therefore, >                 expects the fonts to be monospaced (each glyphA                 occupies the same number of pixels). Proportional C                 fonts can be chosen, but they produce unpredictable                  results.  C                 Furthermore, DECterm fonts are supplied in familiesfC                 of 26 related fonts, including variations for bold, E                 double-width, double-width/double-height, normal, andrA                 condensed characters. Also, DECterm fonts included@                 special characters, such as the Line Drawing andD                 the DIGITAL Technical character sets. A DECterm fontC                 family is identified by the font naming convention.a  B                 Use of fonts that do not have all the related fontD                 family variations, fonts that do not have the needed@                 special characters, or font families that do notE                 adhere to the DECterm font family naming conventions,g  I                                                                      2-51  h  D           General User Release Notes     2.7 DECterm     >              may not result in an optimal display or otherwise!              perform as expected.e  C              ______________________________________________________   C           On OpenVMS systems, Version 6.1 or higher, the VT330 fonttA           has been made available. The VT330 font is based on theaD           10x20 font used in the VT330 and VT340 terminals. Use thisC           font on a system where they are available by entering theeB           following font-name strings in the font-name text field:  0               -DEC-VT330-*-*-*--20-*-*-*-c-*-*-*       2.7.3.5 Local Echo             V1.2  D           DECterm supports a local echo mode. In the Options/GeneralC           dialog box, select Local Echo, which causes all characterrA           sequences generated locally to be echoed on the displayrD           and passed to the remote host. This feature is useful whenB           connected to a host that does not echo typed characters.       2.7.3.6 Answerback Message             V1.2  E           A user interface is available to enter answerback messages. A           This answerback message field is for compatibility with            Compaq terminals.s  >           The answerback field is a buffer that contains up toC           thirty characters. The answerback field in earlier Compaq B           terminals contained a message used to identify itself toD           the host system. For DECterm windows, the answerback fieldD           can be used to store a sequence of characters that you can)           use for any repetitive purpose..  B           A field is provided in the Options/General dialog box toB           enter answerback text. Click on the answerback field andB           enter your text. To enter control characters, encode theC           control character as a two-digit hex ASCII code, precededr           by a number sign (#).d  B           For example, when you enter #0D in the answerback field,2           DECterm responds with a carriage return.  E           If two consecutive number sign characters are entered (##),u.           a single number sign is transmitted.       2-52    s      I                                                General User Release Notes I                                                               2.7 DECterm     B               If anything other than a valid two-digit hex code orE               another number sign is detected after an initial numberc?               sign, the number sign is treated as a normal textoE               character. Refer to any ASCII table for a complete listy               of characters.  I               The answerback text can also be concealed. When the ConcealIE               Answerback button is enabled, the answerback message is I               concealed. To deselect the Conceal Answerback button, clickeE               on the answerback text field, which erases the previouse!               answerback message.m  )         2.7.3.7 Seven-Bit Printer Supportn                 V1.2  >               When the 7-Bit Printer button is selected in theB               Options/Printer dialog box, DECterm modifies printedE               text to be compatible with printers that do not supportbH               8-bit characters. This includes modifying control sequenceD               introducer (CSI) strings to use the format Escape-LeftA               Bracket rather than the single 8-bit CSI character.   G               When the 8-Bit Printer button is selected, DECterm allowsrF               the use of 8-bit characters when printing. This mode canI               cause problems for older printers if they can not interpretn               8-bit characters.p  #               The default is 8-Bit.h  /         2.7.3.8 Printing to an Attached Printerr                 V1.1  A               Printing to a port device requires you to have readoD               and write privileges on that port. You cannot print byI               allocating the device, since the controller requires access A               to the device. Instead, set the device to WORLD:RW.e  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:r  4               $ SET PROTECTION=WORLD:RW TTA3:/DEVICE  I                                                                      2-53t i  w           General User Release Notes     2.7 DECtermM         2.7.3.9 DECterm Graphics             V1.1  D           The following information is specific to DECterm graphics:  E           o  In some cases, a private colormap is created in DECterm. A              This private colormap is created when ReGIS or Sixel B              graphics are displayed in the window and a sufficientA              number of colors from the default colormap cannot be_B              allocated. The result is that when the DECterm windowA              has input focus, the colormap changes for the entire B              workstation. The default colormap is four colors on aC              four-plane or monochrome system and 16 colors on colorp0              systems with more than four planes.  A              To restore a DECterm window to the default colormap,CA              select Clear Display from the Commands menu to clearsE              the window. Then select Reset Terminal from the Commands (              menu to reset the terminal.  A           o  Only graphics, not text, are written to the graphicssC              backing store. When part of a window has to be redrawn D              in DECterm, the graphics portion of the window is drawn?              first, then the text is overlaid. As a result, theGC              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 andhE              graphics might not always be the same as on the VT330 ort              VT340 terminal.  >           o  The following ReGIS features are not implemented:  $              -  Command Display mode                -  Scrollingc                -  Output cursors  #     2.7.3.10 DECterm Resource Usage              V1.1  B           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 messagei>           indicating that no additional DECterm windows can be           created.       2-54    e      I                                                General User Release Notes I                                                               2.7 DECterm     I               To reduce the memory requirement of each DECterm window andnH               create additional terminal windows, decrease the number ofI               Record Lines Off Top in the Display dialog box and decreaser<               the number of columns for each DECterm window.  H               Once the resource limit is reached, log out of all DECtermD               windows that are running on the host system before you6               increase the number of terminal windows.  3         2.7.3.11 Diagnostic Crash File and Messages                  V1.1  F               DECterm produces a diagnostic file when a status code ofG               fatal is returned. The DECTERM_ERROR.LOG file is produced:A               in the login directory when the DECterm application F               exits abnormally. If you have a problem with the DECtermA               application, submit a copy of this log file to your C               Compaq service representative. However, under certain I               circumstances, a log file is generated even when no problemeH               is encountered. Therefore, the appearance of a log file asI               an isolated event should not be cause for a problem report.t  H               You can enable additional levels of diagnostic messages byG               defining either a logical name or a symbol named DECTERM_tD               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 beoE               generated for each new DECterm created from the Session                Manager.  G               DECterm diagnostics can be captured in a file by defininghG               the logical name DECW$TERMINAL_OUTPUT to point to a file.   3         2.7.3.12 VT330 and VT340 Terminal Emulation                  V1.0  E               DECterm incorporates some of the features of the VT330- G               and VT340-series video terminals, such as ReGIS and SixelxI               graphics. DECterm does not provide complete VT330 and VT340a!               terminal emulation.n  :               The following restrictions apply to DECterm:  I               o  User-loadable characters (DRCS), local mode, and controln?                  representation mode (CRM) are not implemented.   I                                                                      2-55o    m           General User Release Notes     2.7 DECtermo    D           o  The checkerboard character (character 97 in the DIGITAL?              Special Graphic character set) is used as an errori=              character in place of the reverse question mark.f  ?           o  DECterm uses replace mode as the default for SixelrE              drawing on servers with eight planes or less. On servers D              with more than eight planes, DECterm uses overlay mode;=              replace mode is not functional on those servers.   -     2.7.3.13 CREATE/TERMINAL/DETACHED/PROCESS.             V1.0  C           The /PROCESS=procnam qualifier does not work when used inoC           conjunction with the /DETACHED qualifier, unless there is C           already a process running on the system where its processt)           name is equal to the user name.   @           To work around this problem, use the following command           procedure:  !           $! CREATE_TERM_PROC.COMt           $!>           $! Invoke as SPAWN/NOWAIT @CREATE_TERM_PROC procname           $!           $ SET NOON           $!)           $! Set Process name to usernamer           $!K           $ X = F$CONTEXT("PROCESS", PID, "PRCNAM", "''F$PROCESS()'","EQL") <           $ NAME = F$EDIT(F$GETJPI(X,"USERNAME"),"COLLAPSE")&           $ SET PROCESS/NAME="''NAME'"4           $ CREATE/TERMINAL/DETACHED/PROCESS="''P1'"           $!H           $! Allow new process to RUN LOGINOUT before exiting subprocess           $ WAIT 00:00:10   D           If the /PROCESS=procnam qualifier specifies a process nameE           that is already in use, the DECterm is created but creation D           of the process inside the DECterm fails. In this case, theA           DCL command CREATE/TERMINAL returns the following error            message:              Duplicate process name       2-56           I                                                General User Release NotesvI                                                               2.7 DECtermy    %         2.7.3.14 ReGIS Locator Reporto                 V1.0  F               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, DECtermlF               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).                                                                     I                                                                      2-57                 General User Release Notes     2.8 DECW$CDPLAYER          2.8 DECW$CDPLAYERt  C           This section contains information about the DECW$CDPLAYER            application.  #     2.8.1 Problems and Restrictions   =           The following notes describe the known problems andoB           restrictions that currently exist with the DECW$CDPLAYER           application.       2.8.1.1 Required Privileges              V1.1  <           The DECW$CDPLAYER application in the DECW$EXAMPLES>           directory requires PHY_IO and DIAGNOSE privileges to?           operate the compact-disc player hardware. Either your :           process or the image must have these privileges.       2.9 DECwindows Mailn  E           This section contains information about the DECwindows Mailo           application.       2.9.1 Correctionst  A           The following notes describe the resolution of problemsl>           with the DECwindows Mail application that previously8           resulted in an error or required a workaround.  D     2.9.1.1 Can Drag Messages Between Folders While Text is Selected"             in an Alternate Window             V1.2-6  D           You can now drag one or more mail messages between folders?           in DECwindows mail after selecting a range of text in ?           another application window, such as a DECterm window.   B           Previously, this action caused a selection conflict whenD           the user returned to the Mail application and attempted toE           drag the highlighted messages to a new folder. This problemh           has been corrected.        2-58 a         I                                                General User Release Notes I                                                       2.9 DECwindows Mail     F         2.9.1.2 Can Send Multiple Messages from the DECnotes Interface                 V1.2-6  G               You can now send multiple mail messages from the DECnotes G               interface to DECmail. This action no longer results in anh               access violation.   B         2.9.1.3 Can Pick Inbox on Receipt of New Mail (Alpha Only)                 V1.2-6  C               You can use the Pick menu to select messages from the F               Inbox while new messages are being received. This action8               no longer causes the application to crash.  E         2.9.1.4 Window Color Options Displayed Correctly (New Desktopt                 Only)l                 V1.2-6  H               Previously, when attempting to change colors in DECwindowsI               Mail, the five window color options in the lower portion of G               the Window dialog box were unreadable (displayed as blackgI               text on black background). This problem has been corrected; F               all options are now displayed in the appropriate colors.  '         2.9.2 Problems and Restrictionse  =               The following notes describe known problems and.H               restrictions that currently exist with the DECwindows Mail               application.  6         2.9.2.1 Support Removed for Display PostScript                 V1.2-6  I               With the removal of the support for Display PostScript fromtI               the current version of DECwindows Motif, DECWmail no longer C               supports the display of messages that are exclusively D               PostScript code. In previous versions, DECWmail sensedF               the presence of a mail message containing PostScript and=               used Display PostScript to display the message.e  A               Currently, when DECWmail detects a messages that isgD               exclusively PostScript code, it displays the following               error message:  G               [This PostScript message cannot currently be displayed.]   I                                                                      2-59I    h           General User Release Notes     2.9 DECwindows Mail     C           As a workaround, use the Extract option in the File menu,sB           (deselect the "Include Header Information" button in the<           Extract dialog box), and print the extracted file.  6     2.9.2.2 Pasting Messages from the Directory Window             V1.2-4  =           In DECwindows Mail, if the user selects one or more D           messages in the directory window using MB1 and then clicksB           on MB2 in another window (such as a DECterm window), theA           entire contents of the selected messages is pasted intoaD           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.n  )     2.9.2.3 Responses to Keyboard Actions              V1.2-3  C           Enhancements in the DECwindows Mail application to complyaB           more closely with OSF/Motif style conventions cause someA           changes with application responses to keyboard actions.*%           Note the following changes.   D           If you use the Tab key to advance through text entry boxesC           in the Create/Send window, the current field is no longerhA           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 the B           space bar to activate a pushbutton through the keyboard.A           Note that the Return key and the Enter key are bound toaA           other widgets in the dialog box. Alternatively, you canr9           continue to click MB1 to activate a pushbutton.y  ;     2.9.2.4 Using the Color Customizer with DECwindows Mail              V1.2  A           If you use the color customizer sample program providedrC           in the directory DECW$EXAMPLES to control DECwindows Maile@           colors, the DECwindows Mail color customization dialog?           boxes used to modify those colors may not reflect theG@           correct current color values. This is normal behavior;A           use the color customizer instead of the DECwindows Mail B           color customization dialog boxes to change these values.C           Alternatively, exit from the color customizer and restart        2-60 w         I                                                General User Release NoteseI                                                       2.9 DECwindows Mail     G               DECwindows Mail. See Section 2.1.1.2 for more information )               about the color customizer.   6         2.10 Extended File Specification (EFS) Support  E               In general, DECwindows Motif supports the Extended FilefC               Specifications (EFS) option provided in OpenVMS AlphatF               Version 7.2. The interface either supports the new ODS-5I               file names or provides an error message indicating that thefB               particular component does not support the new names.  '         2.10.1 Changes and Enhancementsa  I               The following notes describe those changes and enhancementsaI               made to the DECwindows Motif environment in support of EFS.C  ,         2.10.1.1 File Selection Popup Window                 V1.2-5  C               The standard file selection popup window used by most F               DECwindows Motif applications fully supports ODS-5 styleD               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 name-G               character and displays files using the extended file namenG               character set using the circumflex character (^). See theeF               OpenVMS Guide to Extended File Support for more specificG               information about using deep directories and the extended &               file name character set.  ?         2.10.1.2 FileView Application (DECwindows Desktop Only)a                 V1.2-5  E               With an ODS-5 volume, the FileView application supports F               deep directories, case preservation, and extended-lengthE               file names. FileView supports entry of file names using G               the extended file name character and displays files using G               the extended file name character set using the circumflex C               character (^). See the OpenVMS Guide to Extended File D               Support for more specific information about using deepC               directories and the extended file name character set.   H               Any custom FileView command extensions must be modified to               support EFS.  I                                                                      2-61     2           General User Release Notes2     2.10 Extended File Specification (EFS) Support    8     2.10.1.3 File Manager Application (New Desktop Only)             V1.2-5  E           The File Manager application supports case preservation and B           creates files with the extended file name character set,;           but does not support any operations on its files.t  D           The File Manager application supports deep directories andD           extended-length file names with the following restriction.E           As indicated in the OpenVMS Guide to Extended File Support,sC           ODS-5 volumes allow file names up to 236 8-bit characterso>           in length and deep directory structures if the totalA           file specification does not exceed 512 8-bit characterse<           in length. The current version of the File Manager@           supports extended-length file names and deep directoryA           structures with the additional restriction that a totalrB           file specification cannot exceed 235 8-bit characters inB           length. Exceeding this limit causes an error message for           some menu items.  &     2.10.1.4 The Programming Libraries             V1.2-5  B           The programming libraries fully support deep directoriesC           and extended-length file names. However, the libraries doiA           not support case preservation or the extended file name            character set.       2.10.2 Corrections  @           The following notes describe the resolution of all EFSE           problems that previously resulted in an error or required ae           workaround.   @     2.10.2.1 File Manager Corrections for EFS (New Desktop Only)             V1.2-6  ;           o  The "Selected/Copy to" menu item supports casecD              preservation. The files are copied correctly with their              case preserved.  A           o  The "Selected/Copy to" menu item no longer causes an >              error with file names that exceed 235 characters.  B           o  The "Selected/Change Permissions" menu works on filesC              with file names that exceed 235 characters. Permission.>              can now be changed on files with long file names.       2-62 r  U      I                                                General User Release Notes I                            2.10 Extended File Specification (EFS) SupportC    (         2.10.3 Problems and Restrictions  A               The following notes describe the known problems andn?               restrictions that currently exist with EFS in the +               DECwindows Motif environment..  B         2.10.3.1 File Manager Problems with EFS (New Desktop Only)                 V1.2-5  G               o  The "Selected/Move to" menu item does not support caseeI                  preservation. The files are moved correctly, but case isa                  not preserved.1  A               o  The File Manager currently does not support casedE                  preservation when you create file names that containoG                  special characters. For example, "Special^&Characters" ?                  will be converted to "SPECIAL^&CHARACTERS.;1".D  D               o  The "Selected/Put in Trash" menu item does not work?                  on ODS-5 volumes marked for EFS (Extended FileeC                  Specifications). This applies only to folders withnE                  extended file names. An error message similar to thef(                  following is displayed:  (                  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 involvede"                  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               o  Dragging a file or folder with an extended file name E                  to Trash causes an error message. On an ODS-2 volume1E                  you can drag a file or folder with a short file name3F                  to Trash and still be able to restore it. On an ODS-5G                  volume you can drag a file or folder with a short namenG                  to Trash, but you cannot restore even files with shortnG                  names from an ODS-5 volume. These files can be deletedt"                  at the DCL level.  I                                                                      2-63                 General User Release Notes2     2.10 Extended File Specification (EFS) Support    D           o  The "File/New Folder" menu item can handle the creationE              of a folder when the path length exceeds 255 characters,rE              but the folder cannot be displayed (it is hidden). Theser2              files can be viewed at the DCL level.  C           o  The "File/Find/File" menu item cannot find a file withhC              file name that exceeds 235 characters if the full file A              name has been entered in the dialog's form field. TotD              avoid the problem, use wildcards to conduct the search.  B           o  The "Selected/Purge" menu item does not work for longA              file names on ODS-5 volumes marked for EFS (ExtendedAD              File Specifications). "Short" file names do not present?              this problem. An error similar to the following isu              displayed:o  $              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 involved               files or folders.7              To view permissions, select the object and 9              then select "Change Permissions..." from the $              Selected or popup menu.  D              These files with long file names can still be purged at              the DCL level.I  ?           o  Updated protection settings are not displayed when A              invoking "Fileview/Command/Protection," although the B              settings have actually been updated. However, the newE              settings can be verified by either issuing a DCL command 6              or invoking "Fileview/Command/Show File."  @     2.10.3.2 Translated Image Support (TIS) Library (Alpha Only)             V1.2-5  A           The translated image support (TIS) library has not beens!           updated to support EFS.            2-64           I                                                General User Release Notes I                                                              2.11 Notepado             2.11 Notepad  A               This section contains information about the Notepada               application.  (         2.11.1 Problems and Restrictions  =               The following notes describe known problems and @               restrictions that currently exist with the Notepad               application.  C         2.11.1.1 Notepad Is Linked with the OSF/Motif Release 1.1.3                   Toolkit                 V1.2-3  B               The Notepad application is linked with the OSF/MotifD               Release 1.1.3 Toolkit. Notepad is not modified to linkI               with the OSF/Motif Release 1.2.3 Toolkit, which is providedWI               with the Compaq DECwindows Motif for OpenVMS, Version 1.2-6 8               product. The following restrictions apply:  I               o  OSF/Motif Release 1.2 drag-and-drop functionality is not G                  supported. As a workaround, use the standard clipboard1H                  operations (Cut, Copy, and Paste) to transfer text into                  Notepad.   H               o  OSF/Motif Release 1.2 tear-off menus are not supported.           2.12 Paint  ?               This section contains information about the PaintE               application.  (         2.12.1 Problems and Restrictions  =               The following notes describe known problems andt>               restrictions that currently exist with the Paint               application.  "         2.12.1.1 Private Colormaps                 V1.1  C               If your workstation does not have sufficient colormapeB               entries to view or edit a color image, Paint createsD               a private colormap. When this happens, the Paint imageC               retains its colors, but the colors on the rest of thelF               workstation are modified. To restore the colors to their  I                                                                      2-65c l              General User Release Notes     2.12 Paint    =           original values, give another window input focus byn           clicking on it.   6     2.12.1.2 Slow Performance of Some Paint Operations             V1.0  ;           On GPX systems, Paint might appear slow even when E           performing basic operations such as drawing a brush stroke. E           This is because the pixmap is being swapped into the pixmap C           memory in order to paint the object. If Paint performancelC           is slow, click on the Pencil tool and draw a point in thesC           image area. This should improve performance following the            initial Pencil click.   @           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.t       2.13 Print Screen(  B           This section contains information about the Print Screen           utility.  $     2.13.1 Problems and Restrictions  9           The following notes describe known problems andtA           restrictions that currently exist with the Print Screena           utility.  &     2.13.1.1 PostScript Output Problem             V1.2-5  <           When using the Print Screen application to produce@           PostScript output on some printers, part of the output=           may be lost. Usually, the upper and left portion islC           missing when printing in landscape mode and the lower andCA           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 Version E           1.2-5 for OpenVMS added support for four resources that can /           be specified in DECW$PRINTSCREEN.DAT:        2-66           I                                                General User Release Notes I                                                         2.13 Print Screend    &               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 of C               the image in inches from the origin. The plxscale andoE               plyscale resources are an x and y scale factor to allowFD               the entire image to be displayed on the page after the               origin is moved.  )         2.14 Session Manager and FileView   I               This section contains information about the Session Manager (               and FileView applications.           2.14.1 Corrections  E               The following notes describe the resolution of problems2E               with either the Session Manager or FileView applicationn@               that previously resulted in an error or required a               workaround.a  F         2.14.1.1 Can Create DECterm Windows from the Qualifiers Dialog.                  Box (DECwindows Desktop Only)                 V1.2-6  I               Creating DECterm windows from the DECterm Qualifiers dialog3B               box now creates a single window each time you selectE               the Apply or OK button. Previously, this action createdeC               duplicate instances of the window, which occasionally -               caused Session Manager to fail.   (         2.14.2 Problems and Restrictions  =               The following notes describe known problems andeE               restrictions that currently exist in either the Sessionn/               Manager or FileView applications.         I                                                                      2-67.                General User Release Notes%     2.14 Session Manager and FileView     D     2.14.2.1 Invoking DECchart from the Session Manager Applications              Menua             V1.2-3  9           If you invoke the DECchart application from thea=           Session Manager applications menu, your session can >           fail. As a workaround to this problem, edit the fileC           VUE$LIBRARY:DECCHART$VUE.COM to incorporate the followingo           text:r             $!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_dialogse           $ A           $    if show_hidden_dialogs then goto select_qualifiers $           $       vue$get_qualifiers           $       goto do_chart            $            $select_qualifiers: &           $       vue$popup_qualifiers           $m           $o           $do_chart:           $u$           $ vue$popup_progress_box 8            $ vue$read vue$command           $ @           $ if "''vue$command'" .eqs. "DETACHED_APPLY" then goto           $ select_qualifierso           $            $ 'vue$command           $.7           $ decchart :== $sys$system:decchart$motif.exe "           $ vue$get_next_selection       2-68 i  t      I                                                General User Release Notes H                                        2.14 Session Manager and FileView    "               $ vue$read selection#               $ decchart 'selectiono               $e#               $ vue$check_verb_loop0               $ vue$read loopwE               $ if "''loop'" .eqs. "TRUE" then goto select_qualifierso  H               The only change is to relocate the following line from theA               beginning of the VUE$LIBRARY:DECCHART$VUE.COM file:   (               $ vue$popup_progress_box 8  H               This statement causes the Progress Box to pop up after the'               qualifiers are processed.e  !         2.14.2.2 Security Optionsi                 V1.2  G               In the Session Manager Security Options dialog box, placeaG               the node name within quotation marks if the name containsf#               any of the following:m  E               o  Reserved characters: space, tab, comma (,) or doublen#                  quotation mark (")2  "               o  Double colon (::)  D               o  A colon (:) as the final character in the node name  G               Session Manager automatically adds quotation marks to thepG               node name if they are needed, unless the node name beginsoH               with a double quotation mark. If the node name begins withG               a double quotation mark, Session Manager assumes that theaG               user has already quoted the node name and does not changeV               it.d  G               Within a quoted string, a double quotation mark should bepG               replaced by two double quotation marks (""). For example, I               the quoted string "DEC:.zko."my node"" should be changed to                the following:  '               ("DEC:.zko.""my node""").     I                                                                      2-69  0  t           General User Release Notes%     2.14 Session Manager and FileViewt    <     2.14.2.3 Using the Color Customizer with Session Manager             V1.2  ?           If you are using the color customizer example programeD           provided in the directory DECW$EXAMPLES to control SessionA           Manager colors, the Session Manager color customizationsB           dialog boxes used to modify those colors may not reflectD           the correct current color values. This is normal behavior;A           use the color customizer instead of the Session ManagereB           color customization dialog boxes to change these values.C           Alternatively, exit the color customizer and restart your E           session. See Section 2.1.1.2 for more information about theo           color customizer.   :     2.14.2.4 Input Focus Change When Starting Private Logo             V1.0  E           If you are logging into DECwindows and using a private logocD           command file, input focus might revert unexpectedly to the9           Username field when the private logo starts up.m  /     2.14.2.5 Stopping a Session Manager Process              V1.0  ?           Stopping the Session Manager process can have serious ;           consequences for nonprivileged workstation users.s=           DECwindows must be restarted to avoid the followingi           problems:h  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 onF              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 eacheC              workstation in a batch job that runs during off-hours.n       2-70 d  5      I                                                General User Release Notes H                                        2.14 Session Manager and FileView    I               If you stop the Session Manager process, restart DECwindowslH               (if you have system manager privileges) with the following               command:  1               $ @SYS$MANAGER:DECW$STARTUP RESTART            2.15 Window Managerr  D               This section contains information about the DECwindows#               Motif Window Manager.r  '         2.15.1 Changes and Enhancements   H               The following notes describe changes and enhancements made5               to the DECwindows Motif Window Manager.s  ,         2.15.1.1 DECwindows XUI Applications                 V1.0  E               The resource Mwm*useDECMode allows previous versions of F               DECwindows XUI applications to behave correctly with theH               Motif Window Manager. In particular, this resource is usedF               to control focus, window placement, multiline icons, and?               the window's initial state (normal or minimized).   (         2.15.2 Problems and Restrictions  =               The following notes describe known problems andoI               restrictions that currently exist with the DECwindows Motife               Window Manager.   H         2.15.2.1 Using the Color Customizer with DECwindows Motif Window                  Manager                 V1.2  C               If you are using the color customizer provided in theDE               DECW$EXAMPLES directory to control Motif Window ManagerhC               colors, the Motif Window Manager customization dialogiC               boxes used to modify those colors may not reflect thewD               correct current color values. This is normal behavior;B               use the color customizer instead of the Motif WindowF               Manager color customization dialog boxes to change theseG               values. Alternatively, exit the color customizer and then H               restart Motif Window Manager. See Section 2.1.1.2 for more5               information about the color customizer.r  I                                                                      2-71n S              General User Release Notes     2.15 Window Managero         2.15.2.2 Configuration Fileb             V1.0  @           The configuration file DECW$MWM_RC.DAT defines how the<           Window Manager uses the function keys. Most of theA           accelerators use the form Alt key (or Compose Character 4           key) and function key, for example Alt+F7.  E           If any application needs to use these keys, you must either A           comment them out by placing an exclamation point (!) at E           the beginning of the line, or create new keyboard bindings. C           Then change Mwm*keyBindings:DefaultKeyBindings in the MWM 5           resource file to point to the new bindings.   ;           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 ComposeT@           Character sequences in DECterm. Use Shift+F11 to bring           up the Window menu.e  A           To reenable Alt+space, select the appropriate option in @           the Workspace Options dialog box and apply the currentC           settings. You can also remove the comment for the defaultbD           button bindings for Alt+space in the DECW$MWM_RC.DAT file.  ,     2.15.2.3 Restarting Motif Window Manager             V1.0  C           The file SYS$MANAGER:DECW$MWM.COM is used for information A           on how to restart the Window Manager. By default, it is A           always restarted on all the screens that are available.iB           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.pB           You can modify this file to change the way the window is$           restarted for your system.  ?     2.15.2.4 Customizing Color-Related Resources for Monochromew              Monitorsk             V1.0  8           The Motif Window Manager does not support fullA           customization of color-related resources for monochromeeD           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. Forr       2-72 s  o      I                                                General User Release Notes4I                                                       2.15 Window Manager     G               example, to change the color of the active window's title2H               background, you must change the Mwm*activeBackgroundPixmapI               resource. Some values include 25_foreground, 50_foreground,.4               75_foreground, and unspecified pixmap.  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.   /         2.15.2.5 Moving the Icon Box Off Screen                  V1.0  D               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 untilaH               you reach that window and then press Shift Escape (F11) toI               bring up the Window menu for that window. You can then movea.               the window back onto the screen.  8         2.15.2.6 Customizing Colors on Multihead Systems                 V1.0  I               If you have a multihead system with different monitor types G               (color, monochrome, or gray-scale), you can customize theeI               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 alI               system with that monitor type or directly edit the resource                files.  2         2.15.2.7 Multiline Icon Title Not Centered                 V1.0  C               The Window Manager does not center all the lines of a #               multiline icon title.g              I                                                                      2-73                          I                                                                         3iI         _________________________________________________________________   I                                              System Manager Release NotesN    A               This chapter contains system manager release notes.w  0         3.1 Installation and Upgrade Information  H               This section describes important considerations related toG               the DECwindows Motif installation and upgrade procedures.r  &         3.1.1 Changes and Enhancements  C               The following notes describe changes and enhancementsoC               made to the DECwindows Motif installation and upgrade                procedures.s  4         3.1.1.1 DMA Disabled by Default (Alpha Only)                 V1.2-6  G               In support of the PowerStorm 3D30 or 4D20 (TGA2) graphicskA               cards shipped with most Compaq AlphaServer systems,cD               Direct Memory Access (DMA) is now disabled by default.D               During DECwindows Motif installation, the startup fileI               DECW$DEVICE_CONFIG_GY.COM sets the logical DECW$FFBDODMA to &               a value of 0 (disabled).  D         3.1.1.2 DECW$GETPARAMS.COM Modified to Accept Large GBLPAGES#                 Values (Alpha Only)m                 V1.2-6  I               The procedure DECW$GETPARAMS.COM has been modified to treatoE               large GBLPAGES values (those exceeding the 2 GB pagelet I               limit imposed by SYSGEN) as unsigned longwords. Previously,uC               values that exceeded this limit were parsed as signedtD               comparisons, which prevented DECwindows from starting.    I                                                                       3-1e d  n            System Manager Release Notes,     3.1 Installation and Upgrade Information    +     3.1.1.3 Previously Optional Files Movede             V1.2-4  D           The files listed in Table 3-1 from the optional areas haveC           been moved into the required files areas. These files are #           now installed by default.C  E     Table_3-1_Previously_Optional_Files_Now_Required_________________   E     File_Name_________________________________File_Function__________   A     [SYSHLP.EXAMPLES.DECW]ICO.EXE             Programming examplee3                                               imagee  ?     [SYSHLP.EXAMPLES.DECW.UTILS]BITMAP.EXE    MIT utility images  ?     [SYSHLP.EXAMPLES.DECW.UTILS]ATOBM.EXE     MIT utility image   ?     [SYSHLP.EXAMPLES.DECW.UTILS]BMTOA.EXE     MIT utility imagee  ?     [SYSHLP.EXAMPLES.DECW.UTILS]XDPYINFO.EXE  MIT utility imagee  ?     [SYSHLP.EXAMPLES.DECW.UTILS]XEV.EXE       MIT utility imagec  ?     [SYSHLP.EXAMPLES.DECW.UTILS]XLSATOMS.EXE  MIT utility imaget  ?     [SYSHLP.EXAMPLES.DECW.UTILS]XLSFONTS.EXE  MIT utility image   ?     [SYSHLP.EXAMPLES.DECW.UTILS]XLSWINS.EXE   MIT utility imagei  ?     [SYSHLP.EXAMPLES.DECW.UTILS]XMAG.EXE      MIT utility imageo  ?     [SYSHLP.EXAMPLES.DECW.UTILS]XMBIND.EXE    MIT utility imagei  ?     [SYSHLP.EXAMPLES.DECW.UTILS]XMODMAP.EXE   MIT utility imagen  ?     [SYSHLP.EXAMPLES.DECW.UTILS]XPR.EXE       MIT utility imaget  ?     [SYSHLP.EXAMPLES.DECW.UTILS]XPROP.EXE     MIT utility imaget  ?     [SYSHLP.EXAMPLES.DECW.UTILS]XRDB.EXE      MIT utility imager  ?     [SYSHLP.EXAMPLES.DECW.UTILS]XREFRESH.EXE  MIT utility imagei  ?     [SYSHLP.EXAMPLES.DECW.UTILS]XSET.EXE      MIT utility image   ?     [SYSHLP.EXAMPLES.DECW.UTILS]XSETROOT.EXE  MIT utility image   ?     [SYSHLP.EXAMPLES.DECW.UTILS]XWD.EXE       MIT utility imagew  ?     [SYSHLP.EXAMPLES.DECW.UTILS]XWININFO.EXE  MIT utility imager  E     [SYSHLP.EXAMPLES.DECW.UTILS]XWUD.EXE______MIT_utility_image______w       3-2h c  o      I                                              System Manager Release Notes I                                  3.1 Installation and Upgrade Informationm    G         3.1.1.4 Using Shareable Linkages to Install Images (Alpha Only)n                 V1.2-4  C               On OpenVMS Alpha systems, using shareable linkages to C               install images on Compaq DECwindows Motif for OpenVMSr7               software offers the following advantages:   B               o  Enhanced startup performance by decreasing image-                   activation time  I               o  Conserved memory usage by decreasing the total of memory (                  pages used by the image  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)  E               o  DECW$DXMLIBSHR12.EXE (Compaq Extensions to the Motif                   Toolkit)p  @               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 Motif G               software. As a result, when you restart DECwindows Motif, F               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 be$X               reinstalled. If you are restarting DECwindows to reinstall images then you%               must reboot the system.   F               To replace new images installed with this option, rebootB               the system. Note that you can disable shared-linkageF               sections by defining the logical name DECW$IGNORE_SHARE_A               ADDRESS in the SYSTARTUP_VMS.COM command procedure.   I                                                                       3-3i                 System Manager Release Notes,     3.1 Installation and Upgrade Information    8     3.1.1.5 Version Checking Available for Command Files             V1.0  >           The Compaq DECwindows Motif for OpenVMS kit containsC           version-checking command procedures that layered productsVD           can use during their installation procedure. The followingC           three files are placed in the SYS$UPDATE directory duringoB           the installation of Compaq DECwindows Motif for OpenVMS:  '           o  DECW$GET_IMAGE_VERSION.COM   8              A command procedure that extracts the imageE              identification string from an image and places it into as!              user-defined symbol.   &           o  DECW$COMPARE_VERSIONS.COM  8              A command procedure that compares two imageB              identification strings and assigns a value to a user-8              defined symbol with these possible results:  ,              -  Facility codes do not match.  )              -  Identifiers are the same.p  :              -  Second identifier is older than the first.  :              -  Second identifier is newer then the first.             o  DECW$VERSIONS.COM  =              A command procedure used to display the versions :              of several components of the DECwindows Motif<              layered product and the X11 display server. TheA              DECW$VERSIONS.COM procedure uses the DECW$GET_IMAGE_cE              VERSION.COM command procedure to obtain the image idents C              of each file. Use the following command to display the $              versions on sys$output:                 3-4            I                                              System Manager Release Notes I                                  3.1 Installation and Upgrade Informationt    .                  $ @SYS$UPDATE:DECW$VERSIONS *  I                  ________________________________________________________oI                  Component_____________Description_______________________o  ;                  DECwindows ident      Xlib shareable image   6                  DECwindows server     Server DIX file  7                  DECwindows transport  Transport commonn  ;                  DECwindows Xlib       Xlib shareable imageo  ;                  DECwindows OSF/Motif  OSF/Motif Xm Toolkitu                  Toolkit  :                  DECwindows            DECwindows FileView                  applications   =                  DECwindows            OSF/Motif UIL compiler I                  programming_____________________________________________S  D                  The output from the command procedure shows DW, theC                  version number, and the date the image is created.u                    For example:                      DW V1.2-4960312  D                  is version 1.2-4 and was created on March 12, 1996.  '         3.1.2 Problems and Restrictionst  =               The following notes describe known problems andoI               restrictions that currently exist with the DECwindows Motif /               installation and upgrade process.r  8         3.1.2.1 Check System Parameters Prior to Upgrade                 V1.2-6  A               If you are upgrading to Compaq DECwindows Motif for H               OpenVMS, Version 1.2-6 from a system running Version 1.2-4G               or earlier, be sure to adjust the NPAGEDYN, GBLPAGES, and F               FREE_GBLPAGES system parameters to the following minimum+               values prior to installation:o  I               ___________________________________________________________hI               Parameter________Minimum_Value_____________________________   (               NPAGEDYN         1,998,848  I                                                                       3-5     0            System Manager Release Notes,     3.1 Installation and Upgrade Information  E           ___________________________________________________________eE           Parameter________Minimum_Value_____________________________t  $           GBLPAGES           150,000  E           FREE_GBLPAGES_______20,000_________________________________   >           Otherwise, the installation procedure terminates andC           prompts you to run AUTOGEN to set these parameters to theb           appropriate values.   >     3.1.2.2 Upgrade Problem After Installing Required PCSI ECO             V1.2-5  D           For systems running OpenVMS Alpha Version 7.1-2 or OpenVMSC           VAX Version 7.2 or earlier, you must install a POLYCENTERdB           Software Installation (PCSI) utility ECO (see the CompaqA           DECwindows Motif for OpenVMS Installation Guide). AfterwD           installing the required PCSI utility ECO, your system willC           use the new features provided by this version of the PCSI C           utility. If a layered product is installed that makes use @           of this new functionality, then it may not be possible@           to revert back to an older version of the utility. The@           restriction occurs because there may be records in theA           software product database that the older version of then0           utility will not be able to interpret.  @           This scenario occurs if you install the PCSI ECO, then=           install DECwindows Motif, and later install certainiC           upgrades to the OpenVMS operating system. The steps belowl7           describe the situations when this will occur:i  B           1. Install the PCSI ECO kit onto an OpenVMS Version 6.2,@              6.2-1H1, 6.2-1H2, 6.2-1H3, 7.1, 7.1-1H1, or 7.1-1H2              system.  A           2. Install the DECwindows Motif Version 1.2-6 software.h  D           3. Upgrade to (or reinstall) OpenVMS Version 6.2, 6.2-1H1,8              6.2-1H2, 6.2-1H3, 7.1, 7.1-1H1, or 7.1-1H2.  A           Upgrading to any of the OpenVMS versions listed in itemn@           3 may fail (or other PRODUCT command operations on the>           product database may fail) with one of the following           errors:   1           %SYSTEM-F-ACCVIO, access violation, ...l  J           %PCSI-E-UNSDOCENC, unsupported product document encoding version       3-61           I                                              System Manager Release NotesMI                                  3.1 Installation and Upgrade Informationf    I               To prevent these failures after installing the PCSI ECO ande<               DECwindows Motif, perform the following steps:  E               1. Remove DECwindows Motif using the following command:n  )                  $ PRODUCT REMOVE DWMOTIFe  H               2. Upgrade to (or reinstall) OpenVMS Version 6.2, 6.2-1H1,<                  6.2-1H2, 6.2-1H3, 7.1, 7.1-1H1, or 7.1-1H2.  (               3. Reinstall the PCSI ECO.  ,               4. Reinstall DECwindows Motif.  G               This workaround is not needed if you upgrading to OpenVMS G               Alpha Version 7.2-1 or higher, or if you are upgrading torH               OpenVMS VAX Version 7.2 or higher. These versions (and allI               later versions) already include the new functionality addedi               by the PCSI ECO.  5         3.1.2.3 Reboot Recommended After Installation                  V1.2-4  I               Although system parameters are correct, it may be necessary$I               to reboot the system after installing the Compaq DECwindows )               Motif for OpenVMS software.C  C               If the DECwindows login box does not appear after youdF               install DECwindows Motif and restarting DECwindows MotifE               with the command @SYS$MANAGER:DECW$STARTUP RESTART, yout-               will need to reboot the system.a  I         3.1.2.4 Installation Verification Procedure Error in UIL Compilere                 V1.2-5  D               If you installed a previous version of DECwindows (forF               example, V1.2-4) without using the PCSI_INSTALLATION.COMF               procedure, you might get this error. Enter the followingF               code into a command file and run it. This will check for;               .CLD files. If it finds any, it deletes them:m           $ VAX   = 1i         $ Alpha = 2b&         $ ARCH = F$Getsyi("ARCH_TYPE")
         $!K         $! See if the user wants the New Desktop to be the default desktop.C
         $!7         $ if ARCH .ne. Alpha then goto skip_new_desktop          $ type sys$input  I                                                                       3-7                  System Manager Release Notes,     3.1 Installation and Upgrade Information    L       The New Desktop is a graphical user interface that is derived from theM       Common Desktop Environment (CDE).  It offers the following features note8       available with the traditional DECwindows desktop:  P             o Multiple workspaces for greater flexibility in managing windows on               the screen.d  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 underlying1P       X and Motif libraries and the same DECterm, Bookreader, Mail, and Calendar       applications.d       $ inquire/nopunct answer -H        "Do you want the New Desktop to be your default desktop ([y]/n)?",     $ if answer .eqs. "" then answer = "yes"     $ !fK     $ ! Create the decw$default_desktop.com file on the destination device.a     $ !z)     $ dest = "sys$sysdevice:[vms$common]"t.     $ sysmgr_dir = f$search(dest+"SYSMGR.DIR")0     $ sysmgr_node = f$parse(sysmgr_dir,,,"NODE")4     $ sysmgr_device = f$parse(sysmgr_dir,,,"DEVICE")M     $ sysmgr_directory = f$parse(sysmgr_dir,,,"DIRECTORY") - "]" + ".SYSMGR]"r@     $ dname = sysmgr_node + sysmgr_device + sysmgr_directory + -&             "DECW$DEFAULT_DESKTOP.COM"7     $ if f$search(dname) .nes. "" then delete 'dname';*d-     $ open/write/error=dopenerr dfile 'dname'      $ if answert?     $   then write dfile "$ DECW$START_NEW_DESKTOP == ""TRUE""" @     $   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_desktop_     $dopenerr:     $ write sys$output "" 9     $ write sys$output "  WARNING: Can't create ''dname'"      $ write sys$output ""c     $skip_new_desktop:       3-8s           I                                              System Manager Release NotesrI                                  3.1 Installation and Upgrade Informationf    
         $!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 -l8               /output=SYS$COMMON:[SYSLIB]DCLTABLES.EXE -6               SYS$SYSROOT:[SYSLIB]DECW$UILCOMPILER.CLD         $!$ skip_uil:hW         $ IF f$search("SYS$COMMON:[SYSLIB]ddif$view.cld")  .EQS. "" THEN GOTO skip_view ?         $ SET COMMAND/tables=SYS$COMMON:[SYSLIB]DCLTABLES.EXE -n8               /output=SYS$COMMON:[SYSLIB]DCLTABLES.EXE -.               SYS$COMMON:[SYSLIB]ddif$view.cld
         $!         $skip_view:lV         $ IF f$search("SYS$COMMON:[SYSLIB]pswrap.cld")  .EQS. "" THEN GOTO skip_pswrap?         $ SET COMMAND/tables=SYS$COMMON:[SYSLIB]DCLTABLES.EXE - 8               /output=SYS$COMMON:[SYSLIB]DCLTABLES.EXE -+               SYS$COMMON:[SYSLIB]pswrap.cldo         $skip_pswrap:a
         $!          $! Install the DCLTABLES
         $!         $ set noon,         $ INSTALL LIST SYS$LIBRARY:DCLTABLES         $ status = $status5         $ if status .eq. %X10000001 !%SYSTEM-S-NORMAL          $ thenM         $   INSTALL REPLACE SYS$LIBRARY:DCLTABLES/OPEN/HEADER_RESIDENT/SHARED          $ endif          $ set on  &         3.2 System Startup Information  E               This section describes important considerations related G               to the startup of the Compaq DECwindows Motif for OpenVMSr               software.m              I                                                                       3-9C                 System Manager Release Notes"     3.2 System Startup Information    "     3.2.1 Changes and Enhancements  ?           The following notes describe changes and enhancements ?           made to the DECwindows Motif system startup and login            mechanisms.S  8     3.2.1.1 Starting DECwindows Independently of OpenVMS             V1.2-4  E           If DECwindows is not started during OpenVMS startup, it canCB           be started later by running SYS$MANAGER:DECW$STARTUP.COM=           from a system account. Perform the following steps:S  B           1. Define the logical name DECW$IGNORE_DECWINDOWS with a<              value of TRUE in SYS$STARTUP:SYSTARTUP_VMS.COM.             2. Reboot the system.t  D           3. When system startup has completed, press Return and log+              in to the workstation console.M  ?           4. After logging in, start DECwindows by invoking theMB              SYS$MANAGER:DECW$STARTUP.COM command procedure, as in#              the following example:   (              $ @SYS$MANAGER:DECW$STARTUP  C              ________________________ Note ________________________t  B              Once DECW$STARTUP.COM has completed, you must log out=              of the console in order for DECwindows to start.   C              ______________________________________________________l  #     3.2.2 Problems and Restrictions.  9           The following notes describe known problems andSC           restrictions that exist with the current DECwindows MotifD.           system startup and login mechanisms.  @     3.2.2.1 Problem With Delayed DECwindows Startup (Alpha Only)             V1.2-4  C           On OpenVMS Alpha systems, error messages similar to thosee2           shown in Example 3-1 are displayed when:  A           o  Shareable address linkage is being used (the defaultl              setting).       3-10 y         I                                              System Manager Release Notes I                                            3.2 System Startup Informationp    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 canyI               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 duringrH               system startup and releases the unused memory once startupI               has completed. Starting with DECwindows Motif Version 1.2-4bE               for OpenVMS DECwindows Motif takes advantage of this bysE               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 started 9               during system startup, as it is by default.   A         Example 3-1 Error Messages Displayed Due to Low Memory in ,                     Granularity Hints Region  W         %INSTALL-I-FAIL, failed to create shared linkage entry for DISK$ALPHASYS:<SYS0.aX          -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint re  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  E         %RUN-S-PROC_ID, identification of created process is 00000092   E         %RUN-S-PROC_ID, identification of created process is 00000093   W         %INSTALL-I-FAIL, failed to create shared linkage entry for DISK$ALPHASYS:<SYS0. X          -INSTALL-E-NOGHREG, insufficient memory in the code or data granularity hint re  I                                                  (continued on next page)   I                                                                      3-11r t  i            System Manager Release Notes"     3.2 System Startup Information    E     Example 3-1 (Cont.) Error Messages Displayed Due to Low Memory ina0                         Granularity Hints Region  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 completionr0      -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. 8      -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. 8      -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. 8      -SYSTEM-F-VA_IN_USE, virtual address already in use3      -SYSTEM-S-NORMAL, normal successful completiont0      -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. 8      -SYSTEM-F-VA_IN_USE, virtual address already in use3      -SYSTEM-S-NORMAL, normal successful completioni0      -DEBUG-W-NOIOCHAN, no I/O channel available  E                                              (continued on next page)        3-12    2      I                                              System Manager Release Notes I                                            3.2 System Startup Information     I         Example 3-1 (Cont.) Error Messages Displayed Due to Low Memory inR4                             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  8         3.2.2.2 Color Problem in DECwindows Login Screen                 V1.2  C               A problem may occur on systems that have a customized B               DECW$LOGIN.DAT file. The Start Session dialog box isF               the color blue instead of tan. If this condition exists,H               look for a customized DECW$LOGIN.DAT file in the directoryI               SYS$COMMON:[DECW$DEFAULTS.USER] and move it to SYS$MANAGER.GF               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 customized F               versions of this file should reside only in SYS$MANAGER.  5         3.3 System and Environment Tuning Informationt  H               This section describes important considerations related to4               the tuning of DECwindows Motif system.  &         3.3.1 Changes and Enhancements  H               The following notes describe changes and enhancements madeD               to the DECwindows Motif system tuning recommendations.  I         3.3.1.1 Displaying an Expanded Welcome Message (New Desktop Only)o                 V1.2-6  D               You can now enter a longer, customized welcome messageB               to be displayed on the Login Screen. The size of theF               welcome message string (Dtlogin*greeting.labelString) inI               XRESOURCES.DAT has been expanded allowing you to enter more #               than 8 lines of text.e  D               Note that the actual number of lines you can enter andB               display is limited by the size of the screen and theF               selected font. However, a minimum of 25 lines is allowed&               on most display devices.  I                                                                      3-13t D  i            System Manager Release Notes1     3.3 System and Environment Tuning Informationi    D     3.3.1.2 Setting the File Manager Refresh Rate (New Desktop Only)             V1.2-6  @           You can now specify that the File Manager periodicallyD           update its view by adjusting the Dtfile.rereadTime settingD           in the DTFILE.DAT resource file. The value of this settingE           represents the seconds elapsed between checking for changesDD           in the viewed directories. Note that this setting does not)           work when viewing search lists.   -     3.3.1.3 System Tuning for Non-VGA Devices              V1.2  <           The DECwindows server requires specific tuning forC           graphics-intensive and 3D applications because of greater C           demand for system resources. You need to make adjustments @           for server quotas on 3D accelerated systems. These areD           minimum values suggested for a system with as little as 64@           MB of physical memory and for running complex clients.  ?           Use the AUTHORIZE utility to set the following SYSTEMsB           account quotas to the minimum values shown in Table 3-2.  E           Table_3-2_Recommended_Quotas_for_System_Tuning_____________   E           Parameter______Value_______________________________________r             FILLM          400             ENQLM          1024              WSDEF          10240             WSQUO          16384             WSEXTENT[1]    20480             PGFLQUO[2]     270000e
           [3]dE           [1]This_value_cannot_exceed_WSMAX._________________________s  >           [2]PAGEFILE.SYS must be of the same or greater size.9           [3]Use for 370000 for ZLX-E and ZLXp-E systems. E           ___________________________________________________________C  7           The server has its own quotas that are set in ;           SYS$COMMON:[SYSMGR]DECW$PRIVATE_SERVER_SETUP.COM. 4           If this file does not exist, copy the file;           SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE to        3-14 .  n      I                                              System Manager Release Notes I                             3.3 System and Environment Tuning Information     D               SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM and edit the3               file to include the following values:e  I               ___________________________________________________________kI               Quota______________________Value___________________________   ,               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]   270000 I               [1]Use_for_370000_for_ZLX-E_and_ZLXp-E_systems.____________R  I               ___________________________________________________________   @               If you use larger values, you must also modify theG               corresponding SYSTEM account quotas that you set with thee                AUTHORIZE utility.  /               Tuning for Animation Applicationsw  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_______________________________________   "               WSDEF          10240  "               WSQUO          20480  I               WSEXTENT_______32768_______________________________________d  I               You need to set the corresponding server quotas as follows:k  I               ___________________________________________________________wI               Quota______________________Value___________________________)  .               DECW$SERVER_WSDEF          10240  .               DECW$SERVER_WSQUOTA        20480  I               DECW$SERVER_WSEXTENT_______32768___________________________v  F                 ________________________ Note ________________________  D                 The parameters should not be tuned upward unless you8                 have at least 128 MB of physical memory.  F                 ______________________________________________________  I                                                                      3-15  f  s            System Manager Release Notes1     3.3 System and Environment Tuning Information       "           Determining Tuning Needs  A           To determine whether you need to set larger parameters,"@           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 VIRTUALPAGECNTt?           command to determine the current virtual page count ahE           process is allowed to have. If it is less than 525000, editsA           the SYS$SYSTEM:MODPARAMS.DAT file and add the following            line:i  (              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-R@           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 thelB           OpenVMS System Manager's Manual for more information. DoE           not exceed what AUTOGEN gives for WSMAX. See the warning inC           the AUTOGEN report.o  B           The next time you run AUTOGEN and reboot, the new valuesB           will take effect. VIRTUALPAGECNT should not be less thanD           the sum of your WSEXTENT and PGFLQUO, or the server cannot?           make full use of the quotas. In addition, you need to ?           increase the size of the page file to accommodate the C           pagefile quotas of both the server and your clients. NoteAC           that pagefile quota for the server is derived from systemp           page files.   C           If, after initial tuning and considerable use, the server A           is failing or is unnecessarily unresponsive, the server >           may have run out of memory or memory may have become>           fragmented. A particularly demanding application mayB           require that you give the server even larger PGFLQUO and            VIRTUALPAGECNT values.       3-16           I                                              System Manager Release NoteswI                             3.3 System and Environment Tuning Information.    I               If the server error log SYS$MANAGER:DECW$SERVER_0_ERROR.LOG E               contains the statement xxx: Out of memory, increase the G               pagefile quota for the server. Set this by modifying bothaH               system quota PGFLQUO and DECW$PRIVATE_SERVER_SETUP.COM and?               virtual page count via MODPARAMS.DAT and AUTOGEN.   D               Note that, in multiheaded configurations (for example,G               ZLX-E1 and ZLX-E2), the PGFLQUO and the DECW$SERVER_PAGE_gE               FILE parameters should be increased to meet your systemg               requirements.i  I         3.3.1.4 Define DECW$UTILS Global Symbol When Moving DECW$EXAMPLES                  Global Symbole                 V1.2  C               DECwindows Motif Version 1.2 for OpenVMS introduced a B               new symbol, DECW$UTILS. Normally, this symbol pointsA               to a subdirectory of DECW$EXAMPLES. If you define adC               DECW$EXAMPLES global symbol in the DECW$PRIVATE_APPS__A               SETUP.COM command procedure to change the directorynC               for DECwindows example programs, you must also define ?               DECW$UTILS to change the directory for utilities.   I               For example, to redefine both DECW$EXAMPLES and DECW$UTILS,lF               add the following lines to the SYS$MANAGER:DECW$PRIVATE_'               APPS_SETUP.COM procedure:m  <               $ DECW$EXAMPLES == "SYS$SYSROOT:[DECWEXAMPLES]?               $ DECW$UTILS == "SYS$SYSROOT:[DECWEXAMPLES.UTILS]e  F                 ________________________ Note ________________________  >                 If the SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM7                 file does not exist, create it from thenB                 SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.TEMPLATE file.  F                 ______________________________________________________  H               Then, restart DECwindows Motif with the following command:  0               $@SYS$MANAGER:DECW$STARTUP RESTART      I                                                                      3-17     h            System Manager Release Notes1     3.3 System and Environment Tuning Informatione    (     3.3.1.5 Customizing the Login Screen             V1.2  <           To customize the login screen, create a file named:           DECW$LOGIN.DAT in the SYS$MANAGER directory thatA           contains your resource definitions. The custom resourceo@           definitions from SYS$MANAGER:DECW$LOGIN.DAT are merged=           with the resource definitions supplied by Compaq in A           SYS$COMMON:[DECW$DEFAULTS.SYSTEM]DECW$LOGIN.DAT to form            the new login screen.s  A           Keep customized versions of the DECW$LOGIN.DAT resource D           file in the SYS$MANAGER directory, and not in DECW$SYSTEM_>           DEFAULTS, to prevent your customized file from being@           overwritten when upgraded to a newer version of CompaqE           DECwindows Motif for OpenVMS software. In addition, storingsC           the file in the SYS$MANAGER directory prevents the customeD           file from superseding the file that is supplied by Compaq.  @           3.3.1.5.1 Customizing the Compaq Logo and Login Screen?           Colors   You can define the resources in Table 3-3 tog@           control the position and colors of the Compaq logo andA           the color of the screen background in the Start Sessiond           screen.i  D           Table 3-3 Moving the Compaq Logo and Changing Login ScreenE           __________Colors___________________________________________   E           Resource__________Description______________________________a  ;           rootColor         Color of the screen background.r  @           logoColor         Color of the Compaq logo (default is&                             burgundy).  E           logoX             x position of the Compaq logo (default isr                             0).N  E           logoY             y position of the Compaq logo (default isS                              75).  B           centerLogoX       Boolean; if true (default), the Compaq@                             logo is centered horizontally on theE           __________________screen.__________________________________e  <           For example, to position the Compaq logo at x=100,>           y=600, add the following resource definitions to the*           SYS$MANAGER:DECW$LOGIN.DAT file:       3-18 C  .      I                                              System Manager Release NotesrI                             3.3 System and Environment Tuning Informationh    #               decw$login.logoX: 100-#               decw$login.logoY: 600o+               decw$login.centerLogoX: falseL  G               3.3.1.5.2 Changing Positions of the Start Session and Set D               Password Dialog Boxes  You can define the resources inH               Table 3-4 to control the position of the Start Session and(               Set Password dialog boxes.  F               Table 3-4 Changing Position of the Start Session and SetI               __________Password_Dialog_Boxes____________________________I  I               Resource______________Description__________________________-  C               centerStartSessionX   Boolean; if true (default), theAH                                     Start Session dialog box is centered1                                     horizontally.n  C               centerStartSessionY   Boolean; if true (default), thefH                                     Start Session dialog box is centered/                                     vertically.S  C               centerSetPasswordX    Boolean; if true (default), thenG                                     Set Password dialog box for expired-G                                     passwords is centered horizontally.a  C               centerSetPasswordY    Boolean; if true (default), theiG                                     Set Password dialog box is centeredLI               ______________________vertically.__________________________   F               For example, to position the Start Session dialog box atI               x=100, y=600, add the following resource definitions to thea.               SYS$MANAGER:DECW$LOGIN.DAT file:  3               decw$login.centerStartSessionX: falseT3               decw$login.centerStartSessionY: falsea+               decw$login.HiddenShell.x: 100f+               decw$login.HiddenShell.y: 600$  >               To position the Set Password dialog box at x=30,B               y=100, add the following resource definitions to the.               SYS$MANAGER:DECW$LOGIN.DAT file:  2               decw$login.centerSetPasswordX: false2               decw$login.centerSetPasswordY: false/               decw$login.SetPasswordShell.x: 30e0               decw$login.SetPasswordShell.y: 100  I                                                                      3-19r    s            System Manager Release Notes1     3.3 System and Environment Tuning Information     8           3.3.1.5.3 Disabling a Node Name Display in the;           Start Session Dialog Box   To prevent a node namei:           from being displayed in the Start Session dialog;           box, add the following resource definition to the *           SYS$MANAGER:DECW$LOGIN.DAT file:  +           decw$login.displayNodeName: false   -     3.3.1.6 Displaying Customized Login Logosa             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 Motif A           license for SYSTEM, add the following definition to the 7           SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM file:.  '           $ DECW$LOGINLOGOSUB == "TRUE"   C              ________________________ Note ________________________E  >              If the file does not exist, copy it from the file:              SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.TEMPLATE.  C              ______________________________________________________m  @           After editing the setup file, restart DECwindows Motif&           using the following command:  -           $ @SYS$MANAGER:DECW$STARTUP RESTART   =           DECwindows Motif login starts the logo process as anB           subprocess instead of as a detached process. The licenseB           check sees that the logo process is a child of the login6           process and that the X connection is opened.  #     3.3.2 Problems and Restrictionst  =           The following notes describe the known problems and ;           restrictions that currently exist with tuning and 7           customizing the DECwindows Motif environment.e       3-20           I                                              System Manager Release NotesfI                             3.3 System and Environment Tuning Informationa    5         3.3.2.1 System Hangs With Some Graphics Cards                  V1.2-5  H               On systems with Powerstorm 4d20 or ZLXp-E2 graphics cards,H               the operating system may hang or become extremely sluggishD               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 ErrorseD               utility in the Desktop Tools drawer of the ApplicationE               Manager. If the system hang is due to this problem, yout%               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:ss   B               At the present time, there is no workaround for thisD               problem other than using fewer windows (increasing theI               MAXBOBMEM value doesn't fix the problem). If you experienceoI               this problem, you may want to keep a DECterm window free soeG               that you can perform a graceful system reboot. Otherwise,i5               you will need to perform a hard reboot.f  8         3.3.2.2 Performance Problem with Certain Keymaps                 V1.2-5  E               There is a performance problem when using the Austrian- E               German keymap (AUSTRIAN_GERMAN_LK401AG_TW). The problem I               can also occur with other keyboard and/or language changes,0I               when the user selects a sequence of keyboard maps/languages_C               which force the Mode_switch modifier into the mod4 oreC               mod5 entry in the keyboard modifier map. This happens A               in response to the user selecting a keyboard map in_D               the "Keyboard Options" popup that uses the Mode_switch               modifier.D  G               To verify the position of the Mode_switch modifier in the @               keyboard modifier map, use the following commands:  3               $ XMODMAP :== $DECW$UTILS:XMODMAP.EXE                $ XMODMAPeM               xmodmap:  up to 3 keys per modifier, (keycodes in parentheses):t  I                                                                      3-21.                 System Manager Release Notes1     3.3 System and Environment Tuning Information_    5           shift       Shift_R (0xab),  Shift_L (0xae) &           lock        Caps_Lock (0xb0)&           control     Control_L (0xaf)1           mod1        Alt_L (0xac),  Alt_R (0xb2)E(           mod2        Mode_switch (0xb1)&           mod3        Multi_key (0xad)(           mod4        Mode_switch (0x7a)!           mod5        Help (0x7c)_  6           As a workaround, change the modifier mapping7           after selecting the keyboard map by using the_)           DECW$UTILS:XMODMAP.EXE utility.   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 mod2o              clear mod3i              clear mod4               clear mod5e(              add shift = Shift_R Shift_L!              add lock = Caps_Locko$              add control = Control_L#              add mod1 = Alt_R Alt_L_!              add mod2 = Multi_key #              add mod3 = Mode_switch_              add mod5 = Help  C           2. Pass the file to XMODMAP using the following commands:   2              $ XMODMAP :== $DECW$UTILS:XMODMAP.EXE$              $ XMODMAP XMODMAPRC.DAT       3.4 Console Window  D           This section contains information about the Console Window           application.           3-22 _  _      I                                              System Manager Release Notes I                                                        3.4 Console Window_    &         3.4.1 Changes and Enhancements  H               The following notes describe changes and enhancements made0               to the Console Window application.  +         3.4.1.1 Displaying Console Messages                  V1.2-3  C               DECwindows Motif Version 1.2-3 for OpenVMS introduced G               the feature of displaying console messages in the Console G               Window application. Previous versions of DECwindows Motifs6               displayed the console window by default.  F                 ________________________ Note ________________________  ?                 The new default for displaying console messageseD                 starting with the DECwindows Motif Version 1.2-3 forC                 OpenVMS release is DISABLE. The default in previous E                 versions of DECwindows Motif was ENABLE. These values F                 are discussed in greater detail later in this section.B                 If the user selects the Alternate Console port forE                 console communications, the DECwindows Console WindowaC                 is disabled and the console broadcasts are enabled.EC                 Refer to the owner's guide for your workstation forhA                 information about selecting the Alternate Consolee                 port.$  F                 ______________________________________________________  D               Specify how to display messages by defining the globalE               symbol DECW$CONSOLE_SELECTION in the customized startup5H               file SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM. Enter one of?               the following values: WINDOW, DISABLE, or ENABLE.t                 o  WINDOW   @                  Displays console messages in the Console WindowE                  application. This is a new application starting with I                  the DECwindows Motif Version 1.2-3 for OpenVMS software.nG                  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                                                                      3-23e a  t            System Manager Release Notes     3.4 Console Window    ;              The Console Window application shares the samehE              executable file and looks similar to the Message Window.A@              However, a menu bar is not displayed in the ConsoleE              Window; it reads its resources from the DECW$CONSOLE.DATcA              file instead of from the DECW$MESSAGEPANEL.DAT file.iE              Internally, the Console Window is invoked by running theeC              DECW$MESSAGEPANEL.EXE executable with the command linea              option -console.r  B              To control the initial position of the Console WindowB              and the classes of OPCOM output that are enabled, youC              can the define the following global symbol in the file 5              SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM:   %                 DECW$CONSOLE_GEOMETRY   @                 This symbol specifies the value of the -geometryA                 option in the DECW$MESSAGEPANEL.EXE command line;o@                 this command is used to start the Console Window?                 application. The default value is "-0-0", which A                 specifies the location of the window in the lower +                 right corner of the screen.(  B                 To position the window at the lower left corner of?                 the screen, for example, add the following lineeB                 to the command file SYS$MANAGER:DECW$PRIVATE_APPS_                 SETUP.COM:  2                  $ DECW$CONSOLE_GEOMETRY == "+0-0"             o  DISABLE (default)  =              Disables broadcasts to the OPA0: device. Consoleu(              messages are not displayed.             o  ENABLEo  A              Displays console messages in the console window. ThefD              console window is a six-line display area at the top of$              the workstation screen.  C              ________________________ Note ________________________p  >              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       3-24 O  D      I                                              System Manager Release Notes I                                                        3.4 Console Window     B                 window can corrupt the contents of the workstation                 display.  F                 ______________________________________________________  D               Refer to Managing DECwindows Motif for OpenVMS SystemsG               for information about defining global symbols in the file 6               SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM.           3.5 DECterm   D               This section contains information about DECterm system                management issues.  &         3.5.1 Changes and Enhancements  H               The following notes describe changes and enhancements that?               effect the management of the DECterm application.   /         3.5.1.1 Supported DECterm Logical NamesA                 V1.1  I               Table 3-5 describes the logical names that are supported byeG               DECterm. If you do not define these logical names in yourrD               LOGIN.COM file, the controller uses the default files.  I         Table_3-5_Logical_Names_Supported_by_DECterm_____________________   I         Logical_Name______________________Description____________________   F         DECTERM_DIAG                      Enables diagnostic messages.  F         DECTERM_SHOW_PARSING              Shows characters as they are1                                           parsed.   I         DECTERM_CHECK_MEMORY              Enables strict memory checking.i  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; defaultd?                                           is DECTERM_ERROR.LOG.i  I         DECW$DECTERM_OUTPUT               Name of diagnostic output file;r@                                           default is SYS$OUTPUT.  I         +VAX_specific____________________________________________________o  I                                                  (continued on next page)_  I                                                                      3-25o f  e            System Manager Release Notes     3.5 DECterm     E     Table_3-5_(Cont.)_Logical_Names_Supported_by_DECterm_____________   E     Logical_Name______________________Description____________________   C     DECW$DECTERM_REGIS_CURSOR         Specifies which cursor to useo0                                       for ReGIS.  E     DECW$TERMINAL_NODENAME            Node name used by controller if B                                       it cannot find another name.  C     DECW$DECTERM_CTRL_SSRWAIT         Sets the SSRWAIT flag for the_1                                       controller.C  C     DECW$DECTERM_CTRL_PSWAPM          Sets the PSWAPM quota for thei1                                       controller.f  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.n  ?     DECW$DECTERM_DISABLE_QUOTA_       Turns off quota checking.      CHECKING  <     DECW$DECTERM_MEM_DIAG             Shows controller quotaE     __________________________________calculations.__________________   (     3.5.1.2 Automatic Window Positioning             V1.1  ?           A resource has been defined to manage repositioning a C           DECterm window when a resize operation forces part of the_C           window off the screen. If a DECterm window is enlarged by B           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 thatrA           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:r  =           DECW$TERMINAL.main.terminal.autoAdjustPosition: off          3-26           I                                              System Manager Release Notes I                                                               3.5 DECterm     3         3.5.1.3 Improving Hold Screen Response Time                  V1.1  G               If the hold screen key response time is too slow, add the E               following lines to your DECW$TERMINAL_DEFAULT.DAT file:_  :               DECW$TERMINAL.main.terminal.syncFrequency: 1=               DECW$TERMINAL.main.terminal.batchScrollCount: 1   C               Using this resource can affect the performance of thehE               DECterm window. The actual impact on performance varieswE               from site to site. You can trade off scrolling speed totF               hold-screen response time. A faster hold-screen responseI               results in a slower scrolling speed. The default values fora9               these resources are 10 and 0, respectively.l  "         3.5.1.4 Using the Debugger                 V1.0  C               To redirect the output from the debugger to a DECtermf2               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 the H               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 ther!               following commands:s  +               $ DEFINE /USER DBG$INPUT xxx:s,               $ DEFINE /USER DBG$OUTPUT xxx:*               $ RUN /DEBUG application.EXE  (         3.5.1.5 Virtual Terminal Support                 V1.0  I               To create a process that uses a virtual terminal, enter thew                following command:  )               $ CREATE/TERMINAL/NOPROCESSn  F               Then establish focus to the newly created DECterm, pressH               Return, and log in. Note that the /DEFINE qualifier is not               required.e  I                                                                      3-27s i               System Manager Release Notes     3.5 DECtermY    #     3.5.2 Problems and Restrictions   9           The following notes describe known problems and B           restrictions that currently effect the management of the           DECterm application.  ,     3.5.2.1 DECterm Window Shrinking Problem             V1.2-5  E           If the XUI window manager is in use, "Auto Resize Terminal" E           is on, and you used the mouse to resize the DECterm window, A           the DECterm window shrinks. To workaround this problem, =           add the following line to the DECterm resource fileR$           DECW$TERMINAL_DEFAULT.DAT:  7           DECW$TERMINAL.main.terminal.useWMHints: false   C           If you make this change, be aware that the window managerhE           will report the size of the DECterm window in pixels rathers?           than character cells. Also, if you maximize a DECtermRE           window, it might not properly restore to its previous size.m,           However, it will no longer shrink.  $     3.6 Session Manager and FileView  D           This section describes important considerations related to8           the Session Manager and FileView applications.  "     3.6.1 Changes and Enhancements  D           The following notes describe changes and enhancements thatC           effect the management of the Session Manager and FileView            applications.   A     3.6.1.1 Implications of the Message, "System Menu Bar: Pseudon              Mouse Not Available"             V1.2-3  =           "System Menu Bar: Pseudo Mouse not available" is an >           informational message that is included in the user'sE           DECW$USER_DEFAULTS:DECW$SM.LOG file when you run a session.hA           It is not an error message. The message occurs when theAB           OpenVMS Session Manager is run remotely to a non-OpenVMSA           server. The OpenVMS server provides pseudomouse mode, a B           mode that allows you to use arrow keys to move the mouse           cursor.x       3-28 d  u      I                                              System Manager Release Notes(I                                          3.6 Session Manager and FileView     5         3.6.1.2 Detached Processes Created by Default                  V1.1  F               Applications created by FileView and Session Manager are!               detached processes.   A               The implication is that during application startup,aE               SYS$MANAGER:SYLOGIN.COM and SYS$LOGIN:LOGIN.COM command D               procedures are executed. Any command executed by theseF               command procedures which reads from SYS$INPUT reads dataD               intended to be used by FileView or Session Manager forD               the application startup. This prevents the applicationC               from starting. Examples of such commands are INQUIRE,e4               READ/PROMPT, and SET TERMINAL/INQUIRE.  C               Extensive SYLOGIN.COM or LOGIN.COM command procedures C               slow down application startup. Many of the operations E               performed in a SYLOGIN.COM or LOGIN.COM are meaningless @               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 thedH               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.COM H               and LOGIN.COM immediately following the commands necessary               for DECwindows:2                 $ mode = f$mode()c+               $ tt_devname = f$trnlnm("TT")aG               $ session_mgr_login = (mode .eqs. "INTERACTIVE") .and.  -(G                     (f$locate("WSA",tt_devname) .ne. f$len(tt_devname)) M               $ session_detached_process = (mode .eqs. "INTERACTIVE") .and. -EG                     (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.r      I                                                                      3-29                  System Manager Release Notes$     3.6 Session Manager and FileView    #     3.6.2 Problems and Restrictionso  9           The following notes describe known problems and B           restrictions that currently effect the management of the&           Session Manager application.  8     3.6.2.1 DTSESSION Logging Problem (New Desktop Only)             V1.2-5  =           In some cases, DTSESSION continues to log errors to ;           its log file until all free disk space is filled. @           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.e  D           If the New Desktop's Session Manager (DTSESSION) is unableC           to start the Screen Saver (DTSCREEN), it logs an error tohD           the log file device:[user.DT]ERRORLOG. DTSESSION logs thisC           error at a user-settable interval controlled by the Stylen4           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 thani           locking the screen.        3.7 Window Manager  @           This section contains information about Window Manager#           system management issues.a  "     3.7.1 Changes and Enhancements  ?           The following notes describe changes and enhancementsrC           that effect the management of the DECwindows Motif Window            Manager application.       3.7.1.1 Overlay Supporte             V1.2-3  ;           The latest version of the Window Manager (MWM) is =           modified to support overlays and utilize additionalrC           planes of memory, which are available on some 3D graphicsoE           accelerators. The Window Manager places borders and bannersE?           for all the windows into these extra planes of memory B           and thereby reduces the number of expose events for your)           applications that use overlays.        3-30 _  _      I                                              System Manager Release NotessI                                                        3.7 Window Managern    H               You may need to modify your existing applications that useE               overlays to avoid potential problems with the colormap.LH               Compaq recommends that you set up your system to share theG               overlay colormap with the Window Manager, as the hardwarei@               supports only one colormap for the overlay planes.  B               See the associated documentation for your 3D graphicA               accelerator to determine if overlays are supported.d  -               Setting Up the Overlay Colormapc  G               To modify your applications to share the overlay colormapsE               with the Window Manager, query the server property name D               SERVER_OVERLAY_COLORMAPS. When you make the query, theF               server returns the 32-bit value for the overlay Colormap               ID.p  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:A  !                $ mwm -multiscreenl  G               Edit this line by adding the -Overlay command-line optionP               as follows:e  ,                $ 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.e  I               o  Border and banner colors also change when you change the )                  colors of your colormap.                  Restrictions  I               The following restrictions apply when you enable the Windowm&               Manager to use overlays:  G               o  The Window Manager supports only single-screen systemsuG                  and does not function correctly with multiple graphics %                  devices (multihead).i  H               o  If you select a Matte Size value other than "None" fromE                  the Window Manager options list, the Matte color mayfF                  not be correct; that is, the color does not match the;                  selection and is occasionally transparent.D  I                                                                      3-31  D  b            System Manager Release Notes     3.7 Window Manager    A           o  If you select "Show feedback when moving or resizing A              windows" from the Workspace Options menu, the windoww@              with the feedback information causes expose events.  @           o  When you move windows by showing the outline of the?              window, the outline appears to go below the windowf!              borders and banners.   C           o  Window borders are occasionally and randomly displayed B              in clear or black. If this problem occurs, select theB              restart option from the Workspace menu to restart the              Window Manager.                                                                       3-32 S  e                    I                                                                         4nI         _________________________________________________________________n  I                                                  Programmer Release Notes_    =               This chapter contains programmer release notes.s  %         4.1 OSF/Motif Toolkit Support                  V1.2-6  D               The Compaq DECwindows Motif for OpenVMS, Version 1.2-6F               release is based on the CDE Motif 1.0 Toolkit (OSF/Motif/               Release 1.2.5) and X11 Release 5.                  V1.2-5  D               The DECwindows Motif Version 1.2-5 for OpenVMS releaseF               is based on the CDE Motif 1.0 Toolkit (OSF/Motif Release'               1.2.5) and X11 Release 5.                  V1.2-4  D               The DECwindows Motif Version 1.2-4 for OpenVMS releaseG               was based on the CDE Motif 1.0 Toolkit (OSF/Motif ReleaseE'               1.2.5) and X11 Release 5.                  V1.2-3  D               The DECwindows Motif Version 1.2-3 for OpenVMS releaseD               was based on the OSF/Motif Release 1.2.3 Toolkit (withF               extensions for the Common Desktop Environment (CDE)) and!               X11 Release 5 (R5).                  V1.2  F               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).                  V1.1  F               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).D  I                                                                       4-1                 Programmer Release Notes!     4.1 OSF/Motif Toolkit SupportT               V1.0  B           The DECwindows Motif Version 1.0 for OpenVMS release wasB           based on the OSF/Motif Release 1.1.1 Toolkit and MIT X11           Release 4 (R4)._  9           Note that although DECwindows Motif Version 1.1(E           applications will continue to run without modification with E           current version of DECwindows Motif for OpenVMS, only thoseeA           applications that have been built against the OSF/MotifuA           Release 1.2.2 Toolkit can take advantage of Version 1.2_D           features, such as drag-and-drop functionality and tear-off           menus.  >           See Appendix B additional information related to the           OSF/Motif Toolkit.  4     4.2 Run-Time and Programming Environment Support             V1.2-4  A           The following run-time and programming environments areS?           provided with the Compaq DECwindows Motif for OpenVMS            software:t  ?           o  Run-time support is provided for the CDE Motif 1.0uA              Toolkit (OSF/Motif Release 1.2.5), OSF/Motif Release 1              1.1.3 Toolkit, and the XUI Toolkits.T  B           o  Development support is provided for the CDE Motif 1.0              Toolkit only.  @              However, you can choose during installation to save?              the OSF/Motif Release 1.1.3 programming files that A              existed on your system prior to the DECwindows MotifMC              Version 1.2-4 for OpenVMS product. Refer to the Compaq_@              DECwindows Motif for OpenVMS Installation Guide for=              details about saving the OSF/Motif Release 1.1.3h%              programming environment.   ?              -  If you install the software using the VMSINSTAL E                 procedure and choose to save these programming files,b@                 the files are moved to subdirectories and can be)                 accessed for programming.M       4-2n o  n      I                                                  Programmer Release Notes I                          4.2 Run-Time and Programming Environment Supporto    D                  -  If you install the software using the POLYCENTERD                     Software Installation utility and if programmingC                     support for the OSF/Motif Release 1.1.3 Toolkit F                     is present, then you can choose to save the headerD                     files and UIL compiler that were used to developF                     OSF/Motif Release 1.1.3 applications. If selected,E                     the installation procedure creates a subdirectory D                     called [.DECW$113], and the previous programming>                     files are moved into the new subdirectory.  I                  See the Compaq DECwindows Motif for OpenVMS InstallationhB                  Guide for additional information about saving the7                  Release 1.1.3 programming environment.   I               o  Application development with the Compaq DECwindows Motif H                  for OpenVMS product is supported for Compaq C++ as wellH                  as for updated Motif language bindings for Ada, Pascal,H                  Fortran, and C. Language bindings for Ada are availableD                  in the Compaq Ada Version 3.5A for OpenVMS (VAX and)                  Alpha) layered products.   &         4.2.1 Changes and Enhancements  C               The following notes describe changes and enhancements F               related to the DECwindows Motif development environment.  +         4.2.1.1 Available Language Bindingss                 V1.2-3  ?               Fortran, Pascal, C, and C++ language bindings are H               provided to support software development for the following$               DECwindows components:  !               o  Xlib (Release 5)                  o  Xt (Release 5)   #               o  Xm (Release 1.2.3)   $               o  Mrm (Release 1.2.3)                 o  DXm    I                                                                       4-3  1              Programmer Release Notes4     4.2 Run-Time and Programming Environment Support    8     4.2.1.2 Running Translated Images on OpenVMS Systems             V1.2-3  D           In versions of OpenVMS Alpha systems prior to Version 1.5,C           translation support was provided to address the following C           problems for users who migrated to OpenVMS Alpha systems:   6           o  Lack of full-language programming support  <           o  Unavailability of source code for recompilation  =           o  Difficulty recompiling code that depended on VAXm"              architecture features  B           For programming languages whose OpenVMS VAX versions are@           currently under development, native Alpha versions are>           available in the OpenVMS Alpha Version 6.1 operating@           system. The translated-image environment is maintainedC           to support language features that are available as of then$           VMS Version 5.5-2 release.  B           Similarly, translation is supported for images whose useA           of system services and run-time library entry points issD           restricted to those images that existed on the VMS Version!           5.5-2 operating system.e  ?           If you have installed layered products on your systemcC           since the VMS Version 5.5-2 release, you may need to maket?           additional changes if you rebuild an image to supporti>           translation. For instance, for applications that are?           included with Compaq DECwindows Motif for OpenVMS VAX D           software, you must build images with the OSF Motif ReleaseA           1.1.3 library or the DECwindows XUI library, instead ofi3           with the OSF Motif Release 1.2.3 library.e  @           The Compaq DECwindows Motif for OpenVMS, Version 1.2-6A           release includes the same translated-image support file:E           that was provided with the DECwindows Motif Version 1.2 for             OpenVMS Alpha release.  A           DECwindows Motif Version 1.2 for OpenVMS Alpha includesdB           support for DECwindows Motif Version 1.1 for OpenVMS VAX,           images on an OpenVMS Alpha system.             V1.2       4-4u w         I                                                  Programmer Release Notes I                          4.2 Run-Time and Programming Environment Supportt    H               The DECwindows Motif Version 1.2 for OpenVMS Alpha releaseH               does not include support for running translated DECwindowsG               Motif Version 1.2 for OpenVMS VAX images on OpenVMS Alphan               systems.  H               If you want to run an application against DECwindows MotifF               Version 1.2 shareable images on an OpenVMS Alpha system,I               build it (compile and link) on an OpenVMS Alpha system. You F               cannot obtain a Version 1.2 translated image by buildingC               your application against the DECwindows Motif VersioneD               1.2 shareable images on an OpenVMS VAX system, copyingF               the resulting image file to an OpenVMS Alpha system, and0               translating it (using DECmigrate).  @               If you cannot build your application on an OpenVMSE               Alpha system and need to obtain a translated image with G               DECmigrate, you should continue to build your applicationII               against the OSF/Motif Release 1.1.3 programming environment F               provided in the DECwindows Motif Version 1.1 for OpenVMSF               VAX product. (Note that you are given the option to saveG               your OSF/Motif Release 1.1.3 programming environment when E               you upgrade to DECwindows Motif Version 1.2 for OpenVMSaH               VAX.) VAX images built against the OSF/Motif Release 1.1.3G               programming environment can be copied to an OpenVMS Alpha <               system, translated, and executed successfully.  A               You can install translated-image support during theLI               DECwindows Motif installation procedure. See the DECwindowssD               Motif Version 1.2-4 for OpenVMS Installation Guide for               instructions.   H               The OSF/Motif Release 1.1.3 shareable images that are usedH               with translated images are different from and incompatibleD               with the shareable images used for native images. As a=               result, the following image restrictions apply:o  F               o  Do not use both native and translated images that use8                  DECwindows Motif software in a process.  A                  Either port or translate all the images that use H                  DECwindows Motif software and all images that call each                  other.s  I               o  Translated images that dynamically activate a DECwindowsc?                  Motif image using LIB$FIND_IMAGE_SYMBOL from a 4                  translated image are not supported.  I                                                                       4-5                 Programmer Release Notes4     4.2 Run-Time and Programming Environment Support    ?           For more information on translated-image support, seekC           the DECmigrate for OpenVMS AXP Systems Translating Imagesm           guide.  #     4.2.2 Problems and Restrictions   @           The following notes describe problems and restrictionsB           that currently exist in the DECwindows Motif development           environment.  2     4.2.2.1 Support for Display PostScript Removed             V1.2-6  B           Starting August 1, 1998, Compaq discontinued its support?           for the Display PostScript software licensed by AdobeEE           Systems Incorporated. Compaq took this action because AdobeMC           ended their former ongoing support of Display PostScript.S  A           Due to this decision, Compaq is contractually obligatedE>           to remove all Display PostScript capability from the>           DECwindows Motif software. This includes all relatedB           translated-image support and any functionality described9           in the following programming reference manuals:e  A           o  VMS DECwindows Display PostScript System Programmingr              Supplementa  @           o  Display PostScript System: Perspective for Software              Developersn  @           o  Display PostScript System: Client Library Reference              Manualn  8           o  Display PostScript System: Color Extensions  ?           o  Display PostScript System: pswrap Reference Manualo  8           o  PostScript Document Structuring Conventions&              Specification Version 2.1  >           Currently, there is no workaround. See the followingB           sections for more information on the potential impact to;           applications in the DECwindows Motif environment.s       4-6h o         I                                                  Programmer Release NotesoI                          4.2 Run-Time and Programming Environment Support     ?               4.2.2.1.1 Impact on DECwindows Motif ApplicationstG               Removing Display PostScript from DECwindows Motif impacts H               any application that relies on its capabilities to presentF               and display graphics and documents in PostScript format.  F               Unfortunately, this includes not only those applicationsG               developed by Compaq, such as the CDA Viewer, but also anyqG               third-party, user-written, or translated VAX applicationsaC               that depend on one or more of the following files anduE               libraries. These items are no longer a part the producthH               kit and are removed from your system when upgrading from aC               previous version of DECwindows Motif client software.t  %               o  PSWRAP command (DCL)m  4               o  Display PostScript (XDPS) libraries  3                     [SYSLIB]XDPS$DPSBINDINGSSHR.EXE 1                     [SYSLIB]XDPS$DPSCLIENTSHR.EXEA.                     [SYSLIB]XDPS$DPSLIBSHR.EXE  D               o  Display PostScript header files and sample programs  5               o  Translated-Image Support (TIS) fileso  >                     [SYSLIB]XDPS$DPSBINDINGSSHR_TV_SUPPORT.EXE<                     [SYSLIB]XDPS$DPSCLIENTSHR_TV_SUPPORT.EXE9                     [SYSLIB]XDPS$DPSLIBSHR_TV_SUPPORT.EXE 5                     [SYSLIB]CDA$ACCESS_TV_SUPPORT.EXE 7                     [SYSLIB]DDIF$VIEWSHR_TV_SUPPORT.EXE 7                     [SYSLIB]DECW$BKRSHR__TV_SUPPORT.EXE 7                     [SYSLIB]DECW$MAILSHR_TV_SUPPORT.EXE-  I               The actual effect of removing Display PostScript depends onaH               the extent to which it was implemented in the application.F               Applications that call the PSWRAP command, may fail onlyA               at the point where the command is invoked. However, D               applications that link against one or more of the XDPSH               libraries or TIS images will fail to function entirely due.               to unresolved links at run time.  C               As a result, you may need to modify those portions of D               DECwindows Motif applications that rely on these filesD               to run successfully in the Compaq DECwindows Motif for1               OpenVMS, Version 1.2-6 environment.   I                                                                       4-7                 Programmer Release Notes4     4.2 Run-Time and Programming Environment Support    :           4.2.2.1.2 Impact on Java Applications   The JavaD           Development Kit (JDK) for OpenVMS Version 1.2.2-1 contains=           two shareable images (JAVA$FONT_MANAGER_SHR.EXE and <           JAVA$FONT_MANAGER_G_SHR.EXE) that link against the?           Display PostScript (XPDS) libraries. As a result, all @           Java applications built with this kit that use DisplayE           PostScript capabilities will fail in the DECwindows Version            1.2-6 environment.  @           Note that this restriction only applies to the VersionD           1.2.2-1 kit. The Java machine for the 1.1* series, as wellC           as all releases of the JDK subsequent to Version 1.2.2-1, D           are not dependent on the Adobe Display PostScript software           or its libraries.   9     4.2.2.2 Using Multithreading and Upcalls (Alpha Only)-             V1.2-6  >           The transports used to communicate to the DECwindowsD           Server do not currently support the use of multiple kernelE           threads. Consequently, DECwindows Motif client applications @           that use multiple kernel threads multiple threads withE           upcalls enabled are not supported. This restriction appliespA           even if the application restricts DECwindows calls to a            single thread.  <     4.2.2.3 Problems Using the DECW$INCLUDE:INTRINSIC.H File             V1.2-5  ?           The DECwindows header file, DECW$INCLUDE:INTRINSIC.H,5?           redefines the globalref macro to be extern when usingrC           the DEC C compiler, even when the /STANDARD=VAXC compilerfD           switch is specified. This could have a wide impact on user           applications.   >           This redefinition in INTRINSIC.H is required because<           DECwindows needs to ensure that references to dataA           located in the DECwindows shared images by user-written C           applications use the same extern model that was used when 5           the DECwindows shared images were compiled.o  =           To workaround this problem, rather than having youro=           application use globalref and globaldef for its own >           variables, use the following preprocessor directive:  ,           #pragma extern_model strict_refdef       4-8R a  1      I                                                  Programmer Release Notes I                          4.2 Run-Time and Programming Environment Support     F               This workaround has the advantage of being strictly ANSIH               compliant. This pragma directive is described in the DEC C6               User's Guide for OpenVMS Systems manual.  ;         4.2.2.4 DECW$WML.EXE Looks in Current Directory For #                 DECW$WML_TOKENS.DATt                 1.2-4V  @               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 previousnG               versions of DECwindows Motif, this tokens file was alwaysdF               read from SYS$LIBRARY. However, starting with DECwindowsG               Motif Version 1.2-4 for OpenVMS, DECW$WML.EXE first looksaG               for this file in the current directory before looking foriH               it in SYS$LIBRARY. This allows a customized tokens file to               be used.  =         4.2.2.5 DECW$COMPARE_VERSIONS Command File Limitationr                 1.2-4o  E               The DECW$COMPARE_VERSIONS command file compares versiongB               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.  #         4.2.2.6 Use of _Xm Routinesl                 V1.2  G               The OSF/Motif Toolkit libraries contain many undocumentedvG               routines, which are prefixed with _Xm. These routines arefE               intended to be used only by the standard Motif widgets.sG               OSF reserves the right to modify the API or functionalitySG               of these routines, or to delete them altogether in future                releases.   G                 _______________________ Caution _______________________p  E                 Compaq supplies access to the _Xm routines by copyingsA                 them into the shareable image transfer vector foreD                 the OSF/Motif Release 1.2.2 Toolkit. Compaq does notE                 document or support these routines or guarantee their-C                 continued existence in future releases. Applicationo  I                                                                       4-9  i  m           Programmer Release Notes4     4.2 Run-Time and Programming Environment Support    A              developers who use these routines do so at their own               risk.  C              ______________________________________________________e  B     4.2.2.7 Compiling Applications Written in Fortran (Alpha Only)             V1.1  B           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 compilero           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 your 5                 program, add the following statement:   4                 CDEC$ OPTIONS /ALIGN=RECORDS=NATURAL  B              -  Following the INCLUDE statement, add the following                 statement:  !                 CDEC$ END OPTIONSr                   For example:  4                 CDEC$ OPTIONS /ALIGN=RECORDS=NATURAL(                 INCLUDE "DECW$MOTIF.FOR"!                 CDEC$ END OPTIONSa  E           o  Use the Fortran compiler switch, /ALIGN=RECORDS=NATURAL,e,              when you compile your programs.  /     4.2.2.8 Compiling Applications Written in C              V1.0  B           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>        4-10           I                                                  Programmer Release Notes.I                          4.2 Run-Time and Programming Environment Supportn    B               The DECwindows header files assume that the .h filesC               were extracted. They contain #include <module_name.h>lI               notation for the included files. The DECwindows programmingr7               documentation also makes this assumption.   G               VAX C should, therefore, be installed using the option tot*               extract the library modules.  I               If you have already installed VAX C and you did not extracteI               the .h files, the DECwindows sample C programs do not work.sI               To correct this problem, reinstall VAX C and extract the .h                files.  F               With DEC C, the header files do not need to be extractedG               from the text library if you define the DECC$TEXT_LIBRARYt&               logical name as follows:  D               $ DEFINE DECC$TEXT_LIBRARY SYS$LIBRARY:DECC$RTLDEF.TLB           4.3 CDAe  I               This section contains programming information about the CDA 0               application and run-time services.  &         4.3.1 Changes and Enhancements  H               The following notes describe changes and enhancements made;               to the CDA application and run-time services.   /         4.3.1.1 Drag-and-Drop Feature Availablel                 V1.2  D               The drag-and-drop feature, which lets you move or copyH               information between widgets, is implemented in the widgets"               listed in Table 4-1.  I               Table_4-1_Drag-and-Drop_Widgets____________________________s  I               Widget____________Drag_Operation____Drop_Operation_________h  ?               XmText            copy and move     copy and movee  ?               XmTextField       copy and move     copy and movet  $               XmLabel           copy  I                                                  (continued on next page)t  I                                                                      4-11M f  r           Programmer Release Notes     4.3 CDAO    E           Table_4-1_(Cont.)_Drag-and-Drop_Widgets____________________   E           Widget____________Drag_Operation____Drop_Operation_________               XmPushButton      copy              XmToggleButton    copy  E           XmList____________copy_____________________________________   C           For information about how to include additional drag-and-sB           drop functionality in applications and for an example ofD           a drag-and-drop program, see the Open Software Foundation:<           OSF/Motif Programmer's Guide, Revision 1.2 manual.  0     4.3.1.2 Changes to the Programming Interface             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 amounto;           of system-specific code in your CDA applications.y  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_ E           VERSION symbol is now declared as DDIF_K_DSC_MAJOR_VERSION,tA           and the CDA$_NORMAL status value is now defined as CDA_o           NORMAL.   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 use D           the new CDA features, change the file names in your source           code.t       4-12           I                                                  Programmer Release NoteshI                                                                   4.3 CDAt    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,oH               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.a  @               By using the previous set of header files, you canC               successfully build existing source code that uses theo*               previous naming conventions.  @               See Table 4-2 for a list of new header file names.  I               Table_4-2_New_Header_File_Names____________________________   I               Previous_Name____New_Name__________________________________   '               cda$def.h        cdadef.ha  '               cda$msg.h        cdamsg.h.  (               ddif$def.h       ddifdef.h  (               dtif$def.h       dtifdef.h  '               cda$ptp.h        cdaptp.hi  '               cda$typ.h        cdatyp.h   '               dvr$msg.h        dvrmsg.hi  )               dvr$cc_def.h     dvrccdef.h   )               dvr$cc_ptp.h     dvrccptp.hi  (               dvr$decw_def.h   dvrwdef.h  I               dvr$decw_ptp.h___dvrwptp.h_________________________________   8         4.3.1.3 Changes to External Reference Processing                 V1.2  I               CDA Run-Time Services supports relative file specificationsaC               for external references. Relative references are alsolF               supported: that is, a reference where the directory pathE               is not fully specified but is relative to the directoryd*               path of the parent document.  I                                                                      4-13g m  r           Programmer Release Notes     4.3 CDAy    ,     4.3.1.4 Message for Style Guide Fallback             V1.2  E           The following message is displayed when a local style guide            cannot be found:  B       STYGDEFBK, Fallback to nonlocale-specific style guide: file-
          spec             Level: Informational   E          Explanation: Since the locale-specific style guide cannot beSD          found, the nonlocale-specific version of the style guide is          used.  5     4.3.1.5 Using Logical Names with CONVERT Commandsn             V1.2  A           During a document conversion, if a logical name is usedhB           to specify the directory of the primary document and theA           document file extension is omitted, external referencesr=           that contain relative file specifications cause thea           conversion to fail.i  E           This failure occurs because the back-end converter examinesaB           the converter processing options, although the front-end?           converter opens the input file. Because the converteroA           software cannot predict what default file extension theoC           front-end converter might apply, it uses the OpenVMS fileeE           services to resolve the logical name and to find the actual D           file specification so that the directory can be parsed and1           extended with a relative specification.e  D           The conversion fails only when the external reference uses)           a format such as the following:              sys$login:mydocs  ?           In this case, the reference will not be resolved. TheP@           reference is resolved in all other cases. For example:             sys$login:mydoc.doc            disk$:[smith]mydoc            disk$:[smith]mydoc.doc       4-14 .  A      I                                                  Programmer Release NotesSI                                                                   4.3 CDA     .         4.3.1.6 Restructuring Shareable Images                 V1.2  C               The CDA Viewer includes two shareable images to allowEH               installation on systems where DECwindows is not installed.  C               In DECwindows Motif Version 1.2 for OpenVMS software,ID               shareable images that use the X services were renamed.A               Table 4-3 lists the shareable images in the variousP)               versions of the CDA Viewer.   I               Table_4-3_Names_of_Shareable_Images________________________                  CDA I               Version_____Image_Name_______Description___________________m  @               Version     CDA$ACCESS       CDA Run-Time Services;               1.6                          shareable image.e  B                           DDIF$VIEWSHR     Callable viewer widget.  @               Version     CDA$ACCESS       CDA Run-Time Services;               1.7                          shareable image.s  G                           DDIF$VIEWSHR     The DDIF$DECW_VIEWSHR widgeteF                           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_VIEWSHRaE                                            (character-cell interface) 3                                            widgets..  @               Version     CDA$ACCESS       CDA Run-Time Services;               1.8A or                      shareable image.t               latera  G                           DDIF$VIEWSHR12   The DDIF$VIEWSHR12 widget ispH                                            a callable viewer widget thatH                                            uses LIB$FIND_IMAGE_SYMBOL toI                                            invoke the DDIF$DECW_VIEWSHR12 E                                            (DECwindows interface) and F                                            DDIF$CC_VIEWSHR (character-I               _____________________________cell_interface)_widgets.______y  I               By using the LIB$FIND_IMAGE_SYMBOL routine to reference the I               entry points to the DDIF$DECW_VIEWSHR, DDIF$DECW_VIEWSHR12,eH               and DDIF$CC_VIEWSHR images, an application can dynamically  I                                                                      4-15  p  l           Programmer Release Notes     4.3 CDAl    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.                                                                                4-16 d  c      I                                                  Programmer Release NotesaI                                                               4.4 DECterms             4.4 DECterml  =               This section contains information about DECterm                programming.  &         4.4.1 Changes and Enhancements  H               The following notes describe changes and enhancements made)               to the DECterm application.s  #         4.4.1.1 ReGIS Input Cursorse                 V1.2-3  G               DECterm supports the following input cursors: cross-hair,PF               rubber-band line, diamond, and rubber-band rectangle. ToF               select input cursors use the S(C(In)) command. Table 4-4$               shows the values of n.  I               Table_4-4_ReGIS_Input_Cursors-Cursor_styles_and_Values_____   I               Cursor_Style__________Variable_n___________________________E  +               Cross-hair            Omitted   %               Cross-hair (default)  0.  %               Diamond               1T  %               Cross-hair            2   %               Rubber-band line      3t  %               Rubber-band           4oI               rectangle__________________________________________________w  F                 ________________________ Note ________________________  C                 If a shape other than the diamond cursor is desired.=                 when n is equal to 1, define the logical namehB                 DECW$DECTERM_REGIS_CURSOR to be one of the numbers>                 defined in the SYS$LIBRARY:DECW$CURSOR.H file.  F                 ______________________________________________________  I                                                                      4-17  m              Programmer Release Notes     4.4 DECterm     *     4.4.1.2 Page-Movement Escape Sequences             V1.2  :           The following page-movement escape sequences are!           implemented in DECterm:i  1               NP       <CSI> Pn U       Next Pager5               PP       <CSI> Pn V       Previous Pagem>               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.l  C              ________________________ Note ________________________f  A              DECterm does not support cursor coupling; the cursor_=              is always bound to the current (displayed) page.q  C              ______________________________________________________i       4.4.1.3 DECCRA Sequencer             V1.2  =           DECterm supports the DECCRA (Copy Rectangular Area) @           sequence in a limited way. The entire page needs to beB           copied at once, and either the source or the destinationE           page must be the current page (for example, you cannot copy /           from one off-screen page to another).e       4.4.1.4 DECLFKC Sequence             V1.2  B           Since DECterm does not have a user interface to redefine=           the F5 (Break) key, the DECLFKC (Local Function Key_D           Control) sequence redefines the F5 key when "0" (all keys)8           is used to select which key is to be modified.       4.4.2 CorrectionsA  E           The following notes describe the resolution of any problemsn=           specific to the DECterm application that previously$8           resulted in an error or required a workaround.       4-18 r  a      I                                                  Programmer Release NotesoI                                                               4.4 DECterm     @         4.4.2.1 CREATE/TERM/WAIT SHOW PROCESS No Longer Disrupts                 SYS$INPUT                  V1.2-6  H               Issuing the CREATE/TERMINAL/WAIT SHOW PROCESS command fromF               a command procedure no longer disrupts the definition of               SYS$INPUT.  '         4.5 DECTPU for DECwindows Motifn  @               This section contains information about DECTPU for+               DECwindows Motif programming.   '         4.5.1 Problems and Restrictions   =               The following notes describe known problems andDC               restrictions that currently exist with the DECTPU fore               DECwindows Motif.I  1         4.5.1.1 Small Display Monitors and DECTPUo                 V1.0  G               When running DECTPU for DECwindows Motif on small displayuG               monitors, the main window can be less than fully visible.e  <               To correct this condition, follow these steps:  F               1. Add the following resources to your DECTPU X resource                  file:  D                  Tpu.Tpu$MainWindow.X:                             0D                  Tpu.Tpu$MainWindow.Y:                             0E                  Tpu.Tpu$MainWindow.Rows:                          21.E                  Tpu*condensedFont:                                onpD                  Tpu*fontSetSelection:                             1  H               2. Copy the resource file from SYS$LIBRARY:EVE.DAT and add$                  the previous lines.  F               3. Use the logical name TPU$DEFAULTS to point at the new                  resource file.   G                  The following example invokes the EVE DECwindows Motif D                  user interface using the X resource file names eve_E                  small_window.dat in your login directory to edit theh                   file LOGIN.COM.  F                  $  DEFINE TPU$DEFAULTS SYS$LOGIN:EVE_SMALL_WINDOW.DAT7                  $  EDIT/TPU/INTER=DECWINDOWS LOGIN.COMD  I                                                                      4-19x i  r           Programmer Release Notes&     4.6 DECwindows Extensions to Motif    &     4.6 DECwindows Extensions to Motif  C           This section contains information about the extensions tos           the Motif Toolkit.  "     4.6.1 Changes and Enhancements  D           The following notes describe changes and enhancements made0           to the DECwindows Extensions to Motif.  2     4.6.1.1 SVN Widget Supports Extended Selection             V1.2-6  B           The Structured Visual Navigation (SVN) widget now allowsD           users to extend a range of selection using the Shift+Down-A           Arrow key sequence. Note that this change has also beeng5           applied to the sample program SVNMSAMPLE.C.d  *     4.6.1.2 DXmCSText Input Method Support             V1.2  ?           X11 R5 input method support is added to the DXmCSTextg>           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.  #     4.6.2 Problems and Restrictions   9           The following notes describe known problems andr?           restrictions that currently exist with the DECwindows            Extensions to Motif.  2     4.6.2.1 DXmFormSpaceButtonsEqually Restriction             V1.1  B           The convenience routine DXmFormSpaceButtonsEqually sizes@           and spaces all widgets or gadgets equally if they haveA           a subclass of XmLabel or XmLabelGadget. The results areo>           undefined if a widget or gadget is not a subclass of#           XmLabel or XmLabelGadget.        4-20           I                                                  Programmer Release Notes I                                        4.6 DECwindows Extensions to Motifr    E         4.6.2.2 SVN Widget Does Not Support Horizontal Live Scrollingc                 V1.0  C               Horizontal live scrolling is not supported in the SVN                widget.p           4.6.3 Correctionsi  I               The following notes describe the resolution of any problems A               specific to the DECwindows Extensions to Motif thatsG               previously resulted in an error or required a workaround.a  B         4.6.3.1 Calling DXmSvnDeleteEntries after DXmSvnAddEntries                 V1.2-6  E               Calling the DXmSvnDeleteEntries routine after a call topG               the DXmSvnAddEntries routine no longer causes the related #               application to crash.   %         4.7 Display Server Extensionsl  H               This section contains information about the display server               extensions.   &         4.7.1 Changes and Enhancements  H               The following notes describe changes and enhancements made/               to the display server extensions.s  <         4.7.1.1 Shared Memory Extension Support (Alpha Only)                 V1.2  G               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, F               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 ofeI               shared memory pixmaps, you can change the contents of these 6               pixmaps without using any Xlib routines.  I                                                                      4-21c                Programmer Release Notes!     4.7 Display Server Extensions     B           These routines are included in the client side extensionB           library. See Section 4.7.1.4 for details on linking this           library.  B           4.7.1.1.1 How to Use Shared Memory Extension   Code thatE           uses the shared memory extension must include the following.           header files:s  )           # include "DECW$INCLUDE:Xlib.h"f(           # include "DECW$INCLUDE:shm.h")           # include "DECW$INCLUDE:XShm.h"t  ?           Any code that uses the shared memory extension should @           first check that the server provides the extension. InE           some cases, such as running over the network, the extension            does not work.  A           To check if the shared memory extension is available on_:           your system, call one of the following routines:  -           Status XShmQueryExtension (display) !                  Display *displayp  B           Status XShmQueryVersion (display, major, minor, pixmaps)"                  Display *display;$                  int *major, *minor;                  Bool *pixmaps  9           The following table lists each argument and its            description.  E           ___________________________________________________________ E           Argument____Description____________________________________e  *           display     The current display.  =                       If the shared memory extension is used,w>                       the return value from either function isB                       True. Otherwise, your program operates using.                       conventional Xlib calls.  ;           major       Major version number of the extensioneC                       implementation. Returned by XShmQueryVersion.v  ;           minor       Minor version number of the extensionnC                       implementation. Returned by XShmQueryVersion.   E           pixmaps_____True,_if_shared_memory_pixmaps.________________e       4-22 o  o      I                                                  Programmer Release NoteseI                                             4.7 Display Server Extensions     C               4.7.1.1.2 Using Shared Memory XImages   The followingaF               sequence shows the process for creating and using shared               memory XImages:d  ;               1. Create the shared memory XImage structure.e  H               2. Create a shared memory segment to store the image data.  2               3. Attach the shared memory segment.  C               4. Inform the server about the shared memory segment.t  .               5. Use the shared memory XImage.  G               The following sections explain each step in this process:a  >               Step 1-Creating a Shared Memory XImage Structure  G               To create a shared memory XImage, use the XShmCreateImageo6               routine, which has the following format:  L               XImage *XShmCreateImage (display, visual, depth, format, data,1                           shminfo, width, height) &                      Display *display;$                      Visual *visual;7                      unsigned int depth, width, height;r                       int format;                       char *data;.                      XShmSegmentInfo *shminfo;  I               Most of the arguments are the same as for XCreateImage (SeeDG               the X Window System for a description of the XCreateImageiE               routine.) Note that there are no offset, bitmap_pad, orCG               bytes_per_line arguments. These quantities are set by the F               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 this ;               structure before the call to XShmCreateImage.e  G               If successful, an XImage structure is returned, which you /               can use for the subsequent steps.   I                                                                      4-23                 Programmer Release Notes!     4.7 Display Server Extensions     3           Step 2-Creating the Shared Memory Segment   @           Create the shared memory segment after the creation of@           the XImage because the XImage returns information that0           indicates how much memory to allocate.  =           The following example illustrates how to create the            segment:  .           shminfo.shmid = shmget (IPC_PRIVATE,I                   image->bytes_per_line * image->height, IPC_CREAT|0777);T  A           This example assumes that you called your shared memoryaD           XImage structure. A return value of 0 indicates the sharedE           memory allocation has failed. Use the bytes_per_line field, E           not the width you used to create the XImage, as they may be            different.  B           Note that the shared memory ID returned by the system isC           stored in the shminfo structure. The server needs that IDw*           to attach itself to the segment.  4           Step 3-Attaching the Shared Memory Segment  D           Attach the shared memory segment to your process as in the           following example:  F           shminfo.shmaddr = image->data = shmat (shminfo.shmid, 0, 0);  D           The address returned by shmat is stored in both the XImage.           structure and the shminfo structure.  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 asi           follows:  #           shminfo.readOnly = False;c  C           If you set the structure to True, the server cannot writem7           to this segment, and XShmGetImage calls fail.y  C              ________________________ Note ________________________o  <              The shared memory segment routines are provided@              with DECwindows Motif. Using global sections, these@              routines emulate the shared memory routines on UNIX              systems.   C              ______________________________________________________s       4-24           I                                                  Programmer Release Notes I                                             4.7 Display Server Extensions     I               Step 4-Informing the Server About the Shared Memory Segment   H               Tell the server to attach to your shared memory segment as'               in the following example:   3               Status XShmAttach (display, shminfo);   C               If successful, a nonzero status is returned, and yourr&               XImage is ready for use.  3               Step 5-Using the Shared Memory XImaget  E               To write a shared memory XImage into an X drawable, usehI               the XShmPutImage routine. The XShmPutImage routine uses the_               following format:   @               XShmPutImage (display, d, gc, image, src_x, src_y,M                                    dest_x, dest_y, width, height, send_event) &                      Display *display;                       Drawable d;                      GC gc; #                      XImage *image; 6                      int src_x, src_y, dest_x, dest_y;0                      unsigned int width, height;%                      Bool send_event;_  F               The interface is identical to the XPutImage routine (seeH               the X Window System), except for one additional parameter,B               send_event. If this parameter is passed as True, theF               server generates a completion event when the image writeF               is complete. This allows your program to know when it isI               safe to begin manipulating the shared memory segment again.   F               The completion event is of the type XShmCompletionEvent,*               which is defined as follows:  #                    typedef struct { ;                        inttype;              /* of event */mN                        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;   I                                                                      4-25  .              Programmer Release Notes!     4.7 Display Server ExtensionsC    ?           To determine the event type value that is used at runeD           time, use the XShmGetEventBase routine as in the following           example:  O                int CompletionType = XShmGetEventBase (display) + ShmCompletion;   C              ________________________ Note ________________________e  ?              If you modify the shared memory segment before thei@              arrival of the completion event, the results may be              inconsistent.  C              ______________________________________________________   A           To read image data into a shared memory XImage, use then@           XShmGetImage routine, which uses the following format:  C           Status XShmGetImage (display, d, image, x, y, plane_mask)l"                  Display *display;                  Drawable d;                  XImage *image;                   int x, y;*                  unsigned long plane_mask;  9           The following table lists each argument and itst           description.  E           ___________________________________________________________NE           Argument____Description____________________________________A  .           display     The display of interest.  *           d           The source drawable.  -           image       The destination XImage.   :           x           X-offset within the source drawable.  :           y           Y-offset within the source drawable.  E           plane_mask__The_planes_that_are_to_be_read.________________   ?           To destroy a shared memory XImage, first instruct the D           server to detach from it, then destroy the segment itself.C           The following example illustrates how to destroy a sharedC           memory XImage:  (           XShmDetach (display, shminfo);            XDestroyImage (image);"           shmdt (shminfo.shmaddr);.           shmctl (shminfo.shmid, IPC_RMID, 0);       4-26 t  i      I                                                  Programmer Release NotestI                                             4.7 Display Server Extensionsu    F               4.7.1.1.3 Using Shared Memory Pixmaps   Unlike X images,E               for which any image format is usable, the shared memorynB               extension supports only a single format for the dataE               stored in a shared memory pixmap (XYPixmap or ZPixmap).tF               This format is independent of the depth of the image andI               independent of the screen. (For 1-bit pixmaps the format is                irrelevant.)  D               The XShmPixmapFormat routine returns the shared memoryH               pixmap format for the server. The XShmPixmapFormat routine'               has the following format:n  ,               int XShmPixmapFormat (display)&                      Display *display;  H               Your application can only use shared memory pixmaps in theH               format returned by the XShmPixmapFormat routine (includingF               bits-per-pixel). To create a shared memory pixmap do the               following:  E               o  Create a shared memory segment and shminfo structure D                  exactly the same way as is listed for shared memoryI                  XImages steps 1 through 4 (see Section 4.7.1.1.2). WhilesD                  it is not necessary to create an XImage first (stepD                  1), doing so incurs little overhead and provides an9                  appropriate bytes_per_line value to use.   A               o  Call the XShmCreatePixmap routine, which has the "                  following format:  K                  Pixmap XShmCreatePixmap (display, d, data, shminfo, width,n9                                           height, depth);t)                         Display *display;p#                         Drawable d;E#                         char *data;e1                         XShmSegmentInfo *shminfo;i:                         unsigned int width, height, depth;  I                  The arguments are the same as for XCreatePixmap (see therG                  X Window System) except for two additional parameters,tD                  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.h  I                                                                      4-27u n  u           Programmer Release Notes!     4.7 Display Server Extensions     ?              If successful, a pixmap is returned, which you can A              manipulate. You can manipulate its contents directlyLE              through the shared memory segment. Shared memory pixmaps E              are destroyed with the XFreePixmap routine, although you E              should detach and destroy the shared memory segment (seee*              step 4 in Section 4.7.1.1.2).  .     4.7.1.2 Specifying Extension Include Files             V1.2  @           To ensure that programs that contain extension includeC           files compile properly, add the logical name DECW$INCLUDEd1           to the C include directory search list..  @           To add the logical name for VAX C, enter the following           command:  )           $ DEFINE C$INCLUDE DECW$INCLUDEs  @           To add the logical name for DEC C, enter the following           command:  1           $ DEFINE DECC$USER_INCLUDE DECW$INCLUDEn  %     4.7.1.3 X Image Extension Support              V1.1  A           Starting with DECwindows Motif Version 1.1 for OpenVMS, @           DECwindows Motif supports the X Image Extension (XIE).D           XIE allows image display processing using resources on theB           server side of the X client-server model. XIE eliminatesD           the need to transmit image data repeatedly from the clientA           to the server and also allows data to be transmitted ine5           compressed form, reducing the network load.s  @           DECwindows Motif includes the XIE client side sharableE           library (XIE$SHRLIB.EXE) and C language header files. TheseAD           allow applications to communicate with any X11 server that%           supports the XIE extension..  @           An XIE program uses a structure called the XIEImage to>           describe image data on the client side. This generalA           mechanism describes data that the destination server iso@           incapable of processing. Consult the documentation forB           the server system for information on what data types andA           sizes are supported. Unless the documentation specifies ?           different limits, the server is capable of processing B           unsigned byte (UdpK_DTypeBU), unaligned bit field (UdpK_       4-28    m      I                                                  Programmer Release NoteshI                                             4.7 Display Server Extensionsi    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 asH               unsigned word (UdpK_DTypeWU), and a depth of up to 16 bits&               per pixel per component.  B               The XIE protocol and programming interface are beingG               standardized within the X Consortium for R6, and programsnI               that use XIE will probably have to be modified. You can useoD               the Image Display Services (IDS) component of DECimageC               Application Services for VMS as an alternative to thelF               XIE library interface. IDS provides a higher level modelD               of image display and automatically uses XIE when it is(               available and appropriate.  7         4.7.1.4 Client Side Extension Library Available                  V1.1  E               Starting with DECwindows Motif Version 1.1 for OpenVMS, B               Xlib added a client side library that allows OpenVMSE               clients to issue Shape, XInput, Multibuffer, and shared E               memory extension requests to servers that provide these G               features. (For example, the DECwindows X11 display server B               for OpenVMS VAX does not support the Shape extensionG               while the DECwindows X11 display server for OpenVMS Alpha_E               system does support Shape.) The name of this library isi"               DECW$XEXTLIBSHR.EXE.  :               You must modify the linking file options for;               client applications that issue Shape, XInput, >               Multibuffer, or shared memory extension requests?               to link to the Xlib extensions shareable image in E               SYS$LIBRARY:DECW$XEXTLIBSHR.EXE. Add the following linea*               to your linker options file:  /               SYS$LIBRARY:DECW$XEXTLIBSHR/SHAREr  D               For more information on Shape, XInput, and MultibufferC               extensions, see the following text files in SYS$HELP:n                    DECW$SHAPE.TXTf                   DECW$XINPUT.TXT%                  DECW$MULTIBUFFER.TXT   I                                                                      4-29                 Programmer Release Notes     4.8 Internationalization         4.8 Internationalization  ;           This section contains release notes pertaining tot0           internationalization and localization.  "     4.8.1 Changes and Enhancements  D           The following notes describe changes and enhancements madeA           to internationalization and localization support. These E           changes enable users to view and convert files that containe$           Asian-language characters.  <     4.8.1.1 Using the CDA Viewer to View Asian-Language Text             V1.2-3  C           You can use the CDA Viewer in two ways to view text filest(           that contain Asian characters:  C           o  Specify an options file to the CDA Viewer application.   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.   C           4.8.1.1.1 Specifying an Options File   Specify an optionse?           file by including a one-line entry in the file in the            following format:   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 4-5 for a list of values.)   D           Table 4-5 shows the languages, codesets, and text-encoding           values.            4-30    a      I                                                  Programmer Release NotessI                                                  4.8 Internationalization     I               Table_4-5_Asian_Language_Codes_for_Options_Files___________   I               Language_________Codeset__________Text_Encoding_Value______h  9               Japanese         DEC Kanji        DEC_KANJI   9               Japanese         Super DEC Kanji  SDECKANJIi  9               Traditional      DEC Hanyu        DEC_HANYUe               Chineses  9               Simplified       DEC Hanzi        DEC_HANZI                Chinese   I               Korean___________DEC_Korean_______DEC_HANGUL_______________   E               The following table shows examples of one-line entries.i  I               ___________________________________________________________mI               Options_File_____________One-Line_Entry____________________   G               HANYU.CDA$OPTIONS        TEXT   TEXT_ENCODING   DEC_HANYUn  G               HANZI.CDA$OPTIONS        TEXT   TEXT_ENCODING   DEC_HANZIu  I               HANGUL.CDA$OPTIONS_______TEXT___TEXT_ENCODING___DEC_HANGUL_h  C               To view the EXAMPLES_CUSTOMERS.TXT file that containsiF               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:t  *               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 isyD               viewable in the DEC Kanji codeset (Japanese language).  E               4.8.1.1.2 Defining Logical Names   The second option totG               enable viewing files in Asian languages is to specify theeI               text file and encoding value by defining two logical names:   "               o  DDIF$READ_TEXT_GL  "               o  DDIF$READ_TEXT_GR  G               Table 4-6 shows the logical names and associated encodingt               values.   I                                                                      4-31e                Programmer Release Notes     4.8 Internationalization    E           Table_4-6_Logical_Names_for_Specifying_Text_Encoding_______l  E           DDIF$READ_TEXT_GL_____DDIF$READ_TEXT_GR_____Encoding_Value_s  9           LATIN1                MCS                   MCS   A           LATIN1                LATIN1                ISO Latin-1_  @           LATIN1                KATAKANA              ASCII-Kana  ?           LATIN1                KANJI                 DEC KanjiM  ?           ROMAN                 MCS                   Roman-MCSh  ;           ROMAN                 LATIN1                Roman   A           ROMAN                 KANJI                 Roman-Kanji   @           ROMAN                 KATAKANA              Roman-Kana  ?           LATIN1                HANZI                 DEC Hanzi   @           LATIN1                HANGUL                DEC Hangul  E           LATIN1________________HANYU_________________DEC_Hanyu______e  E           You can define the logical names on the DCL command line orf.           in your LOGIN.COM file. For example:  +           $ DEFINE DDIF$READ_TEXT_GL LATIN1s*           $ DEFINE DDIF$READ_TEXT_GR KANJI  B           Note that this example defines the text encoding for DEC            Kanji (see Table 4-6).  C     4.8.1.2 Converting Files That Contain Asian-Language Charactersh             V1.2-3  @           You can convert an Asian-language text file to anotherA           format by specifying an options file or by defining thecB           logical names DDIF$READ_TEXT_GL and DDIF$READ_TEXT_GR as?           discussed in Section 4.8.1.1.1 and Section 4.8.1.1.2.*  C           The format for converting a document from TEXT to another            format is as follows:a  S           $ CONVERT/DOCUMENT/OPTION=language.CDA$OPTIONS filename.TXT/FORMAT=TEXT -g;           _$ filename.output_extension/FORMAT=output_format_  E           For example, to convert a traditional Chinese language texte@           file to a DDIF file, enter the following command line:  7           $ CONVERT/DOCUMENT/OPTION=HANYU.CDA$OPTIONS -sL           _$ GUIDELINES_PERSONNEL.TXT/FORMAT=TEXT  GUIDELINES_PERSONNEL.DDIF       4-32           I                                                  Programmer Release NoteseI                                                  4.8 Internationalizationh    >               Note that this command line does not include the:               /FORMAT=DDIF qualifier; DDIF is the default.  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 fontseE               are available on the printer. Otherwise, the PostScripttF               file defaults to a basic set of fonts. If these fonts doG               not exist, the PostScript file defaults to Courier fonts. F               Table 4-7 shows the languages and their associated basic               fonts.  I               Table_4-7_Languages_and_Associated_Basic_Fonts_____________t  I               Language______________Basic_Fonts__________________________e  G               Japanese              Ryumin-Light-EUC-H or Ryumin-Light-_+                                     Hankaku_  I               Hanyu                 Sung-Light-CNS11643, Sung-Light-DTSCS   )               Hangul                Munjol  I               Hanzi_________________XiSong-GB2312-80_____________________n  F                 ________________________ Note ________________________  <                 Vertical writing is not supported by the CDAF                 converters. All vertical text is printed horizontally.  F                 ______________________________________________________  I                                                                      4-33_ e  i           Programmer Release Notes     4.9 XNL Libraryi         4.9 XNL Libraryi  B           This section contains information about the XNL library.  "     4.9.1 Changes and Enhancements  D           The following notes describe changes and enhancements made           to the XNL library.        4.9.1.1 xnl_parsedatetimen             V1.2-5  A           xnl_parsedatetime (and its VAX binding, XNL$PARSE_DATE_ B           TIME) accepts two-digit or four-digit years in the inputB           argument XmString s (which is the date-time string to beA           parsed). Valid years in the two-digit format are in the A           range 70 to 99, which mean the years from 1970 to 1999.iD           Values from 00 to 69 are invalid. Year 2000 and later must0           be specified in the four-digit format.       4.9.1.2 xnl_langinfo             V1.2-5  B           xnl_langinfo (and its VAX binding, XNL$LANGINFO) returnsA           a string for date-time formatting when D_FMT or D_T_FMThB           is specified in the item argument. In the locales listedE           below, this function returns a formatting string containingpC           %y. This formatting string should be used carefully afterrC           the year 2000, as %y indicates the two-digit year format.s             o  es_ES Spanish  !           o  fr_BE French Belgiumn              o  fr_CA French Canada             o  iw_IL Hebrew              o  no_NO Norwegian  
     4.10 Xlibt  7           This section contains information about Xlib.r       4-34 v         I                                                  Programmer Release Notes I                                                                 4.10 Xlib;    '         4.10.1 Changes and Enhancementss  H               The following notes describe changes and enhancements made               to the Xlib.  1         4.10.1.1 X11 Environment Variable Parsinge                 V1.2-6  D               Xlib now accepts the equivalent X11 Release 5 (X11 R5);               forms of the following environment variables:   I               ___________________________________________________________eI               OpenVMS_Form______X11_R5_Form______________________________e  '               DECW$DISPLAY      DISPLAY,  -               DECW$RESOURCE_    RESOURCE_NAME I               NAME_______________________________________________________   F               On startup, if the OpenVMS variable is not defined, XlibF               then checks for the X11 R5 equivalent before returning a               status value.   -         4.10.1.2 UIDPATH Environment Variable)                 V1.2-6  D               When opening a hierarchy, Xlib searches the DECW$USER_B               DEFAULTS and DECW$SYSTEM_DEFAULTS areas for the UserB               Interface Definition (UID) file. On UNIX systems andD               according to X11 R5 specifications, the search path isC               defined using the UIDPATH variable and its fallbacks.a  G               Now, Xlib also checks for the UIDPATH variable if the UIDeE               file is not found using either of the OpenVMS variables I               state above. This variable references a UNIX-style pathnameeB               (for example, /foo/bar) and allows the substitutionsI               strings as specified by X11 standards. For more information E               on the UIDPATH variable, see the OSF/Motif Programmer's                Reference.  F                 ________________________ Note ________________________  ?                 The UIDPATH variable does not work with OpenVMSeC                 directory specifications. Use the DECW$xxx_DEFAULTS ?                 logicals to specify OpenVMS-style search paths.h  F                 ______________________________________________________  I                                                                      4-35  2              Programmer Release Notes
     4.10 Xlibn    5     4.10.1.3 New Default Format for XtResolvePathnamei             V1.2-6  @           In XtResolvePathname, the default pathname is required>           to have certain properties when either no other path;           information is present in the call, or when it is E           referenced by the environment variable XFILESEARCHPATH. The D           former default OpenVMS format of the pathname consisted ofD           a type-name-suffix substitution. The modified pathname nowC           reflects the 6-part fallback, as specified by X11 Releasew           5.  =           The new pathname behavior is enabled by setting thed2           DECW$VSW_COMPLIANT variable, as follows:  '           $ DEFINE DECW$VSW_COMPLIANT 1I  "     4.10.1.4 XtAppMainLoop Routine             V1.2-5  ?           Previously, if a program entered its event loop, (foraD           example, by calling XtAppMainLoop) without having opened aD           display or specified a timer or event flag for the programD           to wait for (by calling XtAppAddTimeout or XtAppAddInput),>           Xlib terminated the program with the following error           message:  ;                   X Toolkit Error: Error in XMultiplexInputm  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 regaining >           control, such as specifying an event flag by calling           XtAppAddInput.  .     4.10.1.5 Locale Support in OpenVMS Systems             V1.2-4  A           The locale support provided in DECwindows Motif Version D           1.2-4 for OpenVMS is compatible with the locale support inD           the DEC C Run-Time Library. If you write internationalized:           applications using these functions in the locale(           environment, do the following:       4-36 e  o      I                                                  Programmer Release Notes I                                                                 4.10 Xlibs    @               o  For Xlib applications, include <X11/Xlocale.h>.A                  If you include <stdlib.h>, you must do so befored!                  <X11/Xlocale.h>.d  I               o  For Motif applications, <X11/Xlocale.h> is automatically                   included.  9               o  Turn on the following compilation flags:   E                  /define=(X_LOCALE,X_WCHAR,_WCHAR_T_,XLIB_XPG4_FUNCS)   *         4.10.1.6 Xlib Internationalization                 V1.2  H               The X Window System Version 11, Release 5 (X11 R5) definesG               a number of services to support writing internationalized C               X applications. Internationalization of X is based onnE               the concept of a locale. A locale defines the localized H               behavior of a program at run time. Locales affect Xlib by:  :               o  Encoding and processing input method text  3               o  Encoding resource files and values   2               o  Encoding and imaging text strings  I               o  Encoding and decoding for interclient text communication   C               The X Window System defines a general methodology and C               a set of application programming interfaces (APIs) to C               standardize programming in X. Standards have not beenhE               established for implementing these internationalizationeD               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,fH               but their underlying processing differs. These differences6               are described in the following sections.        I                                                                      4-37                 Programmer Release Notes
     4.10 Xlibi    ?           4.10.1.6.1 Vendor Pluggable Layer   Compaq provides an>           general mechanism called the vendor pluggable layer,B           which allows you to choose your own internationalizationD           implementations. Different implementations can be built asD           standalone shareable libraries and can be selected through(           the logical DECW$XVENDORLAYER.  @           If this logical is not defined, the mechanism searchesC           for an internationalization implementation library in the1           following order:  %              DECW$XI18NLIBSHR (Xi18n) !              DECW$XSILIBSHR (Xsi)n#              DECW$XIMPLIBSHR (Ximp)a  A           If a shareable library is not found, the default is the B           Xi18n implementations that are already linked with Xlib.  D           The following functions act as interfaces between Xlib andD           the internationalization implementation shareable library:                XDefaultStringa              XwcFreeStringList&              XwcTextListToTextProperty&              XmbTextListToTextProperty&              XwcTextPropertyToTextList&              XmbTextPropertyToTextList              _XrmInitParseInfo              _XlcDefaultLoader  B           When creating the Xsi or the Ximp shareable library, youC           need to know the names of the interfaces because they arel@           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")        4-38    n      I                                                  Programmer Release Notes I                                                                 4.10 Xlib     H               4.10.1.6.2 Compaq Internationalization Xlib ImplementationB                The Compaq implementation (Xi18n) provides enhancedD               support and a stable internationalization environment.F               The Compaq implementation (Xi18n) provides the followingH               advantages over the Xsi or Ximp environments provided with!               the X distribution:   I               o  Most European locales and Asian locales are supported bye6                  the DECwindows Motif version of Xlib.  E               o  New locales can easily be supported without changing H                  Xlib. New locales can be added by plugging in a locale-H                  specific shareable library and a corresponding X locale/                  database file for that locale.t  C               o  Encoding of input processing can be different fromaF                  output encodings. The output methods create a defaultG                  font set and use available font resources installed in H                  the X server. The code conversion is transparent to the                  user.  A         4.10.1.7 XSelectAsyncEvent and XSelectAsyncInput Routines                  V1.1  B               The XSelectAsyncEvent and XSelectAsyncInput routines=               allocate memory for the storage of AST delivery F               information. This memory is freed in the following ways:  D               o  If you close a display (XCloseDisplay), all the ASTI                  delivery information associated with all windows on thatG"                  display is freed.  B               o  If you destroy a window (XDestroyWindow), the AST?                  delivery information for that window is freed.i  I               The AST delivery information for subwindows is not freed by                XDestroyWindow.A  D               If you want to turn off AST notification for all event?               types within a given window and also free the ASTIC               delivery information, the client application can call G               XSelectAsyncEvent or XSelectAsyncInput passing the event_ E               mask argument equal to minus one (all bits set) and the 1               ast_routine argument equal to zero.A  I                                                                      4-39_ _  _           Programmer Release Notes
     4.10 Xlibl    0     4.10.1.8 Command Procedure Builds .PEN Files             V1.0  ?           To allow Pascal programs to inherit environment files ;           for Xlib and Motif, execute the command procedurea@           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 then           provided .PAS files.       4.10.2 Corrections  E           The following notes describe the resolution of any problemsDB           specific to Xlib that previously resulted in an error or            required a workaround.  1     4.10.2.1 UNIX Filename Emulation (Alpha Only)t             V1.2-6  =           Previously, UNIX-style filenames with embedded pathEA           syntax "../" within functions such as XtResolvePathname @           and MrmOpenHierarchy were not handled correctly. While?           this syntax is highly unusual, it can occur when both ?           the filename and the pathname contain a relative path            specification.  D           This problem has been corrected; UNIX-style filenames with6           this embedded syntax are parsed as expected.  8     4.10.2.2 XmTextField Widget Switches Focus Correctly             V1.2-6  @           A crash no longer occurs when the losingFocus callback>           peforms an XtSetValues()  on an XmTextField routine.  8     4.10.2.3 XrmoptionStickyArg Produces Correct Results             V1.2-6  @           Problems with the XrmoptionStickyArg routine have beenE           corrected; this routine no longer returns incorrect resultsg0           when referenced from the command line.       4-40 A  I      I                                                  Programmer Release NotesoI                                                                 4.10 XlibR    *         4.10.2.4 PAllHints Macro Corrected                 V1.2-6  C               The value of the PAllHints macro in XUTILS.H has beenv               corrected.  (         4.10.3 Problems and Restrictions  I               The following notes describe problems and restrictions that_(               currently pertain to Xlib.  ;         4.10.3.1 XtOpenDisplay Routine and Case Sensitivity                  V1.2-6  G               In some cases the application name in XtOpenDisplay comesvH               from argv[0], which represents the name of the application"               on the command line.  F               Be aware that case sensitivity must be preserved in suchE               environments as when referencing ODS-5 system with caseoF               preservation enabled or when passing a user-defined argv               list.F  7         4.10.3.2 Parameter/Protocol Datasize Mismatchesa                 V1.0  G               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 the I               least significant 16 bits of the parameter value. This is aiI               constraint of the field size within the X Protocol message._  F               Table 4-8 lists routine names and the longword arguments2               that are sent only as 16-bit values.  I               Table_4-8_Routine_Names_and_Arguments_Sent_as_16-Bit_Values_  I               Routine_Name_______________________Routine_Arguments_______   @               XAllocColorCells/ALLOC_COLOR_      nplanes,npixels               CELLS   B               XDrawArc/DRAW_ARC                  x,y,width,height,>                                                  angle1,angle2  I                                                  (continued on next page)e  I                                                                      4-41                 Programmer Release Notes
     4.10 XlibV    C           Table 4-8 (Cont.) Routine Names and Arguments Sent as 16-iE           __________________Bit_Values_______________________________e  E           Routine_Name_______________________Routine_Arguments_______t  8           XDrawLine/DRAW_LINE                x1,x2,x3,x4  0           XDrawPoint/DRAW_POINT              x,y  =           XDrawRectangle/DRAW_RECTANGLE      x,y,width,height   0           XDrawString/DRAW_STRING            x,y  0           XDrawString16/DRAW_STRING16        x,y  0           XDrawText/DRAW_TEXT                x,y  0           XDrawText16/DRAW_TEXT16            x,y  7           XFillArc/FILL_ARC                  x,y,width,eA                                              height,angle1,angle2g  E           XFillRectangle/FILL_RECTANGLE______x,y,width,height________l                                                 4-42 o  g                    I                                                                         5 I         _________________________________________________________________O  I                                               Documentation Release Notesb    H               This chapter describes corrections to the DECwindows Motif               documentation.  0         5.1 Getting Started With the New Desktop  D               This section contains documentation corrections to the:               Getting Started With the New Desktop manual.  *         5.1.1 File Specification Incorrect                 V1.2-5  E               A file specification for a command procedure in GettinglG               Started With the New Desktop (part number AA-QUW1A-TE) is I               incorrect. The file specification appears in Section 3.4.9,_&               paragraph 5, as follows:  C               "Optional DECwindows applications, such as DECwindows_B               Notes, may not provide any information and thereforeC               are not restarted. For such cases, there is a command_A               procedure called disk$:[user.DT]SESSIONETC.COM that B               you can use to start any applications that cannot beE               restarted automatically. This procedure is analogous tovH               the DECW$LOGIN.COM procedure in the traditional DECwindows               environment."o  0               The correct file specification is:  4               disk$:[user.DT.SESSIONS]SESSIONETC.COM  ;         5.2 DECwindows Motif for OpenVMS Applications GuideX  D               This section contains documentation corrections to theE               DECwindows Motif for OpenVMS Applications Guide manual.l    I                                                                       5-1  e              Documentation Release Notesh7     5.2 DECwindows Motif for OpenVMS Applications GuideT    @     5.2.1 Enhancing Information About the Finish Printing Option             V1.2-3  B           The section called "Printing Information" in the chapterB           on DECterm provides information about the Print menu. To@           further clarify the information in the Finish Printing&           section, note the following:  @           Selecting the Finish Printing option on the Print menuB           closes the print job and toggles Auto Print mode back to           Normal Print mode.                                                                       5-2            I                                               Documentation Release Notes I                                    5.3 Using DECwindows Motif for OpenVMSg    .         5.3 Using DECwindows Motif for OpenVMS  A               This section contains documentation corrections and D               enhancements to the Using DECwindows Motif for OpenVMS               manual.p  -         5.3.1 Using the Drag-and-Drop Featurem                 V1.2  D               The drag-and-drop feature lets you move or copy screenF               objects. For example, you can move text from buttons and!               paste it elsewhere.y  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 holdr                  Ctrl/MB2.  -                  A move or copy icon appears.4  I               3. Drag the icon to the location where you want to drop ther&                  text and release MB2.  I                  If the object is highlighted as you drag the icon acrossp>                  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 applications F               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 MaillH               has its own drag-and-drop feature; you can use MB2 to move5               messages around with the SVN interface.c  "         5.3.2 Using Tear-Off Menus                 V1.2-3  F               The DECwindows Mail application supports tear-off menus.                 V1.2  E               The DECwindows Motif applications allow you to tear offnD               pull-down and popup menus. Tear-off menus let you keepH               frequently used menus displayed without repeatedly pulling+               them down or popping them up.i  I                                                                       5-3                 Documentation Release Notese*     5.3 Using DECwindows Motif for OpenVMS               To tear off a menu:   /           1. Display a pull-down or popup menu.   =              If the menu is a tear-off menu, a dotted line is .              displayed at the top of the menu.  /           2. Click on the dotted line with MB1.<  D              The menu remains active until it is closed or until the*              parent application is closed.  #           To close a tear-off menu:O  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 Viewere             o  DECwindows Mail             o  Notepad             o  Print Screeno  @     5.3.3 Adding Target Screen Options to Application Menu Items             V1.2  B           The example "Adding Target Screen Options to Application>           Menu Items" in Using DECwindows Motif for OpenVMS is=           incorrect. To correct the problem, remove the firstd+           occurrence of the following line:g             $ select_qualifiers:  *     5.3.4 Changing the Startup Environment             V1.2  C           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/LOG   2           The code example should read as follows:  F           $ COPY SYS$COMMON:[SYSMGR]DECW$PRIVATE_APPS_SETUP.TEMPLATE -A           _$ SYS$SPECIFIC:[SYSMGR]DECW$PRIVATE_APPS_SETUP.COM/LOGq       5-4n           I                                               Documentation Release NoteslI                                    5.3 Using DECwindows Motif for OpenVMSa    +         5.3.5 Enhancing Startup PerformanceP                 V1.1  C               Extensive SYLOGIN.COM or LOGIN.COM command procedures C               slow down application startup. Many of the operations E               performed in a SYLOGIN.COM or LOGIN.COM are meaningless @               for DECwindows application startup. Therefore, theG               SYLOGIN.COM and LOGIN.COM files should be conditionalizedsB               for DECwindows application startup performance. WhenI               starting a DECwindows application, a minimum of SYLOGIN.COMi8               and LOGIN.COM commands should be executed.  E               Typically, the commands that should be executed are theEH               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.COM H               and LOGIN.COM immediately following the commands necessary               for DECwindows:a                 $ mode = f$mode() +               $ tt_devname = f$trnlnm("TT")eG               $ session_mgr_login = (mode .eqs. "INTERACTIVE") .and.  -rG                     (f$locate("WSA",tt_devname) .ne. f$len(tt_devname))gM               $ session_detached_process = (mode .eqs. "INTERACTIVE") .and. -pG                     (f$locate("MBA",tt_devname) .ne. f$len(tt_devname))yL               $ 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.l  1         5.3.6 Enhancing Hold-Screen Response Timea                 V1.1  G               If the Hold Screen key response time is too slow, add thelE               following lines to your DECW$TERMINAL_DEFAULT.DAT file:X  :               DECW$TERMINAL.main.terminal.syncFrequency: 1=               DECW$TERMINAL.main.terminal.batchScrollCount: 1x  C               Using this resource can affect the performance of theTE               DECterm window. The actual impact on performance varieswE               from site to site. You can trade off scrolling speed to_F               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.   I                                                                       5-5                 Documentation Release Notes 5     5.4 Managing DECwindows Motif for OpenVMS Systemsl    5     5.4 Managing DECwindows Motif for OpenVMS Systems)  >           This section contains documentation enhancements andB           corrections to the Managing DECwindows Motif for OpenVMS           Systems manual.        5.4.1 Global Symbols             V1.2-3  B           The following additional global symbols are available in:           the Compaq DECwindows Motif for OpenVMS product:  #           o  DECW$CONSOLE_SELECTIONw  @              Specifies how to display operator-messages options.  "           o  DECW$CONSOLE_GEOMETRY  ?              Specifies the value of the -geometry option in the 0              DECW$MESSAGEPANEL.EXE command line.  =           For information about using these symbols, refer too>           Section 3.4.1.1 in these Release Notes. Refer to theE           chapter "Using DECwindows" in Managing DECwindows Motif forrB           OpenVMS Systems for the complete list of global symbols.       5.4.2 Security Options             V1.2  C           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 double               quotation mark (")              o  Double colon (::)  @           o  A colon (:) as the final character in the node name  C           Session Manager automatically adds quotation marks to the C           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 theoC           user has already quoted the node name and does not changen
           it.        5-6d           I                                               Documentation Release NotesaI                         5.4 Managing DECwindows Motif for OpenVMS Systems     G               Within a quoted string, a double quotation mark should be H               replaced by two double quotation marks (" "). For example,I               the quoted string "DEC:.zko."my node"" should be changed to                the following:  '               ("DEC:.zko.""my node""").   *         5.4.3 Displaying a Customized Logo                 V1.1  A               By default, if there is no DECwindows Motif licensedD               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 MotifhE               license for SYSTEM, add the following definition to the ;               SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM file:D  +               $ DECW$LOGINLOGOSUB == "TRUE"s  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 RESTARTo  A               DECwindows Motif login starts the logo process as abF               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                                                                       5-7d s  r           Documentation Release Notes 5     5.4 Managing DECwindows Motif for OpenVMS Systems     /     5.4.4 Enabling and Disabling Access Controlu             V1.0  E           DECwindows Motif does not enable access control by default.ID           Instead, it uses the access control set by the server. TheA           DECwindows X11 display server enables access control at            startup time.   >           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   A           If the logical name is not defined, or if it is defined A           to some other value, such as "SERVER", DECwindows login 6           neither enables nor disables access control.  A           In most cases, it should not be necessary to define thel           logical name.a  <     5.5 DECwindows Motif for OpenVMS Guide to Non-C Bindings  >           This section contains documentation enhancements andB           corrections to the DECwindows Motif for OpenVMS Guide to           Non-C Bindings.   "     5.5.1 GET_CHAR_STRUCT Function             V1.2-3  E           The access related to the char_struct argument for the XLIBaA           GET_CHAR_STRUCT function is incorrectly documented. The "           correct access is write.  A     5.6 VMS DECwindows Guide to Xlib (Release 4) Programming: VAX          Bindingi             V1.2  B           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) / 2g       5-8_           I                                               Documentation Release NotesLI     5.6 VMS DECwindows Guide to Xlib (Release 4) Programming: VAX Binding     1               The example should read as follows:n  E               WINDOW_1X = (X$WIDTH_OF_SCREEN(SCREEN) - WINDOW_1W) / 2xF               WINDOW_1Y = (X$HEIGHT_OF_SCREEN(SCREEN) - WINDOW_1H) / 2  F               Example 3-1 in the VMS DECwindows Guide to Xlib (ReleaseF               4) Programming: VAX Binding is incorrect. To correct the6               problem, change the following two lines:  M               WINDOW_1X = (X$DISPLAY_WIDTH_OF_SCREEN(SCREEN) - WINDOW_1W) / 2nN               WINDOW_1Y = (X$DISPLAY_HEIGHT_OF_SCREEN(SCREEN) - WINDOW_1H) / 2  1               The example should read as follows:   J               WINDOW_1X = (X$DISPLAY_WIDTH_OF_SCREEN(DPY) - WINDOW_1W) / 2K               WINDOW_1Y = (X$DISPLAY_HEIGHT_OF_SCREEN(DPY) - WINDOW_1H) / 2x  *         5.7 DECwindows Extensions to Motif  >               This section lists documentation corrections andA               enhancements for the DECwindows Extensions to Motif                document.   4         5.7.1 DXmNlayoutDirection Resource Constants                 V1.2-3  F               The section on DXmNlayoutDirection Resource in Chapter 2,               lists the following constants:  $               o  DXmLAYOUT_LEFT_DOWN  "               o  DXmLAYOUT_LEFT_UP  %               o  DXmLAYOUT_RIGHT_DOWN_  #               o  DXmLAYOUT_RIGHT_UP   A               Note that the following constants are not currently =               available for the DXmNlayoutDirection resource:   "               o  DXmLAYOUT_LEFT_UP  #               o  DXmLAYOUT_RIGHT_UPt  C               The introduction to Table 2-1 is incorrect. Table 2-1tG               describes the effect of the constants DXmLAYOUT_LEFT_DOWN 8               and DXmLAYOUT_RIGHT_DOWN on the functions.                 V1.2  I                                                                       5-9i t  N           Documentation Release Notes &     5.7 DECwindows Extensions to Motif    >           In Section 2.2 of the DECwindows Extensions to MotifC           manual, the description of DXmChildren indicates that theDA           routine can be used to learn the length of widget_list.d  C           The documentation is incorrect. The sentence should read, E           "You can use the DXmNumChildren routine to learn the lengtht6           of the widget list returned by DXmChildren."  9     5.8 DECwindows Motif Guide to Application Programming   :           This section lists documentation corrections andD           enhancements for the DECwindows Motif Guide to Application           Programming manual.e  ?     5.8.1 UIL Source Code for the OpenVMS DECburger ApplicationE             V1.2-3  =           The introduction to the section in Chapter 4 called ?           "Creating the Help Widget with UIL", which introduces A           Example 4-6, "UIL Help Widget Implementation," does not A           clearly state that the complete UIL source code for the D           OpenVMS DECburger application is included in DECW$EXAMPLES           on OpenVMS systems.i  )     5.8.2 Help Widget Implementation Codeo             V1.2-3  D           In the title of Example 4-7, "Help Widget Implementation-CD           Language Module", DECBURGER.C should be added to the title           as follows:e  7           "Help Widget Implementation-C Language Modulen           (DECburger.C)"  .     5.8.3 Help Widget Implementation-Callbacks             V1.2-3  :           The title of Example 4-8 should read as follows:  <           "Help Widget Implementation-Callbacks (DECburger.C           continued)"        5-10           I                                               Documentation Release Notes I                     5.8 DECwindows Motif Guide to Application Programming3    1         5.8.4 Using UIL to Create the Help Widgets                 V1.2-3  G               The title of Section 4.10, "Using the Toolkit Help WidgetnI               Creation Routine," does not accurately reflect the contents C               of this section. The title should read, "Using UIL tom&               Create the Help Widget".  F               The introductory paragraph to Example 4-9 in the sectionH               called "Using the Toolkit Help Widget Creation Routine" isE               incomplete. The information should state the following:o  H               "The code in Example 4-9 is included in DECburger.C but isI               commented and will not be compiled when the example programo               is built."  D               The implementation in this example is not complete; it?               requires some sections from Examples 4-7 and 4-8.y  H               To summarize, the documentation should state the following               information:  E               o  Examples 4-6 and 4-7 are UIL code (DECburger.UIL(D)) ?                  that, when combined, create the DECburger.EXE.e  9               o  Example 4-8 is C code for DECburger.EXE.   =               o  Example 4-9 is C code for a Toolkit example.M                                I                                                                      5-11t                         I                                                                         AeI         _________________________________________________________________   I                                       OSF/Motif Release 1.2 Release Notes     G               The release notes in this document are based on Chapter 3 H               of the OSF/Motif Release Notes for Release 1.2 and 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 discussaE               performance improvements and information about backward                compatibility.  @               These release notes support the OSF/Motif softwareE               currently provided with the Compaq DECwindows Motif fore               OpenVMS product.  $         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 aCG               minimum, to not allow it to degrade below the performancee'               of OSF/Motif Release 1.1.   :               Performance testing was done in three areas:  -               o  Aspects obvious to end usersm  !               o  Data space usage                  o  Memory leakagee  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.tG               A significant improvement was made for scrolling inside a H               Scrolled Text region that contains a large amount of test.  D               Data space usage has improved throughout the OSF/MotifG               Toolkit, particularly for the Text widget. In some cases, B               data space usage has been reduced by as much as 40%.H               Also, the memory used for the text in a Text widget is now  I                                                                       A-1e p  i      '     OSF/Motif Release 1.2 Release NotesS      A.1 Performance Improvements    C           correctly reduced when that text is replaced by a smallerO           amount of text.a  C           Memory leakage has been reduced to a minimum for multipleWC           creates and destroys of all Toolkit widgets. Although theWA           Motif tests showed small memory leaks, the OSF believes ?           that this amount of memory is required as part of the 9           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-n=           time compatibility as well as visual and behavioralO           compatibility.  -     A.2.1 Visual and Behavioral Compatibilityn  ;           The OSF ran automated tests that compared current C           visuals with those recorded using OSF/Motif Release 1.1.4oE           libraries. Once all differences between the Release 1.2 andtE           Release 1.1.4 versions were accounted for, the visuals wereEB           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 and >           behaviorally compatible with Release 1.1.4. However,@           they have made extensive improvements to the Traversal@           and Geometry Management algorithms that result in some?           differences between those versions. These differences @           reflect efforts to fix defects in the earlier release.  D           For example, one such modification involves the new policyA           in which an initial size set for a manager widget in an A           application is now honored by the Toolkit. In OSF/Motifn>           Release 1.1, applications set the initial size for aA           manager widget, but did not, in fact, use that size. In ?           Release 1.2, Motif now uses that size setting and theL0           initial layout is changed accordingly.         A-2S e  e      I                                       OSF/Motif Release 1.2 Release NotessI                    A.3 Changes and New Features for OSF/Motif Release 1.2R    >         A.3 Changes and New Features for OSF/Motif Release 1.2  G               This section summarizes changes and new features that theuI               OSF has made to OSF/Motif Release 1.2. Detailed informationhA               about these modifications is contained in the MotifvD               reference pages and the Motif Release 1.2 revisions of               following books:  &               o  OSF/Motif Style Guide  -               o  OSF/Motif Programmer's Guiden  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 Releaset.               1.1 are obsolete in Release 1.2:                    ExtObject.h                  Traversal.h                  VaSimple.hm                  VendorE.h                  VendorEP.hi  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 Translations$  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 nowoG               make incorrect assumptions for certain keyboards, such as I               those that have the arrow keys defined in the keypad. Otherx;               Motif applications might be affected as well.h  G               You can avoid this problem by creating a file to redefine I               the bindings for the keys in question and then passing that"*               file to the xmodmap utility.  I                                                                       A-3s    a      '     OSF/Motif Release 1.2 Release Notes :     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 definitionsaE           allow the application to use modifiers with the arrow keys.              !            ! Always force:            !   KP_2 = Down            !   KP_8 = Upw           !   KP_4 = Left            !   KP_6 = Right           keycode 120 = Down           keycode 76  = Up           keycode 98  = Left           keycode 100 = Rightm       A.3.3 ANSI C Compliances  C           All references to caddr_t have been changed to XtPointer.lA           This change affects all callback routines and any other C           routines that reference caddr_t. The OSF made this changeyC           so that OSF/Motif Release 1.2 would be compliant with thei           ANSI C specification.C  *     A.3.4 Display and Screen Specific Data  E           Motif now has an XmDisplay object that supports per-displaydD           data and resources. An XmScreen object has been added that1           supports per-screen data and resources.        A.3.5 Drag and Drop   C           OSF/Motif Release 1.2 supports the drag and drop metaphor C           for data interchange. The drag-and-drop specification has D           been fully implemented. See the Release 1.2 version of theB           OSF/Motif Programmer's Guide for information on the drag           and drop interface._  C              ________________________ Note ________________________   A              If you want to use Btn2 to have pop-up menus pop up, B              drag and drop will not function properly. You need to5              disable drag and drop in such instances.   C              ______________________________________________________        A-4  s         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 theeC               display area for subsequent selections. Each tearableeG               menupane is a tear-off button. When the mouse drag button G               is pressed on the tear-off button, the pane tears off and H               can be dragged and then placed by releasing the mouse dragH               button. The window manager surrounds the tear-off menupaneG               with a menu button and a title. Shifting focus to a torn-,G               off menu's windowpane follows the standard window managerX               policy.e  I               Tear-off behavior is enabled by setting the XmNtearOffModeliI               resource to XmTEAR_OFF_ENABLED. (The default is XmTEAR_OFF_i               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 XmNtearOffModeleF               resource using the XmRepTypeInstallTearOffModelConverter               function.o  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,sG               if a tear-off menu is mapped, the sensitivity of its menu B               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 innE               operations being enabled at unexpected times. If a user D               activates one of these menu items, the application can<               crash or the persistent data can be corrupted.  !         A.3.7 Insensitive 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:.                    XmArrowButton                  XmList                   XmScrollBar                  XmTextf  I                                                                       A-5  x         '     OSF/Motif Release 1.2 Release NotesE:     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-dimensionalR              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.n  C           o  Motif now adds a location cursor to surround all itemsxC              in a List whenever a List widget has the focus and theo2              current keyboard item is not visible.  C           o  There are minor layout differences because of fixes int!              geometry management.w       A.3.9 Titles for Frames   B           In OSF/Motif Release 1.2, you can specify a Title widget@           in a Frame widget. The release has added the followingB           new constraint resources for specifying the position and.           alignment of the title in the Frame:  (              XmNchildHorizontalAlignment&              XmNchildHorizontalSpacing              XmNchildType &              XmNchildVerticalAlignment       A.3.10 Audible Warning  @           The VendorShell has a new resource, XmNaudibleWarning,D           that can specify whether an audible cue should accompany aD           warning message. Text widgets determine the value for this7           resource from the value of XmNaudibleWarning.            A-6  w  o      I                                       OSF/Motif Release 1.2 Release Notes I                    A.3 Changes and New Features for OSF/Motif Release 1.2h    !         A.3.11 Color Enhancementsa  B               The following three resources have been added to theC               XmScreen widget so that users can specify the defaultiE               background color and thresholds for shadow calculation:e  "                  XmNlightThreshold!                  XmNdarkThresholda'                  XmNforegroundThresholdc  I               Motif has added the XmChangeColor function that changes theuA               background and other colors for a specified widget.   !         A.3.12 Baseline Alignment   G               Motif has added two functions for baseline alignment. TheoF               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 Sete  C               In OSF/Motif Release 1.2, you can use more widgets to G               support traversal using the keyboard. For example, insideaG               a tab group, users can now use the arrow keys to traversetF               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 tab4               group.  -         A.3.14 Two-Dimensional Menu Traversall  G               With OSF/Motif Release 1.2, the left, right, up, and down I               traversal arrows now navigate within a menupane. The up and F               down arrow keys wrap between columns. The right and leftE               arrow keys post the previous or next menupane when they1E               are pressed in the rightmost and leftmost column of thep%               menupane, respectively.e           A.3.15 Input Focus  A               OSF/Motif Release 1.2 has added the XmNinitialFocus D               resource to the Manager class. This resource specifiesH               the first widget to receive input focus. This resource canH               only specify a widget; it is ignored for all pop-up menus,:               menubars, option menus, and pull-down menus.  I                                                                       A-7            '     OSF/Motif Release 1.2 Release Notesx:     A.3 Changes and New Features for OSF/Motif Release 1.2    %     A.3.16 Traversal Access Functionsp  E           OSF/Motif Release 1.2 has added the following new functionsy@           to support better interaction with keyboard traversal:                XmGetFocusWidgett              XmGetTabGroup              XmGetVisibility              XmIsTraversable              XmIsVisible  C           The XmTrackingLocate function has been modified to do thee           following:  7           o  Field all events, not just a button press.p  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 that_.           it returns a pointer to the X event.       A.3.17 Virtual Keys   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.d  0           Motif defines two new virtual keysyms:                osfPageLeft              osfPageRightc  @           You must have the X11 Release 5 XKeysymDB installed inC           /usr/lib/X11 to use these new virtual keys. Otherwise youfC           get a warning message on application startup. Specify theo6           following information in the XKeysymDB file:  #           osfPageLeft     :1004FF40   #           osfPageUp       :1004FF41i  #           osfPageDown     :1004FF42   #           osfPageRight    :1004FF43r  ?           To comply with the OSF/Motif Style Guide, the defaulto>           binding for osfMenu has been changed from <key>F4 to           Shift<key>F10.       A-8     i      I                                       OSF/Motif Release 1.2 Release NotestI                    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 warning G               messages, add the hp prefix as follows to the appropriate                 lines in the file:  3               osfDelete :         <key>hpDeleteChara  3               osfInsert :         <key>hpInsertChar   3               osfPrimaryPaste :   <key>hpInsertLines  3               osfQuickPaste :     <key>hpDeleteLinea  G               OSF/Motif Release 1.2 has a new client, xmbind, that setswD               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 xmbind E               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 individualiA               vendors. If there is no .motifbind file in the homekE               directory, you can use the xmbind.alias file to provideaI               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 fore,               managing representation types:  "                  XmRepTypeRegister$                  XmRepTypeAddReverse$                  XmRepTypeValidValue'                  XmRepTypeGetRegisteredb                  XmRepTypeGetIdh%                  XmRepTypeGetNameList #                  XmRepTypeGetRecord   C               These functions are useful for developers who want to G               define new resource converters that use an enumerated set                of values.  I                                                                       A-9g l  e      '     OSF/Motif Release 1.2 Release Notesu:     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.i  E           If your application has a default button associated with anmA           XmBulletinBoard, pressing Return (except in a multilineo?           XmText), Ctrl/Return, or the key bound to osfActivate A           while the focus is in the XmBulletinBoard now activates            the default button.e  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 enable ?           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 timef              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  usePPositionp  >              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 withineC              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 ________________________h  @              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.u  @           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                    I                                                                         BnI         _________________________________________________________________   I                                             OSF/Motif Toolkit Information     =               This appendix contains information about notes, D               restrictions, and corrections related to the OSF/Motif0               and DECwindows OSF/Motif Toolkits.  I         B.1 OSF/Motif Release 1.2.2 and X11 Release 5 Shareable Librariesu                 V1.2  A               Because the OSF/Motif Release 1.2.2 Toolkit and the H               OSF/Motif Release 1.1.3 Toolkit are not binary compatible,C               applications must link with one toolkit or the other.SI               Applications based on OSF/Motif Release 1.2.2 can only linkdF               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/MotifaI               Release 1.1.3-based shareable libraries, the Release 1.1.3-nG               based libraries have the same file names as in DECwindows F               Motif Version 1.1, and the Release 1.2.2-based libraries6               contain a suffix of either "R5" or "12".  E               Shareable libraries that work with either the OSF/Motif B               Release 1.1.3 Toolkit or the OSF/Motif Release 1.2.2B               Toolkit do not have a suffix. These libraries are as               follows:                 V1.2-6                 o  CDA$ACCESS.EXE   $               o  DECW$D2DXLIBSHR.EXE  $               o  DECW$XEXTLIBSHR.EXE  !               o  DECW$XLIBSHR.EXEe                 o  XIE$SHRLIB.EXE   I                                                                       B-1i l         !     OSF/Motif Toolkit InformationeE     B.1 OSF/Motif Release 1.2.2 and X11 Release 5 Shareable Libraries.    D           Shareable libraries that are linked with Release 5 (R5) ofB           the Xt Toolkit have a suffix of "R5". Libraries based onD           the XUI Toolkit have no R5 equivalent libraries and shouldE           not be included in a linker options file based on X11 R5 or D           OSF/Motif Release 1.2.2. Table B-1 lists these file names.  C              ________________________ Note ________________________   ;              The DECW$XLIBSHR.EXE file is the MIT Release 5n<              version, not the MIT Release 4 version of Xlib.  C              ______________________________________________________a  E           Table_B-1_Names_of_Shareable_Libraries_Based_on_R5_________e  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____________t  ;           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 onlyoA           with libraries compatible with R5 and OSF/Motif Releasel2           1.2.2. Table B-2 lists these file names.  C           Table B-2 Names of Shareable Libraries Based on OSF/Motif E           __________Release_1.2.2____________________________________   E           Names of Files Based on     Names of Files Based on Release E           Release_1.1.3_______________1.2.2__________________________r  8           DDIF$VIEWSHR.EXE            DDIF$VIEWSHR12.EXE  7           DECW$BKRSHR.EXE             DECW$BKRSHR12.EXEl  E                                              (continued on next page)        B-2C e  t      I                                             OSF/Motif Toolkit Information I         B.1 OSF/Motif Release 1.2.2 and X11 Release 5 Shareable LibrariesA    E               Table B-2 (Cont.) Names of Shareable Libraries Based onlI               __________________OSF/Motif_Release_1.2.2__________________V  I               Names of Files Based on     Names of Files Based on Release I               Release_1.1.3_______________1.2.2__________________________   >               DECW$DXMLIBSHR.EXE          DECW$DXMLIBSHR12.EXE  <               DECW$MAILSHR.EXE            DECW$MAILSHR12.EXE  >               (None)                      DECW$MRMLIBSHR12.EXE  0               DECW$PRINTWGTSHR.EXE        (None)  @               DECW$TERMINALSHR.EXE        DECW$TERMINALSHR12.EXE  =               DECW$XMLIBSHR.EXE           DECW$XMLIBSHR12.EXEe  ;               DGIT$LIBSHR.EXE             DGIT$LIBSHR12.EXEe  :               IMG$SHRLIB.EXE              IMG$SHRLIB12.EXE  :               LWK$DXMSHR.EXE              LWK$DXMSHR12.EXE  I               XNL$SHR.EXE_________________XNL$SHR12.EXE__________________c  G               There is no DECW$PRINTWGTSHR12.EXE file; the Print Widget 7               is part of the DECW$DXMLIBSHR12.EXE file.   H               The DECW$MRMLIBSHR12.EXE file is a new image that includesF               Motif Resource Manager (Mrm) routines that were formerlyF               part of the DECW$XMLIBSHR.EXE file. Any program based onG               OSF/Motif Release 1.2.2 that calls Mrm routines to accesss7               .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:x  *               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:u  *               SYS$SHARE:DECW$XLIBSHR/SHARE-               SYS$SHARE:DECW$XTLIBSHRR5/SHAREn-               SYS$SHARE:DECW$XMLIBSHR12/SHARE<.               SYS$SHARE:DECW$MRMLIBSHR12/SHARE.               SYS$SHARE:DECW$DXMLIBSHR12/SHARE  I                                                                       B-3  1         !     OSF/Motif Toolkit InformationeE     B.1 OSF/Motif Release 1.2.2 and X11 Release 5 Shareable Libraries     B           These changes eliminate the reference to the XUI Toolkit@           (DECW$DWTLIBSHR.EXE) and links with the Motif Resource)           Manager (DECW$MRMLIBSHR12.EXE).   ;     B.2 OSF/Motif Release 1.1.3 Programming Support and XUIi             V1.2-3             Restrictions             o  Problem:e  A              You will encounter problems if you save the previous_@              (Release 1.1.3) programming environment and attempt?              to run an OSF/Motif Release 1.1.3 (Xlib Release 4)dB              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 wheresC              OSF/Motif Release 1.1.3 is installed, the result is ans(              ident mismatch fatal error.  =              In addition, the OSF/Motif Release 1.1.3 and the D              Release 1.2.2 files produce different output; they haveC              different structures and are therefore not compatible. D              Use the appropriate UIL compiler to produce the correct              UID file.             o  Resolution:  ;              1. Rename the DECwindows Motif Version Version >                 1.1 executable compiler, DECW$UILMOTIF.EXE, to=                 DECW$UILMOTIF113.EXE and keep the file in thee@                 SYS$COMMON directory. By doing this, the name ofB                 the new Version 1.2-3 compiler, DECW$UILMOTIF.EXE,=                 does not conflict with the previous compiler.   B              2. Copy the DECW$XLIBSHR.EXE file (Xlib Release 4) to;                 the SYS$COMMON:[SYSEXE.DECW$113] directory.   E                 The Xlib Release 5 version of Xlib has the same name; E                 however, a logical name is defined to use the Release C                 4 version when the programs are linked. The changes E                 in minor ident of DECW$XLIBSHR.EXE between DECwindows B                 Motif Version 1.1 and DECwindows Motif Version 1.2       B-4c n  t      I                                             OSF/Motif Toolkit InformationMI                   B.2 OSF/Motif Release 1.1.3 Programming Support and XUI     G                     for OpenVMS caused a loss of backward compatibilityl>                     with DECwindows Motif Version 1.1 systems.                                                                                      I                                                                       B-5            !     OSF/Motif Toolkit Information ;     B.2 OSF/Motif Release 1.1.3 Programming Support and XUIl    @              3. If you save the previous programming environmentC                 during installation, create the following two filesoA                 and copy them to the SYS$COMMON:[SYSEXE.DECW$113]c                 directory:  *                 -  DECW$UILCOMPILER113.CLD  A                    This file enables UIL/OSF Motif and UIL/XUI tosE                    function for either XUI or OSF/Motif Release 1.1.3iC                    if you select DECW$UILMOTIF113.EXE for OSF/MotifhA                    Release 1.1.3 or DECW$UILCOMPILER.EXE for XUI.   .                 -  DECW$DEFINE113_LOGICALS.COM  D                    This file points to the saved header files, whichE                    in turn point to the Xlib Release 4 version of thee)                    DECW$XLIBSHR.EXE file.   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 is E                 linked on a VMS Version 5.4-3 system must be run on ao5                 VMS Version 5.4-3 (or higher) system.   >                 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.a             V1.2  D           The X Window and OSF/Motif libraries that are shipped with?           DECwindows Motif Version 1.2 for OpenVMS software are A           incompatible with those shipped with previous versions.M<           Run-time compatibility has been preserved, but the4           programming environment is not compatible.  C           Programming in the XUI or Motif Release 1.1.3 environment C           that is provided in previous versions of DECwindows MotifeD           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 existbA           on your system. If you choose to save these programming.?           files, they are moved to subdirectories where you canoE           access them for programming. Specifically, the installationaB           creates a subdirectory called [.DECW$113] in each of the@           directories listed in Table B-3 and moves the previous*           files into the new subdirectory.       B-6w    d      I                                             OSF/Motif Toolkit Information I                   B.2 OSF/Motif Release 1.1.3 Programming Support and XUI     ?               For more information about saving the programmingeE               files, see the DECwindows Motif Version 1.2 for OpenVMSw!               Installation Guide.i  I               Table B-3 Directories for Previous XUI or Motif Programming I               __________Environment______________________________________y  I               Directory_____Contents____New_Location_____________________t  K               DECW$INCLUDE  C header    SYS$SYSROOT:[DECW$INCLUDE.DECW$113]t!                             filess  E               SYS$SYSTEM    UIL         SYS$SYSROOT:[SYSEXE.DECW$113]r$                             compiler  E               SYS$LIBRARY   Non-C       SYS$SYSROOT:[SYSLIB.DECW$113]a$                             languageI               ______________bindings_____________________________________   F               To program with these files, include the new [.DECW$113]G               subdirectories in the search path for each of the logical 8               names. For example, perform the following:  B               o  Change the definition of DECW$INCLUDE as follows:  ,                  $ SHOW LOGICAL DECW$INCLUDEV                     "DECW$INCLUDE" = "SYS$SYSROOT:[DECW$INCLUDE]" (DECW$LOGICAL_NAMES)B                          = "SYS$SYSROOT:[DECW$INCLUDE.EXTENSIONS]"  K                  $ DEFINE/EXECUTIVE/TABLE=DECW$LOGICAL_NAMES DECW$INCLUDE - 8                   SYS$SYSROOT:[DECW$INCLUDE.DECW$113], -/                   SYS$SYSROOT:[DECW$INCLUDE], -c7                   SYS$SYSROOT:[DECW$INCLUDE.EXTENSIONS]t  H               Place the new [.DECW$113] subdirectory first in the searchF               list, since many of the files that have been updated forD               this release have the same name as the files that wereG               moved to the [.DECW$113] subdirectory. Thus, the files in <               [.DECW$113] are used for software development.  1               If DECW$INCLUDE is redefined in theeH               SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM command procedure,@               then modify the previous instructions accordingly.    I                                                                       B-7            !     OSF/Motif Toolkit Information/;     B.2 OSF/Motif Release 1.1.3 Programming Support and XUI     E           To use the UIL compiler for XUI or OSF/Motif Release 1.1.3, &           perform the following steps:  !           1. Create a file called C              SYS$SYSROOT:[SYSEXE.DECW$113]DECW$UILCOMPILER.CLD thatl)              contains the following text:o  '              define type trace_keywordso               keyword tokens               keyword symbols_  )              define type warning_keywords                 keyword nowarnings&               keyword noinformationals  )              define type version_keywordss(               keyword V1, syntax=xui_uil1               keyword V2, syntax=xui_uil, default /               keyword MOTIF11, syntax=motif_uil_  "              define syntax xui_uil$               image decw$uilcompiler  $              define syntax motif_uil!               image decw$uilmotifu                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,n,                value(type=version_keywords),                nonnegatablegB               qualifier XUI, default, nonnegatable, syntax=xui_uil=               qualifier MOTIF, nonnegatable, syntax=motif_uils  C               qualifier widget_meta_description, label=widget_qual, ;                value(required, noconcatenate, type=$infile)        B-8            I                                             OSF/Motif Toolkit Information_I                   B.2 OSF/Motif Release 1.1.3 Programming Support and XUI     (                   disallow XUI and MOTIF  I               2. Set the DCL command table to use the XUI UIL compiler aso                  follows:   P                  $ SET COMMAND SYS$SYSROOT:[SYSEXE.DECW$113]DECW$UILCOMPILER.CLD  F                 ________________________ Note ________________________  F                 If you want to revert back to the previous UIL command:                 definition, execute the following command:  >                 $ SET COMMAND SYS$LIBRARY:DECW$UILCOMPILER.CLD  F                 ______________________________________________________  (         B.3 DECwindows OSF/Motif Toolkit  <               This section contains information about notes,H               restrictions, and corrections for the DECwindows OSF/Motif               Toolkit.  :         B.3.1 Callable OSF/Motif UIL Compiler (Alpha Only)                 V1.2-6  E               The OSF/Motif Release 1.2.2 Toolkit contains a callable F               User Interface Language (UIL) compiler. You can now linkH               against this image by including the following in your link               options:  )               SYS$SHARE:DECW$UILSHR/SHAREs  C               For information about the callable interface, see the F               OSF/Motif Programmer's Guide published by Prentice Hall.  ,         B.3.2 Motif Text Widget Translations                 V1.0  G               To implement virtual bindings, it is necessary for Compaq:F               to modify the default XmText and XmTextField translationH               manager syntax. Specifically, the following syntax line is               removed:  F               Shift ~Ctrl ~Meta ~Alt <Key>osfDelete:   cut-clipboard()  I                                                                       B-9  l         !     OSF/Motif Toolkit Information.$     B.3 DECwindows OSF/Motif Toolkit    A           If you use virtual bindings in which the osfCut virtual(:           keysym is not bound, no key sequence is bound to=           the cut-clipboard action by default. To work around >           this limitation, override the XmText and XmTextField7           translations in your DECW$XDEFAULTS.DAT file.        B.3.3 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 applications B           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 have D           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 IntrinsicssA           Release 3 semantics of the Intrinsics. However, as soono?           as that application relinks (or dynamically activatese?           DECW$DWTLIBSHR), it uses the MIT X Toolkit Intrinsicsr0           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?           to follow it. However, the intent is to add code thata=           allows existing executable images to run unchanged./           B-10 _  _      I                                             OSF/Motif Toolkit InformationoI                                          B.3 DECwindows OSF/Motif Toolkit_    <         B.3.3.1 Restrictions on Mixing Motif and XUI Widgets                 V1.0  E               Mixing Motif and XUI widgets is restricted. The problemnF               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 compatibilityLF               with DECwindows XUI. If an application is linked againstG               Motif, the Motif Vendor Shell widget class is used. Motif E               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 (using G               LIB$FIND_IMAGE_SYMBOL) a shareable image that uses Motif. H               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 logicalOE               name contains a comma-separated list of image names for:E               which the toolkit is to use the Motif Vendor Shell. The H               value of DECW$USE_XM_VENDOR_SHELL logical name defaults toG               NOTES$MAIN. To add additional image names to this logicall(               name, enter the following:  =               $ DEFINE DECW$USE_XM_VENDOR_SHELL "NOTES$MAIN,-u+               _$ yourimage1,yourimage2,..."E  @               Note that DECW$USE_XM_VENDOR_SHELL does not affectF               applications that use Motif since they are already using%               the Motif Vendor Shell.I  B         B.3.4 Compile-Time Incompatibilities in Motif Header Files                 V1.2-3  I               Several macro definitions are removed from the Motif header.E               files in the OSF/Motif programming support. The changesl0               affect the following header files:  #               o  DECW$INCLUDE:XMP.Hh  7                  The following definitions are removed:   9                  -  #define XmLONGBITS sizeof(Cardinal)*8U  9                  -  #define XmHALFLONGBITS (XmLONGBITS/2)   I                                                                      B-11i _         !     OSF/Motif Toolkit Informationv$     B.3 DECwindows OSF/Motif Toolkit    C              These macros are replaced in the same header file witha!              the following macro:V                -  XmOFFSETBITS  <              Update the code to call the XmOFFSETBITS macro.  !           o  DECW$INCLUDE:TEXTP.Ht  3              The following definitions are removed:o  )              -  #define MAXINT 214748364729                 /* Biggest number that can fit in long */a  &              -  #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 constanta  "     B.4 OSF/Motif Example Programs  ?           This section describes example programs from the Openo<           Software Foundation (OSF) that are included in the<           DECwindows Motif Version 1.2 for OpenVMS software.  '     B.4.1 Cut and Paste Example ProgramD             V1.2  C           This example demonstrates the use of the Motif Clipboard.E@           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.   !     B.4.2 DNDDemo Example Program              V1.2  E           This example illustrates a typical use of the drag-and-drop            feature.       B-12 1  d      I                                             OSF/Motif Toolkit InformationeI                                            B.4 OSF/Motif Example Programs     F               When the example starts, it does not have any valid dropG               sites. It starts with different color rectangles that act H               as drag sources for dragging the colors around. Create the$               drop sites as follows:  C               o  Move the pointer into the drawing area (with white                   background).m  I               o  Press MB1 and drag. You see the "rubber-banding" effect.c  ?               o  Release MB1 after dragging a desired distance.s  B                  A black rectangle appears. You can create as many(                  rectangles as you like.  E               The rectangles inside the drawing area that you created F               act as valid drop sites for colors. You can test this byE               initiating the drag from the yellow color rectangle andrG               dragging over to one of the rectangles inside the drawingt%               area and releasing MB2.   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.S  ;               While you are dragging, notice the following:E  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 thereeF                  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 withEC               the pointer over any part of the drawing area outsidepD               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 youFH               attempted failed. If you release MB2 with the pointer overE               any of the rectangles inside the drawing area, the drageF               icon disappears into the background; this indicates thatE               the drop was a success. The rectangle on which the drop   I                                                                      B-13     t      !     OSF/Motif Toolkit Informationi"     B.4 OSF/Motif Example Programs    B           was attempted, becomes filled in with the color that was           dragged.  E           The rectangles inside the drawing area act as drag sources.sB           Initiate the drag with the pointer on any rectangle, and?           the cursor changes to a rectangle (either of the samet?           size or a smaller size depending on the X cursor sizeiB           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 timeSA           you attempt the drop (Ctrl is the modifier key for copy C           in the current implementation). When you drag a rectangleiE           with no modifier key pressed or with the Shift key pressed,nB           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 untilt@           you press the Ctrl key, which changes the operation to@           Copy. At that time it regains its original solid form.  C              ________________________ Note ________________________Y  @              During dragging you can cancel the drag by pressingC              the Cancel key (F11). Also, you can press the Help key3C              to get information about whether the drop will succeed_*              and possible drop operations.  C              ______________________________________________________$       B.4.3 Dogs Example Program             V1.1  D           This example uses the dog and square widgets. It shows howE           to incorporate new widgets into the UIL source by using thea            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().$       B-14 3  -      I                                             OSF/Motif Toolkit Information:I                                            B.4 OSF/Motif Example Programsr             B.4.3.1 Dog Widget                 V1.1  H               The dog widget (DogWidget) demonstrates how to subclassifyD               a primitive widget that remains binary compatible withF               future versions of Motif. It uses XmResolvePartOffsets():               and associated macros and implements all theB               recommendations in the XmResolvePartOffsets manpage.  F               The dog widget is a subclass of XmPrimitive. It can barkE               and wag its tail. If you want more advanced tricks, you I               must subclassify it, or replace up.bm, down.bm, and bark.bmm)               with more advanced bitmaps.g  9               The dog widget has the following resources:e  C               o  DogNwagTime: Time in milliseconds between each wag   G               o  DogNbarkTime: Time in milliseconds the bark graphic isE                  displayed  E               o  DogNbarkCallback: Callback called by the bark actionf  <               The dog widget has the following translations:  4               o  osfActivate/Return/Space/MB1 = Bark  !               o  W/MB2 = Wag tailo  0               o  S/Shift-MB2 = Stop wagging tail                 o  osfHelp = Helpy           B.4.3.2 Square Widget                  V1.1  ?               The square widget (SquareWidget) demonstrates how =               to subclassify a constraint widget that remainsl>               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.k  I                                                                      B-15,           !     OSF/Motif Toolkit Informationr"     B.4 OSF/Motif Example Programs    C           The square widget has the resource SquareNmajorDimension.)>           This resource determines which dimension is used for>           the new size of the child. Values are SquareWIDTH or           SquareHEIGHT.)  7           The square widget has the constraint resourceuA           SquareNmakeSquare. This resource determines whether thenE           child is forced to be square or set to its preferred shape.x  "     B.4.4 Helloint Example Program             V1.2  D           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.   <           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 namefA           LANG or the xnlLanguage resource to set the locale. Set$C           the LOCALSTRINGS suffix and the locale name to one of theN           following:  E           ___________________________________________________________cE           Locale______Interface_Type_________________________________              Japan       Kanji$             Hebrew      Hebrew             French      French  E           English_____Standard_English_______________________________f  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:       B-16 6         I                                             OSF/Motif Toolkit Information I                                            B.4 OSF/Motif Example Programs   I               ___________________________________________________________iI               Locale____Font_Name________________________________________o  H               French    -adobe-helvetica-medium-r-normal-12-120-75-75-p-$                         67-iso8859-1  I               English   -adobe-times-medium-r-normal-14-100-100-100-p-74- !                         iso8859-1b  F               Hebrew    -Misc-Fixed-Medium-R-Normal-13-120-75-75-C-80-!                         ISO8859-8   *               Japan     -*-JISX0208.1983-1  I               __________-*-JISX0201.1976-0_______________________________r  F               If you do not have these fonts installed on your system,E               either change the UIL files to reference other fonts orSH               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.h  (         B.4.5 Hellomotif Example Program                 V1.2  H               This example is a simple UIL/Xm program with a label and a               push button.  '         B.4.6 Motifanim Example Program                  V1.1  H               The motifanim program demonstrates the following OSF/Motif               features:n  E               o  Declaration of icon/bitmap using UIL for portabilityW                  across visualsm  >               o  Exchange of value between UIL and C using Mrm  -               o  Use of the Motif form widget   I               o  Background procedure running while the client process isa:                  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                                                                      B-17e t         !     OSF/Motif Toolkit Information "     B.4 OSF/Motif Example Programs    A           The syntax of all the animation.uid files can add a newTB           set of pixmaps to be animated using motifanim. Some tree3           examples of animation data files include:D                dog.uil              plane.uil  C           The default animation is dog. To run the example with the 7           other animations, use the following commands:c  %           $ SET DEFAULT DECW$EXAMPLES 3           $ motifanim := "$DECW$EXAMPLES:motifanim"h!           $ motifanim -anim planel  E           The files motiflogo.uil, motifanim.uil, and motifanim.c are -           the core components of the program.e  ,     B.4.7 Motifgif and Pict Viewing Programs             V1.2  0           The following .gif files are provided:  ?           o  TOUCAN.GIF, which is a picture of a tropical bird.   D           o  CHALLENGER.GIF, which is a picture of the space shuttle              Challenger.             V1.1  A           The motifgif and pict programs work together to displayeA           a .gif formatted picture. The motifgif program displayscC           a .gif file within Motif constructs. The motifgif program 8           looks for .gif files in the current directory.  @           The motifgif program has three significant components:             o  motifgif   B              The source and executable code in this directory is aA              Motif program driving the display of a .gif picture.t             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.   5           The following problems exist with motifgif:   .           o  Resizing a picture does not work.       B-18    a      I                                             OSF/Motif Toolkit InformationcI                                            B.4 OSF/Motif Example Programs     G               o  The -d option is not used when calling pict, so remoterD                  displays must set the DISPLAY environment variable.  (         B.4.8 Motifshell Example Program                 V1.2  D               The motifshell program is an example of an environmentC               created using Motif. The purpose of the example is toiD               show how Motif may be used as a standalone environment;               for dispatching other programs and utilities.i  G               The motifshell program is written in C code. There are noR               UIL references.a  F                 ________________________ Note ________________________  F                 Displaying a file listing or process status takes someE                 time. These operations are accomplished by spawning aoE                 DCL command, capturing the output in a file, and thena!                 reading the file.o  ?                 The default font is proportionally spaced. SomeMC                 listings are more readable if a fixed space font is F                 used, such as Courier. Use the Font option to select a                 different font.a  F                 ______________________________________________________  &         B.4.9 Periodic Example Program                 V1.2  H               The periodic example is a demonstration of the displayableG               widgets in Motif. The program displays Motif widgets in a $               periodic chart format.  '         B.4.10 Textedit Example Program                  V1.2  F               The textedit program is a primitive text editor based onE               the Motif XmText widget that makes use of its XmNsourcedE               resource to allow multiple views of the same underlying                text.   I                                                                      B-19. E  n      !     OSF/Motif Toolkit InformationT"     B.4 OSF/Motif Example Programs    4           Table B-4 describes the View menu options.  E           Table_B-4_View_Menu_Options________________________________X  E           Option_______Description___________________________________T  B           Split Pane   Adds a new independently scrollable view of                         the text.  1           Remove Pane  Removes a designated pane.   E           One_Pane_____Removes_all_panes_except_the_designated_pane._o  A           The designated pane is determined in the following way:p  C           o  If using an explicit focus policy, it is the last view-              which had focus.m  A           o  If using a pointer focus policy, it is the last viewo,              with which the user interacted.  =           The designated pane is also the one whose clipboarduB           contents are pasted when Paste is selected from the Edit           Menu.e  E           The textedit sources are separated into independent layers.1A           Textedit contains the source files listed in Table B-5.b  E           Table_B-5_Textedit_Source_Files____________________________              FileE           Name_____Description_______________________________________g  C           tfile.c  The code to read, write, and remove files. Hides.C                    any operating system or filesystem dependencies.p  E           app.c    Uses tfile.c to provide all the code to manipulate D                    files and their related buffers. This is toolkit-                    dependent.   E                                              (continued on next page)              B-20 n  e      I                                             OSF/Motif Toolkit InformationwI                                            B.4 OSF/Motif Example Programs     I               Table_B-5_(Cont.)_Textedit_Source_Files____________________                  FileI               Name_____Description_______________________________________)  ?               tk.c     Isolates dependencies on the Xm Toolkit.i  B                        The first half of the file provides utility>                        routines and a toolkit-independent (butG                        application-specific) interface that can be used E                        by the toolkit-independent dialog layer of the #                        application.   B                        The second half of the file defines all theD                        callback routines. Many of these update stateH                        internal to this layer; others perform additionalF                        actions. Those actions unambiguously correspondI                        to toolkit-specific action routines defined in thenF                        first half of the file. Otherwise, an upcall isF                        made to the toolkit-independent dialog layer to)                        decide what to do.   I               dlg.c    Uses tk.c to manage dialog with the user. The code .                        is toolkit-independent.  C               textedit.Initializes the application and instantiates D                        widget hierarchies. The code hides the use ofI               _________UIL_and_Mrm_from_the_rest_of_the_application._____   F                 ________________________ Note ________________________  :                 Moving and removing files is not currently                 implemented.  F                 ______________________________________________________  (         B.4.10.1 Additional Translations                 V1.2  E               Users familiar with emacs may want to add the followingu=               translations to their DECW$XDEFAULTS.DAT files:t      I                                                                      B-21            !     OSF/Motif Toolkit Informationo"     B.4 OSF/Motif Example Programs    Q           *XmText.translations:     Mod1<Btn3Down>: scroll-cursor-vertically()\n\c;             Mod1<Btn3Motion>: scroll-cursor-vertically()\n\n-            Ctrl<key>a: beginning-of-line()\n\ .            Ctrl<key>b: backward-character()\n\1            Ctrl<key>d: delete-next-character()\n\ '            Ctrl<key>e: end-of-line()\n\ -            Ctrl<key>f: forward-character()\n\i             Ctrl<key>g: beep()\n\5            Ctrl<key>h: delete-previous-character()\n\f'            Ctrl<key>i: cut-primary()\n\ .            Ctrl<key>j: newline-and-indent()\n\Q            Ctrl<key>k: set-anchor() end-of-line() key-select() cut-clipboard()\n\o*            Ctrl<key>l: redraw-display()\n\#            Ctrl<key>m: newline()\n\s%            Ctrl<key>n: next-line()\n\d.            Ctrl<key>o: newline-and-backup()\n\)            Ctrl<key>p: previous-line()\n\n%            Ctrl<key>v: next-page()\n\n)            Ctrl<key>w: cut-clipboard()\n\ +            Ctrl<key>y: paste-clipboard()\n\ .            Ctrl<key>z: scroll-one-line-up()\n\)            Mod1<key>b: backward-word()\n\i,            Mod1<key>d: delete-next-word()\n\(            Mod1<key>f: forward-word()\n\0            Mod1<key>h: delete-previous-word()\n\(            Mod1<key>i: copy-primary()\n\1            Mod1<key>k: delete-to-end-of-line()\n\i)            Mod1<key>v: previous-page()\n\o*            Mod1<key>w: copy-clipboard()\n\0            Mod1<key>z: scroll-one-line-down()\n\3            Mod1 Shift<key>greater: end-of-file()\n\ 0            Mod1<key>less: beginning-of-file()\n\-            Mod1<key>]: forward-paragraph()\n\p+            Mod1<key>[: backward-paragraph()e       B.4.11 View Example Program              V1.2  B           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.            B-22 n  m      I                                             OSF/Motif Toolkit InformationiI                                            B.4 OSF/Motif Example Programs$    F               The command file DECW$EXAMPLES:FILEVIEW.COM is provided,H               which allows you to select a language. Valid languages areH               French, English, and German. To select a language, perform%               the following commands:o  .               $ SET DEFAULT DECW$USER_DEFAULTS0               $ @DECW$EXAMPLES:FILEVIEW language  E               This command file copies the .UID and .DAT files to the C               current directory. It sets the appropriate locale and 8               executes the file viewing example program.  H               When the application is started, a primary top-level shellC               is created. From the primary top-level shell, you can &               create secondary shells.  I               Each top-level shell is a parent of a Main Window, the workl-               area of which is a PanedWindow.e  5               The menu bar has the following entries:n  I               o  File-opening and closing files, creating new shells, ando                  exiting  >               o  View-controlling the panes in the pane window                 File Menui  ;               The file menu contains the following options:n                 o  Open New File  F                  A file selection box is mapped to choose the file. IfD                  OpenFile is successful, the current file is closed,F                  all existing panes are destroyed, and the new file is                  displayed.i                 o  Open New Shell   H                  Creates a secondary shell similar to the primary shell.A                  Files can be viewed in each shell independently.                  o  Close  D                  This entry only exists on the secondary windows. ItB                  destroys the top-level shell and closes the file.                 o  Exit   G                  This entry only exists on the primary shell; it closesH(                  the file and the shell.  I                                                                      B-23a           !     OSF/Motif Toolkit Informationn"     B.4 OSF/Motif Example Programs               View Menuf  7           The view menu contains the following options:l             o  New Panet  4              Creates a new pane in the paned window.             o  Delete Pane  &              Deletes the current pane.             o  Searchd  @              Causes a dialog box to pop up for searching text inA              the file. The OK callback of the dialog box searches C              the string. If the string is found, it is displayed in C              the current pane. If the string is not found, then the/               dialog box pops up.  E           Opening a second file in a window causes the application to ?           end abruptly. The View options do not work correctly.h  "     B.4.12 Xmpiano Example Program             V1.2  B           The xmpiano program shows how to write a Motif InterfaceC           to Dumb Instruments (MIDI) application. Both a staff, fort3           writing music, and keyboard are provided.e  @           At the bottom of the window is a set of notes that mayC           be used on the staff. Selecting one of these note buttonsiC           changes the active note accordingly. The selected note iso1           also displayed as the new mouse cursor.   A           Though the note selection is limited, it is possible toeD           play sharps as well as naturals. The program interface hasA           not been written to play flats. The staff automaticallyDB           resizes larger as notes are added past the right side ofC           the staff. To see these notes, scroll the score window as            needed.   ?           To use this application, press the right mouse button B           on a staff that is visible. The following menu items are           displayed:       B-24    a      I                                             OSF/Motif Toolkit Information I                                            B.4 OSF/Motif Example Programs                    o  Add Voice  I                  Connects another display to a new staff. After selectingeB                  this command, you are prompted for the display toE                  connect. Any music written in the new staff plays totH                  this display. Note that pressing the right mouse buttonF                  on the new staff shows the name of the display in theG                  menu title. In addition, the menu commands in the menuEA                  bar relate to the staff that is being displayed._                 o  Remove Voice   C                  Removes the staff as well as the connection to the A                  corresponding display. There is no undo for this7D                  command-all music written in this staff is deleted.                 o  Clear Voice  H                  Erases all notes on the staff. This does not affect the$                  display connection.                 o  Play Voice   F                  Plays the voice of the staff in which the right mouseI                  was pressed. If the voice is the same as the local host, F                  the keys on the keyboard that correspond to the notesI                  appear as though they are being pressed as the notes are G                  played. It is possible to make the keyboard play along I                  with all voices at the same time; however, the code mustyI                  be compiled with the -DCHORDS option. Note that this canmI                  slow down the application significantly on many servers.                  o  Play Alla  A                  Plays all voices at the same time on each of thex$                  specified displays.                 o  Save Voicer  ;                  Saves the corresponding voice to a file. ArH                  FileSelectionDialog is displayed to prompt for the nameD                  of the file in which to save the voice. The display5                  connection information is not saved.U                 o  Load Voice   @                  Loads (appends) a previously saved voice to the%                  corresponding staff.p                 o  Quit)  +                  Exits the example program.   I                                                                      B-25m f  m      !     OSF/Motif Toolkit Informationf"     B.4 OSF/Motif Example Programs    @           This version does not allow editing of notes. To edit,B           clear the staff and start again, or read the data from a           saved file.   D           To set the color of the notes, change the foreground colorC           of the application. To do this, use the -fg option on the $           command line. For example:  .           $ xmpiano :== $DECW$EXAMPLES:xmpiano           $ xmpiano -fg blue                                                                           B-26 o  w      I                                             OSF/Motif Toolkit Information=I                                            B.4 OSF/Motif Example Programs     $         B.4.13 Motif Sample Programs                 V1.2  C               Table B-6 lists sample programs showing various Motifd$               Toolkit functionality.  I               Table_B-6_Motif_Sample_Programs____________________________.  I               File_Name_____Description__________________________________w  *               xmdialogs.c   dialog sampler  (               xmfonts.c     font browser  '               xmeditor.c    text editoro  (               xmlist.c      list example  <               xmprotocol.c  window manager protocols example  5               xmter.c       shape & animation example   3               xmform.c      form attachment example   ?               xmforc.c      form attachment + rowcolumn example   @               xmmap.c       drawingarea + scrolledwindow example  5               xmgetres.c    resource fetching examplet  I               xmapdef.c_____app_defined_scrolled_window_example__________r  A               The following notes apply to these sample programs:p  E               1. The xmfonts program defaults to displaying the fontseG                  whose name length are less than 10 characters. On someiD                  systems, the font path contains only long XLFD fontF                  names. It may be necessary either to set the resourceH                  XMFONTS*maxLen to a larger number (80), or to specify a*                  numColumns resource of 1.  C               2. If you run the program xmter with a window managerdE                  other than Motif Window Manager, that window manageriG                  has to remove all the window decorations (for example,eI                  borders). The program xmter directs Motif Window Manageri2                  to remove the window decorations.  C               3. The xmform program displays a string made of MotifoH                  widgets embedded in a Form. Use the following commands:  I                                                                      B-27a           !     OSF/Motif Toolkit Information "     B.4 OSF/Motif Example Programs    /              $ xmform :== $DECW$EXAMPLES:xmforma              $ 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, $              xmform returns "MOTIF".  =           4. The xmgetres program is an example of how to use C              XmGetSecondaryResourceData. Use the following commands_               to invoke xmgetres:  3              $ xmgetres :== $DECW$EXAMPLES:xmgetres1#              $ xmgetres WidgetClassp  D              The variable WidgetClass is optional. If WidgetClass isD              omitted, it defaults to a class named "Widget". You canC              also use the class "All", which displays the resources D              for all the Xt and the Motif widgets. See the OSF/MotifB              Programmer's Reference manual for a list of available              widget classes.  #     B.4.14 Xmtravel Example Program              V1.2  ?           The xmtravel example is a front end to a travel agent @           client and flight database. The program is designed toC           illustrate various user-interface design concepts as welll9           as be compliant with the OSF/Motif Style Guide.-  C           The program is just an example, many of the functions aren<           either not implemented or use predefined settings.  .     B.4.15 Resource Files for Example Programs             V1.2  E           Many of the example programs have associated resource filese?           for defining various display attributes. To use theseeB           files, either copy them from the directory DECW$EXAMPLESE           to your DECW$USER_DEFAULTS directory, or add their contentst*           to your DECW$XDEFAULTS.DAT file.       B-28           I                                             OSF/Motif Toolkit Information I                                            B.4 OSF/Motif Example Programs     A               The list of example programs and the resource filesh1               associated with them is as follows:s  I               ___________________________________________________________hI               Example_Program_______Resource_File_________________________  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.DAT   /               XMDIALOGS.EXE         XMDEMOS.DATe  /               XMEDITOR.EXE          XMDEMOS.DATt  /               XMFONTS.EXE           XMDEMOS.DAT   /               XMFORC.EXE            XMDEMOS.DAT   /               XMFORM.EXE            XMDEMOS.DAT   /               XMGETRES.EXE          XMDEMOS.DAT   /               XMLIST.EXE            XMDEMOS.DAT   /               XMMAP.EXE             XMDEMOS.DATE  /               XMPROTOCOL.EXE        XMDEMOS.DAT.  /               XMTER.EXE             XMDEMOS.DAT   I               XMTRAVEL.EXE__________XMTRAVEL.DAT__________________________  H               If a resource file is not found, the example programs run,B               but some of the display attributes may be incorrect.  -         B.4.16 UID Files for Example Programsl                 V1.2  H               The UID files used by the example programs must be locatedH               in either the current directory or your DECW$USER_DEFAULTSH               directory. If they are not found, the application fails toG               start. The UID files can be copied from the DECW$EXAMPLESa               directory.  ,         B.5 OSF/Motif List of Known Problems  A               Included in the DECwindows Motif software is an OSFnE               file that contains the OSF/Motif known problems. DuringaB               the installation this file is copied from the kit to6               SYS$HELP:DECW$MOTIF_OSF_BUGLIST_V12.TXT.  I                                                                      B-29c    t                    I                                                                         C I         _________________________________________________________________s  I                            Using the NCSA Mosaic Browser (VMS 5.5-2 Only).    G               Compaq DECwindows Motif for OpenVMS provides the NationaloB               Center for Supercomputing Applications (NCSA) Mosaic@               Version 2.4 browser to let you navigate and access*               information on the Internet.  D               The NCSA Mosaic browser is provided as sample, "as is"D               software to introduce you to the Internet and help youD               get started using a World Wide Web viewer. Because theH               NCSA Mosaic browser that ships with this release is only aI               sample implementation, we have placed Mosaic with the other :               sample software in the DECW$UTILS directory.  A               The Mosaic browser enables OpenVMS users to search,oB               retrieve, display, store, and forward data using theF               Internet. Mosaic functions in conjunction with the WorldH               Wide Web environment, which is a collection of information               servers.  F               Note that the graphical user interface for Mosaic is notI               compliant with the Motif style guide; therefore, the Mosaic\D               browser does not look the same as the DECwindows Motif1               out-of-the-box (OOTB) applications.:  H               The following information about Mosaic is included in this               appendix:d  6               o  Section C.1, Starting Mosaic Software  2               o  Section C.2, Creating a Home Page  F               o  Section C.3, Configuring Mosaic to Process Multimedia                  Files  <               o  Section C.4, Customizing the Mosaic Browser  I               o  Section C.5, Restrictions for Using Mosaic from Behind a                   Firewalll  I                                                                       C-1d e  :      2     Using the NCSA Mosaic Browser (VMS 5.5-2 Only)      C.1 Starting Mosaic Software          C.1 Starting Mosaic Software             V1.2-3  @           The Mosaic browser, which is located in the DECW$UTILSE           directory, is installed as part of the product installationr>           for the Compaq DECwindows Motif for OpenVMS product.  C           To access the verb and start Mosaic, select Menus... froms?           the Options Menu in FileView. Mosaic is listed in thehA           Item Names list. Add the verb Mosaic to a menu, such asVB           the Applications Menu, so that you can invoke Mosaic and@           display the DECwindows Motif home page. Refer to UsingC           DECwindows Motif for OpenVMS for information about addinge           verbs to menus.                                                                  C-2  S  o      I                            Using the NCSA Mosaic Browser (VMS 5.5-2 Only)fI                                              C.1 Starting Mosaic SoftwareE    F                 ________________________ Note ________________________  E                 You can display the sample DECwindows Motif home pagelD                 without a TCP/IP connection to the network. However,D                 to access information contained in the topics in theB                 Help menu requires that Compaq TCP/IP Services for%                 OpenVMS be installed.u  F                 ______________________________________________________            C.2 Creating a Home Page                 V1.2-3  C               A home page lets you make information about yourself,cA               your company, your products, and so on available onrE               the Internet. Click on the On HTML... topic in the HelptE               menu for information about using HTML (Hypertext MarkupdG               Language) to create a home page. HTML uses markup tags to H               tell Mosaic how to format text. A Beginner's Guide to HTMLI               is displayed, which provides information about markup tags,nH               examples, formatting, creating links, troubleshooting, andE               so on. Note that you can access topics in the Help menu D               only if your system is connected to the TCP/IP network7               using Compaq TCP/IP Services for OpenVMS.o  G               As an example of an HTML source, see the DECwindows MotifsE               sample home page. Click on View Source... from the File *               menu to see the HTML source.  :         C.3 Configuring Mosaic to Process Multimedia Files                 V1.2-4  H               The Mosaic browser that is included with Compaq DECwindowsD               Motif for OpenVMS provides support for recognizing and6               processing the following types of files:                 o  GIF                 o  Audio                 o  MPEG                  o  MIME   I                                                                       C-3            2     Using the NCSA Mosaic Browser (VMS 5.5-2 Only)6     C.3 Configuring Mosaic to Process Multimedia Files    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 in 4           case the data is needed outside of Mosaic.  E           To determine what external viewer will display the image orh4           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 an C              extension map file that can be configured by the user.d  ?           2. Matches the MIME file type of the incoming file tom@              an external viewer according to either the built-inC              default list or a setup that is configured by the useroD              and specified in the file DECW$UTILS:XMOSAIC-SETUP.COM.  A           For example, GIF files are mapped to the xv viewer. The C           xv viewer is shareware software that is not provided with D           DECwindows Motif. However, the xv viewer is available fromA           the following location as an OpenVMS freeware offering:h  H              http://www.openvms.compaq.com/openvms/internetnetworks.html  C           The xv mapping is defined in the file DECW$UTILS:XMOSAIC- E           SETUP.COM, a self-documented command procedure, as follows:   4                   $ XV   :== $DECW$EXAMPLES:PICT.EXE  B           The executable PICT.EXE is used to display the GIF file.C           Note that PICT.EXE cannot be used to display a JPEG file.   /           Other mappings include the following:n  E           ___________________________________________________________tE           Image_Type____________Display/Sound_Logical_Name___________e  .           audio/*               - >  showaudio  )           image/xwd             - >  xwuds  )           image/x-xwd           - >  xwudo  )           image/x-xwindowdump   - >  xwud   E           image/*_______________-_>__xv______________________________e       C-4            I                            Using the NCSA Mosaic Browser (VMS 5.5-2 Only) I                        C.3 Configuring Mosaic to Process Multimedia Filesh    C               Mappings in the previous list that are followed by an C               asterisk (*) are available in some versions of Mosaic G               (for example, Version 2.4) that contain native HDF/netCDFs               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 -play8                 $ XWUD          :== $decw$utils:xwud.exe  *         C.4 Customizing the Mosaic Browser                 V1.2-4  A               You can customize the Mosaic browser by setting anysC               of the NCSA Mosaic X resources in the file DECW$USER_t"               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:   %               o  Functional resourcesT  !               o  Visual resourceso                 o  Font resources   (               o  Proxy gateway resources  "               Functional Resources  H               Table C-1 lists the functional resources and descriptions.          I                                                                       C-5            2     Using the NCSA Mosaic Browser (VMS 5.5-2 Only)&     C.4 Customizing the Mosaic Browser    E           Table_C-1_Functional_Resources_____________________________n  E           Resource______________Description__________________________t  B           annotationsOnTop:     Indicates whether inlined documentC           Boolean               annotation hyperlinks are prependedd<                                 to the document (if true) orB                                 postpended (if false). (Default is'                                 false).   A           autoPlaceWindows:     If set to false, the new Document B           Boolean               View windows are not automaticallyA                                 positioned by the program itself;tB                                 your Window Manager determines the=                                 placement. (Default is true.)m  E           catchPriorAndNext:    Controls whether using the keys Prior ?           Boolean               and Next (Page Up and Page Down.A                                 on most keyboards) are explicitly_B                                 caught in the Document View windowE                                 and passed to the vertical scrollbar,iD                                 or whether the normal Motif scrolled?                                 window mechanism is relied upon.B                                 to automatically take this action.3                                 (Default is false.)   @                                 If the Page Up and Page Down key=                                 sequences are not functioningcC                                 appropriately for your environment,iD                                 set this resource to true. (Refer to@                                 the information about hot keys.)  D           confirmDeleteAnnotatioConfirms deleted annotations throughC           Boolean               a confirmation dialog box. (Defaults)                                 is true.)   B           confirmExit: Boolean  Determines whether the NCSA Mosaic?                                 browser pops up a dialog box too@                                 confirm exiting from the programD                                 when the Exit Program menu option is<                                 selected. (Default is true.)  E                                              (continued on next page)p         C-6            I                            Using the NCSA Mosaic Browser (VMS 5.5-2 Only)eI                                        C.4 Customizing the Mosaic Browsers    I               Table_C-1_(Cont.)_Functional_Resources_____________________f  I               Resource______________Description__________________________   B               defaultAuthorName:    Identifies your full name (forB               string                example, John Q. Public). YourG                                     full name is normally stored in therD                                     system password file, and MosaicG                                     extracts the name from that file ifeE                                     this resource is NULL; otherwise,aG                                     the value of this resource is used. 6                                     (Default is NULL.)  C               defaultHeight:        Specifies the default height inmF               integer               pixels for a Document View window.5                                     (Default is 680.)t  B               defaultHotlistFile:   Specifies a file name to storeE               string                the default hotlist (or a list ofYE                                     bookmarks). (Default is ".mosaic-rB                                     hotlist-default". The value ofE                                     the environment variable $HOME isb>                                     prepended to this string.)  I               defaultWidth:         Specifies the default width in pixelsoH               integer               for a Document View window. (Default,                                     is 620.)  I                                                  (continued on next page)f                                I                                                                       C-7t p  e      2     Using the NCSA Mosaic Browser (VMS 5.5-2 Only)&     C.4 Customizing the Mosaic Browser    E           Table_C-1_(Cont.)_Functional_Resources_____________________e  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-rC                                 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.   E                                 Selecting Load Images in Current fromIA                                 the Mosaic Options menu loads and B                                 displays all the inlined-images inC                                 the current document. Delayed image E                                 loading can also be selected with the C                                 -dil command-line flag or on a per- E                                 window basis from the Options menu inR;                                 Mosaic. (Default is false.)   ?           displayURLsNotTitles: Displays URLs wherever documentA@           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 "Documents2=                                 Menu Specfile" to allow sitess?                                 to add their own Documents menuu@                                 to the Mosaic menu bar. For moreB                                 information, see the documentation=                                 about creating a configurable ;                                 Documents menu. (Default is H                                 "/usr/local/lib/mosaic/documents.menu".)  E                                              (continued on next page)t           C-8i i  o      I                            Using the NCSA Mosaic Browser (VMS 5.5-2 Only) I                                        C.4 Customizing the Mosaic Browser     I               Table_C-1_(Cont.)_Functional_Resources_____________________   I               Resource______________Description___________________________  E               fancySelections:      Cuts and pastes from the DocumentoE               Boolean               View window with fancy selectionspE                                     enabled in the HTML widget, whichpB                                     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 withb8                                     gethostbynameIsEvil.  B               gethostbynameIsEvil:  Set to true if you are runningB               Boolean               your system on a Sun set up soA                                     that when the system attemptshB                                     to find its own full host nameG                                     through gethostbyname(), the system B                                     coredumps. (Default is false.)  F               globalExtensionMap:   Set to the location of the system-B               string                wide extension map config file?                                     of your choice. (Default iscH                                     "/usr/local/lib/mosaic/mime.types".)  E               globalHistoryFile:    Specifies the name of the file to C               string                store the global history of all F                                     documents accessed from session toH                                     session. (Default is .mosaic-global-I                                     history. The value of the environment G                                     variable $HOME will be prepended toa1                                     this string.)   I                                                  (continued on next page)       I                                                                       C-9            2     Using the NCSA Mosaic Browser (VMS 5.5-2 Only)&     C.4 Customizing the Mosaic Browser    E           Table_C-1_(Cont.)_Functional_Resources_____________________a  E           Resource______________Description__________________________n  E           globalTypeMap:        Specifies the location of the system- >           string                wide mailcap (type map config)@                                 file of your choice. (Default isA                                 "/usr/local/lib/mosaic/mailcap".)f  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 - C                                 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.)u  ?           hdfMaxDisplayedDatasetSpecifies the maximum number oftB           integer               displayed data sets while browsingC                                 HDF files. If more than the maximumtC                                 number exist in an HDF file, Mosaico?                                 displays the HDF file in "briefs7                                 mode". (Default is 15.)   ?           hdfMaxDisplayedAttribuSpecifies the maximum number ofaC           integer               displayed attributes while browsingmC                                 HDF files. If more than the maximumtC                                 number exist in an HDF file, Mosaic ?                                 displays the HDF file in "briefi7                                 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.)e  @           homeDocument: string  Specifies the document to access;                                 at program startup. See theo?                                 information about on specifyingA?                                 your home document. (Default is M                                 http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/ 4                                 NCSAMosaicHome.html)  E                                              (continued on next page)f       C-10 e  a      I                            Using the NCSA Mosaic Browser (VMS 5.5-2 Only)sI                                        C.4 Customizing the Mosaic Browsern    I               Table_C-1_(Cont.)_Functional_Resources_____________________t  I               Resource______________Description__________________________i  F               imageCacheSize:       Specifies the size of the inlined-C               integer               image cache in kilobytes. The -lE                                     ics command-line flag can also be C                                     used. All the images in a givenfE                                     document are (temporarily) cacheduI                                     while on that page, regardless of the G                                     imageCacheSize value. Cache flushes G                                     the least recently viewed. (Defaultr-                                     is 2048.)f  E               initialWindowIconic:  Set to true if the first DocumenteH               Boolean               View window opened (when the programG                                     starts) will be iconified. (DefaultU.                                     is false.)  B               maxWaisResponses:     Controls the maximum number ofG               integer               matches Mosaic accesses from a WAIS =                                     server. (Default is 200.)n  G               personalAnnotationDireSpecifies the name of the directoryo>               string                in which to store personalC                                     annotations (as well as the loguD                                     file of all personal annotationsC                                     currently in existence). If the F                                     named directory does not exist, itE                                     is created. However, intermediategB                                     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 ofaD                                     the environment variable HOME isG                                     prepended. (Default is .mime.types)e  I                                                  (continued on next page)   I                                                                      C-11            2     Using the NCSA Mosaic Browser (VMS 5.5-2 Only)&     C.4 Customizing the Mosaic Browser    E           Table_C-1_(Cont.)_Functional_Resources_____________________   E           Resource______________Description__________________________   =           personalTypeMap:      Specifies the location of thetE           string                personal mailcap file of your choice. E                                 The value of the environment variableN>                                 HOME is prepended. (Default is)                                 .mailcap)s  A           printCommand: string  Specifies the name of the defaulttB                                 command for the Print menu option.=                                 This command accepts a single A                                 argument: the name of the file to E                                 print. Note that this location can beiE                                 changed at any time through the PrintsE                                 option's dialog box. (Default is lpr)P  A           recordCommandLocation:Specifies the location (full path C           string                name) of the command used to record ?                                 audio annotations (on Sun, SGI, ?                                 and HP platforms). If the named B                                 command does not exist when Mosaic=                                 is started, audio annotationsn<                                 are disabled (the menu entry>                                 becomes insensitive). (DefaultA                                 is "/usr/sbin/recordaiff" on SGI;r@                                 "/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 fulloC                                 command, using the command named in B                                 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 a 0                                 SIGINT is sent.)  E                                              (continued on next page)        C-12           I                            Using the NCSA Mosaic Browser (VMS 5.5-2 Only)DI                                        C.4 Customizing the Mosaic Browserg    I               Table_C-1_(Cont.)_Functional_Resources_____________________   I               Resource______________Description__________________________   G               reloadReloadsImages:  Clears out the Reload option cached G               Boolean               image data for the current documentAH                                     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 messagesyF                                     should be mailed and accepts otherH                                     headers and message text from stdin.E                                     (Default is "/usr/lib/sendmail".)_  I               simpleInterface:      Allows the Mosaic menu bar and bottomlH               Boolean               button configuration to be minimizedE                                     considerably. (Default is false).i  G               tmpDirectory: string  Specifies the name of the directorycE                                     in which to store temporary filesiG                                     generated by Mosaic. This directoryaD                                     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  I                                                  (continued on next page)w      I                                                                      C-13            2     Using the NCSA Mosaic Browser (VMS 5.5-2 Only)&     C.4 Customizing the Mosaic Browser    E           Table_C-1_(Cont.)_Functional_Resources_____________________s  E           Resource______________Description__________________________a  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 arelD                                 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.)   B           tweakGopherTypes:     Mosaic interprets Gopher documentsE           Boolean               strictly by the Gopher typing system, B                                 if set to false. When set to true,@                                 Mosaic uses its own mechanism toB                                 determine the file types of Gopher=                                 documents. (Default is true.)   E           twirlIncrement:       Indicates the minimum number of bytes @           integer               that are are transferred between@                                 updates of the twirling transferC                                 icon for normal (FTP, Gopher, HTTP) =                                 transfers. (Default is 4096.)e  E           twirlingTransferIcon: Set to false to turn off the twirling D           Boolean               NCSA logo during document transfers.D                                 Clicking the icon still interrupts a<                                 transfer. (Default is true.)  C           uncompressCommand:    Specifies the command to uncompressa@           string                compressed files (that is, filesE                                 with an extension of .Z). (Default iso,                                 uncompress).  E                                              (continued on next page)          C-14    f      I                            Using the NCSA Mosaic Browser (VMS 5.5-2 Only))I                                        C.4 Customizing the Mosaic Browser     I               Table_C-1_(Cont.)_Functional_Resources_____________________B  I               Resource______________Description__________________________i  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.)   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 this F                                     resource set to true; override theE                                     setting as necessary. (Default ist*                                     true.)  I               useGlobalHistory:     Automatically stores a global history C               Boolean               of everywhere you visit, if set E                                     to true. (This history is used to E                                     shade anchors in different colors D                                     based on whether you visited theC                                     corresponding documents, if the G                                     resource trackVisitedAnchors is set @                                     to true.) (Default is true.)  E               xtermCommand: string  Specifies the name of the command G                                     used to start a terminal window for G                                     a telnet session. (Default is xtermoE                                     on most platforms; the default is I               ______________________aixterm_-v_on_IBM_AIX_3.x_systems.)__                  Visual Resources  F               Table C-2 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                                                                      C-15            2     Using the NCSA Mosaic Browser (VMS 5.5-2 Only)&     C.4 Customizing the Mosaic Browser    %              Mosaic*anchorColor: cyan   E           Table_C-2_Visual_Resources_________________________________   E           Resource______________Description__________________________   D           anchorColor: color    Specifies the color to shade anchorsB                                 whose corresponding documents haveE                                 not previously been visited. (Defaultl*                                 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.)i  @           anchorUnderlines:     Specifies the number of lines to=           integer               draw underneath the unvisiteduB                                 anchors (Valid values: 0, 1, 2, 3)/                                 (Default is 1.)p  E           visitedAnchorUnderlineSpecifies the number of lines to draw.E           integer               underneath the visited anchors. ValidtB                                 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.)t  @           dashedVisitedAnchorUndSetsndrawn lines under unvisitedB           Boolean               anchors to dashes, if set to true.3                                 (Default is false.)   E                                              (continued on next page)        C-16    1      I                            Using the NCSA Mosaic Browser (VMS 5.5-2 Only) I                                        C.4 Customizing the Mosaic Browser     I               Table_C-2_(Cont.)_Visual_Resources_________________________   I               Resource______________Description__________________________s  I               colorsPerInlinedImage:Specifies the number of unique colorsyG               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 browsereI                                     (for example, GIF images passed to an.G                                     external viewer).) (Default is 50.)s  H               percentVerticalSpace: Specifies the height of the verticalI               integer               space between paragraphs, headers and_G                                     paragraphs, and so on, as expressediF                                     as a percentage of the normal line<                                     height. (Default is 90.)  G               reverseInlinedBitmapCoSpecifies to reverse foreground andhD               Boolean               background colors in inlined XBMH                                     bitmaps, if set to true. (Default is+                                     false.)   D               verticalScrollOnRight:Specifies that the Document ViewG               Boolean               window places its scroll bar on the H                                     left side, if set to false. (DefaultI               ______________________is_true.)____________________________o                 Font Resources  E               Font resources, which are also associated with the HTML G               widget, can be changed dynamically from the Options menu.sG               Table C-3 lists the font resource names and descriptions.   I               Table_C-3_Font_Resources___________________________________e  I               Resource_______Description_________________________________   G               font: font     Used in normal formatted text. (Default isrV                              "-adobe-times-medium-r-normal-*-17-*-*-*-*-*-iso8859-1".)  G               italicFont:    Used in italic formatted text. (Default is V               font           "-adobe-times-medium-i-normal-*-17-*-*-*-*-*-iso8859-1".)  I                                                  (continued on next page)   I                                                                      C-17t e  i      2     Using the NCSA Mosaic Browser (VMS 5.5-2 Only)&     C.4 Customizing the Mosaic Browser    E           Table_C-3_(Cont.)_Font_Resources___________________________   E           Resource_______Description_________________________________   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) formattedpf           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 istP           font           "-adobe-times-bold-r-normal-*-17-*-*-*-*-*-iso8859-1".)  =           header4Font:   Used in level 4 headers. (Default isoP           font           "-adobe-times-bold-r-normal-*-14-*-*-*-*-*-iso8859-1".)  =           header5Font:   Used in level 5 headers. (Default islP           font           "-adobe-times-bold-r-normal-*-12-*-*-*-*-*-iso8859-1".)  =           header6Font:   Used in level 6 headers. (Default isaP           font           "-adobe-times-bold-r-normal-*-10-*-*-*-*-*-iso8859-1".)  q           addressFont:   Used in addresses. (Default is "-adobe-times-medium-i-normal-*-17-*-*-*-*-*-iso8859-1".)            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 isnT           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)u(           font           formatted text.  >           plainboldFont: Used for bold in plaintext regions or0           font           preformatted documents.  @           plainitalicFontUsed for italic in plaintext regions orE           font___________preformatted_documents._____________________   !           Proxy Gateway Resources   >           When your proxy gateway has been established by yourE           network or system administrator, you can use its resources. C           Table C-4 provides additional details about proxy gateway 9           support in the NCSA Mosaic Version 2.4 browser.o       C-18 t  g      I                            Using the NCSA Mosaic Browser (VMS 5.5-2 Only) I                                        C.4 Customizing the Mosaic Browsere    I               Table_C-4_Proxy_Gateway_Resources__________________________t  I               Resource______________Description__________________________r  6               ftpProxy: String      Used for ftp URLs.  9               gopherProxy: String   Used for gopher URLs.n  7               httpProxy: String     Used for http URLs.n  7               newsProxy: String     Used for news URLs.   7               waisProxy: String     Used for wais URLs.   I               ProxyGateway:_String__Used_for_all_access_methods._________   @         C.5 Restrictions for Using Mosaic from Behind a Firewall                 V1.2-3  H               The following sections present information about using theF               ProxyGateway and NoProxy resources with Mosaic to accessD               information on the Internet when security restrictionsG               (that is, a firewall) exist between internal and external_*               network access at your site.  #         C.5.1 ProxyGateway Resourcea  C               NCSA Mosaic Version 2.4 provided in Compaq DECwindows I               Motif for OpenVMS supports the proxy gateway (ProxyGateway) G               resource. A proxy gateway is a trusted agent that enables H               Mosaic to access network information that is either within4               or outside 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 proxy D               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 outsidedD               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.   I                                                                      C-19            2     Using the NCSA Mosaic Browser (VMS 5.5-2 Only)<     C.5 Restrictions for Using Mosaic from Behind a Firewall         C.5.2 NoProxy Resource  >           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 not (           go through the proxy gateway).  E           As previously stated, the NoProxy resource restricts accessn@           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__________________________e  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_______s  E           Refer to the following URL for additional information about            proxy gateways:t  7             http://webservices.web.cern.ch/WebServices/i                   C-20                                 F      _________________________________________________________________  F                                                                  Index      F      A______________________________   C______________________________  /      Access control,  2-22             Calendar B        enabling and disabling, 5-8       removing from a subpanel,0      AccessX support                        2-28*        keyboard enhancements, 2-18     CDAB      Animation applications,  3-15       applications,  2-38, 2-40A      Answerback message                     dynamic font support, 3        DECterm, 2-52                           2-39h:      Applications                           packing,  2-41<        compiling Fortran, 4-10              unpacking,  2-42D      Auto Repeat setting                    WRITE$FONT logical name,3        changing in DECterm, 2-50               2-39   F      B                                   changes to external reference<      _______________________________        processing, 4-13:      Backdrop                            converters,  4-32B        default, 2-35                     converting Asian-language<      Bindings support                       text files, 4-32F        languages, 4-3                    defining logical names,  4-31B      Bookreader                          Display Options...,  2-446        draft-quality printing, 2-37      drag-and-drop?        restoring last login state,          implementing,  4-11 F          2-37                            internationalization support,0        specifying DECW$BOOKSHELF            4-30D          files,  2-38                    logical names with convert,0        using comments in the                4-147          DECW$BOOKSHELF file,  2-38      message,  2-44 D        using UNIX command line,          packing and unpacking error:          2-37                               messages, 2-43  A                                          paper size button,  2-44_4                                          programmingA                                             external referencing,e3                                                4-13   F                                                                Index-1                   E     CDA                                Compound Document Architecture /       programming (cont'd)              See CDA 3          interface changes,  4-12      Console portg8          logical names with convert     selecting,  3-235             , 4-14                     Console Windowe?          release notes,  4-11           console messages,  3-23 ?          restructuring of shareable     controlling the initial 9             images, 4-15                   position, 3-24 A          style guide message,  4-14     defining a global symbol, /       restructuring of shareable           3-24tD          images, 4-15                   displaying console messages,/       specifying an options file,          3-23 D          4-30                              DISABLE (default),  3-23,2       style guide message,  4-14              3-248     C header files,  4-10                  ENABLE,  3-248     Clock                                  values,  3-238       using the alarm,  2-45               WINDOW,  3-237     Color Customizer,  2-3              invoking,  3-24t?       auto shadowing toggle button,     selecting the Alternatet=          2-9                               Console port, 3-23i7       building,  2-4                   Copyright notice ?       command summary,  2-6             displaying in a DECtermg7       DECterms unaffected,  2-9            window, 2-48 !       mapping color resources andmF          color cells, 2-7              D______________________________/       modifying DECW$LOGIN.COM,        Debugger ?          2-5                            using in DECterm,  3-27_B       running,  2-5                    DEC CDA Base Services, 4-12;       supported                        DECchart applicationrA          applications,  2-4             invoking from the Sessiona8          displays,  2-3                    Manager, 2-685       using on multiheaded systems,    DECsound, 2-45 .          2-9                           DECtermA       xsetroot_cust demo,  2-10         answerback message,  2-52 E     Command files                       automatic window positioning,5/       for checking version,  3-4           3-26r>     Compatibility                       batch scrolling,  2-46@       shareable images,  B-10           changing the Auto Repeat8     Compiling applications                 setting, 2-50  >       See also Applications             color selection,  2-50>       Fortran,  4-10                    DECCRA sequence,  4-18@     Compose character,  2-36            DECLFKC sequences,  4-18  B                                         device output files,  2-49D                                         diagnostic crash file,  2-55       Index-2                    E         DECterm (cont'd)                  DECW$INCLUDE:TEXTP.H headerb1          diagnostic crash messages,          file D             2-55                            definition changes, B-12H          displaying the copyright         DECW$INCLUDE:XMP.H header file  A             notice,  2-48                   See also Header filesr9          escape sequences,  2-47            changes, B-11 ?          finish printing option,  5-2       removed definitionsnC          font sizes,  2-46, 2-49               XmHALFLONGBITS, B-11n?          graphics,  2-54                       XmLONGBITS, B-11 8          hold-screen response time,       DECW$LOGIN.DATI             3-27, 5-5                       customizing the login screen, 2          local echo,  2-52                    3-184          logicals,  3-25                  DECW$UTILS@          page-movement sequences,           global symbols, 3-174             4-18                          DECwindowsE          positioning,  2-51                 delayed startup on Alpha,r2          printing files,  2-49                3-10<          /PROCESS problem,  2-56          DECwindows DesktopE          programming issues,  4-17          release notes for generaln9          ReGIS input cursors,  4-17           user,  2-36lH          ReGIS locator report,  2-57      DECwindows Extensions to Motif3          reporting window size,  2-48        , 4-20iF          resizing the terminal,  2-48     DECwindows OSF/Motif Toolkit7          resource file name,  2-47          See Toolkit C          resource usage,  2-54            Detached processes,  2-26 C          screen print services,  2-53     Development support,  4-2 6          scrolling through the            Dialog boxesA             keyboard,  2-48                 changing the positionoA          seven-bit printer support,            Set Password, 3-19uB             2-53                               Start Session, 3-198          system management,  3-25         Display serverD          terminal emulator,  2-55           shared memory extension,2          user font selection,  2-51           4-21G          using the debugger,  3-27          shared memory pixmaps, 4-27 G          virtual terminal support,          shared memory XImages, 4-23hD             3-27                            supporting AccessX, 2-187         DECTPU                            Drag-and-drop B          programming issues,  4-19          using, 2-19, 4-11, 5-3:         DECW$CDPLAYER                     DXmCSText widgetF          required privileges,  2-58         input method support, 4-20D         DECW$CONSOLE_GEOMETRY             DXmFormSpaceButtonsEqually4          global symbol,  5-6                 routineG         DECW$CONSOLE_SELECTION              sizing and spacing widgets,t2          global symbol,  5-6                  4-20  I                                                                   Index-3r r  f              =     DXmLAYOUT_LEFT_DOWN constant       Finish printing optionn5       DXmNlayoutDirection resource,     DECterm,  5-2 =          5-9                           Font limitations, 2-35a5     DXmLAYOUT_LEFT_UP constant         Font resources 2       DXmNlayoutDirection resource,     See Mosaic.          5-9                           FortranE     DXmLAYOUT_RIGHT_DOWN constant       compiling applications,  4-10 ;       DXmNlayoutDirection resource,    Functional resources_2          5-9                            See Mosaic     DXmLAYOUT_RIGHT_UP constantr(       DXmNlayoutDirection resource,    GF          5-9                           _______________________________>     DXmNlayoutDirection resource       GBLPAGES parameter, 3-1?       constants,  5-9                  GET_CHAR_STRUCT function_4                                         access,  5-85     E______________________________    Global symbols C     EFS                                 DECW$CONSOLE_GEOMETRY,  5-6 D                                         DECW$CONSOLE_SELECTION,  5-6<       See Extended File                Graphics card support5          Specifications                 Cirrus,  2-29o     Escape sequencesF       DECterm,  2-47                   H______________________________3     Extended File Specifications       Header files C        (EFS)                            DECW$INCLUDE:TEXTP.H,  B-12 A       File Manager support,  2-62       DECW$INCLUDE:XMP.H,  B-11u7       file selection popup,  2-61       languages,  4-3n@       FileView support,  2-61          Hold-screen response time7       programming library support,      enhancing,  5-5 0          2-62                          Home page7       Support overview,  2-61           See also Mosaicb6       translated image support,         creating,  C-3
          2-64e  F     F                                  I______________________________1     _______________________________    Icon files-6     File Manager                        viewing,  2-244       accessing files using ACLs,      Input cursors9          2-28                           cross-hair,  4-17 6       limitations,  2-33                diamond,  4-17?       refreshing views,  3-14           rubber-band line,  4-17-D       shredding files,  2-24            rubber-band rectangle,  4-178     Files                               selecting,  4-173       previously optional,  3-2        Installation 9     FileView                            DMA setting,  3-1 D       application startup,  3-29        system parameters,  3-1, 3-5       private logos,  2-70       Index-4l l  h              .         Internationalization              MailE          converting files,  4-32            keyboard actions (cont'd)eH          locale support,  4-37                 activating pushbuttons inD          viewing files,  4-30                    dialog boxes,  2-60G         Internet                               highlighting selections,*  5          See also Mosaic                         2-60 B          browsing,  2-2, 2-3, C-1           pasting messages, 2-60  A                                             sending messages from*=         K______________________________       DECnotes,  2-59g  2         Key bindings, 2-36                MessagesI         Keyboard                            System Menu Bar: Pseudo MousenB          enhancements for disabled            not available,  3-281             users,  2-18                  MIT X11 @          scrolling in DECterm,  2-48        Release 3 Intrinsics=                                                messages, B-10l@         L______________________________     Release 4 Intrinsics=         Language variants                      messages, B-10i0          selecting,  2-24                 Mosaic7         Local echo                          configuringe9          DECterm,  2-52                        processingbB         Locale support, 4-36                      Audio files, C-3@         Logical names                             GIF files, C-3A          defining in the CDA Viewer,              MIME files, C-3nA             4-31                                  MPEG files, C-3 G         Login logos                               multimedia files, C-3 E          customizing,  3-20, 5-7            creating a home page, C-3aC         Login screen                        determining an external :          changing colors,  3-18               viewer,  C-4?          customizing,  3-18                 external view setup <             DECW$LOGIN.DAT,  3-18              examples, C-5>          entering username and              file location, C-2:             password,  2-29                 firewall, C-19@          position,  2-29                    font resources, C-17E          welcome message,  2-29, 3-13       functional resources, C-5 9         Logos                               mappings, C-4a<          modifying the Compaq logo,         NoProxy resourceA                                                restrictions, C-20yE             3-18                            providing as the Internet   ;                                               browser,  C-1 D         M______________________________     proxy gateway resources,  2         Mail                                  C-18>          choosing window colors,  2-59      restrictions, C-19G          color customizer,  2-60            setting Mosaic X resources,g1          dragging messages,  2-58             C-5r9          keyboard actions,  2-60            starting, C-2   I                                                                   Index-5o i  t              ;     Mosaic                             New Desktop (cont'd) @       starting (cont'd)                 removing calendar from a  9          an external program,  C-4         subpanel, 2-28e<       supporting the NoProxy            saving and restoring=          resource, C-20                    applications, 2-32 >       supporting the ProxyGateway       saving sessions,  2-27C          resource, C-19                 screen saver support,  2-23 @       visual resources,  C-15           setting default display,/     Motif and XUI widgets                  2-28 <       mixing,  B-11                     shredding multilevel<     Motif Window Manager                   directories, 2-24?       centering lines for multiline     ToolTalk support,  2-32y9          icon titles, 2-73              using ACLs,  2-28 @       color customizer,  2-71           using screen lock,  2-28A       configuration file,  2-72         viewing icon files,  2-24 8       customizing                      Node name display8          colors on multihead            disabling,  3-20.             systems, 2-73              Notepad@       moving the icon box off the       linking with the Release>          screen, 2-73                      1.1.3 Toolkit, 2-65       restarting,  2-72tF       running earlier versions of      O______________________________3          DECwindows, 2-71              Options filee9       supporting customization for      specifying,  4-30.8          monochrome monitors, 2-72     OSF/Motif Toolkit7     Mozilla,  2-2                       examples,  B-12t  :     MWM                                    cutpaste,  B-129       See Motif Window Manager             dnddemo,  B-12v6                                            Dogs,  B-14;     N______________________________           widget,  B-15 :     NCSA Enhanced Mosaic,  2-3             helloint,  B-16<     Netscape Navigator,  2-2               hellomotif,  B-17;     New Desktop                            MOTIFANIM,  B-17 :       changing workspaces,  2-29           MOTIFGIF,  B-18?       detached processes,  2-26            motif samples,  B-27_<       font selection,  2-35                motifshell,  B-19:       Front Panel,  2-32                   periodic,  B-196       language variants,  2-24             pict,  B-186       logging in,  2-29                    PICT,  B-18E       Login Screen,  2-29                  resource files for examplea<       overview of,  2-23                      programs, B-28?       reference pages,  2-26               Square widget,  B-15u:       release notes for general            textedit,  B-19            user, 2-23 to 2-35        Index-6f o  g              A         OSF/Motif Toolkit                 Proxy gateway resources 6          examples (cont'd)                  See Mosaic5             uid files for example         Pushbuttons_;                programs,  B-29              DECwindows Mail_I             view,  B-22                        activating in dialog boxesx8             xmpiano,  B-24                       ,  2-60             xmtravel,  B-28AI          known problems,  B-29            R______________________________5G         Overlay support                   Rebooting after installation,   0          See also Window Manager             3-79          colormap                         Reference pages 9             avoiding potential              viewing, 2-26a=                problems,  3-31            ReGIS input cursors B          modifying applications,  3-31      See also Input cursors3          sharing overlay colormaps        Resourcesn;             with the Window Manager,        See also MosaicO6             3-31                            font, C-17  ;         P                                   functional, C-5g?         _______________________________     proxy gateway, C-18 B         Paint                               setting in Mosaic, C-58          creating private colormaps,        visual, C-15@             2-65                          Run-time support,  4-2%          enhancing performance during-I             basic operations,  2-66       S______________________________ F         Parameter datasize                Save/restore protocol,  2-32@          mismatches,  4-41                Security options,  5-6A         Pascal programming                  Session Manager, 2-69 0          .PEN files,  4-40                Server8         PEN files                           tuning, 3-149          using with Pascal programs,      Session ManagermB             4-40                            color customizer, 2-70F         Printing                            DECchart application, 2-68A          Bookreader,  2-37                  DECterm windows, 2-67e:         Print Screen                        known problemsB          problems with PostScript              private logos, 2-70A             output,  2-66                   saving sessions, 2-27rB         Process                             security options, 2-69D          creating with virtual              stopping a process, 2-70A             terminal support,  3-27       Set Password dialog boxnG         Programming environments, 4-2       changing the position, 3-19 C         Programming support and XUI,      Seven-bit printer supportc9           B-4                               DECterm, 2-53-  I                                                                   Index-7  o  l              7     Shareable images                   Toolkit (cont'd) 2       compatibility,  B-10              extensionsB       upward compatibility,  B-10          DXmCSText widget,  4-20B     Shareable linkages                     SVN widget,  4-20, 4-21E       installing images,  3-3           mixing Motif and XUI Widgets,,/     Shared memory                          B-11 <       creating and using XImages,       modifying XmText andB          4-23                              XmTextField translation>       extension support,  4-21             manager syntax, B-9E       pixmaps,  4-27                    OSF/Motif Release 1.2.3,  4-1-E     Spyglass Enhanced Mosaic            OSF/Motif Release 1.2.4,  4-1 E       no longer supported,  2-3         OSF/Motif Release 1.2.5,  4-1 E     Start Session                       OSF/Motif Release 1.2.6,  4-12B       blue login screen,  3-13          release 1.1.3 applications6     Start Session dialog box               abort, 2-22:       changing the position,  3-19      saving programming  <     Structured Visual Navigation           environments, B-4  :       See SVN                           UIL compiler,  B-9?     SVN widget                         Toolkit shareable images <       DXmSvnDeleteEntries routine,      See Shareable images?          4-21                          Translated image support D       extended selection,  4-20         Extended File Specifications6       live horizontal scrolling,           (EFS), 2-64D          4-21                          Translated-image support, 4-6C     System                              running on OpenVMS systems, .       recommended quotas,  3-14            4-43       tuning non-VGA devices,  3-14    Translations ?     System menu bar                     unsupported with XmText 7       messages,  3-28                      Widget, 2-20   (     T______________________________    UF     Tear-off menus                     _______________________________0       using,  5-3                      UIL files7     Terminal                            compiling,  B-9 5       resizing,  2-48                   parsing,  4-986     Toolkit                            UIL source code<       compatibility,  4-2               documentation,  5-10            naming in OSF/MotifF             Release 1.2.2 and X11      V______________________________  E             R5 Shareable Libraries,    Version checking command filesC/             B-1                          ,  3-4e?          using _Xm routines,  4-9      Virtual terminal support A       description of Release 1.2.3,     creating a process,  3-27             A-1       Index-8e                   7         Visual resources                  Xlib (cont'd)   H          See Mosaic                         vendor pluggable layer, 4-38A                                           XmNinputMethod resource6F         W______________________________     using the shell to specifyB         Widgets                               input methods,  4-207          See also Motif and XUI           XmText Widget E             widgets,  B-11                  unsupported translations,22          sizing and spacing using             2-205             DXmFormSpaceButtonsEqually    XNL libraryeC             ,  4-20                         xnl_parsedatetime, 4-34 B         Window Dump utility                 xnl_xnl_langinfo, 4-346          dump to print file (xpr),        xnl_langinfoA             2-10                            year 200 issues, 4-34w;         Window Manager                    xnl_parsedatetimeeB          overlay support,  3-30             year 2000 issues, 4-34C         Window size                       XSelectAsyncEvent routinesC          reporting for DECterm,  2-48       allocating memory, 4-394C         Workspaces, 2-35                  XSelectAsyncInput routineTC          changing,  2-29                    allocating memory, 4-39 F                                           XtAppMainLoop routine,  4-36  '         X______________________________m           X Image extension, 4-28i         Xlib"          Compaq international Xlib!             implementation,  4-39h          extensions &             client side library,  4-29$          Internationalization,  4-37          locale,  4-36          macrost             PAllHints,  4-41          routines &             files for Pascal programs,                4-40 %             parameter datasize,  4-41 $             XSelectAsyncEvent,  4-39$             XSelectAsyncInput,  4-39              XtAppMainLoop,  4-36              XtOpenDisplay,  4-41$             XtResolvePathname,  4-36          variables             DISPLAY,  4-35              RESOURCE_NAME,  4-35             UIDPATH,  4-35  I                                                                   Index-9,