                                 H                     ____________________________________________________>                     DECwindows Motif Version 1.2-3 for OpenVMS!                     Release Notes                           January 1995  @                     This manual describes new features, softwareG                     problems, corrections, and restrictions, as well as H                     documentation changes that pertain to the DECwindowsI                     Motif Version 1.2-3 for OpenVMS Alpha and OpenVMS VAX                      products.               H                     Revision/Update Information:  This manual supersedes@                                                   the DECwindowsC                                                   Motif Version 1.2 E                                                   for OpenVMS Release 8                                                   Notes.  I                     Operating System:             OpenVMS AXP Version 1.5 C                                                   VMS Version 5.5-2   B                     Software Version:             DECwindows Motif?                                                   Version 1.2-3 C                                                   for OpenVMS Alpha B                                                   DECwindows Motif?                                                   Version 1.2-3 A                                                   for OpenVMS VAX   1                     Digital Equipment Corporation *                     Maynard, Massachusetts             January 1995  @           Digital Equipment Corporation makes no representationsA           that the use of its products in the manner described in B           this publication will not infringe on existing or futureB           patent rights, nor do the descriptions contained in thisB           publication imply the granting of licenses to make, use,>           or sell equipment or software in accordance with the           description.  B           Possession, use, or copying of the software described inA           this publication is authorized only pursuant to a valid D           written license from Digital or an authorized sublicensor.  D            Digital Equipment Corporation 1995. All rights reserved.  ;           The following are trademarks of Digital Equipment B           Corporation: Alpha, AlphaStation, Bookreader, CDA, DDIF,@           DEC, DECfonts, DEClinks, DECnet, DECpresent, DECsound,@           DECterm, DECwindows, DECwrite, DEC Ada, Digital, DTIF,D           LinkWorks, LN03, OpenVMS, POLYCENTER. ReGIS, TURBOchannel,C           ULTRIX, VAX, VAX C, VAX DOCUMENT, VAXstation, VMS, VT320, 2           VT330, VT340, XUI, and the DIGITAL logo.  3           The following are third-party trademarks:   <           Ada is a registered trademark of the United StatesD           government. Adobe and POSTSCRIPT are registered trademarksK           of Adobe Systems Incorporated. HP, LaserJet, PaintJet, QuietJet,  B           RuggedWriter, and ThinkJet are registered trademarks of D           Hewlett-Packard Company. IBM is a registered trademark of E           International Business Machines Corporation. Internet is a  N           registered trademark of Internet, Inc. LaserWriter is a registered  M           trademark of Apple Computer, Inc. Motif, OSF, OSF/1, and OSF/Motif  F           are registered trademarks and Open Software Foundation is a J           trademark of the Open Software Foundation, Inc. National Center F           for Supercomputer Applications (NCSA) Mosaic and Mosaic are H           trademarks of the University of Illinois at Urbana-Champaign. O           This version is based on Enhanced NCSA Mosaic developed by Spyglass,  E           Inc. POSIX is a registered trademark of the IEEE. Sun is a  N           registered trademark of Sun Microsystems, Inc. UNIX is a registered C           trademark licensed exclusively by X/Open Company Limited. K           X Window System is a trademark of the Massachusetts Institute of  L           Technology. All other trademarks and registered trademarks are the/           property of their respective holders.   E                                                                ZK6433 /           This document is available on CD-ROM.   D           This document was prepared using VAX DOCUMENT Version 2.1.                            Send Us Your Comments   C               We welcome your comments on this or any other OpenVMS H               manual. If you have suggestions for improving a particularD               section or find any errors, please indicate the title,A               order number, chapter, section, and page number (if E               available). We also welcome more general comments. Your C               input is valuable in improving future releases of our                documentation.  @               You can send comments to us in the following ways:  E               o  Internet electronic mail: openvmsdoc@zko.mts.dec.com   ?               o  Fax: 603-881-0120 Attn: OpenVMS Documentation, 3                                          ZKO3-4/U08                  o  Online form  C                  Print or edit the online form SYS$HELP:OPENVMSDOC_ @                  COMMENTS.TXT. Send the completed online form byE                  electronic mail to our Internet address, or send the E                  completed hardcopy form by fax or through the postal                   service.   4                  Please send letters or the form to:  .                  Digital Equipment Corporation2                  Information Design and Consulting&                  OpenVMS Documentation0                  110 Spit Brook Road, ZKO3-4/U08'                  Nashua, NH  03062-2698                   USA                 Thank you.                    I                                                                       iii      )     How To Order Additional Documentation   C           Use the following table to order additional documentation 9           or information. If you need help deciding which ?           documentation best meets your needs, call 800-DIGITAL            (800-344-4825).     0         Table 1 Telephone and Direct Mail Orders  7         Location    Call           Fax            Write   C         U.S.A.      DECdirect      Fax:           Digital Equipment =                     800-DIGITAL    800-234-2298   Corporation A                     800-344-4825                  P.O. Box CS2008 B                                                   Nashua, NH 03061  C         Puerto      809-781-0505   Fax:           Digital Equipment A         Rico                       809-749-8300   Caribbean, Inc. F                                                   3 Digital Plaza, 1stC                                                   Street, Suite 200 @                                                   P.O. Box 11038C                                                   Metro Office Park G                                                   San Juan, Puerto Rico <                                                   00910-2138  F         Canada      800-267-6215   Fax:           Digital Equipment of=                                    613-592-1946   Canada Ltd. ;                                                   Box 13000 C                                                   100 Herzberg Road I                                                   Kanata, Ontario, Canada 9                                                   K2K 2A6 G                                                   Attn: DECdirect Sales   ?         International                             Local Digital H                                                   subsidiary or approved=                                                   distributor     F         Internal    DTN: 264-3030  Fax:           U.S. Software Supply:         Orders      603-884-3030   603-884-3960   BusinessC                                                   Digital Equipment =                                                   Corporation @                                                   10 Cotton RoadG                                                   Nashua, NH 03063-1260                        iv                                 C   _________________________________________________________________   C                                                            Contents       E   Preface...................................................     xvii   <   1  DECwindows Motif Version 1.2-3 for OpenVMS New Features  C         1.1   OSF/Motif Release 1.2.3 Toolkit...............    1-1 6         1.2   POLYCENTER Software Installation UtilityC               Integration...................................    1-2 C         1.3   DECterm Features..............................    1-3 C         1.3.1     Scrolling Through the Keyboard............    1-3 C         1.3.2     Reporting the DECterm Window Size.........    1-3 C         1.3.3     Resizing the Terminal.....................    1-3 6         1.3.4     Timeout for Displaying the CopyrightC                   Notice....................................    1-4 7         1.3.5     Cross-Hair and Rubberband-Line Cursor C                   Support...................................    1-4 C         1.4   DECwindows Mail Enhancements..................    1-4 C         1.5   DECnet/OSI Full Names Support.................    1-4 C         1.6   Internationalization Enhancements.............    1-5 .         1.6.1     Using the CDA Viewer to ViewC                   Asian-Language Text.......................    1-5 C         1.6.1.1     Specifying an Options File..............    1-5 C         1.6.1.2     Defining Logical Names..................    1-6 /         1.6.2     Converting Files That Contain C                   Asian-Language Characters.................    1-7 C         1.7   NCSA Mosaic Browser...........................    1-9 C         1.7.1     Starting Mosaic Software..................   1-10 C         1.7.2     Creating a Home Page......................   1-10 :         1.7.3     Configuring Mosaic to Process MultimediaC                   Files.....................................   1-11 C         1.7.4     Customizing the Mosaic Browser............   1-12         C                                                                   v                    =           1.7.5     Restrictions for Using Mosaic from Behind E                     a Firewall................................   1-26 E           1.7.5.1     ProxyGateway Resource...................   1-26 E           1.7.5.2     NoProxy Resource........................   1-27 E           1.8   Console Window Application....................   1-28 E           1.9   Using Shareable Linkages to Install Images....   1-30 E           1.10  Window Manager Overlay Support................   1-31   !     2  General User Release Notes   :           2.1   Notes Specific to DECwindows Motif VersionE                 1.2-3 for OpenVMS Software....................    2-1 E           2.2   Using Drag and Drop...........................    2-2 E           2.3   Using Tear-Off Menus..........................    2-3 8           2.4   Access Control Not Explicitly Enabled byE                 Default.......................................    2-3 >           2.5   Toolkit Warning in the Work in Progress DialogE                 Box...........................................    2-3 E           2.6   DECwindows Motif Application Notes............    2-4 E           2.6.1     Bookreader................................    2-4 E           2.6.1.1     Draft-Quality Printing..................    2-4 7           2.6.2     Including Comment Characters in the E                     DECW$BOOKSHELF File.......................    2-4 E           2.6.3     Calendar..................................    2-4 E           2.6.3.1     Data-File Format........................    2-4 E           2.6.3.2     Additional Problems and Restrictions....    2-5 E           2.6.4     Cardfiler.................................    2-5 E           2.6.5     CDA Run-Time Services.....................    2-5 E           2.6.5.1     CDA Dynamic Font Support................    2-6 E           2.6.5.2     CDA WRITE$FONTS Logical Name............    2-7 E           2.6.5.3     CDA Documents...........................    2-7 E           2.6.5.4     CDA PostScript Documents................    2-8 E           2.6.6     CDA-Additional Applications...............    2-8 E           2.6.6.1     Pack and Unpack Applications............    2-8 E           2.6.6.2     Pack Application........................    2-9 E           2.6.6.3     Unpack Application......................   2-10 E           2.6.6.4     Pack and Unpack Error Messages..........   2-11 6           2.6.7     CDA-Hints, Restrictions, and KnownE                     Problems..................................   2-12 5           2.6.7.1     Display PostScript with the CDA E                       Viewer..................................   2-12 E           2.6.7.2     Message for CDA Viewer..................   2-12 E           2.6.7.3     CDA Paper Size Button Renamed...........   2-13          vi                   I               2.6.7.4     CDA Watch Progress Restriction..........   2-13 >               2.6.7.5     CDA Viewer Supports DECfonts VersionI                           1.2.....................................   2-13 B               2.6.7.6     CDA Viewer-Viewing PostScript Files withI                           Errors..................................   2-13 I               2.6.8     Clock-DECsound Capability.................   2-13 I               2.6.9     DECsound Application......................   2-14 I               2.6.9.1     DECsound Prerequisites..................   2-14 I               2.6.9.2     DECsound Problems.......................   2-14 I               2.6.9.3     Escape Sequences........................   2-15 I               2.6.10    DECterm-Restrictions and Problems.........   2-15 I               2.6.10.1    Changing the Auto Repeat Setting........   2-15 I               2.6.10.2    Positioning DECterm.....................   2-15 I               2.6.10.3    User Font Selection.....................   2-16 I               2.6.10.4    Local Echo..............................   2-17 I               2.6.10.5    Answerback Message......................   2-17 I               2.6.10.6    Seven-Bit Printer Support...............   2-18 I               2.6.10.7    VT330 and VT340 Terminal Emulation......   2-18 I               2.6.10.8    CREATE/TERMINAL/DETACHED/PROCESS........   2-19 I               2.6.10.9    Printing to an Attached Printer.........   2-19 I               2.6.10.10   DECterm Graphics........................   2-20 I               2.6.10.11   Initializing DECterm....................   2-20 I               2.6.10.12   DECterm Resource Usage..................   2-22 I               2.6.10.13   Diagnostic Crash File and Messages......   2-22 A               2.6.10.14   Monitor Screen Width Determines Default I                           Font Size...............................   2-23 I               2.6.10.15   ReGIS Locator Report....................   2-23 I               2.6.11    DECW$CDPLAYER.............................   2-23 I               2.6.12    LinkWorks.................................   2-23 @               2.6.12.1    Removing Support for LinkWorks ManagerI                           (DEClinks)..............................   2-24 I               2.6.13    DECwindows Mail...........................   2-24 I               2.6.13.1    Responses to Keyboard Actions...........   2-24 9               2.6.13.2    Using the Color Customizer with I                           DECwindows Mail.........................   2-25 I               2.6.13.3    DECwindows Mail-Known Problems..........   2-25 I               2.6.14    DECwindows Motif Window Manager...........   2-25 9               2.6.14.1    Using the Color Customizer with I                           DECwindows Motif Window Manager.........   2-25 I               2.6.14.2    Configuration File......................   2-26 I               2.6.14.3    DECwindows XUI Applications.............   2-26 I               2.6.14.4    Restarting Motif Window Manager.........   2-26       I                                                                       viin s  t              E           2.6.15    Motif Window Manager-Known Problems.......   2-27 E           2.6.15.1    Accelerators for Icon in Icon Box.......   2-27rE           2.6.15.2    Application Started as Icon ............   2-27n=           2.6.15.3    Customizing Color-Related Resources forpE                       Monochrome Monitors.....................   2-27p3           2.6.15.4    Customizing Colors on 4-PlanedE                       Displays................................   2-27 8           2.6.15.5    Customizing Icon Placement in IconE                       Box.....................................   2-28 E           2.6.15.6    DECwindows XUI Modal Dialog Boxes.......   2-28 E           2.6.15.7    Customizing the Icon Box................   2-28 E           2.6.15.8    Moving the Icon Box Off Screen..........   2-28nE           2.6.15.9    Truncating the Icon Title...............   2-28 E           2.6.15.10   Invoking Motif Window Manager Help......   2-28 E           2.6.15.11   Multihead Systems-Customizing Colors....   2-29sE           2.6.15.12   Multiline Icon Title Not Centered ......   2-29M;           2.6.15.13   Truncated Icon Title in Vertical IconEE                       Box.....................................   2-29oE           2.6.16    Notepad...................................   2-29 :           2.6.16.1    Notepad Is Linked with the OSF/MotifE                       Release 1.1.3 Toolkit...................   2-29 E           2.6.17    Paint.....................................   2-29 E           2.6.17.1    Private Colormaps.......................   2-30 =           2.6.17.2    Enhancing the Performance of Some Paint E                       Operations..............................   2-30 E           2.6.18    Print Screen..............................   2-30rE           2.6.18.1    Large Default Icon......................   2-30oE           2.6.19    Session Manager and FileView .............   2-30n<           2.6.19.1    Removing Support for LinkWorks ManagerE                       and LinkWorks...........................   2-31n8           2.6.19.2    Invoking DECchart from the SessionE                       Manager Applications Menu...............   2-31 4           2.6.19.3    Eastern European Languages NowE                       Available...............................   2-32CE           2.6.19.4    Security Options........................   2-33i=           2.6.19.5    Using the Color Customizer with SessioneE                       Manager.................................   2-33i>           2.6.19.6    Input Focus Change When Starting PrivateE                       Logo....................................   2-34 E           2.6.19.7    Session Manager Process-Stopping........   2-34eE           2.6.19.8    Public Profiles for Layered Products....   2-34SE           2.7   Window Dump to Print File (xpr) Utility.......   2-35gE           2.8   Keyboard Enhancements for Disabled Users......   2-43-         viii I  i              I               2.8.1     Sticky Keys...............................   2-43rI               2.8.2     Mouse Keys................................   2-43 I               2.8.3     Toggle Keys...............................   2-44/I               2.8.4     Repeat Keys...............................   2-44oI               2.8.5     Slow Keys.................................   2-44aI               2.8.6     Bounce Keys...............................   2-44MI               2.8.7     Time Out..................................   2-44aI               2.9   Printing from Applications....................   2-45 @               2.10  Unsupported Translations by the Motif XmTextI                     Widget........................................   2-45n  '         3  System Manager Release Notesr  >               3.1   Notes Specific to DECwindows Motif VersionI                     1.2-3 for OpenVMS Software....................    3-1e@               3.2   Required Reboot on OpenVMS Alpha Version 6.2I                     Systems.......................................    3-1 =               3.3   DECwindows Motif Login Screen-Known ColordI                     Problem.......................................    3-2iI               3.4   Color Customizer Example Program..............    3-2mI               3.4.1     Supported Displays........................    3-2MI               3.4.2     Supported Applications....................    3-2r@               3.4.3     Building the Color Customizer on OpenVMSI                         Systems...................................    3-3 I               3.4.4     Running the Color Customizer..............    3-3 I               3.4.5     Modifying the DECW$LOGIN.COM File.........    3-4 I               3.4.6     Command Interface Summary ................    3-4i:               3.4.7     Changing the Mapping Between ColorI                         Resources and Color Cells.................    3-6DI               3.4.8     DECterm Windows Not Affected..............    3-7 9               3.4.9     Changing the Default Value of thetI                         Automatic Shadowing Toggle Button.........    3-8h9               3.4.10    Using the Customizer on MultiheadlI                         Systems...................................    3-8 A               3.4.11    Using the XSETROOT_CUST.EXE Demonstration I                         Program...................................    3-8t?               3.5   Define DECW$UTILS Global Symbol When Moving I                     DECW$EXAMPLES Global Symbol...................    3-9i:               3.6   FileView Creates Detached Processes byI                     Default.......................................    3-9 I               3.7   Customizing the Login Screen..................   3-10 >               3.7.1     Customizing the Digital Logo and LoginI                         Screen Colors.............................   3-11i    I                                                                        ixs u  e              ;           3.7.2     Changing Positions of the Start SessioneE                     and Set Password Dialog Boxes.............   3-11 >           3.7.3     Disabling a Node Name Display in the StartE                     Session Dialog Box........................   3-129E           3.8   Customized Login Logos........................   3-13.E           3.9   Version Checking Command Files................   3-13 >           3.10  Implications of the Message, "System Menu Bar:E                 Pseudo Mouse Not Available"...................   3-15iE           3.11  DECterm System Management Issues..............   3-15aE           3.11.1    DECterm Logical Names.....................   3-15 E           3.11.2    Automatic Window Positioning..............   3-161E           3.11.3    Hold Screen Response Time.................   3-16rE           3.11.4    Using the Debugger........................   3-17RE           3.11.5    Virtual Terminal Support..................   3-17        4  Programmer Release Notesx  5           4.1   Programming Release Notes Specific to :                 DECwindows Motif Version 1.2-3 for OpenVMSE                 Software......................................    4-1 4           4.2   DECwindows Motif for OpenVMS ToolkitE                 Versions......................................    4-2 E           4.3   Run-Time and Programming Environments.........    4-2 E           4.4   OSF/Motif Toolkit Compatibility...............    4-3oE           4.4.1     _Xm Routines..............................    4-4 =           4.4.2     OSF/Motif Release 1.2.2 and X11 Release 5 E                     Shareable Libraries.......................    4-5 E           4.5   Language Bindings.............................    4-8 E           4.5.1     OSF/Motif Release 1.1.3 Ada Bindings......    4-8 ;           4.6   OSF/Motif Release 1.1.3 Programming Support E                 and XUI.......................................    4-8 >           4.7   Adding POSIX for OpenVMS Support to DECwindowsE                 Transports....................................   4-12 E           4.7.1     POSIX fork()  Routine .....................  4-13_E           4.7.2     SYS$POSIX_FORK_CONTROL System Service.....   4-13 E           4.8   Translated Image Support......................   4-14.8           4.8.1     Running Translated Images on OpenVMSE                     Systems...................................   4-14 E           4.8.2     DECwindows Motif Toolkit Functionality....   4-16SE           4.9   Cross-Development Tools.......................   4-16.E           4.10  Compiling Applications Written in C...........   4-18.E           4.11  Compiling Applications Written in Fortran.....   4-18aE           4.12  CDA Application...............................   4-19S         x.                   :               4.12.1    CDA-Implementing the Drag-and-DropI                         Feature...................................   4-19iI               4.12.2    CDA Run-Time Services Features............   4-20rI               4.12.2.1    Version Number..........................   4-20.B               4.12.2.2    Changes to the Programming Interface forI                           CDA.....................................   4-20.7               4.12.2.3    Changes to External ReferencehI                           Processing..............................   4-22iI               4.12.2.4    Message for Style Guide Fallback........   4-22 :               4.12.2.5    Using Logical Names with CONVERTI                           Commands................................   4-22 I               4.12.2.6    Restructuring Shareable Images..........   4-23-I               4.13  DECterm Programming...........................   4-24wI               4.13.1    Page-Movement Escape Sequences............   4-24oI               4.13.2    DECCRA Sequence...........................   4-24.I               4.13.3    DECLFKC Sequence..........................   4-25 I               4.13.4    ReGIS Input Cursors.......................   4-251I               4.14  DECwindows OSF/Motif Toolkit..................   4-25 =               4.14.1    Compilation Error When Including Both I                         CURSES.H and XMP.H Files..................   4-26iI               4.14.2    Motif Text Widget Translations............   4-26.I               4.14.3    Upward Compatibility......................   4-26.>               4.14.3.1    Restrictions on Mixing Motif and XUII                           Widgets.................................   4-27.?               4.14.4    Compile-Time Incompatibilities in MotifnI                         Header Files..............................   4-28.I               4.15  OSF/Motif Example Programs....................   4-29 I               4.15.1    Cut and Paste Example Program.............   4-29nI               4.15.2    DNDDemo Example Program...................   4-29oI               4.15.3    Dogs Example Program......................   4-31.I               4.15.3.1    Dog Widget..............................   4-31iI               4.15.3.2    Square Widget...........................   4-32.I               4.15.4    Helloint Example Program..................   4-32 I               4.15.5    Hellomotif Example Program................   4-33 I               4.15.6    Motifanim Example Program.................   4-33 I               4.15.7    Motifgif and Pict Viewing Programs........   4-34.I               4.15.8    Motifshell Example Program................   4-35 I               4.15.9    Periodic Example Program..................   4-35FI               4.15.10   Textedit Example Program..................   4-35.I               4.15.10.1   Additional Translations.................   4-37.I               4.15.11   View Example Program......................   4-38 I               4.15.12   Xmpiano Example Program...................   4-40.I               4.15.13   Motif Sample Programs.....................   4-42.    I                                                                        xi.                   E           4.15.14   Xmtravel Example Program..................   4-43.E           4.15.15   Resource Files for Example Programs.......   4-43.E           4.15.16   UID Files for Example Programs............   4-44.E           4.16  DECwindows Extensions to Motif................   4-44.E           4.16.1    DXmCSText Input Method Support............   4-45.5           4.16.2    SVN-Horizontal Live Scrolling Not-E                     Supported.................................   4-451E           4.16.3    SVN Horizontal Separator Line.............   4-451E           4.16.4    DXmFormSpaceButtonsEqually Restriction....   4-45 E           4.17  Display Server Extensions.....................   4-45.3           4.17.1    Display PostScript (DPS) Server E                     Extension-Color Cells.....................   4-45 E           4.17.2    X Image Extension.........................   4-46 E           4.17.3    Client Side Extension Library.............   4-47iE           4.17.4    Shared Memory Extension Support...........   4-47sE           4.17.4.1    How to Use Shared Memory Extension......   4-48tE           4.17.4.2    Using Shared Memory XImages.............   4-49.E           4.17.4.3    Using Shared Memory Pixmaps.............   4-53sE           4.17.5    Using Extension Include Files.............   4-54.E           4.18  Xlib Issues...................................   4-54tE           4.18.1    xlibint.h Is Now a Public Header File.....   4-54nE           4.18.2    Command Procedure Builds .PEN Files.......   4-54eE           4.18.3    Parameter/Protocol Datasize Mismatches....   4-55P;           4.18.4    XSelectAsyncEvent and XSelectAsyncInput E                     Routines .................................   4-55.E           4.18.5    Xlib Internationalization.................   4-56 E           4.18.5.1    Vendor Pluggable Layer..................   4-56 7           4.18.5.2    Digital Internationalization Xlib E                       Implementation..........................   4-58.E           4.18.5.3    Locale in OpenVMS Systems...............   4-58.  "     5  Documentation Release Notes  ;           5.1   Documentation Release Notes Specific to the :                 DECwindows Motif Version 1.2-3 for OpenVMSE                 Product.......................................    5-1.:           5.2   DECwindows Motif Version 1.2-3 for OpenVMSE                 Documentation.................................    5-2c:           5.3   DECwindows Motif Version 1.2-3 for OpenVMSE                 Documentation Corrections.....................    5-4                xiim .  .              A               5.3.1     DECwindows Motif for OpenVMS Applications.I                         Guide.....................................    5-4s@               5.3.1.1     Enhancing Information About the FinishI                           Printing Option.........................    5-4.I               5.3.2     Using DECwindows Motif for OpenVMS........    5-4.I               5.3.2.1     Using the Drag-and-Drop Feature.........    5-4.I               5.3.2.2     Tear-Off Menus..........................    5-5.9               5.3.2.3     Adding Target Screen Options totI                           Application Menu Items..................    5-6.I               5.3.2.4     Changing the Startup Environment........    5-6.I               5.3.2.5     Enhancing Startup Performance...........    5-6iI               5.3.2.6     Enhancing Hold-Screen Response Time.....    5-7r=               5.3.3     Managing DECwindows Motif for OpenVMS.I                         Systems...................................    5-7sI               5.3.3.1     Global Symbols..........................    5-7.I               5.3.3.2     Security Options........................    5-7tI               5.3.3.3     Displaying a Customized Logo............    5-82I               5.3.3.4     Enabling and Disabling Access Control...    5-92=               5.3.4     DECwindows Motif for OpenVMS Guide to.I                         Non-C Bindings............................    5-9.I               5.3.4.1     GET_CHAR_STRUCT Function................    5-9 @               5.3.5     VMS DECwindows Guide to Xlib (Release 4)I                         Programming: VAX Binding..................    5-9eI               5.3.6     DECwindows Extensions to Motif............   5-10t6               5.3.6.1     DXmNlayoutDirection ResourceI                           Constants...............................   5-10o=               5.3.7     DECwindows Motif Guide to Application4I                         Programming...............................   5-11.9               5.3.7.1     UIL Source Code for the OpenVMSmI                           DECburger Application...................   5-11.I               5.3.7.2     Help Widget Implementation Code.........   5-11 I               5.3.7.3     Help Widget Implementation-Callbacks....   5-11.I               5.3.7.4     Using UIL to Create the Help Widget.....   5-11.@               5.3.8     Overview of DECwindows Motif for OpenVMSI                         Documentation.............................   5-12pI               5.4   OSF/Motif List of Known Problems..............   5-12.                  I                                                                      xiii  .  1              *     A  OSF/Motif Release 1.2 Release Notes  E           A.1   Performance Improvements......................    A-16E           A.2   Backward Compatibility........................    A-26E           A.2.1     Visual and Behavioral Compatibility.......    A-2s>           A.3   Changes and New Features for OSF/Motif ReleaseE                 1.2...........................................    A-3 E           A.3.1     General Toolkit Changes...................    A-3 E           A.3.1.1     Include File Changes....................    A-3tE           A.3.2     Change in XT Translations.................    A-3cE           A.3.3     ANSI C Compliance.........................    A-4 E           A.3.4     Display and Screen Specific Data..........    A-4 E           A.3.5     Drag and Drop.............................    A-4iE           A.3.6     Tear-Off Menus............................    A-5.E           A.3.7     Insensitive Visuals.......................    A-5rE           A.3.8     Other Visual Changes......................    A-6.E           A.3.9     Titles for Frames.........................    A-6wE           A.3.10    Audible Warning...........................    A-6CE           A.3.11    Color Enhancements........................    A-7iE           A.3.12    Baseline Alignment........................    A-7 E           A.3.13    Expanded Traversal Set....................    A-7 E           A.3.14    Two-Dimensional Menu Traversal............    A-7 E           A.3.15    Input Focus...............................    A-7.E           A.3.16    Traversal Access Functions................    A-8.E           A.3.17    Virtual Keys..............................    A-8 E           A.3.18    Resource Management.......................    A-9 E           A.3.19    Changes for CUA and Windows Compliance....   A-10 4           A.4   Changes and Enhancements to SpecificE                 Widgets.......................................   A-10sE           A.4.1     XmClipboard...............................   A-10 E           A.4.2     XmCommand.................................   A-11 E           A.4.3     XmList....................................   A-11.E           A.4.4     XmMessageBox..............................   A-12 E           A.4.5     XmRowColumn and Menus.....................   A-12 E           A.4.6     XmScrollBar...............................   A-12 E           A.4.7     XmScrolledWindow..........................   A-13 E           A.4.8     XmSelectionBox, XmFileSelectionBox........   A-13 E           A.4.9     XmText....................................   A-13 E           A.4.10    XmTextField...............................   A-14pE           A.4.11    XmToggleButton, XmToggleButtonGadget......   A-15ME           A.5   Motif Window Manager Enhancements.............   A-15bE           A.5.1     Changes to MWM............................   A-15.E           A.5.2     New and Enhanced MWM Resources............   A-15tE           A.5.3     New and Enhanced MWM Functions............   A-16.         xiv. .
         Index              Tables  I               1-1       Asian Language Codes for Options Files....    1-6   9               1-2       Logical Names for Specifying Text I                         Encoding..................................    1-7   I               1-3       Languages and Associated Basic Fonts......    1-8   I               1-4       Functional Resources......................   1-13   I               1-5       Visual Resources..........................   1-23   I               1-6       Font Resources............................   1-24o  I               1-7       Proxy Gateway Resources...................   1-26n  I               2-1       Window Dump to Print File Options.........   2-36e  B               3-1       Moving the Digital Logo and Changing LoginI                         Screen Colors ............................   3-11f  B               3-2       Changing Position of the Start Session andI                         Set Password Dialog Boxes.................   3-12u  I               3-3       Logical Names Supported by DECterm........   3-15   =               4-1       Names of Shareable Libraries Based onsI                         R5........................................    4-6.  =               4-2       Names of Shareable Libraries Based onnI                         OSF/Motif Release 1.2.2...................    4-6.  =               4-3       Directories for Previous XUI or Motif I                         Programming Environment...................   4-10-  I               4-4       Drag-and-Drop Widgets.....................   4-19   I               4-5       New Header File Names.....................   4-21   I               4-6       Names of Shareable Images.................   4-23   =               4-7       ReGIS Input Cursors-Cursor styles and I                         Values....................................   4-25e  I               4-8       View Menu Options.........................   4-35   I               4-9       Textedit Source Files.....................   4-36   I               4-10      Motif Sample Programs.....................   4-42u  B               4-11      Routine Names and Arguments Sent as 16-BitI                         Values....................................   4-55l  4               5-1       DECwindows Motif for OpenVMSI                         Documentation.............................    5-2   I                                                                        xvE r  o                          I         _________________________________________________________________.  I                                                                   Preface1      D               The DECwindows Motif Version 1.2-3 for OpenVMS productE               incorporates the OSF/Motif Release 1.2.3 Toolkit and is F               based on Release 5 of the X Window System Intrinsics. AsG               with DECwindows Motif Version 1.2 for OpenVMS, DECwindowsOB               Motif Version 1.2-3 for OpenVMS continues to provideF               run-time support for the XUI user interface and Toolkit.D               Application development is supported for the OSF/Motif$               Release 1.2.3 Toolkit.  F               In this manual, DECwindows XUI (X User Interface) refersI               to the DECwindows product prior to DECwindows Motif Version.               1.0.  A               These release notes describe new features, software A               problems, corrections, and restrictions, as well as @               documentation changes that pertain specifically toG               DECwindows Motif Version 1.2-3 for OpenVMS software. They I               also describe software problems, corrections, restrictions, F               and documentation changes from previous DECwindows MotifA               releases that have not been updated in the existing E               documentation for those products. Margin notes indicate.I               the versions of the DECwindows Motif products that apply to                 each release note.           Intended Audience   =               This manual contains the following information:   I               o  Chapter 1 describes the new features introduced with theyD                  DECwindows Motif Version 1.2-3 for OpenVMS product.  F               o  Chapter 2 contains general user release notes for all                  users..  I                                                                      xvii. .  .              A           o  Chapter 3 contains release notes intended for system               managers.  :           o  Chapter 4 contains release notes intended for0              application and system programmers.  A           o  Chapter 5 describes additions and corrections to the.              documentation set.i  B           o  Appendix A contains a subset of the release notes for%              OSF/Motif Release 1.2.3.o       Conventions.  B           In this manual, every use of OpenVMS Alpha refers to theB           OpenVMS Alpha operating system; every use of OpenVMS VAX?           refers to the OpenVMS VAX operating system; and everyoA           use of OpenVMS refers to both the OpenVMS Alpha and VAX.           operating systems.  @           In this manual, every use of DECwindows and DECwindows@           Motif refers to DECwindows Motif for OpenVMS software.                                              	     xviii. .  .              H               The following conventions are used to identify informationB               specific to OpenVMS Alpha or to OpenVMS VAX systems:  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.O  F               PF1 x            A sequence such as PF1 x indicates thatG                                you must first press and release the keyPE                                labeled PF1 and then press and releaseWG                                another key or a pointing device button.m  G               GOLD x           A sequence such as GOLD x indicates thattG                                you must first press and release the key.I                                defined as GOLD and then press and releaseaG                                another key. GOLD key sequences can also.H                                have a slash (/), dash (-), or underscoreB                                (_) as a delimiter in EVE commands.  I                                The GOLD key definition is often mapped tog9                                the PF1 key on the keypad.s  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.)  <                . . .           Horizontal ellipsis points inE                                examples indicate one of the following.-                                possibilities:   D                                o  Additional optional arguments in a>                                   statement have been omitted.  D                                o  The preceding item or items can be=                                   repeated one or more times.   I                                o  Additional parameters, values, or other4=                                   information can be entered..  D               .                Vertical ellipsis points indicate theD               .                omission of items from a code exampleG               .                or command format; the items are omitted D                                because they are not important to the5                                topic being discussed..  H                                                                      xix                     :           ( )              In command format descriptions,C                            parentheses indicate that, if you choose.E                            more than one option, you must enclose the.2                            choices in parentheses.  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 in44                            an assignment statement.)  A           { }              In command format descriptions, bracespE                            surround a required choice of options; youEA                            must choose one of the options listed.I  D           boldface text    Boldface text represents the introductionD                            of a new term or the name of an argument,A                            an attribute, or a reason (user action.5                            that triggers a callback).l  B                            Boldface text is also used to show user>                            input in Bookreader versions of the"                            manual.  ;           italic text      Italic text emphasizes importantnD                            information and indicates complete titles>                            of manuals and variables. VariablesD                            include information that varies in system?                            messages (Internal error number), innA                            command lines (/PRODUCER=name), and in.D                            command parameters in text (where device-@                            name contains up to five alphanumeric'                            characters).s  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.O             xx                     D               struct           Monospace type in text identifies theI                                following C programming language elements:.C                                keywords, the names of independently E                                compiled external functions and files, B                                syntax summaries, and references toE                                variables or identifiers introduced in *                                an example.  G               -                A hyphen in code examples indicates thatfF                                additional arguments to the request areA                                provided on the line that follows.M  D               numbers          All numbers in text are assumed to beI                                decimal unless otherwise noted. NondecimalsH                                radixes-binary, octal, or hexadecimal-are4                                explicitly indicated.  D               mouse            The term mouse refers to any pointingD                                device, such as a mouse, a puck, or a&                                stylus.  G               MB1, MB2, MB3    MB1 indicates the left mouse button, MB2.E                                indicates the middle mouse button, and.I                                MB3 indicates the right mouse button. (The.>                                user can redefine the buttons.)  I               PB1, PB2, PB3,   PB1, PB2, PB3, and PB4 indicate buttons onc(               PB4              the puck.  H               SB1, SB2, SB3    SB1, SB2, and SB3 indicate buttons on the&                                stylus.                          J                                                                        xxi        n                  I                                                                         1.I         _________________________________________________________________.  I                   DECwindows Motif Version 1.2-3 for OpenVMS New Features     @               This chapter describes features available with theB               DECwindows Motif Version 1.2-3 for OpenVMS software:  0               o  OSF/Motif Release 1.2.3 Toolkit  9               o  POLYCENTER Software Installation utilityo  !               o  DECterm features   -               o  DECwindows Mail enhancements1  A               o  DECnet/OSI full names support on OpenVMS systems.  E               o  Internationalization enhancements for the CDA Viewer.  $               o  NCSA Mosaic browser  +               o  Console Window application   H               o  Installing shareable images by default on OpenVMS Alpha                  systems  /               o  Window Manager overlay support   +         1.1 OSF/Motif Release 1.2.3 Toolkit.  F        V1.2-3 The OSF/Motif Release 1.2.3 Toolkit, which is integratedA               into the DECwindows Motif Version 1.2-3 for OpenVMSFE               software, resolves many problems from previous releasesmF               of the Toolkit. New features are not included in ReleaseH               1.2.3 of the Toolkit. See Appendix A for Release 1.2.2 and(               Release 1.2.3 information.      I                                                                       1-1. .  .      ;     DECwindows Motif Version 1.2-3 for OpenVMS New Featureso<     1.2 POLYCENTER Software Installation Utility Integration    <     1.2 POLYCENTER Software Installation Utility Integration  >    V1.2-3 The POLYCENTER Software Installation utility enables?           users to install software products quickly and with a ?           single command. You can also remove software products-@           that have been installed using the POLYCENTER SoftwareA           Installation utility. The installation utility provides.B           information about the DECwindows Motif Version 1.2-3 forE           OpenVMS product. Refer to the DECwindows Motif Version 1.2-.B           3 for OpenVMS Installation Guide for POLYCENTER Software#           installation information.0                                                                       1-2  o  n      I                   DECwindows Motif Version 1.2-3 for OpenVMS New FeaturestI                  1.2 POLYCENTER Software Installation Utility Integrationt    F                 ________________________ Note ________________________  A                 You must use the POLYCENTER Software Installation.E                 utility to install your DECwindows Motif Version 1.2-oA                 3 for OpenVMS software on OpenVMS Version 6.2 (or.B                 higher) systems. You can use either the POLYCENTER>                 Software Installation utility or the VMSINSTALB                 procedure to install your DECwindows Motif VersionA                 1.2-3 for OpenVMS software on OpenVMS Version 6.1.@                 systems. You must use the VMSINSTAL procedure toB                 install DECwindows Motif Version 1.2-3 software onB                 Version 5.5-2 through Version 6.0 OpenVMS systems.  F                 ______________________________________________________           1.3 DECterm Features  H        V1.2-3 This section describes DECterm features that are availableE               in DECwindows Motif Version 1.2-3 for OpenVMS software..>               Refer to the remaining chapters in this document@               for specific user, system manager, programmer, and(               documentation information.  ,         1.3.1 Scrolling Through the Keyboard  F        V1.2-3 You can scroll through the keyboard by pressing the CtrlG               key and arrow keys or by pressing the Prev or Next key onM!               the editing keypad.g  /         1.3.2 Reporting the DECterm Window Size.  G        V1.2-3 When you enable the Show Feedback option in the Workspace E               Options dialog box of the Window Manager and you resize E               a DECterm window, the size of the window is reported in +               characters instead of pixels.   #         1.3.3 Resizing the Terminalr  I        V1.2-3 If you maximize the DECterm window when you enable the AutofF               Resize Terminal window option, the window is expanded toH               its nearest cell boundary; the window does not necessarilyG               occupy the entire screen. The Restore options continue to.%               function appropriately.   I                                                                       1-3            ;     DECwindows Motif Version 1.2-3 for OpenVMS New Features      1.3 DECterm Features    5     1.3.4 Timeout for Displaying the Copyright Notice   B    V1.2-3 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.  7     1.3.5 Cross-Hair and Rubberband-Line Cursor Supporti  ?    V1.2-3 DECterm supports cross-hair and rubberband-line input.B           cursors, in addition to diamond and rubberband-rectangle;           ReGIS input cursors. Refer to Section 2.6.9.3 andS4           Section 4.13.4 for additional information.  $     1.4 DECwindows Mail Enhancements  B    V1.2-3 The DECwindows Mail application integrates the OSF/MotifA           Release 1.2.3 Toolkit into the DECwindows Motif Version.B           1.2-3 for OpenVMS release. Specifically, DECwindows Mail.           includes the following enhancements:  '           o  Support for tear-off menus   !           o  Enhanced performance   %     1.5 DECnet/OSI Full Names Support   ;    V1.2-3 DECwindows Motif Version 1.2 for OpenVMS supports.@           DECnet/OSI full names on OpenVMS Alpha Version 6.2 andB           OpenVMS VAX Version 6.1 (and higher) systems. DECnet/OSI<           supports the use of names that have a hierarchicalA           structure and are longer than those currently supportedn>           by DECnet Phase IV. The following components support            DECnet/OSI full names:             o  Bookreader              o  DECnet transporte             o  DECterm             o  DECwindows Mail             o  FileViewn             o  Session Manager  &           o  [DCL command] SET DISPLAY       1-4. .  .      I                   DECwindows Motif Version 1.2-3 for OpenVMS New Features I                                         1.5 DECnet/OSI Full Names Support     F               Refer to the OpenVMS VAX Version 6.1 New Features ManualI               and the OpenVMS Version 6.2 New Features Manual manuals for_>               additional information about full names support.  -         1.6 Internationalization Enhancements   C        V1.2-3 Additional internationalization support enables users C               to view and convert files that contain Asian-language                characters.   C               This section provides the following information about =               internationalization support for the CDA Viewero               application:  C               o  Section 1.6.1, Using the CDA Viewer to View Asian-                   Language Text  D               o  Section 1.6.2, Converting Files That Contain Asian-$                  Language Characters  >         1.6.1 Using the CDA Viewer to View Asian-Language Text  G        V1.2-3 You can use the CDA Viewer in two ways to view text files ,               that contain Asian characters:  G               o  Specify an options file to the CDA Viewer application.s  F               o  Define logical names at the DCL command level or in a                   LOGIN.COM file.  D               Refer to the DECwindows Motif for OpenVMS Applications?               Guide for information about using the CDA Viewer.   *         1.6.1.1 Specifying an Options File  F        V1.2-3 Specify an options file by including a one-line entry in/               the file in the following format:s  4               TEXT TEXT_ENCODING text_encoding_value  $               o  TEXT is the format.  @               o  TEXT_ENCODING is the option you specify to CDA.  F               o  text_encoding_value is the value of the codeset. (See1                  Table 1-1 for a list of values.)f  I                                                                       1-5     n      ;     DECwindows Motif Version 1.2-3 for OpenVMS New Featuresl)     1.6 Internationalization Enhancements.    D           Table 1-1 shows the languages, codesets, and text-encoding           values.   :           Table 1-1 Asian Language Codes for Options FilesD           __________________________________________________________  ?           Language         Codeset          Text Encoding ValuerD           __________________________________________________________  5           Japanese         DEC Kanji        DEC_KANJI   5           Japanese         Super DEC Kanji  SDECKANJI   5           Traditional      DEC Hanyu        DEC_HANYU.           Chinesei  5           Simplified       DEC Hanzi        DEC_HANZI            Chinesep  6           Korean           DEC Korean       DEC_HANGUL  A           The following table shows examples of one-line entries.e  E           ___________________________________________________________m  1           Options File             One-Line Entryw  C           HANYU.CDA$OPTIONS        TEXT   TEXT_ENCODING   DEC_HANYUS  C           HANZI.CDA$OPTIONS        TEXT   TEXT_ENCODING   DEC_HANZI.  D           HANGUL.CDA$OPTIONS       TEXT   TEXT_ENCODING   DEC_HANGUL  ?           To view the EXAMPLES_CUSTOMERS.TXT file that contains B           Japanese text in DEC Kanji, use your editor to create anB           options file called KANJI.CDA$OPTIONS. Add the following%           one-line entry to the file:   &           TEXT TEXT_ENCODING DEC_KANJI  B           When you access the file through the Options File dialogE           box with the CDA Viewer, the EXAMPLES_CUSTOMERS.TXT file ist@           viewable in the DEC Kanji codeset (Japanese language).  "     1.6.1.2 Defining Logical Names  <    V1.2-3 The second option to enable viewing files in AsianB           languages is to specify the text file and encoding value(           by defining two logical names:             o  DDIF$READ_TEXT_GL             o  DDIF$READ_TEXT_GR       1-6x d  t      I                   DECwindows Motif Version 1.2-3 for OpenVMS New Features.I                                     1.6 Internationalization Enhancementsa    G               Table 1-2 shows the logical names and associated encoding                values.   B               Table 1-2 Logical Names for Specifying Text EncodingH               __________________________________________________________  H               DDIF$READ TEXT_GL     DDIF$READ_TEXT_GR     Encoding ValueH               __________________________________________________________     =               LATIN1                MCS                   MCSd  E               LATIN1                LATIN1                ISO Latin-1r  D               LATIN1                KATAKANA              ASCII-Kana  C               LATIN1                KANJI                 DEC Kanji   C               ROMAN                 MCS                   Roman-MCSn  ?               ROMAN                 LATIN1                Roman   E               ROMAN                 KANJI                 Roman-Kanji   D               ROMAN                 KATAKANA              Roman-Kana  C               LATIN1                HANZI                 DEC Hanzi   D               LATIN1                HANGUL                DEC Hangul  C               LATIN1                HANYU                 DEC Hanyu   I               You can define the logical names on the DCL command line or 2               in your LOGIN.COM file. For example:  /               $ DEFINE DDIF$READ_TEXT_GL LATIN1 .               $ DEFINE DDIF$READ_TEXT_GR KANJI  F               Note that this example defines the text encoding for DEC$               Kanji (see Table 1-2).  E         1.6.2 Converting Files That Contain Asian-Language Characters   D        V1.2-3 You can convert an Asian-language text file to anotherE               format by specifying an options file or by defining the F               logical names DDIF$READ_TEXT_GL and DDIF$READ_TEXT_GR as?               discussed in Section 1.6.1.1 and Section 1.6.1.2.   G               The format for converting a document from TEXT to anothero#               format is as follows:   O       $ CONVERT/DOCUMENT/OPTION=language.CDA$OPTIONS filename.TXT/FORMAT=TEXT -c7       _$ filename.output_extension/FORMAT=output_format   I                                                                       1-7  e  n      ;     DECwindows Motif Version 1.2-3 for OpenVMS New Featuresf)     1.6 Internationalization Enhancements     E           For example, to convert a traditional Chinese language text @           file to a DDIF file, enter the following command line:  7           $ CONVERT/DOCUMENT/OPTION=HANYU.CDA$OPTIONS - L           _$ GUIDELINES_PERSONNEL.TXT/FORMAT=TEXT  GUIDELINES_PERSONNEL.DDIF  :           Note that this command line does not include the6           /FORMAT=DDIF qualifier; DDIF is the default.  >           The output file, GUIDELINES_PERSONNEL.DDIF, contains           language data.  D           You can also create Asian language PostScript files from aE           DDIF, DTIF, or text (ASCII) file. For example, to convert aoC           DDIF file to PostScript (.PS) format, enter the followingr           command:  @           $ CONVERT/DOCUMENT filename.DDIF filename.PS/FORMAT=PS  C              ________________________ Note ________________________d  C              Convert only DDIF and DTIF files that contain languageb6              data to Asian language PostScript format.  C              ______________________________________________________r  ?           When you print an Asian language PostScript file on aPE           PostScript printer, ensure that the required language fontsnA           are available on the printer. Otherwise, the PostScriptoB           file defaults to a basic set of fonts. If these fonts doC           not exist, the PostScript file defaults to Courier fonts. B           Table 1-3 shows the languages and their associated basic           fonts.  8           Table 1-3 Languages and Associated Basic FontsD           __________________________________________________________  +           Language              Basic Fonts D           __________________________________________________________  C           Japanese              Ryumin-Light-EUC-H or Ryumin-Light- '                                 Hankakus  E           Hanyu                 Sung-Light-CNS11643, Sung-Light-DTSCSn  %           Hangul                Munjor  0           Hanzi                 XiSong-GB2312-80       1-8            I                   DECwindows Motif Version 1.2-3 for OpenVMS New FeaturesaI                                     1.6 Internationalization Enhancements     F                 ________________________ Note ________________________  <                 Vertical writing is not supported by the CDAF                 converters. All vertical text is printed horizontally.  F                 ______________________________________________________           1.7 NCSA Mosaic Browsere  E        V1.2-3 DECwindows Motif Version 1.2-3 for OpenVMS provides theeD               National Center for Supercomputing Applications (NCSA)G               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 E               sample software in the DECW$UTILS directory. We plan to I               replace this sample NCSA Mosaic browser implementation in a                future release.   A               The Mosaic browser enables OpenVMS users to search, B               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 MosaiclD               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               section:  8               o  Section 1.7.1, Starting Mosaic Software  4               o  Section 1.7.2, Creating a Home Page  H               o  Section 1.7.3, Configuring Mosaic to Process Multimedia                  Files  >               o  Section 1.7.4, Customizing the Mosaic Browser  I               o  Section 1.7.5, Restrictions for Using Mosaic from Behinde                  a Firewall   I                                                                       1-9  n  t      ;     DECwindows Motif Version 1.2-3 for OpenVMS New Featuresa     1.7 NCSA Mosaic Browsero    "     1.7.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 installation A           for DECwindows Motif Version 1.2-3 for OpenVMS systems.   C           To access the verb and start Mosaic, select Menus... froms?           the Options Menu in FileView. Mosaic is listed in theRA           Item Names list. Add the verb Mosaic to a menu, such asSB           the Applications Menu, so that you can invoke Mosaic andC           display the DECwindows Motif for OpenVMS home page. ReferfE           to Using DECwindows Motif for OpenVMS for information aboutl            adding verbs to menus.  C              ________________________ Note ________________________   <              You can display the sample DECwindows Motif forA              OpenVMS home page without a TCP/IP connection to the >              network. However, to access information contained@              in the topics in the Help menu requires that TCP/IP/              Services for OpenVMS be installed.   C              ______________________________________________________        1.7.2 Creating a Home Page  ?    V1.2-3 A home page lets you make information about yourself, =           your company, your products, and so on available on A           the Internet. Click on the On HTML... topic in the Help_A           menu for information about using HTML (Hypertext MarkuptC           Language) to create a home page. HTML uses markup tags tonD           tell Mosaic how to format text. A Beginner's Guide to HTMLE           is displayed, which provides information about markup tags,RD           examples, formatting, creating links, troubleshooting, andA           so on. Note that you can access topics in the Help menu @           only if your system is connected to the TCP/IP network,           using TCP/IP Services for OpenVMS.  C           As an example of an HTML source, see the DECwindows Motif3A           sample home page. Click on View Source... from the Filen&           menu to see the HTML source.         1-10 _  _      I                   DECwindows Motif Version 1.2-3 for OpenVMS New FeaturescI                                                   1.7 NCSA Mosaic Browserd    <         1.7.3 Configuring Mosaic to Process Multimedia Files  G               The Mosaic browser that is included with DECwindows MotifeH               Version 1.2-3 for OpenVMS provides support for recognizing:               and processing the following types of files:                 o  GIF                 o  Audio                 o  MPEG                  o  MIME                  o  PostScripty  G               If Mosaic encounters a hyperlink (or an anchor) to any oftH               these file types, it attempts to start an external programI               to display the image or to play the sound. If Mosaic cannotaH               locate an appropriate external viewer, it prompts the userG               to enter a file name where the data file can be stored in.8               case the data is needed outside of Mosaic.  I               To determine what external viewer will display the image ori8               play the sound, Mosaic does the following:  H               1. Determines the MIME type of the incoming file accordingD                  to either the file extension or the way the file is2                  specified by the document server.  H                  If the file extension is used to determine the externalI                  viewer, Mosaic uses either a built-in default list or an G                  extension map file that can be configured by the user.f  C               2. Matches the MIME file type of the incoming file todD                  an external viewer according to either the built-inG                  default list or a setup that is configured by the userdH                  and specified in the file DECW$UTILS:XMOSAIC-SETUP.COM.  E               For example, GIF files are mapped to the xv viewer. The G               xv viewer is shareware software that is not provided with.F               DECwindows Motif. However, the xv viewer is available atC               the following Uniform Resource Locator (URL) address:c  L                   http://gatekeeper.dec.com/pub/net/infosys/pw/pw-fetch.html  G               The xv mapping is defined in the file DECW$UTILS:XMOSAIC-iI               SETUP.COM, a self-documented command procedure, as follows:S  8                       $ XV   :== $DECW$EXAMPLES:PICT.EXE  I                                                                      1-11V i  1      ;     DECwindows Motif Version 1.2-3 for OpenVMS New FeaturesS     1.7 NCSA Mosaic Browser     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.r  /           Other mappings include the following:   E           ___________________________________________________________E  :           Image Type            Display/Sound Logical Name  .           audio/*               - >  showaudio  )           image/xwd             - >  xwudl  )           image/x-xwd           - >  xwud   )           image/x-xwindowdump   - >  xwud.  '           image/*               - >  xvs  .           application           - >  ghostview           /postscript   ?           Mappings in the previous list that are followed by an ?           asterisk (*) are available in some versions of Mosaic C           (for example, Version 2.4) that contain native HDF/netCDF            support.  @           Additional examples of external view setup in the file@           DECW$UTILS:XMOSAIC-SETUP.COM can include the following           definitions:  F             $ APLAY         :== mcr decsound -volume 70 -speaker -playF             $ SHOWAUDIO     :== mcr decsound -volume 70 -speaker -playC             $ GHOSTVIEW     :== view/format=ps/interface=decwindowso4             $ XWUD          :== $decw$utils:xwud.exe  (     1.7.4 Customizing the Mosaic Browser  =           You can customize the Mosaic browser by setting any ?           of the NCSA Mosaic X resources in the file DECW$USER_ ?           DEFAULTS:MOSAIC.DAT. The current list of resources is 7           available at the following Internet location:a  F             http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/Docs/resource  D           The class name for Mosaic for X is Mosaic. The information@           that follows shows the names and descriptions of the XD           resources. Note that class and resource names are the sameA           except that the first character in the resource name ist           capitalized.       1-12 o  b      I                   DECwindows Motif Version 1.2-3 for OpenVMS New Features I                                                   1.7 NCSA Mosaic Browser     1               The following resources are listed:   %               o  Functional resources   !               o  Visual resources                  o  Font resources   (               o  Proxy gateway resources  "               Functional Resources  H               Table 1-4 lists the functional resources and descriptions.  ,               Table 1-4 Functional ResourcesH               __________________________________________________________  /               Resource              DescriptionaH               __________________________________________________________  F               annotationsOnTop:     Indicates whether inlined documentG               Boolean               annotation hyperlinks are prepended_@                                     to the document (if true) orF                                     postpended (if false). (Default is+                                     false).e  E               autoPlaceWindows:     If set to false, the new DocumentrF               Boolean               View windows are not automaticallyE                                     positioned by the program itself; F                                     your Window Manager determines theA                                     placement. (Default is true.)s  I               catchPriorAndNext:    Controls whether using the keys Prior_C               Boolean               and Next (Page Up and Page DownrE                                     on most keyboards) are explicitlyYF                                     caught in the Document View windowI                                     and passed to the vertical scrollbar, H                                     or whether the normal Motif scrolledC                                     window mechanism is relied upon F                                     to automatically take this action.7                                     (Default is false.)G  D                                     If the Page Up and Page Down keyA                                     sequences are not functioning.G                                     appropriately for your environment,aH                                     set this resource to true. (Refer toD                                     the information about hot keys.)  I                                                  (continued on next page)   I                                                                      1-13d t         ;     DECwindows Motif Version 1.2-3 for OpenVMS New Featuresw     1.7 NCSA Mosaic Browser     0           Table 1-4 (Cont.) Functional ResourcesD           __________________________________________________________  +           Resource              Description D           __________________________________________________________  D         confirmDeleteAnnotation:Confirms deleted annotations throughC         Boolean                 a confirmation dialog box. (Default )                                 is true.)_  B           confirmExit: Boolean  Determines whether the NCSA Mosaic?                                 browser pops up a dialog box toA@                                 confirm exiting from the programD                                 when the Exit Program menu option is<                                 selected. (Default is true.)  >           defaultAuthorName:    Identifies your full name (for>           string                example, John Q. Public). YourC                                 full name is normally stored in the @                                 system password file, and MosaicC                                 extracts the name from that file if A                                 this resource is NULL; otherwise,aC                                 the value of this resource is used. 2                                 (Default is NULL.)  ?           defaultHeight:        Specifies the default height iniB           integer               pixels for a Document View window.1                                 (Default is 680.)   >           defaultHotlistFile:   Specifies a file name to storeA           string                the default hotlist (or a list ofiA                                 bookmarks). (Default is ".mosaic-o>                                 hotlist-default". The value ofA                                 the environment variable $HOME is :                                 prepended to this string.)  E           defaultWidth:         Specifies the default width in pixels D           integer               for a Document View window. (Default(                                 is 620.)  E                                              (continued on next page)T                 1-14 m  u      I                   DECwindows Motif Version 1.2-3 for OpenVMS New Features I                                                   1.7 NCSA Mosaic Browsern    4               Table 1-4 (Cont.) Functional ResourcesH               __________________________________________________________  /               Resource              Description,H               __________________________________________________________  B               delayImageLoads:      Selects delayed image loading,H               Boolean               which is for users with slow networkG                                     connections. If set to true, Mosaic I                                     substitutes a small icon for inlined- I                                     images and an arrow icon for inlined-iG                                     images that also act as hyperlinks.oG                                     Clicking on an icon tells Mosaic towH                                     load that inlined-image; clicking onH                                     the arrow is equivalent to following=                                     the associated hyperlink.e  I                                     Selecting Load Images in Current fromaE                                     the Mosaic Options menu loads and_F                                     displays all the inlined-images inG                                     the current document. Delayed image I                                     loading can also be selected with the G                                     -dil command-line flag or on a per-xI                                     window basis from the Options menu inh?                                     Mosaic. (Default is false.)   C               displayURLsNotTitles: Displays URLs wherever document_D               Boolean               titles are usually displayed, ifD                                     set to true. (Default is false.)  F               DocsDirectory:        Overrides the location of the helpA               string                documents. (Default is NULL.)k  G               documentsMenuSpecfile:Specifies the name of the file thatCE               string                holds an optional "Documents Menu I                                     Specfile" to allow sites to add theirnD                                     own Documents menu to the MosaicG                                     menu bar. For more information, see D                                     the documentation about creatingB                                     a configurable Documents menu.F                                     (Default is "/usr/local/lib/mosaic6                                     /documents.menu".)  I                                                  (continued on next page)i      I                                                                      1-15i A  i      ;     DECwindows Motif Version 1.2-3 for OpenVMS New Features      1.7 NCSA Mosaic Browser     0           Table 1-4 (Cont.) Functional ResourcesD           __________________________________________________________  +           Resource              DescriptionpD           __________________________________________________________  A           fancySelections:      Cuts and pastes from the DocumentiA           Boolean               View window with fancy selectionscA                                 enabled in the HTML widget, whichi>                                 results in underlined headers,D                                 bulleted lists, and so on, if set toD                                 true. Uses normal selection behaviorE                                 if set to false. Note that selections C                                 can be for each window at any time. 3                                 (Default is false.)f  D           fullHostname: string  Allows explicit setting of the fullyD                                 qualified host name for systems thatB                                 fail on a call to gethostbyname().B                                 Use the fullHostname resource onlyA                                 if necessary, in conjunction withm4                                 gethostbynameIsEvil.  >           gethostbynameIsEvil:  Set to true if you are running>           Boolean               your system on a Sun set up so=                                 that when the system attemptst>                                 to find its own full host nameD                                 through gethostbyname(),  the system>                                 coredumps. (Default is false.)  B           globalExtensionMap:   Set to the location of the system->           string                wide extension map config file;                                 of your choice. (Default is D                                 "/usr/local/lib/mosaic/mime.types".)  A           globalHistoryFile:    Specifies the name of the file tos?           string                store the global history of allfB                                 documents accessed from session toD                                 session. (Default is .mosaic-global-E                                 history. The value of the environmenteC                                 variable $HOME will be prepended to -                                 this string.)a  E                                              (continued on next page)D           1-16    n      I                   DECwindows Motif Version 1.2-3 for OpenVMS New Features_I                                                   1.7 NCSA Mosaic Browserd  4               Table 1-4 (Cont.) Functional ResourcesH               __________________________________________________________  /               Resource              Description H               __________________________________________________________  I               globalTypeMap:        Specifies the location of the system-_B               string                wide mailcap (type map config)D                                     file of your choice. (Default isE                                     "/usr/local/lib/mosaic/mailcap".)e  G               gunzipCommand:        Specifies the command to uncompressaF               string                gzip files (that is, files with anD                                     extension of .z.) You can obtainG                                     gunzip from prep.ai.mit.edu in /pubvI                                     /gnu. (Default is gunzip -n -f, whichiH                                     requires the 1.2.4 version of gzip.)  G               hdfMaxImageDimension: Specifies the maximum height and/or D               integer               width of an HDF inlined image in=                                     pixels. (Default is 400.)   C             hdfMaxDisplayedDatasets:Specifies the maximum number of F             integer                 displayed data sets while browsingG                                     HDF files. If more than the maximum G                                     number exist in an HDF file, Mosaic C                                     displays the HDF file in "brief <                                     mode."" (Default is 15.)  C           hdfMaxDisplayedAttributes:Specifies the maximum number ofgG           integer                   displayed attributes while browsing G                                     HDF files. If more than the maximum G                                     number exist in an HDF file, MosaicMC                                     displays the HDF file in "brief ;                                     mode." (Default is 10.)   I               hdfPowerUser:         Set to true if most of the supporting H               Boolean               text in an HDF file will be removed.7                                     (Default is false.)   G               homeDocument: string  Specifies the document to access at H                                     program startup. See the informationA                                     about on specifying your home @                                     document. (Default is http:/C                                     /www.ncsa.uiuc.edu/SDG/Software @                                     /Mosaic/NCSAMosaicHome.html)  I                                                  (continued on next page)v  I                                                                      1-17t i  m      ;     DECwindows Motif Version 1.2-3 for OpenVMS New Featurest     1.7 NCSA Mosaic Browsere    0           Table 1-4 (Cont.) Functional ResourcesD           __________________________________________________________  +           Resource              Description D           __________________________________________________________  B           imageCacheSize:       Specifies the size of the inlined-?           integer               image cache in kilobytes. The -dA                                 ics command-line flag can also bev?                                 used. All the images in a given(A                                 document are (temporarily) cachedeE                                 while on that page, regardless of thenC                                 imageCacheSize value. Cache flusheseC                                 the least recently viewed. (Default:)                                 is 2048.)   A           initialWindowIconic:  Set to true if the first Document D           Boolean               View window opened (when the programC                                 starts) will be iconified. (Defaultu*                                 is false.)  >           maxWaisResponses:     Controls the maximum number ofC           integer               matches Mosaic accesses from a WAIS_9                                 server. (Default is 200.)m  C     personalAnnotationDiretory: Specifies the name of the directory :     string                      in which to store personal?                                 annotations (as well as the log @                                 file of all personal annotations?                                 currently in existence). If the B                                 named directory does not exist, itA                                 is created. However, intermediatee>                                 directories, if any are named,<                                 are not created. (Default isA                                 .mosaic-personal-annotations. TheWA                                 value of the environment variablei?                                 $HOME will be prepended to this (                                 string.)  =           personalExtensionMap: Specifies the location of theVD           string                personal extension map configurationA                                 file of your choice. The value ofc@                                 the environment variable HOME isC                                 prepended. (Default is .mime.types)S  E                                              (continued on next page)        1-18 l  t      I                   DECwindows Motif Version 1.2-3 for OpenVMS New FeaturesfI                                                   1.7 NCSA Mosaic BrowserM    4               Table 1-4 (Cont.) Functional ResourcesH               __________________________________________________________  /               Resource              DescriptionhH               __________________________________________________________  A               personalTypeMap:      Specifies the location of thefI               string                personal mailcap file of your choice. I                                     The value of the environment variabletB                                     HOME is prepended. (Default is-                                     .mailcap)r  E               printCommand: string  Specifies the name of the defaultnF                                     command for the Print menu option.A                                     This command accepts a single E                                     argument: the name of the file to I                                     print. Note that this location can be_I                                     changed at any time through the PrintnI                                     option's dialog box. (Default is lpr)   E               recordCommandLocation:Specifies the location (full path G               string                name) of the command used to record C                                     audio annotations (on Sun, SGI, C                                     and HP platforms). If the namedeF                                     command does not exist when MosaicE                                     is started, audio annotations arerD                                     disabled (the menu entry becomesH                                     insensitive). (Default is "/usr/sbinI                                     /recordaiff" on SGI; "/usr/demo/SOUNDeD                                     /record" on Sun; "/usr/audio/bin7                                     /srecorder" on HP.)   H               recordCommand:        Specifies the command used to recordG               string                audio annotations; this is the full G                                     command, using the command named intF                                     recordCommandLocation as the firstD                                     word. (Default is "recordaiff -nD                                     1 -s 8 -r 8000" on SGI; "record"B                                     on Sun; "srecorder -au" on HP.F                                     The named command accepts a singleI                                     additional argument: the file name ofvH                                     the new audio file. The command alsoI                                     correctly terminates recording when ae4                                     SIGINT is sent.)  I                                                  (continued on next page)   I                                                                      1-193 r  e      ;     DECwindows Motif Version 1.2-3 for OpenVMS New Featuresl     1.7 NCSA Mosaic Browseru  0           Table 1-4 (Cont.) Functional ResourcesD           __________________________________________________________  +           Resource              Description_D           __________________________________________________________  C           reloadReloadsImages:  Clears out the Reload option cachednC           Boolean               image data for the current document D                                 before reloading the document if setC                                 to true; thus causing the images to D                                 also be reloaded. This is useful forD                                 HTML authors who are using Mosaic toD                                 view their work. (Default is false.)  C           sendmailCommand:      Specifies a pointer to the sendmail D           string                binary. It assumes that this programC                                 accepts command-line arguments that C                                 specify addresses to which messagesxB                                 should be mailed and accepts otherD                                 headers and message text from stdin.A                                 (Default is "/usr/lib/sendmail".)   E           simpleInterface:      Allows the Mosaic menu bar and bottomlD           Boolean               button configuration to be minimizedA                                 considerably. (Default is false).   C           tmpDirectory: string  Specifies the name of the directory A                                 in which to store temporary files C                                 generated by Mosaic. This directory @                                 should contain at least 10 or 20E                                 megabytes, in case you to pull down a B                                 very large data file. Setting this?                                 resource is equivalent to using B                                 the command-line flag, -tmpdir, or@                                 setting the environment variable'                                 TMPDIR.   B           trackFullURLs:        Enables prototypical smart display>           Boolean               of "where you're going" during@                                 mouse tracking, including formatE                                 definition, if set to false. (Default_)                                 is true.)   E                                              (continued on next page)_           1-20 _  _      I                   DECwindows Motif Version 1.2-3 for OpenVMS New FeaturesgI                                                   1.7 NCSA Mosaic Browserw    4               Table 1-4 (Cont.) Functional ResourcesH               __________________________________________________________  /               Resource              Description H               __________________________________________________________  E               trackPointerMotion:   Sets the mouse pointer so that it H               Boolean               will not be tracked so that URLs areH                                     visible on the lower status line, ifD                                     set to false. (Default is true.)  F               trackVisitedAnchors:  Displays visited anchors (that is,H               Boolean               anchors that point to documents thatG                                     have previously been viewed) with a I                                     different style than anchors that are H                                     not yet visited, if set to true. (OnH                                     slow systems, changing this resourceF                                     to false may substantially improveH                                     the performance of Mosaic.) (Default-                                     is true.)   F               tweakGopherTypes:     Mosaic interprets Gopher documentsI               Boolean               strictly by the Gopher typing system, F                                     if set to false. When set to true,D                                     Mosaic uses its own mechanism toF                                     determine the file types of GopherA                                     documents. (Default is true.)   I               twirlIncrement:       Indicates the minimum number of bytes D               integer               that are are transferred betweenD                                     updates of the twirling transferG                                     icon for normal (FTP, Gopher, HTTP) A                                     transfers. (Default is 4096.)   I               twirlingTransferIcon: Set to false to turn off the twirling H               Boolean               NCSA logo during document transfers.H                                     Clicking the icon still interrupts a@                                     transfer. (Default is true.)  G               uncompressCommand:    Specifies the command to uncompress D               string                compressed files (that is, filesI                                     with an extension of .Z). (Default is 0                                     uncompress).  I                                                  (continued on next page)_    I                                                                      1-21i :         ;     DECwindows Motif Version 1.2-3 for OpenVMS New Features      1.7 NCSA Mosaic Browserc    0           Table 1-4 (Cont.) Functional ResourcesD           __________________________________________________________  +           Resource              Description D           __________________________________________________________  @         useDefaultExtensionMap: Set to false to keep any defaultD         Boolean                 file-extension-to-MIME-type mappingsB                                 from Mosaic. Keeping this resourceB                                 setting to true and overriding the@                                 default as necessary is strongly?                                 recommended. (Default is true.)   @           useDefaultTypeMap:    Set to false to keep any default<           Boolean               MIME-type-to-external-viewerD                                 mappings from Mosaic. It is strongly?                                 recommended that you leave this B                                 resource set to true; override theA                                 setting as necessary. (Default ish&                                 true.)  E           useGlobalHistory:     Automatically stores a global history ?           Boolean               of everywhere you visit, if set A                                 to true. (This history is used topA                                 shade anchors in different colors @                                 based on whether you visited the?                                 corresponding documents, if the/C                                 resource trackVisitedAnchors is set <                                 to true.) (Default is true.)  A           xtermCommand: string  Specifies the name of the command C                                 used to start a terminal window for C                                 a telnet session. (Default is xterm A                                 on most platforms; the default is C                                 aixterm -v on IBM AIX 3.x systems.)              Visual Resources  B           Table 1-5 lists the visual resources that are associated@           with the HTML widget that is used in the Document View@           window. Specify these resources in the file DECW$USER_6           DEFAULTS:MOSAIC.DAT in the following format:  '                Mosaic*anchorColor: cyan              1-22 _  _      I                   DECwindows Motif Version 1.2-3 for OpenVMS New Features I                                                   1.7 NCSA Mosaic Browser_      (               Table 1-5 Visual ResourcesH               __________________________________________________________  /               Resource              Description H               __________________________________________________________  H               anchorColor: color    Specifies the color to shade anchorsF                                     whose corresponding documents haveI                                     not previously been visited. (Default .                                     is blue3.)  H               visitedAnchorColor:   Specifies the color to shade anchorsF               color                 whose corresponding documents haveH                                     previously been visited. (Default is0                                     violetred4.)  H               activeAnchorFG:       Specifies the color to shade anchorsD               color                 that are in the process of being@                                     activated. (Default is red.)  D               activeAnchorBG:       Specifies the color to shade theF               color                 background of the anchors that areF                                     in the process of being activated.D                                     (Default is grey80, which is theG                                     same color as the background in theD-                                     browser.)i  D               anchorUnderlines:     Specifies the number of lines toA               integer               draw underneath the unvisited F                                     anchors (Valid values: 0, 1, 2, 3)3                                     (Default is 1.)   I             visitedAnchorUnderlines:Specifies the number of lines to draw I             integer                 underneath the visited anchors. ValidsF                                     values: 0, 1, 2, 3 (Default is 1.)  H              dashedAnchorUnderlines:Sets drawn lines under the unvisitedF              Boolean                anchors to dashes, if set to true.7                                     (Default is false.)   D       dashedVisitedAnchorUnderlines:Setsndrawn lines under unvisitedF       Boolean                       anchors to dashes, if set to true.7                                     (Default is false.)   I                                                  (continued on next page)   I                                                                      1-23            ;     DECwindows Motif Version 1.2-3 for OpenVMS New Features      1.7 NCSA Mosaic Browser     ,           Table 1-5 (Cont.) Visual ResourcesE           ___________________________________________________________e  +           Resource              DescriptionsE            ___________________________________________________________  E           colorsPerInlinedImage:Specifies the number of unique colors_C           integer               to allocate for each inlined-image.c@                                 (Note that this setting does notD                                 affect the images that are displayedE                                 externally to the NCSA Mosaic browser E                                 (for example, GIF images passed to an C                                 external viewer).) (Default is 50.)   D           percentVerticalSpace: Specifies the height of the verticalE           integer               space between paragraphs, headers andhC                                 paragraphs, and so on, as expressedsB                                 as a percentage of the normal line8                                 height. (Default is 90.)  C      reverseInlinedBitmapColors:Specifies to reverse foreground and @      Boolean                    background colors in inlined XBMD                                 bitmaps, if set to true. (Default is'                                 false.)c  @           verticalScrollOnRight:Specifies that the Document ViewC           Boolean               window places its scroll bar on theoD                                 left side, if set to false. (DefaultE           ______________________is_true.)____________________________              Font Resources  A           Font resources, which are also associated with the HTML C           widget, can be changed dynamically from the Options menu.aC           Table 1-6 lists the font resource names and descriptions.c        Table 1-6 Font Resources J      _____________________________________________________________________  !      Resource         DescriptioneJ      _____________________________________________________________________  A       font: font       Used in normal formatted text. (Default is O                       "-adobe-times-medium-r-normal-*-17-*-*-*-*-*-iso8859-1".)   A       italicFont:      Used in italic formatted text. (Default is P       font             "-adobe-times-medium-i-normal-*-17-*-*-*-*-*-iso8859-1".)  E                                              (continued on next page)o       1-24  I                   DECwindows Motif Version 1.2-3 for OpenVMS New Features I                                                   1.7 NCSA Mosaic Browser       Table 1-6 (Cont.) Font ResourcesE _____________________________________________________________________r    Resource             DescriptionE _____________________________________________________________________w  : boldFont: font    Used in bold formatted text. (Default isI                   "-adobe-times-bold-r-normal-*-17-*-*-*-*-*-iso8859-1".)   A fixedFont: font  Used in fixed (typewriter style) formatted text._P          (Default is "-adobe-courier-medium-r-normal-*-17-*-*-*-*-*-iso8859-1".)  6 header1Font: font Used in level 1 headers. (Default isI                   "-adobe-times-bold-r-normal-*-24-*-*-*-*-*-iso8859-1".)   6 header2Font: font Used in level 2 headers. (Default isI                   "-adobe-times-bold-r-normal-*-18-*-*-*-*-*-iso8859-1".)   6 header3Font: font Used in level 3 headers. (Default isI                   "-adobe-times-bold-r-normal-*-17-*-*-*-*-*-iso8859-1".)   6 header4Font: font Used in level 4 headers. (Default isI                   "-adobe-times-bold-r-normal-*-14-*-*-*-*-*-iso8859-1".)   6 header5Font: font Used in level 5 headers. (Default isI                   "-adobe-times-bold-r-normal-*-12-*-*-*-*-*-iso8859-1".)b  6 header6Font: font Used in level 6 headers. (Default isI                   "-adobe-times-bold-r-normal-*-10-*-*-*-*-*-iso8859-1".)o  1 addressFont: font Used in addresses. (Default is cK                   "-adobe-times-medium-i-normal-*-17-*-*-*-*-*-iso8859-1".)   H plainFont: font   Used in plaintext regions or pre-formatted documents.                    (Default is M                   "-adobe-courier-medium-r-normal-*-14-*-*-*-*-*-iso8859-1".)   6 listingFont: font Used in listing regions. (Default isM                   "-adobe-courier-medium-r-normal-*-12-*-*-*-*-*-iso8859-1".)   ; fixedboldFont:    Used for bold in fixed (typewriter style)s! font              formatted text.   7 fixeditalicFont:  Used for italics in fixed (typewriter ( font              style) formatted text.  7 plainboldFont:    Used for bold in plaintext regions oro) font              preformatted documents.   9 plainitalicFont:  Used for italic in plaintext regions oro) font              preformatted documents. E _____________________________________________________________________t  %               Proxy Gateway Resources   C               Support for proxy gateways is still experimental. The F               resources listed at the following URL may be pointers to               proxy gateways:a  I                                                                      1-25            ;     DECwindows Motif Version 1.2-3 for OpenVMS New Features      1.7 NCSA Mosaic Browserh    6              Mosaic*httpProxy: http://www.cern.ch:911/  C           Table 1-7 provides additional details about proxy gateway 9           support in the NCSA Mosaic Version 2.4 browser.   +           Table 1-7 Proxy Gateway ResourcessD           __________________________________________________________  +           Resource              Description   D           __________________________________________________________  2           ftpProxy: String      Used for ftp URLs.  5           gopherProxy: String   Used for gopher URLs.e  3           httpProxy: String     Used for http URLs.   3           newsProxy: String     Used for news URLs._  3           waisProxy: String     Used for wais URLs.   ;           ProxyGateway: String Used for all access methods._  >     1.7.5 Restrictions for Using Mosaic from Behind a Firewall  D    V1.2-3 The following sections present information about using theB           ProxyGateway and NoProxy resources with Mosaic to access@           information on the Internet when security restrictionsC           (that is, a firewall) exist between internal and external &           network access at your site.  !     1.7.5.1 ProxyGateway Resource   >           NCSA Mosaic Version 2.4 provided in DECwindows Motif>           Version 1.2-3 for OpenVMS supports the proxy gatewayE           (ProxyGateway) resource. A proxy gateway is a trusted agentgC           that enables Mosaic to access network information that is >           either within or outside the firewall, but not both.  A           When the Mosaic browser is used from behind a firewall, C           Mosaic can use the proxy gateway to pass network requests ?           to the Internet in a URL formatted address. The proxy @           gateway returns the results to the Mosaic browser. The>           process of passing and returning network requests is@           transparent to the user. You can view documents on the&           Internet without difficulty.  E           Note, however, that if the proxy gateway is located outsidec@           of your firewall, then information behind the firewallB           (such as home pages, World Wide Web documents, and Notes9           files) cannot be accessed by the proxy gateway.        1-26 d  n      I                   DECwindows Motif Version 1.2-3 for OpenVMS New Features I                                                   1.7 NCSA Mosaic Browser               1.7.5.2 NoProxy Resource  B               If your site requires the ability to access InternetF               information both within and outside the firewall, then aE               version of Mosaic that supports the NoProxy resource is E               required. This resource allows you to specify a list of G               domains that should not be consulted by the proxy gateway G               (that is, access to information in these domains does not ,               go through the proxy gateway).  G               NCSA Mosaic Version 2.4a for OpenVMS supports the NoProxy E               resource and enables access to a proxy gateway. If your E               site operates in a firewall environment and you need touD               access information from both within and outside of theG               firewall, you can copy this pre-release version of Mosaic %               from the following URL:_  9                  ftp://gatekeeper.dec.com/pub/DEC/Mosaic/   I               As previously stated, the NoProxy resource restricts access_D               for the proxy gateway to a set of domains that are notI               consulted by the proxy gateway. You can specify the NoProxy G               resource, provided that you have NCSA Mosaic Version 2.4arD               for OpenVMS, in the file DECW$USER_DEFAULTS:MOSAIC.DAT0               according to the following format:  J                    Mosaic*ProxyGateway:    http://www-proxy.site.org:8080/>                    Mosaic*NoProxy:         localhost, site.org  I               ___________________________________________________________   /               Where:                Description I               ___________________________________________________________   H               www-proxy.site.org    Name of the host that runs the proxy*                                     server  D               8080                  Port number through which MosaicD                                     communicates to the proxy server8                                     through the firewall  A               local host, site.org  List of site names, which arehF                                     separated by commas, excluded fromB                                     going through the proxy server  B               Refer to the following location (URL) for additional/               information about proxy gateways:   H                 http://info.cern.ch/hypertext/WWW/Daemon/user/Guide.html  I                                                                      1-27  h  a      ;     DECwindows Motif Version 1.2-3 for OpenVMS New Featuresa"     1.8 Console Window Application    "     1.8 Console Window Application  C    V1.2-3 DECwindows Motif Version 1.2-3 for OpenVMS introduces ther?           feature of displaying console messages in the Console @           Window application. Console messages are not displayedB           in the console window by default in the DECwindows MotifA           Version 1.2-3 for OpenVMS product. Previous versions of C           DECwindows Motif displayed the console window by default.p  C              ________________________ Note ________________________i  <              The new default for displaying console messages>              in the DECwindows Motif Version 1.2-3 for OpenVMSA              release is DISABLE. The default in previous versions =              of DECwindows Motif was ENABLE. These values are ?              discussed in greater detail later in this section. ?              If the user selects the Alternate Console port foreB              console communications, the DECwindows Console Window@              is disabled and the console broadcasts are enabled.@              Refer to the owner's guide for your workstation for>              information about selecting the Alternate Console              port.C              ______________________________________________________f  @           Specify how to display messages by defining the globalA           symbol DECW$CONSOLE_SELECTION in the customized startupeD           file SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM. Enter one of;           the following values: WINDOW, DISABLE, or ENABLE.              o  WINDOW   <              Displays console messages in the Console WindowB              application. This is a new application available withE              the DECwindows Motif Version 1.2-3 for OpenVMS software. C              If you specify the WINDOW value, the Console Window is D              displayed in the lower right corner of the login screenD              by default and continues to be displayed after the user#              logs in to the system.h  ;              The Console Window application shares the sameHE              executable file and looks similar to the Message Window. @              However, a menu bar is not displayed in the ConsoleE              Window; it reads its resources from the DECW$CONSOLE.DAT A              file instead of from the DECW$MESSAGEPANEL.DAT file. E              Internally, the Console Window is invoked by running the        1-28    u      I                   DECwindows Motif Version 1.2-3 for OpenVMS New FeatureseI                                            1.8 Console Window Application     G                  DECW$MESSAGEPANEL.EXE executable with the command line !                  option -console.n  F                  To control the initial position of the Console WindowF                  and the classes of OPCOM output that are enabled, youG                  can the define the following global symbol in the file.9                  SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM:t  )                     DECW$CONSOLE_GEOMETRY   D                     This symbol specifies the value of the -geometryE                     option in the DECW$MESSAGEPANEL.EXE command line;AD                     this command is used to start the Console WindowC                     application. The default value is "-0-0", whichwE                     specifies the location of the window in the lower /                     right corner of the screen.r  F                     To position the window at the lower left corner ofC                     the screen, for example, add the following line F                     to the command file SYS$MANAGER:DECW$PRIVATE_APPS_                     SETUP.COM:  6                      $ DECW$CONSOLE_GEOMETRY == "+0-0"  "               o  DISABLE (default)  A                  Disables broadcasts to the OPA0: device. Console ,                  messages are not displayed.                 o  ENABLE   E                  Displays console messages in the console window. TherH                  console window is a six-line display area at the top of(                  the workstation screen.  F                 ________________________ Note ________________________  A                 Although ENABLE was the default value in previouseD                 releases of DECwindows Motif, it is recommended thatB                 you do not use this option in the DECwindows MotifE                 Version 1.2-3 for OpenVMS product. Displaying consoleiE                 messages by default in the console window can corrupt 8                 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.  I                                                                      1-29            ;     DECwindows Motif Version 1.2-3 for OpenVMS New Features 2     1.9 Using Shareable Linkages to Install Images    2     1.9 Using Shareable Linkages to Install Images  ?   V1.2-3  On OpenVMS Alpha systems, using shareable linkages to C           install images on DECwindows Motif Version 1.2-3 softwares(           offers the following features:  >           o  Enhanced startup performance by decreasing image-              activation time  E           o  Conserved memory usage by decreasing the total of memory $              pages used by the image  >           By default, the following images are installed usingB           shareable linkages on DECwindows Motif Version 1.2-3 for            OpenVMS Alpha systems:  2           o  DECW$XLIBSHR.EXE (MIT Release 5 Xlib)  <           o  DECW$XTLIBSHRR5.EXE (MIT Release 5 Intrinstics)  B           o  DECW$XMLIBSHR12.EXE (OSF/Motif Release 1.2.3 Toolkit)  @           o  DECW$MRMLIBSHR12.EXE (OSF/Motif Release 1.2.3 Motif              Resource Manager)  <           o  DECW$DXMLIBSHR12.EXE (Digital Extensions to the              OSF/Motif Toolkit)   B           These images are installed using the /SHARE=ADDRESS_DATAC           option. Note that if you accept the default, these images_A           cannot be replaced during a restart of DECwindows MotifnC           software. As a result, when you restart DECwindows Motif, B           the images are not replaced and the following message is           displayed:  L      Shared linkage sections are in use on this system and no images will beO      reinstalled. If you are restarting DECwindows to reinstall images then youe      must reboot the system.  B           To replace new images installed with this option, reboot>           the system. Note that you can disable shared-linkageC           sections by defining the logical name DECW$IGNORE_SHARED_e=           ADDRESS in the SYSTARTUP_VMS.COM command procedure.        1-30           I                   DECwindows Motif Version 1.2-3 for OpenVMS New FeaturesrI                                       1.10 Window Manager Overlay Supportt    +         1.10 Window Manager Overlay Supportf  H        V1.2-3 The latest version of the Window Manager (MWM) is modifiedB               to support overlays and utilize additional planes of@               memory, which are available on several 3D graphicsD               accelerators: ZLX-M1, ZLX-M2, ZLX- L1, ZLX-E2, ZLX-E3,E               ZLXp-E2, and ZLXp-E3. The Window Manager places borders H               and banners for all the windows into these extra planes ofH               memory and thereby reduces the number of expose events for2               your applications that use overlays.  D               Modify your existing applications that use overlays toE               avoid potential problems with the colormap. Set up yoursB               system to share the overlay colormap with the WindowE               Manager, as the hardware supports only one colormap for_!               the overlay planes.o  G               To modify your applications to share the overlay colormap_E               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.o  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:   !                $ mwm -multiscreen-  G               Edit this line by adding the -Overlay command-line option_               as follows:o  ,                $ 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.F  I               o  Border and banner colors also change when you change thel)                  colors of your colormap.-  I                                                                      1-31s           ;     DECwindows Motif Version 1.2-3 for OpenVMS New Features '     1.10 Window Manager Overlay Supportd               Restrictions  E           The following restrictions apply when you enable the Windowr"           Manager to use overlays:  C           o  The Window Manager supports only single-screen systems*C              and does not function correctly with multiple graphicsl!              devices (multihead).e  D           o  If you select a Matte Size value other than "None" fromD              the Window Manager options list, the Matte color is notE              correct; that is, the color does not match the selection -              and is occasionally transparent.b  A           o  If you select "Show feedback when moving or resizingnA              windows" from the Workspace Options menu, the window-@              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 windowr!              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.  E           o  The ZLXp-E2 and ZLXp-E3 3D graphics accelerators are not E              currently supported when you run the Window Manager witht.              the -Overlay command-line option.                                   1-32 i  n                    I                                                                         2_I         _________________________________________________________________e  I                                                General User Release Notesh    F               This chapter contains information about DECwindows Motif                for general users.  H         2.1 Notes Specific to DECwindows Motif Version 1.2-3 for OpenVMS             Software  G        V1.2-3 The release notes in this chapter are cumulative from VMSrH               DECwindows Motif Version 1.0 and still apply to DECwindowsE               Motif Version 1.2-3 for OpenVMS software. The following F               sections contain general user release notes that pertainD               specifically to the DECwindows Motif Version 1.2-3 for               OpenVMS release:  2               o  Section 2.3, Using Tear-Off Menus  E               o  Section 2.5, Toolkit Warning in the Work in Progress                   Dialog Boxf  8               o  Section 2.6.1.1, Draft-Quality Printing  C               o  Section 2.6.2, Including Comment Characters in the $                  DECW$BOOKSHELF File  5               o  Section 2.6.5, CDA Run-Time Servicesw  8               o  Section 2.6.9.1, DECsound Prerequisites  2               o  Section 2.6.9.3, Escape Sequences  C               o  Section 2.6.10.1, Changing the Auto Repeat Settingi  6               o  Section 2.6.10.2, Positioning DECterm  8               o  Section 2.6.10.11, Initializing DECterm  I               o  Section 2.6.12.1, Removing Support for LinkWorks Managerx                  (DEClinks)r  0               o  Section 2.6.13, DECwindows Mail  @               o  Section 2.6.13.1, Responses to Keyboard Actions  I                                                                       2-1e o  g           General User Release NotesM     2.1 Notes Specific to DECwindows Motif Version 1.2-3 for OpenVMS Softwares    C           o  Section 2.6.16.1, Notepad Is Linked with the OSF/Motifr"              Release 1.1.3 Toolkit  E           o  Section 2.6.19.1, Removing Support for LinkWorks Managerc              and LinkWorks  A           o  Section 2.6.19.2, Invoking DECchart from the Sessiona&              Manager Applications Menu  @           o  Section 2.10, Unsupported Translations by the Motif              XmText Widget       2.2 Using Drag and Dropr  ?     V1.2  The DECwindows Motif for OpenVMS applications supportwB           the drag-and-drop feature with the exception of Notepad.C           DECwindows Mail supports the drag-and-drop feature in allnE           windows except the main message area, where DECwindows MailuE           has its own drag-and-drop; you can use MB2 to move messagesw(           around with the SVN interface.  @           The drag-and-drop feature lets you move or copy screenE           objects; this feature is provided primarily for programmers <           who choose to incorporate drag-and-drop into theirC           applications. For example, you can move text from buttonst!           and paste it elsewhere.e  4           To drag and drop text into a new location:  <           1. Select the text to be copied or moved with MB1.  D           2. To move the text, press and hold MB2; to copy the text,              press and hold               Ctrl/MB2.  .              A move or copy icon is displayed.  E           3. Drag the icon to the location where you want to drop theC"              text and release MB2.  E              If the object is highlighted as you drag the icon acrossy:              it, you can drop the text into that location.           2-2n o  e      I                                                General User Release Notes I                                                  2.3 Using Tear-Off Menus               2.3 Using Tear-Off Menus  G        V1.2-3 DECwindows Mail supports tear-off menus in the DECwindowss6               Motif Version 1.2-3 for OpenVMS release.  G         V1.2  The following applications do not support tear-off menus:                  o  CDA Viewero                 o  Notepad                 o  Print Screenr  H               Refer to Section 5.3.2.2 for instructions on tearing off a/               menu and closing a tear-off menu.   <         2.4 Access Control Not Explicitly Enabled by Default  I         V1.0  DECwindows Motif does not enable access control by default. I               Instead, the product uses access control set by the server._I               The DECwindows X11 display server enables access control at                startup time.   B               To force the DECwindows Session Manager to enable orF               disable access control explicitly at login time, you can8               define one of the following logical names:  H               $ DEFINE/SYSTEM/EXECUTIVE DECW$LOGIN_ACCESS_CONTROL ENABLE  I               $ DEFINE/SYSTEM/EXECUTIVE DECW$LOGIN_ACCESS_CONTROL DISABLE   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 thef               logical name.d  >         2.5 Toolkit Warning in the Work in Progress Dialog Box  E        V1.2-3 When you run DECwindows Motif Version 1.2-3 for OpenVMS B               software on OpenVMS Version 6.2 systems, the Work inF               Progress dialog box displays the following error message&               in several applications:  N         X Toolkit Warning: locale not supported by C Library, locale unchanged  I               You can safely ignore this error message; operations of thee,               applications are not affected.  I                                                                       2-3y f  t           General User Release Notes*     2.6 DECwindows Motif Application Notes    *     2.6 DECwindows Motif Application Notes  B           This section contains information about DECwindows Motif           applications._       2.6.1 Bookreader  ;           This section includes problems, restrictions, andi5           enhancements in the Bookreader application.   "     2.6.1.1 Draft-Quality Printing  >    V1.2-3 The Bookreader application allows only draft-quality'           printing for books or topics.s  A     2.6.2 Including Comment Characters in the DECW$BOOKSHELF Filer  A    V1.2-3 If you include a comment character (! or #) in the lastiB           line of the DECW$BOOKSHELF file, Bookreader fails with aE           reserved operand fault. As a workaround, ensure that you do B           not add comment characters to the last line of the file.  E           This restriction will be removed in a future version of the_           product.       2.6.3 Calendar  C           This section describes problems and restrictions with the            Calendar application.T       2.6.3.1 Data-File Format  ?     V1.2  The Calendar data-file format in DECwindows Motif forfA           OpenVMS is incompatible with previous Calendar formats. C           When you run the Calendar application in DECwindows MotifoB           Version 1.2 for OpenVMS for the first time, a dialog boxD           in the Calendar application is displayed that asks whetherE           to convert the Calendar data file to the new format. If youlC           answer "Yes", the data files are converted. Once the data D           file is converted to the new format, the file is no longer@           usable by previous (that is, pre-Version 1.2) versionsA           of Calendar. If you answer "No", the data files are notu@           converted and the Calendar application cannot be used.  A           To prevent this problem, ensure that all the nodes in anC           cluster are running the same version of DECwindows Motif.f       2-4  f         I                                                General User Release NotesiI                                    2.6 DECwindows Motif Application Noteso    4         2.6.3.2 Additional Problems and Restrictions  @         V1.2  The following are known problems with the Calendar               application:  F               o  When you initially run the Calendar application afterC                  you install DECwindows Motif for OpenVMS software, D                  Calendar displays a message dialog box stating thatC                  the Calendar database file needs to be upgraded tolF                  the new format. If the Motif Window Manager is listedI                  before Calendar in the Session Manager Automatic Startup D                  list, then the message dialog box will be small andI                  unreadable. As a possible solution, move Calendar beforehH                  the Motif Window Manager in the Automatic Startup list.  H               o  If the Window Manager buttons are customized so that anF                  action is taken when the pointer is in the window andG                  you press MB1, double clicking on the Month display ise                  disabled.           2.6.4 Cardfilerx  C         V1.0  You cannot modify or save DECwindows Motif card files E               from a DECwindows X User Interface (XUI) version of the                Cardfiler.  I               The DECwindows XUI version of Cardfiler can be used to read F               DECwindows Motif card files. Information in the old cardI               file format is compatible with the DECwindows Motif VersionDE               1.0 Cardfiler. DECwindows XUI card files are changed tocD               Motif format when they are read in and saved using the)               DECwindows Motif Cardfiler.   #         2.6.5 CDA Run-Time Services_  F        V1.2-3 The DECwindows CDA Viewer supports both Versions 1.2 and*               1.3 of the DECfonts product.  A         V1.2  This section describes features in the CDA Run-timee!               Services component:f  ?               o  Pack and Unpack applications are provided. Sees                   Section 2.6.6.1  H               o  Performance enhancements for viewing CDA and PostScript                  documents.   I                                                                       2-5                 General User Release Notes*     2.6 DECwindows Motif Application Notes    A           o  Dynamic font support is implemented. Future upgradesED              to installed fonts are usable by the CDA Viewer and the!              PostScript back end.2  E           o  The DECwindows CDA Viewer supports DECfonts Version 1.2.u  =           o  CDA support is improved for documents created by <              DECwrite that contain links to other documents.  >           You can find additional information about CDA in the           following manuals:  7           o  Digital CDA Base Services Reference Manualf  ?              Provides reference material for using the CDA data >              structures and access routines to create compound<              document applications, converters, and viewers.  @           o  Technical Overview of the Digital CDA Base Services  ?              Provides an introduction to CDA, compound documentt<              processing concepts, and using the DEC CDA Base              Services.  $     2.6.5.1 CDA Dynamic Font Support  <     V1.2  As well as supporting a static-table for the fontsD           supported by the DECfonts Typeface Collection Version 1.2,D           this version of CDA Run-Time Services includes support forB           dynamic font lookup. This enables the CDA Viewer and theD           PostScript back-end converter to use new fonts as they are"           installed on the system.  7           Dynamic font support is implemented using thelE           WRITE$FONTS.INI file, which you can maintain using the FontiC           utility provided with either DECwrite or DECpresent. If anB           document contains a font not found in the static tables,C           the CDA Viewer or the PostScript back-end converter trieseC           to open the WRITE$FONTS.INI file and search for the font.uD           If the font is not found or if the system does not containB           a WRITE$FONTS.INI file, the viewer uses a fallback font.  >           For further information on the Font utility, see the           following documents:  8           o  DECwrite Installation Guide for VMS Systems  :           o  DECpresent Installation Guide for VMS Systems       2-6            I                                                General User Release Notes I                                    2.6 DECwindows Motif Application Notes     B               o  DECfonts Typeface Collection and User's Guide for                  OpenVMS  ,         2.6.5.2 CDA WRITE$FONTS Logical Name  B         V1.2  The default location for the WRITE$FONTS.INI file isB               SYS$LIBRARY, but, if the logical name WRITE$FONTS isI               defined, the CDA Viewer or the PostScript back end uses the-G               logical name definition to search for the WRITE$FONTS.INI                file.e  D               Full path support is included, so any of the following$               definitions are valid:  I               ___________________________________________________________a  !               WRITE$FONTS Logical 2               Name                  Resulting FileI               ___________________________________________________________w  ?               Undefined             SYS$LIBRARY:WRITE$FONTS.INI   C               DISK:[DIRECTORY]      DISK:[DIRECTORY]WRITE$FONTS.INIr  =               SYS$LOGIN:            SYS$LOGIN:WRITE$FONTS.INIt  ?               .TMP                  SYS$LIBRARY:WRITE$FONTS.TMPE  <               DISK:[DIRECTORY]FILE  DISK:[DIRECTORY]FILE.INI           2.6.5.3 CDA Documentsu  C         V1.2  The current version of CDA Run-Time Services includesuB               a performance enhancement that decreases the time itF               takes to display the first page of a CDA document. OtherD               applications that use the CDA Viewer to view documentsC               (for example, DECwindows Mail) also benefit from this                enhancement.  I               The CDA Viewer enables this performance enhancement feature A               by default. You can disable the feature as follows:"  1               $ DEFINE CDA_QUICK_FIRST_PAGE FALSE   G               The CDA Viewer might not display some documents correctly C               when this feature is enabled. If you encounter such aFD               problem, disable the feature and invoke the CDA ViewerF               again. If the problem persists, please submit a SoftwareG               Performance Report along with a copy of the document (and F               any associated documents). The CDA Pack application (seeF               Section 2.6.6.1) allows you to create a single file thatC               includes a .DDIF or .DTIF document and its associated                files.  I                                                                       2-7                 General User Release Notes*     2.6 DECwindows Motif Application Notes    $     2.6.5.4 CDA PostScript Documents  D     V1.2  The PostScript viewing feature of the CDA Viewer no longerD           reads the entire PostScript document before displaying theB           first page. Instead, it processes one page at a time. InE           the case of large documents, this significantly reduces theh0           time needed to display the first page.  B           Note that since the PostScript file is no longer read inB           all at once, the total number of pages in the PostScript<           document is not known until the last page is read.A           Therefore, the current page indicator does not show thebE           number of pages in the document until the entire PostScripti3           document has been read by the CDA Viewer.b  %     2.6.6 CDA-Additional Applicationsa  @     V1.2  This section contains information about additional CDA           applications.   (     2.6.6.1 Pack and Unpack Applications  D     V1.2  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 document B           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 fileUD           that is packaged by the CDA Pack application and creates aC           copy of the original document file and all its externally            referenced files.o  <           These applications allow you to copy CDA documents?           between systems without copying externally referencedM@           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 thep(           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 UNPACK C           to invoke the Pack and Unpack applications, respectively.-       2-8n g         I                                                General User Release Notes I                                    2.6 DECwindows Motif Application Notesr              2.6.6.2 Pack Application  H         V1.2  The CDA Pack application creates a single output file thatC               contains the contents of a .DDIF or .DTIF input file. E               The single 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:   5               $ PACK input-file-spec output-file-spec   C               The following sections explain the format of the PACKR               command.                 input-file-spec D               Specifies the name of the primary .DDIF or .DTIF input               file.t                 output-file-specC               Specifies the name of the output file that is createdcE               by the PACK application. If you do not specify a deviceaE               or directory, the output file is created in the current                 default directory.                 Qualifiers:S                 /[NO]SKIP_MISSINGfH               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 PackrG               application is completed. If you specify /NOSKIP_MISSING,dH               the Pack application does not create an output file if anyI               of the externally referenced files are missing. The defaulte               is /SKIP_MISSING.   "               /[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 youlG               specify /NOCONTROLLED_COPY, the Pack application includestG               all referenced files, regardless of the value of the ERF_ >               CONTROL item. The default is /NOCONTROLLED_COPY.    I                                                                       2-9     e           General User Release Notes*     2.6 DECwindows Motif Application Notes               /ALWAYS_ENCODEC           Controls whether an output file is created when there arenA           no external references in the input file, or if none ofdC           the externally referenced files are found. The default istC           not to create an output file in these cases. If an output E           file is not created for these reasons, the Pack application 1           returns the CDA_W_NOOUTFIL status code.              For example:  &           $ PACK MYFILE.DDIF TEST.PACK       2.6.6.3 Unpack Application  B     V1.2  The CDA Unpack application unpacks an input file createdD           by the Pack application. The output files are the .DDIF orD           .DTIF file that is packed by the Pack application, as wellE           as a file for each external reference in the .DDIF or .DTIFrD           file. The Unpack application sends a list of created files           to SYS$ERROR.   9           The format of the UNPACK command is as follows:1  "           $ UNPACK input-file-spec  A           The following sections explain the format of the UNPACKc           command.             input-file-spechE           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 .DDIFT=           or .DTIF file with the file name you specify in thelC           current default directory. It also creates all externally <           referenced files in the current default directory.         2-10           I                                                General User Release NotesrI                                    2.6 DECwindows Motif Application Notesn    F               If you specify a directory name without a file name, theI               Unpack application creates the main .DDIF or .DTIF file andoI               all externally referenced files in the specified directory.fH               The main .DDIF or .DTIF file has the same name as the file-               packed by the Pack application.b  B               If you specify a directory name and a file name, theE               Unpack application creates the main .DDIF or .DTIF filecG               and all the externally referenced files, in the specified G               directory. The main .DDIF or .DTIF file has the file names               you specify.                 For example:                  $ UNPACK TEST.PACK;               Output file DISK$:[SMITH]MYFILE.DDIF created.p=               Output file DISK$:[SMITH]FIGURE_1.DDIF created.i  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.DDIFnO               Output file DISK$:[SMITH.UNPACK]MYFILE.DDIF renamed NEW_FILE.DDIFaD               Output file DISK$:[SMITH.UNPACK]FIGURE_1.DDIF created.  .         2.6.6.4 Pack and Unpack Error Messages  E         V1.2  This section describes messages associated with the CDAn+               Pack and Unpack applications.   /          FILESPEC,  Missing filespec: file-nameu  #             Severity: Informational   G             Explanation: The Pack application cannot locate an externaliH             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.M  /          NOOUTFIL,  No output file was created.                Severity: Warninga  B             Explanation: The Pack application cannot find externalG             references in the .DDIF or .DTIF document to be packed, ands=             you did not specify the /ALWAYS_ENCODE qualifier.   I                                                                      2-11a c  e           General User Release Notes*     2.6 DECwindows Motif Application Notes    -       OUTFILE, Output file created: file-namee            Severity: Warning            Source: CDA_UNPACK"  B          Explanation: The Unpack application created the specifiedE          file while unpacking a file created by the Pack application.h  5     2.6.7 CDA-Hints, Restrictions, and Known Problems   B           This section contains helpful hints, known restrictions,1           and known problems with the CDA Viewer.   2     2.6.7.1 Display PostScript with the CDA Viewer  E     V1.2  Previously, the CDA Viewer had a compatibility problem withlC           the previous version of the DECwindows Display PostScripts           extensions.   C           This problem sometimes caused parts of the data displayedaB           on a page to be rotated, shifted, or incorrectly scaled-D           sometimes to an extent that the data was no longer visibleB           on the screen. The first page of some documents appearedD           blank but became visible after displaying the second page.  B           The problem is resolved in the latest version of the CDAB           Viewer; however, if a previous version of the CDA Viewer?           is run on one system (the client) with display set tol@           another system (the server) and the server has the newC           Display PostScript engine, then the problem still exists. E           The solution is to upgrade the version of CDA on the client            system.t  "     2.6.7.2 Message for CDA Viewer  E     V1.2  The CDA Viewer issues the following message if it is unabley,           to create the application context:  D       DRMCTXFAIL, DVR could not create application context, aborting            Level: Error   ?          Explanation: The CDA Viewer ends because an attempt to B          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.d       2-12 o         I                                                General User Release Notes I                                    2.6 DECwindows Motif Application NotesE    -         2.6.7.3 CDA Paper Size Button Renamed-  I         V1.2  In the CDA Viewer, the name of the Paper Size button in theoI               Open dialog box is changed to Display Options. However, thes<               function invoked by the button is not changed.  .         2.6.7.4 CDA Watch Progress Restriction  I         V1.2  If you use the CDA Viewer to view a PostScript document and F               you enable the Watch Progress feature, then manipulatingI               CDA Viewer buttons (other than the Cancel button) or scroll G               bars while the wait cursor is active can cause corruptionN               of the display.A  8         2.6.7.5 CDA Viewer Supports DECfonts Version 1.2  D         V1.1  The CDA Viewer supports DECfonts Versions 1.2 and 1.3.  H               The Linotext fonts were renamed following DECfonts VersionB               1.1 and before Version 1.2. If a .DDIF file containsE               DECfonts Version 1.1 Linotext text, the CDA Viewer does I               not find it and defaults to Courier 12 point for this text.a  H               To correct this problem, modify the font using DECwrite orB               DECpresent in conjunction with DECfonts Version 1.2.  ?         2.6.7.6 CDA Viewer-Viewing PostScript Files with Errorss  F         V1.0  If you use the CDA Viewer to view a PostScript file thatH               contains syntax errors, the CDA Viewer can stop processingH               without displaying an error message until you click on theF               Cancel button. This problem also occurs if you specify aE               .PS formatted file other than PostScript to the viewer.SH               This problem can occur in the CDA Viewer application or inI               any application that uses the callable CDA Viewer interface                in DDIF$VIEWSHR.  H               Specify only valid PostScript files to the CDA Viewer when(               specifying the .PS format.  '         2.6.8 Clock-DECsound Capabilityy  B         V1.2  The Clock application includes an alarm feature thatE               can be used if your system is a TURBOchanel system thatoG               supports DECsound. On systems without sound capabilities,CD               you can select only the keyboard bell. When you chooseH               Alarm from the Options menu, a pop-up window appears. ThisH               pop-up window allows you to set the alarm time, choose theG               sound to be played, and indicate an alarm message. To seesE               if your system supports this feature, invoke one of thea  I                                                                      2-13                 General User Release Notes*     2.6 DECwindows Motif Application Notes    E           sounds located in the DECW$EXAMPLES directory (for example,            BELLS.AUD).        2.6.9 DECsound Application  ;           This section contains information about DECsound.   "     2.6.9.1 DECsound Prerequisites  =    V1.2-3 DECsound is supported only on TURBOchannel systems.G@           TURBOchannel systems that support DECsound include the           following:  &           o  DEC 3000 Model 400 series  &           o  DEC 3000 Model 500 series  &           o  DEC 3000 Model 700 series  &           o  DEC 3000 Model 900 series  1           o  VAXstation 4000 Model VLC, 60 and 90   =           DECsound is not supported on the following systems:   &           o  DEC 2000 Model 300 series             o  AlphaStation 200t             o  AlphaStation 400i       2.6.9.2 DECsound Problems   9     V1.1  The following are known problems with DECsound:   D           o  Links to audio files created using DECwrite Version 2.0C              and DECpresent Version 1.0 cannot be played back using_@              the CDA Viewer because these applications currentlyC              store links to audio files as private data that cannot[3              be accessed by other CDA applications.:  C              To correct this problem, use DECwrite or DECpresent to ;              view documents with links to audio recordings.E  D           o  The Record operation does not work when you select part              of the waveform.s  C              To correct this problem, do not select any part of thea<              waveform before you click on the Record button.       2-14 p         I                                                General User Release NotesiI                                    2.6 DECwindows Motif Application Notesm              2.6.9.3 Escape Sequences  G        V1.2-3 The DECterm application supports all ReGIS input cursors:                  o  Crosshair                 o  Diamond  !               o  Rubber-band lineA  &               o  Rubber-band rectangle  G               For a shape other than the diamond cursor when n is equalhI               to 1, define the logical name DECW$TERM_REGIS_CURSOR as one,I               of the numbers defined in the SYS$LIBRARY:DECW$CURSOR file.   F         V1.2  The following escape sequences are supported by DECterm:  I               o  All page movement sequences (NP, PP, PPA, PPB, and PPR).m  B               o  One rectangular area operation sequence (DECCRA).  &               o  The DECLFKC sequence.  D               o  The ReGIS command S(C(In)) supports the rubber-band9                  rectangle cursor and the diamond cursor.   D               See Section 4.13.4, ReGIS Input Cursors for additionalD               information about escape sequences in DECwindows MotifI               software. See Chapter 4 for details and restrictions on the %               use of these sequences.h  0         2.6.10 DECterm-Restrictions and Problems  I               This section discusses restrictions and problems related to &               the DECterm application.  1         2.6.10.1 Changing the Auto Repeat Settingy  F        V1.2-3 You cannot change the Auto Repeat setting in the DECtermI               Keyboard Options dialog box. Instead, change the setting inc=               the Keyboard dialog box in the Session Manager.a  $         2.6.10.2 Positioning DECterm  I        V1.2-3 If the resource Mwm*clientAutoPlace is set to True, DECtermiE               windows are not displayed where the DECW$TERMINAL.x andiG               DECW$TERMINAL.y resources are specified. As a workaround,n9               set this resource to False and restart MWM.c  I                                                                      2-15e r  e           General User Release Notes*     2.6 DECwindows Motif Application Notes          2.6.10.3 User Font Selection  ?     V1.2  DECterm allows you to select available fonts from the E           Options/Window dialog box. A different font can be selectedgB           to replace the default Big Font, default Little Font, or'           default German Standard Font.a  >           In the Options/Window dialog box, you can select the>           default font or enter the name of a font into a text?           field and select that font. When the Big Font, LittlehA           Font, or German Standard Font is selected and the Other E           toggle button for the font is selected, DECterm attempts toeD           locate and use the font name supplied in the adjacent textD           field. For information on font naming conventions or fonts@           available on your system, consult your system manager.  C              ________________________ Note ________________________   >              Not all fonts work properly with DECterm. DECterm@              emulates a character-cell terminal, and, therefore,;              expects the fonts to be monospaced (each glyphp>              occupies the same number of pixels). Proportional@              fonts can be chosen, but they produce unpredictable              results.   @              Furthermore, DECterm fonts are supplied in families@              of 26 related fonts, including variations for bold,>              double-width, double-width/double-height, normal,B              and condensed characters. Also, DECterm fonts includeA              special characters, such as the Line Drawing and thebC              DEC Technical character sets. A DECterm font family isA6              identified by the font naming convention.  ?              Use of fonts that do not have all the related fontsA              family variations, fonts that do not have the needed =              special characters, or font families that do not B              adhere to the DECterm font family naming conventions,>              may not result in an optimal display or otherwise!              perform as expected.   C              ______________________________________________________   C           On OpenVMS systems, Version 6.1 or higher, two additional B           fonts are available: the VT330 font and the VT font. TheE           VT330 font is based on the 10x20 font used in the VT330 and B           VT340 terminals. The VT font is a 9x18 font derived fromD           the VT330 font. Use these fonts on a system where they are       2-16 h  a      I                                                General User Release Notes I                                    2.6 DECwindows Motif Application Notes     F               available by entering the following font-name strings in'               the font-name text field:a  4                   -DEC-VT330-*-*-*--20-*-*-*-c-*-*-*  5                       -DEC-VT-*-*-*--18-*-*-*-c-*-*-*o           2.6.10.4 Local Echoi  H         V1.2  DECterm supports a local echo mode. In the Options/GeneralG               dialog box, select Local Echo, which causes all characterlE               sequences generated locally to be echoed on the displayiH               and passed to the remote host. This feature is useful whenF               connected to a host that does not echo typed characters.  #         2.6.10.5 Answerback Message   I         V1.2  A user interface is available to enter answerback messages.RE               This answerback message field is for compatibility with                 Digital terminals.  B               The answerback field is a buffer that contains up toH               thirty characters. The answerback field in earlier DigitalF               terminals contained a message used to identify itself toH               the host system. For DECterm windows, the answerback fieldH               can be used to store a sequence of characters that you can-               use for any repetitive purpose.   F               A field is provided in the Options/General dialog box toF               enter answerback text. Click on the answerback field andF               enter your text. To enter control characters, encode theG               control character as a two-digit hex ASCII code, preceded #               by a number sign (#).c  F               For example, when you enter #0D in the answerback field,6               DECterm responds with a carriage return.  I               If two consecutive number sign characters are entered (##),p2               a single number sign is transmitted.  B               If anything other than a valid two-digit hex code orE               another number sign is detected after an initial numbert?               sign, the number sign is treated as a normal text E               character. Refer to any ASCII table for a complete list                of characters.  I                                                                      2-17p f              General User Release Notes*     2.6 DECwindows Motif Application Notes    E           The answerback text can also be concealed. When the Conceal A           Answerback button is enabled, the answerback message is E           concealed. To deselect the Conceal Answerback button, click0A           on the answerback text field, which erases the previousr           answerback message.   &     2.6.10.6 Seven-Bit Printer Support  B     V1.2  When the 7-Bit Printer button is selected in the Options?           /Printer dialog box, DECterm modifies printed text toc?           be compatible with printers that do not support 8-bitn>           characters. This includes modifying control sequence@           introducer (CSI) strings to use the format Escape-Left=           Bracket rather than the single 8-bit CSI character.y  C           When the 8-Bit Printer button is selected, DECterm allowsaB           the use of 8-bit characters when printing. This mode canE           cause problems for older printers if they can not interpreti           8-bit characters.T             The default is 8-Bit.   /     2.6.10.7 VT330 and VT340 Terminal Emulation   A     V1.0  DECterm incorporates some of the features of the VT330-IC           and VT340-series video terminals, such as ReGIS and SixelRE           graphics. DECterm does not provide complete VT330 and VT340P           terminal emulation.   6           The following restrictions apply to DECterm:  E           o  User-loadable characters (DRCS), local mode, and controlN;              representation mode (CRM) are not implemented.   @           o  The checkerboard character (character 97 in the DEC?              Special Graphic character set) is used as an errorr=              character in place of the reverse question mark.   ?           o  DECterm uses replace mode as the default for Sixel E              drawing on servers with eight planes or less. On serverssD              with more than eight planes, DECterm uses overlay mode;=              replace mode is not functional on those servers.t           2-18    e      I                                                General User Release NotesoI                                    2.6 DECwindows Motif Application Notes     1         2.6.10.8 CREATE/TERMINAL/DETACHED/PROCESS   G         V1.0  The /PROCESS=procnam qualifier does not work when used innG               conjunction with the /DETACHED qualifier, unless there isoG               already a process running on the system where its processi-               name is equal to the user name.   D               To work around this problem, use the following command               procedure:  %               $! CREATE_TERM_PROC.COMU               $!B               $! Invoke as SPAWN/NOWAIT @CREATE_TERM_PROC procname               $!               $ SET NOON               $!-               $! Set Process name to usernamea               $!O               $ X = F$CONTEXT("PROCESS", PID, "PRCNAM", "''F$PROCESS()'","EQL")l@               $ NAME = F$EDIT(F$GETJPI(X,"USERNAME"),"COLLAPSE")*               $ SET PROCESS/NAME="''NAME'"8               $ CREATE/TERMINAL/DETACHED/PROCESS="''P1'"               $!L               $! Allow new process to RUN LOGINOUT before exiting subprocess               $ WAIT 00:00:10E  H               If the /PROCESS=procnam qualifier specifies a process nameI               that is already in use, the DECterm is created but creation H               of the process inside the DECterm fails. In this case, theE               DCL command CREATE/TERMINAL returns the following errort               message:  $               Duplicate process name  0         2.6.10.9 Printing to an Attached Printer  A         V1.1  Printing to a port device requires you to have readiD               and write privileges on that port. You cannot print byI               allocating the device, since the controller requires accessmA               to the device. Instead, set the device to WORLD:RW.i  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:   4               $ SET PROTECTION=WORLD:RW TTA3:/DEVICE  I                                                                      2-19n n  t           General User Release Notes*     2.6 DECwindows Motif Application Notes         2.6.10.10 DECterm Graphics  D     V1.1  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 entiremB              workstation. The default colormap is four colors on aC              four-plane or monochrome system and 16 colors on colorv0              systems with more than four planes.  A              To restore a DECterm window to the default colormap,AA              select Clear Display from the Commands menu to cleareE              the window. Then select Reset Terminal from the Commandsr(              menu to reset the terminal.  A           o  Only graphics, not text, are written to the graphicseC              backing store. When part of a window has to be redrawniD              in DECterm, the graphics portion of the window is drawn?              first, then the text is overlaid. As a result, thetC              redrawn window might not look the same as the original               picture.a  @           o  ReGIS addresses the entire window, not just 24 rowsA              and 80 columns, so the aspect ratio between text and E              graphics might not always be the same as on the VT330 ore              VT340 terminal.  >           o  The following ReGIS features are not implemented:  $              -  Command Display mode                -  ScrollingE                -  Output cursors  "     2.6.10.11 Initializing DECterm  =    V1.2-3 The workaround that is discussed in the Version 1.1nE           release note that follows is no longer necessary on OpenVMSiC           Alpha Version 6.1 and OpenVMS VAX Version 6.2 (or higher)c           systems.       2-20           I                                                General User Release NotescI                                    2.6 DECwindows Motif Application Notes     ?         V1.1  To ensure that your DECterm windows do not shrinkIB               unexpectedly to the default size of 80 characters byD               24 lines, systemwide and user login command procedures@               (SYLOGIN.COM and LOGIN.COM) should not execute theH               SET TERMINAL/INQUIRE command procedure on DECterm windows.C               Executing the SET TERMINAL/INQUIRE command on mailbox D               devices that are created from the Session Manager alsoE               prevents the Session Manager from starting applicationso               such as DECterm.  F               You do not need to use the SET TERMINAL/INQUIRE command;F               the DECterm controller provides OpenVMS systems with theA               proper characteristics and size of DECterm windows.e  H               To make login procedures work correctly on DECterm windowsE               and in other environments such as on terminals, use theEF               following commands in a systemwide or user login command               procedure:                $ !O              $ ! SYS$MANAGER:SYLOGIN.COM and users' LOGIN.COM might contain then(              $ ! following command line:N              $ ! $ IF (F$MODE() .EQS. "INTERACTIVE") THEN SET TERMINAL/INQUIREM              $ ! To avoid resizing of a terminal window on a workstation, you ?              $ ! can substitute the following command sequence:               $ !2              $ IF f$getdvi( "sys$output:", "trm" )              $ THEN L              $      devnam = f$getdvi( "sys$output:", "devnam" ) - "_" - "_"4              $      devnam = f$extract(0, 2, devnam)?              $      if devnam .eqs. "WT" then goto skip_inquire ?              $      if devnam .eqs. "TW" then goto skip_inquire ?              $      if devnam .eqs. "FT" then goto skip_inquirew?              $      if devnam .eqs. "RT" then goto skip_inquirer4              $      set terminal sys$output:/inquire              $ skip_inquire:              $ ENDIF  G               This routine bypasses the SET TERMINAL/INQUIRE command on I               DECterm, SET HOST, and VWS, and also on nonterminal devicescC               such as the mailboxes created by the Session Manager.o        I                                                                      2-21i e  d           General User Release Notes*     2.6 DECwindows Motif Application Notes    $     2.6.10.12 DECterm Resource Usage  B     V1.1  You cannot create more terminal windows than your system>           resources and quotas allow. If you have insufficient=           resources, a dialog box is displayed with a messagen>           indicating that no additional DECterm windows can be           created.  E           To reduce the memory requirement of each DECterm window andhD           create additional terminal windows, decrease the number ofE           Record Lines Off Top in the Display dialog box and decrease-8           the number of columns for each DECterm window.  D           Once the resource limit is reached, log out of all DECterm@           windows that are running on the host system before you2           increase the number of terminal windows.  0     2.6.10.13 Diagnostic Crash File and Messages  B     V1.1  DECterm produces a diagnostic file when a status code ofC           fatal is returned. The DECTERM_ERROR.LOG file is produced =           in the login directory when the DECterm application B           exits abnormally. If you have a problem with the DECterm>           application and submit a Software Performance Report>           (SPR), include a copy of the log file. Under certainE           circumstances, a log file is generated even when no problemtD           is encountered. Therefore, the appearance of a log file asE           an isolated event should not be cause for a problem report.   D           You can enable additional levels of diagnostic messages byC           defining either a logical name or a symbol named DECTERM_l@           DIAG. When defined, enhanced diagnostics are displayedB           by the DECterm images. Use this mode only for diagnosingC           problems; it causes Session Manager message windows to betA           generated for each new DECterm created from the Session            Manager.  C           DECterm diagnostics can be captured in a file by defining C           the logical name DECW$TERMINAL_OUTPUT to point to a file.i                 2-22 r  o      I                                                General User Release NoteseI                                    2.6 DECwindows Motif Application Notese    C         2.6.10.14 Monitor Screen Width Determines Default Font Size   A         V1.0  Three font sets are available for 100 dots-per-inch F               monitors: 100, 140, and 180 decipoint fonts. When a 100-G               dpi monitor with a physical screen width of less than 325hH               millimeters is used (approximate screen width of a 15-inchE               monitor), the 140 and 100 decipoint fonts are selected, D               respectively, for the Big and Little font sets. If theH               physical screen width is larger than 325 millimeters, then7               the 180 and 140 decipoint fonts are used.   F               To use the smaller font sets on a large 100-dpi monitor,I               place the following lines in the DECW$TERMINAL_DEFAULTS.DATd               file:e  / DECW$TERMINAL.main.terminal.littleFontSetName: n&   -*-terminal-*-*-*--*-100-*-*-*-*-*-*  , DECW$TERMINAL.main.terminal.bigFontSetName: &   -*-terminal-*-*-*--*-140-*-*-*-*-*-*  I               Alternatively, you can enter these font strings in the text_G               fields for the "Other" fonts in the Options/Window dialogt               box.  &         2.6.10.15 ReGIS Locator Report  F         V1.0  When DECterm sends a ReGIS locator report in response toD               the R(P(I)) command, or in multiple input mode and theG               locator position is outside the addressable area, DECterm F               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).,           2.6.11 DECW$CDPLAYER  @         V1.1  The DECW$CDPLAYER application in the DECW$EXAMPLESB               directory requires PHY_IO and DIAGNOSE privileges toC               operate the compact-disc player hardware. Either youre>               process or the image must have these privileges.           2.6.12 LinkWorks  ?               This section contains information about LinkWorks                (DEClinks).a  I                                                                      2-23  i  n           General User Release Notes*     2.6 DECwindows Motif Application Notes    >     2.6.12.1 Removing Support for LinkWorks Manager (DEClinks)  ?    V1.2-3 Support for DEClinks, formerly known as LinkWorks, iss?           removed from the Session Manager and from the desktop ?           applications menus and from the out-of-the-box (OOTB)o           desktop applications.d  =           The verbs "LinkWorks Manager" and "LinkWorks Setup"x?           are removed from the system profile file, VUE$SYSTEM_n;           PROFILE.VUE$DAT. If users modified or moved these ?           verbs, they are stored in their private profile file, =           VUE$PROFILE.VUE$DAT. Delete any customizations thatt@           reference these two verbs, either from autostart or asA           a private verb; these verbs are no longer supported. To ?           eliminate these customizations, delete the verbs from C           Options Automatic Startup and from Options Menus dialogs.E       2.6.13 DECwindows Mail  E           This section contains information about the DECwindows Mailb           application.  E    V1.2-3 Since the DECwindows Motif Version 1.2 release, performanceb9           of the DECwindows Mail application is enhanced.e  *     2.6.13.1 Responses to Keyboard Actions  C    V1.2-3 Enhancements in the DECwindows Mail application to comply B           more closely with OSF/Motif style conventions cause someA           changes with application responses to keyboard actions.e%           Note the following changes.y  D           If you use the Tab key to advance through text entry boxesC           in the Create/Send window, the current field is no longerrA           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 theuB           space bar to activate a pushbutton through the keyboard.A           Note that the Return key and the Enter key are bound to A           other widgets in the dialog box. Alternatively, you can 9           continue to click MB1 to activate a pushbutton.o       2-24           I                                                General User Release NotesnI                                    2.6 DECwindows Motif Application Notess    @         2.6.13.2 Using the Color Customizer with DECwindows Mail  E         V1.2  If you use the color customizer sample program provided#G               in the directory DECW$EXAMPLES to control DECwindows Mail D               colors, the DECwindows Mail color customization dialogC               boxes used to modify those colors may not reflect the D               correct current color values. This is normal behavior;E               use the color customizer instead of the DECwindows MailcF               color customization dialog boxes to change these values.G               Alternatively, exit from the color customizer and restartEI               DECwindows Mail. See Section 3.4 for more information abouto#               the color customizer.   /         2.6.13.3 DECwindows Mail-Known Problemsm  C         V1.0  The following problems exist with the DECwindows Mailt               application:  H               o  The XUI Window Manager does not automatically set inputI                  focus to windows when they are mapped. You must click ont0                  each window to get input focus.  G               o  The next and previous arrow buttons in the Read windowmB                  do not dim at the end or beginning of the folder,@                  respectively. They are ineffective if selected.  G               o  Use of the Message button in the Read window to scroll :                  through a large message can be very slow.  I               o  Performance of the text widget in the Create-Send windowaI                  can be degraded if the word wrap option is turned on. TotD                  enhance performance, turn off the word wrap option.  .         2.6.14 DECwindows Motif Window Manager  D               This section contains information about the DECwindows#               Motif Window Manager.   H         2.6.14.1 Using the Color Customizer with DECwindows Motif Window                  Manager  C         V1.2  If you are using the color customizer provided in the E               DECW$EXAMPLES directory to control Motif Window ManagerdC               colors, the Motif Window Manager customization dialogeC               boxes used to modify those colors may not reflect theoH               correct current color values. This is normal behavior; useF               the color customizer instead of the Motif Window ManagerF               color customization dialog boxes to change these values.G               Alternatively, exit the color customizer and then restartl  I                                                                      2-25l m  ;           General User Release Notes*     2.6 DECwindows Motif Application Notes    D           Motif Window Manager. See Section 3.4 for more information%           about the color customizer.        2.6.14.2 Configuration Filel  @     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 Characteri4           key) and function key, for example Alt+F7.  E           If any application needs to use these keys, you must eitheroA           comment them out by placing an exclamation point (!) attE           the beginning of the line, or create new keyboard bindings.TC           Then change Mwm*keyBindings:DefaultKeyBindings in the MWMN5           resource file to point to the new bindings.   ;           With the Motif binding, you can no longer use theoA           Alt+spacebar or the Compose Character+spacebar to bringT?           up the Window menu because it interferes with Compose @           Character sequences in DECterm. Use Shift+F11 to bring           up the Window menu."  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 defaultfD           button bindings for Alt+space in the DECW$MWM_RC.DAT file.  (     2.6.14.3 DECwindows XUI Applications  A     V1.0  The resource Mwm*useDECMode allows previous versions ofaB           DECwindows XUI applications to behave correctly with theD           Motif Window Manager. In particular, this resource is usedB           to control focus, window placement, multiline icons, and;           the window's initial state (normal or minimized).t  ,     2.6.14.4 Restarting Motif Window Manager  C     V1.0  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.,B           However, if you are not starting the Window Manager from@           the Session Manager, then the Window Manager might notC           have been initially started on all the available screens.EB           You can modify this file to change the way the window is$           restarted for your system.       2-26           I                                                General User Release Notes I                                    2.6 DECwindows Motif Application Notese    2         2.6.15 Motif Window Manager-Known Problems  I               This section contains information about known problems withm'               the Motif Window Manager.   2         2.6.15.1 Accelerators for Icon in Icon Box  C         V1.0  When using an icon box, the accelerators on an icon'sbC               Window menu do not work unless you display that menu.wA               Instead, accelerators always apply to the icon box.m  ,         2.6.15.2 Application Started as Icon  G         V1.0  If an application is started as an icon before the WindowoF               Manager is started, the application's Main window is notD               minimized when the Window Manager is started. This canI               occur when you change X properties relating to icons beforetI               the Window Manager is started or when the Window Manager is H               starting. It can also occur if you start an application asG               an icon when the Window Manager is restarted after it has 6               been previously started and is inactive.  C         2.6.15.3 Customizing Color-Related Resources for Monochromel                  Monitors   <         V1.0  The Motif Window Manager does not support fullE               customization of color-related resources for monochromedH               monitors in the Options dialog box. In order to change theF               colors, you might need to modify the pixmap resources byE               directly editing the DECW$MWM_BW.DAT resource file. ForiG               example, to change the color of the active window's title H               background, you must change the Mwm*activeBackgroundPixmapI               resource. Some values include 25_foreground, 50_foreground,s4               75_foreground, and unspecified pixmap.  G               In addition, by default, the title text is created with apH               white background. To use the same color as the rest of the=               title, set the Mwm*cleanText resource to FALSE.U  7         2.6.15.4 Customizing Colors on 4-Plane DisplaysD  I         V1.1  A 4-plane display has a limited number of colors. You mighttG               not be able to modify colors with the color mix widget ife2               the system usurps the color entries.  G               To correct this problem, distribute as many of the colorsNH               as possible between the screen, window, border, icons, and               pointer.  I                                                                      2-27                 General User Release Notes*     2.6 DECwindows Motif Application Notes    3     2.6.15.5 Customizing Icon Placement in Icon Box   @     V1.0  If you customize the icon placement of applications byC           specifying iconX and iconY resources in the application'soE           resource file, the placement is ignored if you are using and           icon box.o  .     2.6.15.6 DECwindows XUI Modal Dialog Boxes  D     V1.0  Two problems exist with DECwindows XUI modal dialog boxes.  <           If an application displays a dialog box before the?           main window is visible, the modal dialog box might be A           hidden behind the main window. It then appears that theeC           application is hung. In this case, you must terminate thel           application.  @           If you dismiss a modal dialog box, the focus might not-           automatically revert to its parent.o  %     2.6.15.7 Customizing the Icon Box!  E     V1.0  To customize the position and size of an icon box, move and D           resize the icon box and then select Apply Current Settings*           from the Workspace Options menu.  +     2.6.15.8 Moving the Icon Box Off Screen   @     V1.0  If you move the icon box to the edge of the screen and@           then resize it using the keyboard, you can move it offC           the screen. To retrieve the icon box, press Alt+Tab untilsD           you reach that window and then press Shift Escape (F11) toE           bring up the Window menu for that window. You can then move:*           the window back onto the screen.  &     2.6.15.9 Truncating the Icon Title  A     V1.0  The text for inactive icons is truncated to the size oftA           the icons. Currently, there are two methods to view the D           complete text for an icon. You can make the icon active orC           you can customize your icons by choosing the Icon Options28           menu item and changing the width of the icons.  0     2.6.15.10 Invoking Motif Window Manager Help  B     V1.2  Invoking Motif Window Manager Help through the workspace<           Help menu causes the Motif Window Manager to stop.       2-28 n  f      I                                                General User Release Notes I                                    2.6 DECwindows Motif Application Notes     6         2.6.15.11 Multihead Systems-Customizing Colors  I         V1.0  If you have a multihead system with different monitor types G               (color, monochrome, or gray-scale), you can customize the-I               colors only by using the Options dialog box on the monitorseE               that match the type of your main monitor (screen 0). TowG               customize the other monitors, you must either log in to anI               system with that monitor type or directly edit the resourceg               files.  3         2.6.15.12 Multiline Icon Title Not Centered   C         V1.0  The Window Manager does not center all the lines of a #               multiline icon title.E  ;         2.6.15.13 Truncated Icon Title in Vertical Icon Boxr  C         V1.0  If the icon box is displayed vertically with only onefD               column, then when an icon is selected, the active icon3               label is truncated on the right side.r           2.6.16 Notepad  A               This section contains information about the Notepads               application.  C         2.6.16.1 Notepad Is Linked with the OSF/Motif Release 1.1.3e                  Toolkit  B        V1.2-3 The Notepad application is linked with the OSF/MotifI               Release 1.1.3 Toolkit. Notepad is not modified to link withdI               the OSF/Motif Release 1.2.3 Toolkit, which is provided withgI               the DECwindows Motif Version 1.2-3 for OpenVMS product. The +               following restrictions apply:f  I               o  OSF/Motif Release 1.2 drag-and-drop functionality is notcG                  supported. As a workaround, use the standard clipboardOH                  operations (Cut, Copy, and Paste) to transfer text into                  Notepad.   H               o  OSF/Motif Release 1.2 tear-off menus are not supported.           2.6.17 Paint  ?               This section contains information about the Paint                application.  I                                                                      2-29o o              General User Release Notes*     2.6 DECwindows Motif Application Notes         2.6.17.1 Private Colormaps  ?     V1.1  If your workstation does not have sufficient colormapa>           entries to view or edit a color image, Paint creates@           a private colormap. When this happens, the Paint image?           retains its colors, but the colors on the rest of theeB           workstation are modified. To restore the colors to their=           original values, give another window input focus bys           clicking on it.,  ?     2.6.17.2 Enhancing the Performance of Some Paint OperationsU  ;     V1.0  On GPX systems, Paint might appear slow even wheniE           performing basic operations such as drawing a brush stroke.IE           This is because the pixmap is being swapped into the pixmap*C           memory in order to paint the object. If Paint performancenC           is slow, click on the Pencil tool and draw a point in the/C           image area. This should improve performance following the            initial Pencil click.e  @           When editing images (especially color images), you can?           resize the image area using the Picture Size... entryoC           from the Options menu. Resize to the least possible image D           area to significantly reduce the amount of required pixmap           memory.t       2.6.18 Print Screenp  B           This section contains information about the Print Screen           application.       2.6.18.1 Large Default Icon   <     V1.0  The Print Screen application does not have its own@           distinctive icon and does not support icon sizes other           than large.-  A           As a result, the icon is the default Motif icon of foureD           squares. If you attempt to customize the icon size, only a+           portion of this icon is viewable.i  '     2.6.19 Session Manager and FileView   E           This section contains information about the Session Manageri$           and FileView applications.       2-30 E  n      I                                                General User Release NotesaI                                    2.6 DECwindows Motif Application Notesk    E         2.6.19.1 Removing Support for LinkWorks Manager and LinkWorks   H        V1.2-3 Delete the verbs "LinkWorks Manager" and "LinkWorks Setup"H               from your Applications menu; they are no longer supported.A               The verbs are deleted from the system profile file,UD               VUE$SYSTEM_PROFILE.VUE$DAT. If users modified or movedF               these verbs, the verbs are stored in the private profile#               file VUE$PROFILE$DAT.n  E               Remove any customizations that refer to these two verbsaF               either from autostartup or as a private verb by deletingB               the verbs from the Options Automatic Startup and the$               Options Menus dialogs.  H         2.6.19.2 Invoking DECchart from the Session Manager Applications                  Menun  =        V1.2-3 If you invoke the DECchart application from theoA               Session Manager applications menu, your session canfB               fail. As a workaround to this problem, edit the fileG               VUE$LIBRARY:DECCHART$VUE.COM to incorporate the followingi               text:                  $!H               $! Copyright (c) 1989, 1991 Digital Equipment Corporation.%               $! All rights reserved.s               $!J               $! Command procedure to run DECchart from the User Executive               $! in DECwindows               $!*               $  vue$suppress_output_popup               $!5               $! See if we should skip the dialog boxt               $!9               $    vue$get_symbol vue$show_hidden_dialogs /               $    vue$read show_hidden_dialogs.               $sE               $    if show_hidden_dialogs then goto select_qualifiersc(               $       vue$get_qualifiers#               $       goto do_charte               $E!               $select_qualifiers:t*               $       vue$popup_qualifiers               $                $l               $do_chart:  I                                                                      2-31     n       General User Release Notes*     2.6 DECwindows Motif Application Notes               $o$           $ vue$popup_progress_box 8            $ vue$read vue$command           $ @           $ if "''vue$command'" .eqs. "DETACHED_APPLY" then goto           $ select_qualifiersC           $            $ 'vue$command           $ 7           $ decchart :== $sys$system:decchart$motif.exe "           $ vue$get_next_selection           $ vue$read selection           $ decchart 'selectiono           $s           $ vue$check_verb_loop            $ vue$read loopiA           $ if "''loop'" .eqs. "TRUE" then goto select_qualifiersi  D           The only change is to relocate the following line from the=           beginning of the VUE$LIBRARY:DECCHART$VUE.COM file:M  $           $ vue$popup_progress_box 8  D           This statement causes the Progress Box to pop up after the#           qualifiers are processed.   5     2.6.19.3 Eastern European Languages Now Availablei  D     V1.2  In addition to the previously available languages, you canA           select the following languages from the Session Managerw&           Language Options dialog box:             o  Czech             o  Greek             o  Hungarian             o  Polishs             o  Russian             o  Slovak              o  Turkish  C              ________________________ Note ________________________   C              To select these language options, the language variantiB              kits must be installed on your system, along with theB              base English DECwindows Motif Version 1.2 for OpenVMS              product.wC              ______________________________________________________u       2-32           I                                                General User Release NotesDI                                    2.6 DECwindows Motif Application Notesm      !         2.6.19.4 Security Options   G         V1.2  In the Session Manager Security Options dialog box, placeDG               the node name within quotation marks if the name containsa#               any of the following:d  E               o  Reserved characters: space, tab, comma (,) or doublea#                  quotation mark (")i  "               o  Double colon (::)  D               o  A colon (:) as the final character in the node name  G               Session Manager automatically adds quotation marks to the G               node name if they are needed, unless the node name begins H               with a double quotation mark. If the node name begins withG               a double quotation mark, Session Manager assumes that the G               user has already quoted the node name and does not changem               it.e  G               Within a quoted string, a double quotation mark should be G               replaced by two double quotation marks (""). For example, I               the quoted string "DEC:.zko."my node"" should be changed to1               the following:  '               ("DEC:.zko.""my node""").d  @         2.6.19.5 Using the Color Customizer with Session Manager  C         V1.2  If you are using the color customizer example programtH               provided in the directory DECW$EXAMPLES to control SessionE               Manager colors, the Session Manager color customizationeF               dialog boxes used to modify those colors may not reflectH               the correct current color values. This is normal behavior;E               use the color customizer instead of the Session ManagernF               color customization dialog boxes to change these values.G               Alternatively, exit the color customizer and restart your E               session. See Section 3.4 for more information about ther               color customizer.h  I                                                                      2-33+ c  s           General User Release Notes*     2.6 DECwindows Motif Application Notes    :     2.6.19.6 Input Focus Change When Starting Private Logo  E     V1.0  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.o  -     2.6.19.7 Session Manager Process-Stoppingv  ?     V1.0  Stopping the Session Manager process can have serious,;           consequences for nonprivileged workstation users.a=           DECwindows must be restarted to avoid the followinga           problems:e  D           o  A nonprivileged user cannot start a new Session Manager'              or create a new login box.n  @           o  If the session is paused, the Pause cover window isA              deleted and unauthorized users can access windows ona              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 each C              workstation in a batch job that runs during off-hours.   E           If you stop the Session Manager process, restart DECwindows D           (if you have system manager privileges) with the following           command:  -           $ @SYS$MANAGER:DECW$STARTUP RESTART   1     2.6.19.8 Public Profiles for Layered Productsr  B     V1.0  Layered products that provide a DECwindows interface can>           use the Create Public Profile File command to create<           a profile file that ships with the layered product;           and is installed when the system manager installsA<           the layered product. The file can be placed in theC           SYS$COMMON:[VUE$LIBRARY.USER] directory. Product-specifica@           profile files should be named by appending the product-           prefix to the name PROFILE.VUE$DAT.   ;           For example, the file CMS$PROFILE.VUE$DAT names ao9           profile containing CMS definitions. Any commandw<           files or other related files can also be placed in@           SYS$COMMON:[VUE$LIBRARY.USER] and should be referenced(           as VUE$LIBRARY in the profile.       2-34           I                                                General User Release NoteslI                                    2.6 DECwindows Motif Application Notes     E               For more information on using the Create Public Profile H               File command, refer to Using DECwindows Motif for OpenVMS.  3         2.7 Window Dump to Print File (xpr) Utility   F         V1.2  The Window Dump to Print File utility prints an X Window)               dump using the xpr program.c  B               The xpr program receives as input a window dump fileF               produced by the Window Dump utility (xwd) and formats it3               for output on the following printers:e                 o  PostScripte  &               o  Digital LN03 or LA100  (               o  IBM PP3812 page printer  4               o  HP LaserJet (or other PCL printers)                 o  HP PaintJet  H               You must specify an input file. The xpr program prints theI               largest possible representation of the window on the outputeG               page. Options allow the user to add headers and trailers,oD               specify margins, adjust the scale and orientation, andC               append multiple window dumps to a single output file..  /               Use the following command format:t  +               $ xpr input_file [options...]i                 Options include:                        I                                                                      2-35                 General User Release Notes/     2.7 Window Dump to Print File (xpr) Utilityi    7               -append filename  -noff  -output filenameI               -compactJ               -device {ln03 | la100 | ps | lw | pp | ljet | pjet | pjetxl}               -dumpc               -gamma correction                -gray {2 | 3 | 4} +               -height inches  -width inchesb-               -header string  -trailer stringg#               -landscape  -portraitt'               -left inches  -top inches                -nopositiono               -nosixopte               -plane n               -psfig               -render type               -reportn               -rvI               -scale scale               -slide               -split n-pages  2           Table 2-1 defines the available options.           2-36 l  a      I                                                General User Release Notes I                               2.7 Window Dump to Print File (xpr) Utility   9               Table 2-1 Window Dump to Print File Options I               ___________________________________________________________t  *               Option           DescriptionI               ___________________________________________________________n  H               -device devtype  Specifies the device on which the file is'                                printed.x  ;                                Currently supported devices:n  4                                la100  Digital LA100.  3                                ln03   Digital LN03.   B                                ljet   HP LaserJet series and otherD                                       monochrome PCL devices such asG                                       ThinkJet, QuietJet, RuggedWriter, H                                       HP series, and HP-series printers.  ?                                pjet   HP PaintJet (color mode).   C                                pjetxl HP PaintJet XL Color Graphics ;                                       Printer (color mode).f  1                                pp     IBM PP3812.   9                                ps     PostScript printer.8  D                                lw     LaserWriter is equivalent to -H                                       device ps and is provided only for>                                       backwards compatibility.  9                                The default is PostScript.t  D               -scale scale     Affects the size of the window on theA                                page. The PostScript, LN03, and HPiA                                printers can translate each bit inhB                                a window pixel map into a grid of aD                                specified size. For example, each bitD                                might translate into a 3x3 grid. ThisA                                would be specified by -scale 3. By D                                default, a window is printed with theH                                largest scale that will fit onto the page=                                for the specified orientation.s  H               -height inches   Specifies the maximum height of the page.  G               -width inches    Specifies the maximum width of the page.h  C               -left inches     Specifies the left margin in inches.nD                                Fractions are allowed. By default the>                                window is centered in the page.  I                                                  (continued on next page)i  I                                                                      2-37d    k           General User Release Notes/     2.7 Window Dump to Print File (xpr) Utility     =           Table 2-1 (Cont.) Window Dump to Print File OptionshE           ___________________________________________________________F  &           Option           DescriptionE           ___________________________________________________________d  C           -top inches      Specifies the top margin for the picturer<                            in inches. Fractions are allowed.  B           -header string   Specifies a header string to be printed,                            above the window.  C           -trailer string  Specifies a trailer string to be printed ,                            below the window.  =           -landscape       Forces the window to be printed intB                            landscape mode. By default, a window isC                            printed so that its longest side followse6                            the long side of the paper.  =           -portrait        Forces the window to be printed inp@                            portrait mode. By default a window isC                            printed so that its longest side followst6                            the long side of the paper.  A           -plane number    Specifies which bit plane to use in an2B                            image. The default is to use the entireD                            image and map values into black and white6                            based on color intensities.  =           -gray            Uses a 2x2, 3x3, or 4x4 gray scale*>                            conversion on a color image, ratherD                            than mapping to strictly black and white.C                            This doubles, triples, or quadruples thenC                            effective width and height of the image.a  @           -rv              Forces the window to print in reverse!                            video.o  ?           -compact         Uses run-length encoding for compactg?                            representation of windows with white "                            pixels.  9           -output          Specifies an output file name.t           filename  D           -append          Specifies a file name previously produced>           filename         by xpr to which the window is to be$                            appended.  E                                              (continued on next page)t       2-38 d  u  I                                                General User Release NotesoI                               2.7 Window Dump to Print File (xpr) UtilityS  A               Table 2-1 (Cont.) Window Dump to Print File OptionsmI               ___________________________________________________________   *               Option           DescriptionI               ___________________________________________________________   C               -noff            When specified in conjunction with -1E                                append, the window appears on the same ;                                page as the previous window.   E               -split n-pages   Allows the user to split a window onto I                                several pages. This might be necessary for F                                very large windows that would otherwiseF                                cause the printer to overload and print=                                the page in an obscure manner.i  G               -psfig           Suppresses translation of the PostScriptrA                                picture to the center of the page.t  G               -density dpi     Indicates dot-per-inch density tobe used 1                                by the HP printer.a  G               -cutoff level    Changes the intensity level where colors F                                are mapped to either black or white forG                                monochrome output on a LaserJet printer.rF                                The level is expressed as percentage ofF                                full brightness. Fractions are allowed.  @               -noposition      Causes header, trailer, and imageC                                positioning command generation to be B                                bypassed for LaserJet, PaintJet and4                                PaintJet XL printers.  B               -gamma           Changes the intensity of the colorsF               correction       printed by the PaintJet XL printer. TheC                                correction is a floating-point valuerE                                in the range 0.00 to 3.00. Consult thehI                                operator's manual to determine the correctu>                                value for the specific printer.  @               -render          Allows the PaintJet XL printer toE               algorithm        render the image with the best qualityrC                                versus performance tradeoff. Consult E                                the operator's manual to determine thes4                                available algorithms.  C               -slide filename  Allows overhead transparencies to be F                                printed using the PaintJet and PaintJet+                                XL printers.   I                                                                      2-39c r  o           General User Release Notes/     2.7 Window Dump to Print File (xpr) Utility       9           The program contains the following limitations:l  C           o  Support for PostScript output currently cannot use the /              -append, -noff, or -split options.y  A           o  The -compact option is only supported for PostScriptnC              output. It compresses white space but not black space,_;              so it is not useful for reverse-video windows.s  ?           o  For color images, map directly to PostScript image               support.p  3           Program limitations with an LN03 printer:o  E           o  The current version of xpr can print most X Windows thati:              are not larger than two-thirds of the screen.  C              For example, the LN03 prints a large Emacs window, but :              fails when trying to print the entire screen.  =           o  The LN03 has memory limitations that cause it to E              incorrectly print large or complex windows. The two most A              common errors encountered are "band too complex" and A              "page memory exceeded" and are described as follows:   "              -  "band too complex"  A                 A window may have a particular six pixel row that_A                 contains too many changes (from black to white to C                 black). This causes the printer to drop part of thesE                 line and possibly drop parts of the page. The printercC                 flashes the number "1" on its front panel when this2C                 problem occurs. A possible solution to this problem C                 is to increase the scale of the picture or to split 3                 the picture onto two or more pages.R  &              -  "page memory exceeded"       2-40           I                                                General User Release Notes I                               2.7 Window Dump to Print File (xpr) Utilitye    F                     This occurs if the picture contains too much blackI                     space, or if the picture contains complex half-tones,aH                     such as the background color of a display. When thisH                     problem occurs, the printer automatically splits theF                     picture onto two or more pages. The number "5" mayG                     flash on its front panel. As a possible solution tobH                     the problem, it might be necessary to either cut andH                     paste or to rework the application to produce a less$                     complex picture.  7               Program limitations with a LA100 printer:5  @               o  The picture is always printed in portrait mode.  &               o  The scale is ignored.  I               o  The scale factor will be different in the horizontal andS%                  vertical directions.h  5               Program limitations with an HP printer:l  G               o  If the -density option is not specified, 300 dots-per-rE                  inch (dpi) is assumed for the ljet device and 90-dpihI                  for the pjet device. The LaserJet printer supports 300-,tI                  150-, 100-, and 75-dpi. Consult the operator's manual to,E                  determine the densities supported by other printers.e  D               o  If the -scale option is not specified, the image is9                  expanded to fit the printable page area.   H               o  The default printable page area is 8x10.5 inches. OtherF                  paper sizes can be accommodated using the -height and                   -width options.  F               o  Note that a 1024x768 image fits the default printableF                  area when processed at 100-dpi with scale=1; the sameF                  image can also be printed using 300-dpi with scale=3,C                  but it requires more data to be transferred to then                  printer.u  H               o  The xpr program may be tailored for use with monochromeD                  PCL printers other than the LaserJet. To print on aD                  ThinkJet (HP 2225A) printer, invoke xpr as follows:  6                  xpr -density 96 -width 6.667 filename  G                  To print black-and-white output on a PaintJet printer,l'                  invoke xpr as follows:n  I                                                                      2-41a    o           General User Release Notes/     2.7 Window Dump to Print File (xpr) Utilityo    &              xpr -density 180 filename  ?           o  The monochrome intensity of a pixel is computed as.E              0.30*R + 0.59*G + 0.11*B. If the computed intensity of aiC              pixel is less than the -cutoff level, it prints white.iE              This maps light-on-dark display images to black-on-whitesC              hard copy. The default cutoff intensity is 50% of fulliC              brightness. For example, specifying -cutoff 87.5 means$D              that a pixel will be displayed as black if the computed;              intensity is less than 85% of full brightness.r  B           o  A LaserJet printer must be configured with sufficientD              memory to print the image. To print a full page at 300-C              dpi, approximately 2 MB of printer memory is required.h  A           o  Color images are produced on the PaintJet printer atNB              90-dpi. The PaintJet is limited to 16 colors from itsE              330 color palette on each horizontal print line. The xpr D              program issues a warning message if more than 16 colorsE              are encountered on a line. Xpr programs the PaintJet formB              the first 16 colors encountered on each line and usesC              the nearest matching programmed value for other colors               on the line.   E           o  Specifying the -rv option on the PaintJet printer causes D              black and white to be interchanged on the output image.)              No other colors are changed.   A           o  Multiplane images must be recorded by xwd in ZPixmapf?              format. Single-plane (monochrome) images may be in /              either XYPixmap or ZPixmap format.F  A           o  Some PCL printers do not recognize image positioninglC              commands. Output for these printers is not centered on D              the page, and header and trailer strings may not appear              where expected.  E           o  The -gamma and -render options are supported only on theo"              PaintJet XL printers.  E           o  The -slide option is not supported on LaserJet printers.   ?           o  The -split option is not supported on HP printers.r  E           o  The -gray option is not supported on HP or IBM printers.s       2-42    e      I                                                General User Release NoteseI                              2.8 Keyboard Enhancements for Disabled Userse    4         2.8 Keyboard Enhancements for Disabled Users           V1.2  F               On OpenVMS Alpha systems, the AccessX extension providesH               features to help disabled users interact with workstationsB               running DECwindows Motif Version 1.2 software. TheseD               features make it easier to use the keyboard and mouse.I               You can interact with workstations by entering commands andNH               manipulating menus and dialog boxes. However, with AccessXI               features, performing these input operations is even easier.   F               A client application is provided to enable and customizeF               the AccessX features. To run this application, enter the!               following commands:n  )               $ SET DEFAULT DECW$EXAMPLESt               $ RUN AccessX   I               Online help is available by selecting the Help menu option.   D               AccessX offers the features described in the following               sections.            2.8.1 Sticky Keys   D               The Sticky Keys feature allows you to perform multikeyE               operations with one hand, one finger, or a mouth stick.eD               You can use this feature to enter uppercase letters orD               punctuation characters without having to hold down theF               Shift key while pressing the character key. This featureF               also makes it easier to enter control characters such as               Ctrl/C._           2.8.2 Mouse Keys  H               The Mouse Keys feature lets you map actions that you wouldE               perform with a mouse to keys on the numeric keyboard or I               other keys that you specify. With this feature, you can use I               one finger or a mouth stick to move the cursor to differentpI               areas of the screen, manipulate menus, and select, cut, and                paste text.       I                                                                      2-43i a  o           General User Release Notes0     2.8 Keyboard Enhancements for Disabled Users         2.8.3 Toggle Keysh  B           The Toggle Keys feature provides audio feedback when theC           Shift Lock (Caps Lock) key is pressed. This feature helps C           users who might have difficulty seeing the keyboard lightpA           indicator for the Shift Lock key or users who are using C           a keyboard that does not provide light indicators for any            keyboard settings.       2.8.4 Repeat Keys   @           The Repeat Keys feature allows you to adjust the auto-E           repeat keyboard mechanism speed or to turn it off entirely.pC           With this feature turned on, you can set your keyboard sokE           that holding down a key for a longer than average time doeso5           not cause a repeat entry of that character.e       2.8.5 Slow Keyst  E           The Slow Keys feature makes the keys less likely to respond A           when brushed accidentally. With this feature turned on, @           the computer accepts only keystrokes that are held for>           a certain length of time. The computer ignores light5           keystrokes that are held only for a moment.t       2.8.6 Bounce Keys   D           The Bounce Keys feature eliminates the problem of pressing>           a key and then accidentally pressing it again beforeE           moving to another key. You can set this feature to tell the E           computer not to process a second pressing of a key unless a ?           certain length of time elapses between each pressing.        2.8.7 Time Out  B           The Time Out feature shuts off the AccessX features on aB           workstation after a specified period of time. If you areB           sharing a workstation and have set AccessX features, theD           settings are automatically turned off before the next use.C           To retain the AccessX settings at all times, you can turn #           off the Time Out feature.              2-44    2      I                                                General User Release NotesFI                                            2.9 Printing from Applicationsl    &         2.9 Printing from Applications  D         V1.2  Applications that are linked against OSF/Motif ReleaseI               1.1.3 may end abruptly when you attempt to print on systems_F               that do not have print queues. Any layered products thatF               linked against the OSF/Motif Release 1.1.3 libraries andG               use the standard DECwindows print dialog ("print widget")                 are also affected.  A               As a possible solution, either avoid displaying thenF               DECwindows print dialog, or define a print queue on yourF               system. The print queue does not have to be connected toF               a printer to accept print jobs. Assign a name to the theI               print queue that indicates the print queue is not connected 6               to a printer, for example, NULL_PRINTER.  @         2.10 Unsupported Translations by the Motif XmText Widget  F        V1.2-3 By default, the Motif XmText widget does not support theH               following translations for Versions 1.1, 1.2, and 1.2-3 of+               the DECwindows Motif product:w  3                  F12:           beginning-of-line() 6                  F13:           delete-previous-word()-                  Ctrl e:        end-of-line()d6                  Ctrl j:        delete-previous-word()3                  Ctrl h:        beginning-of-line() 0                  Ctrl r:        redraw-display()9                  Ctrl u:        delete-to-start-of-line() @                  ~Ctrl ~Meta ~Shift Alt<Key>space: self-insert()  I               These translations are preferred by OpenVMS users to ensuref>               consistency with the DCL command line interface.  F               The DECwindows Motif for OpenVMS Session Manager definesC               translations so that they can be used by applicationscE               that are displayed to an OpenVMS display server. If you E               display your applications on a different display serversD               (for example, on a PC or DEC OSF/1 workstation), these.               translations are not functional.  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):  I                                                                      2-45l x              General User Release Notes<     2.10 Unsupported Translations by the Motif XmText Widget    /           *XmText.translations:   #override \n\ 3                <Key>F12:     beginning-of-line()\n\ 6                <Key>F13:     delete-previous-word()\n\-                Ctrl<Key>e:   end-of-line()\n\W6                Ctrl<Key>j:   delete-previous-word()\n\3                Ctrl<Key>h:   beginning-of-line()\n\ 0                Ctrl<Key>r:   redraw-display()\n\9                Ctrl<Key>u:   delete-to-start-of-line()\n\r@                ~Ctrl ~Meta ~Shift Alt<Key>space: self-insert()\n  D           You can copy the text for these translations from the file.           DECW$SYSTEM_DEFAULTS:DECW$LOGIN.DAT.  B           Enabling these translations does not affect the standardB           Motif translations, such as Alt-right for end-of-line or%           Ctrl-right for end-of-word.o  C              ________________________ Note ________________________t  4              If you add lines to the file DECW$USER_A              DEFAULTS:XDEFAULTS.DAT file, startup performance for 3              all applications is slightly degraded.   C              ______________________________________________________                                                2-46                         I                                                                         3vI         _________________________________________________________________t  I                                              System Manager Release Notes     A               This chapter contains system manager release notes.g  H         3.1 Notes Specific to DECwindows Motif Version 1.2-3 for OpenVMS             Software  C        V1.2-3 The release notes in this chapter are cumulative from H               DECwindows Motif Version 1.0 and still apply to DECwindowsE               Motif Version 1.2-3 for OpenVMS software. The followingrC               sections contain system management release notes that H               pertain specifically to the DECwindows Motif Version 1.2-3#               for OpenVMS software:u  F               o  Section 3.2, Required Reboot on OpenVMS Alpha Version                  6.2 Systems  G               o  Section 3.10, Implications of the Message, System Menug0                  Bar: Pseudo Mouse Not Available  @         3.2 Required Reboot on OpenVMS Alpha Version 6.2 Systems  F       V1.2-3  Although the installation dialog indicates that a systemF               reboot is necessary to complete the installation, it mayE               not be needed on OpenVMS VAX systems (including VersioniG               6.2) and on OpenVMS Alpha systems prior to Version 6.2 if 1               your system parameters are correct.   F                 ________________________ Note ________________________  A                 You must reboot OpenVMS Alpha Version 6.2 systems B                 after the installation of DECwindows Motif Version+                 1.2-3 for OpenVMS software.h  F                 ______________________________________________________  I                                                                       3-1p s      System Manager Release Notes9     3.3 DECwindows Motif Login Screen-Known Color Problemo    9     3.3 DECwindows Motif Login Screen-Known Color Problemp  ?     V1.2  A problem may occur on systems that have a customizedi>           DECW$LOGIN.DAT file. The Start Session dialog box isB           the color blue instead of tan. If this condition exists,D           look for a customized DECW$LOGIN.DAT file in the directoryE           SYS$COMMON:[DECW$DEFAULTS.USER] and move it to SYS$MANAGER.nB           A DECW$LOGIN.DAT file in SYS$COMMON:[DECW$DEFAULTS.USER]B           prevents the "*background:" resource from being defined;2           thus, it will default to the color blue.  C           Digital provides a copy of the DECW$LOGIN.DAT file in the E           SYS$COMMON:[DECW$DEFAULTS.SYSTEM] directory. Any customized B           versions of this file should reside only in SYS$MANAGER.  (     3.4 Color Customizer Example Program  <     V1.2  The color customizer example program allows you to<           dynamically control the colors of your workstationB           environment. Window, icon, and window manager colors canE           be changed individually or as part of a palette switch. You C           can control mapping between resources and color cells, aseA           well as the size and contents of the palette set. Also,o?           automatic shadowing with the standard Motif shadowing "           algorithms is supported.       3.4.1 Supported Displays  E     V1.2  The color customizer supports any display using pseudocolorDA           or grayscale visuals. This includes most 4- and 8-planer           workstation displays.h        3.4.2 Supported Applications  ;     V1.2  The color customizer can affect the colors of any B           applications that use the current release of the Digital@           X Toolkit Library. Applications from other vendors and@           previous versions of the Digital X Toolkit Library are           unaffected.   C              ________________________ Note ________________________   ;              If the color customizer is used to control the =              colors of applications that have their own colors9              customization dialog boxes (like the SessiongA              Manager, Window Manager, and DECwindows Mail), thoseuB              application-specific color customization dialog boxesC              may not reflect the correct current color values whilen?              the customizer is running the application. This is C              normal; use the customizer instead of the application- >              specific dialog box to change these color values.C              ______________________________________________________        3-2  f  t      I                                              System Manager Release Notes,I                                      3.4 Color Customizer Example Programt    >         3.4.3 Building the Color Customizer on OpenVMS Systems  G         V1.2  To build the color customizer on OpenVMS systems, performo"               the following steps:  D               1. Copy the files to a private directory. For example:  (                  $ SET DEFAULT SYS$LOGIN1                  $ CREATE/DIRECTORY [.CUSTOMIZER] ,                  $ SET DEFAULT [.CUSTOMIZER],                  $ DECW$EXAMPLES:CUSTOM.C []3                  $ COPY DECW$EXAMPLES:CUSTOM.UIL [] 8                  $ COPY DECW$EXAMPLES:CUSTOMIMAGE.DAT []8                  $ COPY DECW$EXAMPLES:XSETROOT_CUST.C []=                  $ COPY DECW$EXAMPLES:BUILD_CUSTOMIZER.COM []   B               2. Build the customizer using the following command:  (                  $ @BUILD_CUSTOMIZER.COM  H               This command procedure creates the following output files:                    CUSTOM.UID                   CUSTOM.EXE-"                  XSETROOT_CUST.EXE  *         3.4.4 Running the Color Customizer  G         V1.2  To run the color 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 locationeG                  is the directory SYS$LOGIN or the directory DECW$USER_.                  DEFAULTS.  G               2. Copy the files CUSTOM.DAT and DXMDEFAULTS.DAT from therD                  directory DECW$EXAMPLES to the same location as youG                  copied the files in step 1. The same typical locations0                  apply.b  I                                                                       3-3i    l            System Manager Release Notes(     3.4 Color Customizer Example Program    ;           3. Run the executable file CUSTOM.EXE as follows:f                $ RUN CUSTOM   C              ________________________ Note ________________________   >              Only the colors of applications invoked after theA              customizer starts will be affected. For this reason, C              start the customizer as the first X application during               the login process.hC              ______________________________________________________n  +     3.4.5 Modifying the DECW$LOGIN.COM Filea  C     V1.2  As noted in Section 3.4.4, the color customizer should betC           the first X application started during the login process.e@           Do this by starting it as a subprocess from within theE           DECW$LOGIN.COM file. Add a command to wait approximately 10tE           seconds between customizer startup and the startup of othere           applications.   D           For example, add the following lines to the DECW$LOGIN.COM           file:d  *           $! Starting the color customizer/           $ DISPLAY = F$LOGICAL("DECW$DISPLAY")tB           $ SPAWN/NOWAIT/OUTPUT='DISPLAY' RUN SYS$LOGIN:CUSTOM.EXE           $ WAIT 0:0:10i  =           See Using DECwindows Motif for OpenVMS and Managing C           DECwindows Motif for OpenVMS Systems for more informationa%           on the file DECW$LOGIN.COM.e  #     3.4.6 Command Interface Summarye  A     V1.2  A box containing a list of available palettes is in therC           leftmost section of the Color Customizer window. Click onn<           the desired palette to see the colors take affect.  ?           Below the palettes are two arrays of colored buttons,P@           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.        3-4e           I                                              System Manager Release NotesdI                                      3.4 Color Customizer Example Programs    F                 ________________________ Hint ________________________  D                 As a shortcut, you can click on the screen facsimileA                 in the rightmost corner of the dialog box. If the F                 portion you click on is colored by one of the resourceF                 values controlled by the customizer, the pop-up window>                 for the appropriate color button is displayed.  F                 ______________________________________________________  G               To modify a single color cell, click on the correspondingAD               color button. A colormix widget pops up; as you modifyB               the color, these modifications are reflected in yourD               workstation environment. Use the colormix widget resetI               button to return to the starting color at any time. You canKF               also change the color cell you are modifying by clickingF               on a different color button while the colormix widget is               displayed.  E               The automatic shadowing option causes shadow and selectlI               colors to be automatically updated when their correspondingfI               background colors are changed. The standard Motif shadowing 9               algorithms are used for these calculations.   I               Use the File menu to modify, add, and delete color palettes                as follows:e  C               o  To modify an existing palette, select the palette, D                  change the colors, and choose Save Palette from the                  File menu.s  I               o  To add a new palette, select an existing palette, modifylG                  the colors as necessary, and choose Save Palette As... F                  from the File menu. A message box prompts you for the)                  name of the new palette.E  C               o  To delete a palette, select the palette and choose 3                  Delete Palette from the File menu.t  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 applicationeE               to exit. A warning dialog is displayed first. Note thataF               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 applications  I                                                                       3-5c a  r            System Manager Release Notes(     3.4 Color Customizer Example Program    @           should be restarted to restore normal colors. Usually,>           there is no need to exit the color customizer; it is?           typically kept running at all times, like the Sessiont           Manager.  @     3.4.7 Changing the Mapping Between Color Resources and Color           Cells   A     V1.2  The file DXMDEFAULTS.DAT allows you to control how many B           dynamic color cells are allocated and what resources areC           affected. This file contains resource specifications like            the following:  7           *background:       DXmDynamicWindowBackgrounde7           *foreground:       DXmDynamicWindowForeground 6           *topShadowColor:   DXmDynamicWindowTopShadow  E           When the customizer is started, the file DXMDEFAULTS.DAT is C           written to a property on the root window. Any applicationX>           that is subsequently run and that uses the correct X@           Toolkit Library merges these resources with its normalA           resource database. Resource specifications in this file =           take precedence over specifications with equivalent 9           resource names in other resource default files.   =           The resource values within the file DXMDEFAULTS.DAT ?           have a special format. For each unique color value ina?           this file that begins with the string "DXmDynamic", an=           color button is created in the color customizer. If A           the string "Shadow" is encountered in a name, the color ?           button is placed in the shadow button box rather than >           the normal color button box. If a color value string<           ends with the suffix "Background", it is linked to@           any color buttons with identical prefixes and suffixes>           of "TopShadow", "BottomShadow", or "SelectColor" forA           purposes of automatic shadowing. If a color value named E           "DXmDynamicScreenBackground" is encountered, the color cell D           allocated is used by the customizer to set the root window           background color.o  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 DECwindowsr@           Mail application, for example, by adding the following,           lines to the file DXMDEFAULTS.DAT:       3-6l (         I                                              System Manager Release Notes I                                      3.4 Color Customizer Example Program)    A               Mail*background:         DXmDynamicMyMailBackground A               Mail*foreground:         DXmDynamicMyMailForegrounde@               Mail*topShadowColor:     DXmDynamicMyMailTopShadowC               Mail*bottomShadowColor:  DXmDynamicMyMailBottomShadowe  G               Adding the previous lines to the file DXMDEFAULTS.DAT andmF               restarting the customizer causes four new color cells toH               be allocated and four new color buttons to be added to theF               customizer interface. These buttons are assigned defaultE               color values (usually black or white) for each palette.eB               These defaults can then be modified for each palette/               through the customizer interface.a    F                 ________________________ Note ________________________  @                 The text of the DXMDEFAULTS.DAT file is read andE                 parsed by the color customizer. The parsing algorithmi>                 does not allow comments, incorrect spacing, or?                 incorrect resource specifications. If this file4?                 or the CUSTOM.DAT resource file become corrupt,oA                 the customizer cannot start correctly. To resolve.@                 the problem, copy the versions of CUSTOM.DAT andE                 DXMDEFAULTS.DAT from the DECW$EXAMPLES directory into\%                 your login directory.-  F                 ______________________________________________________  *         3.4.8 DECterm Windows Not Affected  @         V1.2  The color customizer does not affect the colors ofG               DECterm windows. To change the colors of DECterm windows,hD               copy the DECterm resource specifications from the fileB               DXMDEFAULTS.DAT and add them to the DECterm resourceI               defaults file DECW$USER_DEFAULTS:DECW$TERMINAL_DEFAULT.DAT.hA               For example, add the following lines to the DECterm-%               resource defaults file:d                    .                  .                  .N           DECW$TERMINAL.main.terminal.background: DXmDynamicTerminalBackgroundN           DECW$TERMINAL.main.terminal.foreground: DXmDynamicTerminalForeground  I               This allows the DECterm window colors to be customized with_#               the color customizer.   I                                                                       3-7                  System Manager Release Notes(     3.4 Color Customizer Example Program    ?     3.4.9 Changing the Default Value of the Automatic Shadowing            Toggle Button   =     V1.2  The default value of the automatic shadowing togglecC           button is set using the Custom.autoShadow resource in thep%           CUSTOM.DAT file as follows:3  %           Custom.autoShadowing: False   $           The default value is True.  4     3.4.10 Using the Customizer on Multihead Systems  C     V1.2  The color customizer affects only applications started on B           the same screen as the customizer. On multihead systems,D           you can start a different color customizer for each screen@           and have a different palette in effect on each screen.  >           The color customizer can be configured so that it isA           invoked once and affects all applications regardless of C           where they are started. This mode is invoked by modifying C           the Custom.multiScreen resource in the CUSTOM.DAT file asd           follows:  "           Custom.multiScreen: True  %           The default value is False.c  <     3.4.11 Using the XSETROOT_CUST.EXE Demonstration Program  E     V1.2  The XSETROOT_CUST.EXE demonstration program, created durings@           the customizer build, is a modified version of the MIT?           utility program xsetroot that is used to set a bitmape@           on the root window. The XSETROOT_CUST.EXE program usesC           DXmDynamicScreenBackground and DXmDynamicScreenForeground B           as the background and foreground colors of the specified?           bitmap. If your DXMDEFAULTS.DAT file contains entriestB           for these two dynamic colors, then use the customizer to7           dynamically modify the colors of your bitmap.              For example:  <           $ XSETROOT_CUST :== "$SYS$LOGIN:XSETROOT_CUST.EXE"3           $ XSETROOT_CUST -BITMAP your_xbm_file.XBM        3-8M f  g      I                                              System Manager Release NotesaI  Define  DECW$UTILS Global Symbol When Moving DECW$EXAMPLES Global Symbolo    E         3.5 Define DECW$UTILS Global Symbol When Moving DECW$EXAMPLES              Global Symbole  @         V1.2  By default, DECW$UTILS points to a subdirectory ofH               DECW$EXAMPLES. If you define a DECW$EXAMPLES global symbolE               in the DECW$PRIVATE_APPS_SETUP.COM command procedure tonG               change the directory for DECwindows example programs, youcE               must also define DECW$UTILS to change the directory fori               utilities.  I               For example, to redefine both DECW$EXAMPLES and DECW$UTILS,oF               add the following lines to the SYS$MANAGER:DECW$PRIVATE_'               APPS_SETUP.COM procedure:   <               $ DECW$EXAMPLES == "SYS$SYSROOT:[DECWEXAMPLES]?               $ DECW$UTILS == "SYS$SYSROOT:[DECWEXAMPLES.UTILS]n  F                 ________________________ Note ________________________  >                 If the SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM7                 file does not exist, create it from thelB                 SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.TEMPLATE file.  F                 ______________________________________________________  H               Then, restart DECwindows Motif with the following command:  0               $@SYS$MANAGER:DECW$STARTUP RESTART  E               The DECW$UTILS global symbol is new in DECwindows Motifk&               Version 1.2 for OpenVMS.  :         3.6 FileView Creates Detached Processes by Default  F         V1.1  Applications created by FileView and Session Manager are!               detached processes.r  A               The implication is that during application startup, E               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 applicationH               from starting. Examples of such commands are INQUIRE, READ0               /PROMPT, and SET TERMINAL/INQUIRE.  I                                                                       3-9  r  i            System Manager Release Notes6     3.6 FileView Creates Detached Processes by Default    ?           Extensive SYLOGIN.COM or LOGIN.COM command procedures ?           slow down application startup. Many of the operations A           performed in a SYLOGIN.COM or LOGIN.COM are meaningless <           for DECwindows application startup. Therefore, theC           SYLOGIN.COM and LOGIN.COM files should be conditionalizedu>           for DECwindows application startup performance. When>           starting a DECwindows application, only a minimum of@           SYLOGIN.COM and LOGIN.COM commands should be executed.A           Typically, the commands that should be executed are theUD           redefinition of DECW$USER_DEFAULTS (if present), and otherB           logical name definitions if the user will be referencingC           them from within the context of a DECwindows application.[E           The following code segment can be inserted into SYLOGIN.COM D           and LOGIN.COM immediately following the commands necessary           for DECwindows:M             $ mode = f$mode().'           $ tt_devname = f$trnlnm("TT") C           $ session_mgr_login = (mode .eqs. "INTERACTIVE") .and.  - C                 (f$locate("WSA",tt_devname) .ne. f$len(tt_devname)) I           $ session_detached_process = (mode .eqs. "INTERACTIVE") .and. -OC                 (f$locate("MBA",tt_devname) .ne. f$len(tt_devname))1H           $ if session_mgr_login .or. session_detached_process then exit  B           Applications continue to run even if these lines are not7           added to the SYLOGIN.COM and LOGIN.COM files.r  $     3.7 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 resourceD@           definitions from SYS$MANAGER:DECW$LOGIN.DAT are merged>           with the resource definitions supplied by Digital inA           SYS$COMMON:[DECW$DEFAULTS.SYSTEM]DECW$LOGIN.DAT to form            the new login screen.   A           Keep customized versions of the DECW$LOGIN.DAT resourcenD           file in the SYS$MANAGER directory, and not in DECW$SYSTEM_>           DEFAULTS, to prevent your customized file from beingD           overwritten when upgraded to a newer version of DECwindowsC           Motif for OpenVMS software. In addition, storing the fileoD           in the SYS$MANAGER directory prevents the custom file from;           superseding the file that is supplied by Digital.f       3-10 i  d      I                                              System Manager Release Notes_I                                          3.7 Customizing the Login Screena    B         3.7.1 Customizing the Digital Logo and Login Screen Colors  F         V1.2  You can define the resources in Table 3-1 to control theF               position and colors of the Digital logo and the color of@               the screen background in the Start Session screen.  I               Table 3-1 Moving the Digital Logo and Changing Login Screen                          ColorsJ               ____________________________________________________________  +               Resource          Description J               ____________________________________________________________  ?               rootColor         Color of the screen background.   E               logoColor         Color of the Digital logo (default is *                                 burgundy).  G               logoX             x position of the Digital logo (default &                                 is 0).  G               logoY             y position of the Digital logo (defaultn'                                 is 75).n  G               centerLogoX       Boolean; if true (default), the Digital D                                 logo is centered horizontally on the'                                 screen.c  A               For example, to position the Digital logo at x=100,cB               y=600, add the following resource definitions to the.               SYS$MANAGER:DECW$LOGIN.DAT file:  #               decw$login.logoX: 100 #               decw$login.logoY: 600a+               decw$login.centerLogoX: false   F         3.7.2 Changing Positions of the Start Session and Set Password               Dialog Boxes  F         V1.2  You can define the resources in Table 3-2 to control theC               position of the Start Session and Set Password dialoge               boxes.          I                                                                      3-11  a  s            System Manager Release Notes$     3.7 Customizing the Login Screen    B           Table 3-2 Changing Position of the Start Session and Set)                     Password Dialog Boxes F           ____________________________________________________________  +           Resource              DescriptionsF           ____________________________________________________________  ?           centerStartSessionX   Boolean; if true (default), therD                                 Start Session dialog box is centered-                                 horizontally.g  ?           centerStartSessionY   Boolean; if true (default), thedD                                 Start Session dialog box is centered+                                 vertically.n  ?           centerSetPasswordX    Boolean; if true (default), themC                                 Set Password dialog box for expiredcC                                 passwords is centered horizontally.i  ?           centerSetPasswordY    Boolean; if true (default), theeC                                 Set Password dialog box is centeredl+                                 vertically.i  B           For example, to position the Start Session dialog box atE           x=100, y=600, add the following resource definitions to the *           SYS$MANAGER:DECW$LOGIN.DAT file:  /           decw$login.centerStartSessionX: falser/           decw$login.centerStartSessionY: false '           decw$login.HiddenShell.x: 100a'           decw$login.HiddenShell.y: 600   :           To position the Set Password dialog box at x=30,>           y=100, add the following resource definitions to the*           SYS$MANAGER:DECW$LOGIN.DAT file:  .           decw$login.centerSetPasswordX: false.           decw$login.centerSetPasswordY: false+           decw$login.SetPasswordShell.x: 30 ,           decw$login.SetPasswordShell.y: 100  C     3.7.3 Disabling a Node Name Display in the Start Session Dialogy
           Boxt  B     V1.2  To prevent a node name from being displayed in the StartC           Session dialog box, add the following resource definitionl1           to the SYS$MANAGER:DECW$LOGIN.DAT file:   +           decw$login.displayNodeName: falseu       3-12 o  a      I                                              System Manager Release Notes I                                                3.8 Customized Login Logoss    "         3.8 Customized Login Logos  A         V1.1  By default, if there is no DECwindows Motif licenselD               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 Motif E               license for SYSTEM, add the following definition to the ;               SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM file:i  +               $ DECW$LOGINLOGOSUB == "TRUE"   F                 ________________________ Note ________________________  A                 If the file does not exist, copy it from the fileE=                 SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.TEMPLATE.d  F                 ______________________________________________________  D               After editing the setup file, restart DECwindows Motif*               using the following command:  1               $ @SYS$MANAGER:DECW$STARTUP RESTARTc  A               DECwindows Motif login starts the logo process as atF               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.  *         3.9 Version Checking Command Files  D         V1.0  The DECwindows Motif for OpenVMS kit contains version-G               checking command procedures that layered products can usehF               during their installation procedure. The following threeE               files are placed in the SYS$UPDATE directory during thes?               installation of VMS DECwindows Motif Version 1.0:n  +               o  DECW$GET_IMAGE_VERSION.COMa  <                  A command procedure that extracts the imageI                  identification string from an image and places it into an%                  user-defined symbol.l  *               o  DECW$COMPARE_VERSIONS.COM  I                                                                      3-13X F  T            System Manager Release Notes&     3.9 Version Checking Command Files    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.a  :              -  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 versionsF:              of several components of the DECwindows Motif<              layered product and the X11 display server. TheA              DECW$VERSIONS.COM procedure uses the DECW$GET_IMAGE_ E              VERSION.COM command procedure to obtain the image identseC              of each file. Use the following command to display the $              versions on sys$output:  *              $ @SYS$UPDATE:DECW$VERSIONS *  E              ________________________________________________________i.              Component             DescriptionE              ________________________________________________________u  ;              DECwindows ident      MIT Xlib shareable image_  2              DECwindows server     Server DIX file  3              DECwindows transport  Transport common   ;              DECwindows Xlib       MIT Xlib shareable image   7              DECwindows OSF/Motif  OSF/Motif Xm Toolkit               Toolkit  6              DECwindows            DECwindows FileView              applicationso  9              DECwindows            OSF/Motif UIL compilern              programming  @              The output from the command procedure shows DW, the?              version number, and the date the image is created.c                For example:o  O        DW  V1.23-940924, is version 1.2-3. and was created on September 9, 1994_       3-14           H                                              System Manager Release NoteJ Implications of the Message, "System Menu Bar: Pseudo Mouse Not Available"    H         3.10 Implications of the Message, "System Menu Bar: Pseudo Mouse              Not Available"   A        V1.2-3 "System Menu Bar: Pseudo Mouse not available" is aneB               informational message that is included in the user'sI               DECW$USER_DEFAULTS:DECW$SM.LOG file when you run a session.eE               It is not an error message. The message occurs when the F               OpenVMS Session Manager is run remotely to a non-OpenVMSE               server. The OpenVMS server provides pseudomouse mode, a F               mode that allows you to use arrow keys to move the mouse               cursor.m  -         3.11 DECterm System Management Issues   D               This section contains information about DECterm system                management issues.  $         3.11.1 DECterm Logical Names  I         V1.1  Table 3-3 describes the logical names that are supported byiG               DECterm. If you do not define these logical names in yourtD               LOGIN.COM file, the controller uses the default files.  4         Table 3-3 Logical Names Supported by DECtermI         _________________________________________________________________e  5         Logical Name                      DescriptionnI         _________________________________________________________________o  F         DECTERM_DIAG                      Enables diagnostic messages.  F         DECTERM_SHOW_PARSING              Shows characters as they are1                                           parsed.e  I         DECTERM_CHECK_MEMORY              Enables strict memory checking.t  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; default ?                                           is DECTERM_ERROR.LOG.   I         DECW$DECTERM_OUTPUT               Name of diagnostic output file;t@                                           default is SYS$OUTPUT.  G         DECW$DECTERM_REGIS_CURSOR         Specifies which cursor to useo4                                           for ReGIS.  I                                                  (continued on next page)   I                                                                      3-15o                 System Manager Release Notes)     3.11 DECterm System Management Issues     8     Table 3-3 (Cont.) Logical Names Supported by DECtermE     _________________________________________________________________a  1     Logical Name                      DescriptionoE     _________________________________________________________________X  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 theA1                                       controller.T  C     DECW$DECTERM_CTRL_PSWAPM          Sets the PSWAPM quota for thee1                                       controller.a  E     DECW$DECTERM_CTRL_WSEXTENT        Sets the WSEXTENT quota for theL1                                       controller._  D     DECW$DECTERM_CTRL_WSQUOTA         Sets the WSQUOTA quota for the1                                       controller.   ?     DECW$DECTERM_DISABLE_QUOTA_       Turns off quota checking.      CHECKING  <     DECW$DECTERM_MEM_DIAG             Shows controller quota3                                       calculations.e  '     3.11.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 theOC           window off the screen. If a DECterm window is enlarged byNB           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 thatUA           it can be viewed in its entirety. If you prefer DECterm_D           not to move, add the following line to your DECW$TERMINAL_           DEFAULT.DAT file:   =           DECW$TERMINAL.main.terminal.autoAdjustPosition: off   $     3.11.3 Hold Screen Response Time  C     V1.1  If the hold screen key response time is too slow, add the.A           following lines to your DECW$TERMINAL_DEFAULT.DAT file:p  6           DECW$TERMINAL.main.terminal.syncFrequency: 19           DECW$TERMINAL.main.terminal.batchScrollCount: 1c       3-16 u  g      I                                              System Manager Release Notes.I                                     3.11 DECterm System Management Issuesy    C               Using this resource can affect the performance of the E               DECterm window. The actual impact on performance variesfE               from site to site. You can trade off scrolling speed tonF               hold-screen response time. A faster hold-screen responseI               results in a slower scrolling speed. The default values for 9               these resources are 10 and 0, respectively.   !         3.11.4 Using the DebuggerN  C         V1.0  To redirect the output from the debugger to a DECterm 2               window, enter the following command:  4               $ CREATE/TERMINAL/NOPROCESS/DEFINE=xxx  B               This command creates a DECterm without an associatedG               process but with a logical name of xxx that points to thetH               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 the.!               following commands:e  +               $ DEFINE /USER DBG$INPUT xxx:h  ,               $ DEFINE /USER DBG$OUTPUT xxx:  *               $ RUN /DEBUG application.EXE  '         3.11.5 Virtual Terminal Supporti  I         V1.0  To create a process that uses a virtual terminal, enter theE                following command:  )               $ CREATE/TERMINAL/NOPROCESSt  F               Then establish focus to the newly created DECterm, pressH               Return, and log in. Note that the /DEFINE qualifier is not               required.t                I                                                                      3-17           t                I                                                                         4.I         _________________________________________________________________n  I                                                  Programmer Release Notesd    =               This chapter contains programmer release notes.f  B         4.1 Programming Release Notes Specific to DECwindows Motif.             Version 1.2-3 for OpenVMS Software  C               The release notes in this chapter are cumulative from A               DECwindows Motif Version 1.0 and still apply to thetF               DECwindows Motif Version 1.2-3 for OpenVMS software. TheF               following sections contain programmer release notes thatH               pertain specifically to the DECwindows Motif Version 1.2-3"               for OpenVMS release:  B               o  Section 4.2, DECwindows Motif for OpenVMS Toolkit                  Versionsc  C               o  Section 4.3, Run-Time and Programming Environments_  =               o  Section 4.4, OSF/Motif Toolkit Compatibility   /               o  Section 4.5, Language Bindingsi  I               o  Section 4.6, OSF/Motif Release 1.1.3 Programming Supportt                  and XUI  D               o  Section 4.8.1, Running Translated Images on OpenVMS                  Systems  1               o  Section 4.12.2.1, Version Number   4               o  Section 4.13.4, ReGIS Input Cursors  H               o  Section 4.14.4, Compile-Time Incompatibilities in Motif                  Header Filest      I                                                                       4-1t r  u           Programmer Release Notes5     4.2 DECwindows Motif for OpenVMS Toolkit Versions     5     4.2 DECwindows Motif for OpenVMS Toolkit Versionsa  C    V1.2-3 The DECwindows Motif Version 1.2-3 for OpenVMS release isnB           based on the OSF/Motif Release 1.2.3 Toolkit and MIT X11           Release 5 (R5)._  A     V1.2  The DECwindows Motif Version 1.2 for OpenVMS release is B           based on the OSF/Motif Release 1.2.2 Toolkit and MIT X11           Release 5 (R5).   C     V1.1  The VMS DECwindows Motif Version 1.1 release was based on C           the OSF/Motif Release 1.1.3 Toolkit and MIT X11 Release 4            (R4).   C     V1.0  The VMS DECwindows Motif Version 1.0 release was based onhC           the OSF/Motif Release 1.1.1 Toolkit and MIT X11 Release 4            (R4).   -     4.3 Run-Time and Programming Environmentsl  A    V1.2-3 The following run-time and programming environments areo>           provided with the DECwindows Motif Version 1.2-3 for           OpenVMS software:e  C           o  Run-time support is provided for the OSF/Motif Release D              1.2.3 Toolkit, OSF/Motif Release 1.1.3 Toolkit, and the-              X User Interface (XUI) Toolkits.e  >           o  Development support is provided for the OSF/Motif(              Release 1.2.3 Toolkit only.  A              You can, however, choose during installation to saveg?              the OSF/Motif Release 1.1.3 programming files thato=              existed on your system prior to the installation >              of the DECwindows Motif Version 1.2-3 for OpenVMSA              product. Refer to the DECwindows Motif Version 1.2-3 D              for OpenVMS Installation Guide for details about savingA              the OSF/Motif Release 1.1.3 programming environment.R  ?              -  If you install the software using the VMSINSTALaE                 procedure and choose to save these programming files, @                 the files are moved to subdirectories and can be)                 accessed for programming.   @              -  If you install the software using the POLYCENTER@                 Software Installation utility and if programming?                 support for the OSF/Motif Release 1.1.3 Toolkit B                 is present, then you can choose to save the header       4-2  i  t      I                                                  Programmer Release Notes I                                 4.3 Run-Time and Programming Environments     D                     files and UIL compiler that were used to developF                     OSF/Motif Release 1.1.3 applications. If selected,H                     the preinstallation procedure creates a subdirectoryD                     called [.DECW$113], and the previous programming>                     files are moved into the new subdirectory.  C                  See the DECwindows Motif Version 1.2-3 for OpenVMS D                  Installation Guide for additional information aboutB                  saving the Release 1.1.3 programming environment.  B               o  Application development with the DECwindows MotifG                  Version 1.2-3 for OpenVMS product is supported for DECaG                  C++ as well as for updated Motif language bindings foreG                  Ada, Pascal, Fortran, and C. Language bindings for Ada3F                  are available in the DEC Ada Version 3.0A for OpenVMS2                  (VAX and Alpha) layered products.  +         4.4 OSF/Motif Toolkit Compatibility   H        V1.2-3 You cannot code and compile an application with DECwindowsF               Motif Versions 1.2 or 1.2-3 include files, transport theC               resulting object files to a system running DECwindows G               Motif Version 1.1 software, link the object files against E               DECwindows Motif Version 1.1, and expect the executable G               image (.EXE) to run. Differences in structures defined inlI               the .h files cause the offsets to be misaligned and thereby @               prevent you from creating a meaningful executable.  E         V1.2  The OSF/Motif Release 1.1.3 and Release 1.2.2 Toolkits,u@               on which the DECwindows Motif Versions 1.1 and 1.2F               layered products are based, are not compatible. However,D               applications built against the OSF/Motif Release 1.1.3D               Toolkit will continue to run without modification withE               DECwindows Motif Version 1.2 for OpenVMS; the OSF/Motif E               Release 1.1.3 Toolkit shareable libraries will continuelF               to be supplied with the DECwindows Motif Version 1.2 forG               OpenVMS layered product and will be available to existingE4               DECwindows applications on the system.  E               Although DECwindows Motif Version 1.1 applications will_H               continue to run without modification with DECwindows MotifC               Version 1.2 for OpenVMS, it is important to note thatAF               only those applications that have been built against theG               OSF/Motif Release 1.2.2 Toolkit can take advantage of newt  I                                                                       4-3     S           Programmer Release Notes'     4.4 OSF/Motif Toolkit Compatibilityt    C           Version 1.2 features, such as drag-and-drop functionalitye           and tear-off menus.   :           In most cases, simple applications (for example,C           applications that do not contain private toolkit routines A           or user-written widgets) can be recompiled and relinkedsD           against the OSF/Motif Release 1.2.2 Toolkit to include theD           new Version 1.2 features. However, previously unidentified@           problems in a DECwindows Motif Version 1.1 applicationA           might be exposed by relinking against the new OSF/Motif ?           Release 1.2.2 Toolkit, and behavior and widget layout B           changes in the Release 1.2.2 Toolkit might require other4           modifications to your application as well.  >           More complex applications will probably require moreA           substantial modifications with the new DECwindows MotifC?           Version 1.2 for OpenVMS Toolkit to use the macros and            functions provided.   ?           If the code generates errors because of references tolE           display structure fields, define the constant XLIB_ILLEGAL_ 8           ACCESS for X11 R5 compatible structure access.             For example:  5           $ CC/DEFINE=XLIB_ILLEGAL_ACCESS DECBURGER.Ci       4.4.1 _Xm Routines  C     V1.2  The OSF/Motif Toolkit libraries contain many undocumentediC           routines, which are prefixed with _Xm. These routines areeA           intended to be used only by the standard Motif widgets. C           OSF reserves the right to modify the API or functionality C           of these routines, or to delete them altogether in futured           releases.d  D              _______________________ Caution _______________________  C              Digital supplies access to the _Xm routines by copyinge>              them into the shareable image transfer vector forB              the OSF/Motif Release 1.2.2 Toolkit. Digital does notB              document or support these routines or guarantee their@              continued existence in future releases. ApplicationA              developers who use these routines do so at their own_              risk.  C              _______________________________________________________       4-4     C      I                                                  Programmer Release NotestI                                       4.4 OSF/Motif Toolkit Compatibility     A         4.4.2 OSF/Motif Release 1.2.2 and X11 Release 5 ShareableT               LibrariesC  A         V1.2  Because the OSF/Motif Release 1.2.2 Toolkit and the H               OSF/Motif Release 1.1.3 Toolkit are not binary compatible,C               applications must link with one toolkit or the other.sI               Applications based on OSF/Motif Release 1.2.2 can only link F               against OSF/Motif 1.2.2-based and X11 R5-based shareableF               libraries. Applications based on OSF/Motif Release 1.1.3E               can only link against OSF/Motif 1.1.3-based and X11 R4-m(               based shareable libraries.  I               To provide both OSF/Motif Release 1.2.2-based and OSF/Motif I               Release 1.1.3-based shareable libraries, the Release 1.1.3--G               based libraries have the same file names as in DECwindowsoF               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:                 o  CDA$ACCESS.EXE   $               o  DECW$D2DXLIBSHR.EXE  $               o  DECW$XEXTLIBSHR.EXE  !               o  DECW$XLIBSHR.EXEn  )               o  XDPS$DPSBINDINGSSSHR.EXE   &               o  XDPS$DPSCLIENTSHR.EXE  #               o  XDPS$DPSLIBSHR.EXE                  o  XIE$SHRLIB.EXEa  H               Shareable libraries that are linked with Release 5 (R5) ofF               the Xt Toolkit have a suffix of "R5". Libraries based onH               the XUI Toolkit have no R5 equivalent libraries and shouldI               not be included in a linker options file based on X11 R5 or_H               OSF/Motif Release 1.2.2. Table 4-1 lists these file names.  F                 ________________________ Note ________________________  >                 The DECW$XLIBSHR.EXE file is the MIT Release 5?                 version, not the MIT Release 4 version of Xlib.a  F                 ______________________________________________________  I                                                                       4-5  E       Programmer Release Notes'     4.4 OSF/Motif Toolkit Compatibility   <           Table 4-1 Names of Shareable Libraries Based on R5E           ___________________________________________________________   @           Names of Files Based on R4  Names of Files Based on R5E           ___________________________________________________________   8           DECW$MAILSHR.EXE            DECW$MAILSHRR5.EXE  ,           DECW$DWTLIBSHR.EXE          (None)  ,           DECW$DWTSHR.EXE             (None)  :           DECW$XMULIBSHR.EXE          DECW$XMULIBSHRR5.EXE  <           DECW$XTRAPLIBSHR.EXE        DECW$XTRAPLIBSHRR5.EXE  9           DECW$XTSHR.EXE              DECW$XTLIBSHRR5.EXE   ;           Release 5 does not provide an equivalent file for1B           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 only_A           with libraries compatible with R5 and OSF/Motif Releasem2           1.2.2. Table 4-2 lists these file names.  O         Table 4-2 Names of Shareable Libraries Based on OSF/Motif Release 1.2.2eC         ___________________________________________________________o  C         Names of Files Based on     Names of Files Based on Releaset)         Release 1.1.3               1.2.2 C         ___________________________________________________________W  6         DDIF$VIEWSHR.EXE            DDIF$VIEWSHR12.EXE  5         DECW$BKRSHR.EXE             DECW$BKRSHR12.EXE   8         DECW$DXMLIBSHR.EXE          DECW$DXMLIBSHR12.EXE  *         DECW$MAILSHR12.EXE          (None)  8         (None)                      DECW$MRMLIBSHR12.EXE  *         DECW$PRINTWGTSHR.EXE        (None)  :         DECW$TERMINALSHR.EXE        DECW$TERMINALSHR12.EXE  7         DECW$XMLIBSHR.EXE           DECW$XMLIBSHR12.EXE   5         DGIT$LIBSHR.EXE             DGIT$LIBSHR12.EXE   4         IMG$SHRLIB.EXE              IMG$SHRLIB12.EXE  4         LWK$DXMSHR.EXE              LWK$DXMSHR12.EXE  1         XNL$SHR.EXE                 XNL$SHR12.EXEp         4-6d o  o      I                                                  Programmer Release NotesnI                                       4.4 OSF/Motif Toolkit CompatibilityU    G               There is no DECW$PRINTWGTSHR12.EXE file; the Print Widget 7               is part of the DECW$DXMLIBSHR12.EXE file.A  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 accessE7               .UID files should link with this library.W  F               For example, a typical linker options file for a programC               based on OSF/Motif Release 1.1.3 might be as follows:e  *               SYS$SHARE:DECW$XLIBSHR/SHARE(               SYS$SHARE:DECW$XTSHR/SHARE,               SYS$SHARE:DECW$DWTLIBSHR/SHARE+               SYS$SHARE:DECW$XMLIBSHR/SHAREd,               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:r  *               SYS$SHARE:DECW$XLIBSHR/SHARE-               SYS$SHARE:DECW$XTLIBSHRR5/SHARE -               SYS$SHARE:DECW$XMLIBSHR12/SHAREi.               SYS$SHARE:DECW$MRMLIBSHR12/SHARE.               SYS$SHARE:DECW$DXMLIBSHR12/SHARE  F               These changes eliminate the reference to the XUI ToolkitD               (DECW$DWTLIBSHR.EXE) and links with the Motif Resource-               Manager (DECW$MRMLIBSHR12.EXE).o      I                                                                       4-7                 Programmer Release Notes     4.5 Language Bindingsa         4.5 Language Bindingso  ;    V1.2-3 Fortran, Pascal, C, and C++ language bindings arerD           provided to support software development for the following            DECwindows components:             o  Xlib (Release 5)              o  Xt (Release 5)G             o  Xm (Release 1.2.3)               o  Mrm (Release 1.2.3)             o  DXm  .     4.5.1 OSF/Motif Release 1.1.3 Ada Bindings  ?     V1.2  This release of DECwindows Motif does not include AdamA           bindings for either the OSF/Motif Release 1.1.3 Toolkit @           or the OSF/Motif Release 1.2.2 Toolkit. Strongly typedD           bindings for both toolkits are part of the DEC Ada Version            3.0A language product.  @           If DECwindows Motif is installed on OpenVMS DECwindows@           Motif Version 1.1, then the existing OSF/Motif ReleaseD           1.1.3 Ada bindings, located in the DECW$INCLUDE directory,#           are not deleted or moved._  ;     4.6 OSF/Motif Release 1.1.3 Programming Support and XUI       V1.2-3 Restrictions             o  Problem:   A              You will encounter problems if you save the previousg@              (Release 1.1.3) programming environment and attempt?              to run an OSF/Motif Release 1.1.3 (Xlib Release 4)eB              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 where C              OSF/Motif Release 1.1.3 is installed, the result is an (              ident mismatch fatal error.       4-8            I                                                  Programmer Release NotesoI                   4.6 OSF/Motif Release 1.1.3 Programming Support and XUI     A                  In addition, the OSF/Motif Release 1.1.3 and the H                  Release 1.2.2 files produce different output; they haveG                  different structures and are therefore not compatible.cH                  Use the appropriate UIL compiler to produce the correct                  UID file.                 o  Resolution:  ?                  1. Rename the DECwindows Motif Version Versiona?                     1.1 executable compiler, DECW$MOTIF.EXE, to I                     DECW$MOTIF113.EXE and keep the file in the SYS$COMMON I                     directory. By doing this, the name of the new VersiontE                     1.2-3 compiler, DECW$MOTIF.EXE, does not conflict)/                     with the previous compiler.f  F                  2. Copy the DECW$XLIBSHR.EXE file (Xlib Release 4) to?                     the SYS$COMMON:[SYSEXE.DECW$113] directory.   I                     The Xlib Release 5 version of Xlib has the same name;eI                     however, a logical name is defined to use the ReleasehG                     4 version when the programs are linked. The changesSI                     in minor ident of DECW$XLIBSHR.EXE between DECwindows F                     Motif Version 1.1 and DECwindows Motif Version 1.2G                     for OpenVMS caused a loss of backward compatibilityE>                     with DECwindows Motif Version 1.1 systems.  D                  3. If you save the previous programming environmentG                     during installation, create the following two files E                     and copy them to the SYS$COMMON:[SYSEXE.DECW$113]s                     directory:  .                     -  DECW$UILCOMPILER113.CLD  E                        This file enables UIL/OSF Motif and UIL/XUI to I                        function for either XUI or OSF/Motif Release 1.1.3iD                        if you select DECW$MOTIF113.EXE for OSF/MotifE                        Release 1.1.3 or DECW$UILCOMPILER.EXE for XUI.o  2                     -  DECW$DEFINE113_LOGICALS.COM  H                        This file points to the saved header files, whichI                        in turn point to the Xlib Release 4 version of thea-                        DECW$XLIBSHR.EXE file.   F                  4. An application must be run on the same version (orH                     higher) of the operating system as the version whereE                     it is linked. For example, an application that issI                     linked on a VMS Version 5.4-3 system must be run on ao9                     VMS Version 5.4-3 (or higher) system.   I                                                                       4-9e r              Programmer Release Notes;     4.6 OSF/Motif Release 1.1.3 Programming Support and XUI     >                 DECwindows Motif Version 1.1 applications thatA                 are compiled for OpenVMS Version 6.1 systems willuB                 run only on OpenVMS Version 6.1 systems and not on-                 systems prior to Version 6.1.i  D     V1.2  The X Window and OSF/Motif libraries that are shipped with?           DECwindows Motif Version 1.2 for OpenVMS software areiA           incompatible with those shipped with previous versions.e<           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 Motif D           is no longer supported in DECwindows Motif Version 1.2 forD           OpenVMS. However, the installation procedure gives you theC           option of saving the programming files that already existoA           on your system. If you choose to save these programmingf?           files, they are moved to subdirectories where you can E           access them for programming. Specifically, the installationtB           creates a subdirectory called [.DECW$113] in each of the@           directories listed in Table 4-3 and moves the previous*           files into the new subdirectory.  ;           For more information about saving the programmingeA           files, see the DECwindows Motif Version 1.2 for OpenVMS            Installation Guide.   E           Table 4-3 Directories for Previous XUI or Motif Programming                      EnvironmentoE           ___________________________________________________________e  0           Directory     Contents    New LocationE           ___________________________________________________________w  G           DECW$INCLUDE  C header    SYS$SYSROOT:[DECW$INCLUDE.DECW$113]c                         filese  A           SYS$SYSTEM    UIL         SYS$SYSROOT:[SYSEXE.DECW$113]l                          compiler  A           SYS$LIBRARY   Non-C       SYS$SYSROOT:[SYSLIB.DECW$113]o                          language!                         bindings.s  B           To program with these files, include the new [.DECW$113]C           subdirectories in the search path for each of the logicalp4           names. For example, perform the following:         4-10    w      I                                                  Programmer Release NotessI                   4.6 OSF/Motif Release 1.1.3 Programming Support and XUIi  >           o  Change the definition of DECW$INCLUDE as follows:  ,                  $ SHOW LOGICAL DECW$INCLUDEP               "DECW$INCLUDE" = "SYS$SYSROOT:[DECW$INCLUDE]" (DECW$LOGICAL_NAMES)B                          = "SYS$SYSROOT:[DECW$INCLUDE.EXTENSIONS]"  K                  $ DEFINE/EXECUTIVE/TABLE=DECW$LOGICAL_NAMES DECW$INCLUDE -a8                   SYS$SYSROOT:[DECW$INCLUDE.DECW$113], -/                   SYS$SYSROOT:[DECW$INCLUDE], -r7                   SYS$SYSROOT:[DECW$INCLUDE.EXTENSIONS]   H               Place the new [.DECW$113] subdirectory first in the searchF               list, since many of the files that have been updated forD               this release have the same name as the files that wereG               moved to the [.DECW$113] subdirectory. Thus, the files ino<               [.DECW$113] are used for software development.  1               If DECW$INCLUDE is redefined in the H               SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM command procedure,@               then modify the previous instructions accordingly.  I               To use the UIL compiler for XUI or OSF/Motif Release 1.1.3,i*               perform the following steps:  %               1. Create a file calledaG                  SYS$SYSROOT:[SYSEXE.DECW$113]DECW$UILCOMPILER.CLD thatd-                  contains the following text:o  +                  define type trace_keywordsn                    keyword tokens!                   keyword symbolse  -                  define type warning_keywordse$                   keyword nowarnings*                   keyword noinformationals  -                  define type version_keywords ,                   keyword V1, syntax=xui_uil5                   keyword V2, syntax=xui_uil, defaulti3                   keyword MOTIF11, syntax=motif_uilt  &                  define syntax xui_uil(                   image decw$uilcompiler  (                  define syntax motif_uil%                   image decw$uilmotift  I                                                                      4-11g e  n           Programmer Release Notes;     4.6 OSF/Motif Release 1.1.3 Programming Support and XUI_                  define verb uil$               image decw$uilcompiler.               parameter p1, label=source_file,H                prompt="File", value(required,noconcatenate,type=$infile)0               qualifier trace, label=trace_qual,J                value(list,noconcatenate,type=trace_keywords), nonnegatable6               qualifier warnings, label=warnings_qual,>                value(list,noconcatenate,type=warning_keywords)1               qualifier list, label=listing_file,_*                batch, value(type=$outfile)4               qualifier machine, label=machine_qual,4               qualifier output, label=resource_file,,                default, value(type=$outfile)=               qualifier version, label=version_qual, default, ,                value(type=version_keywords),                nonnegatable.B               qualifier XUI, default, nonnegatable, syntax=xui_uil=               qualifier MOTIF, nonnegatable, syntax=motif_uilw  C               qualifier widget_meta_description, label=widget_qual,/;                value(required, noconcatenate, type=$infile)/  $               disallow XUI and MOTIF  E           2. Set the DCL command table to use the XUI UIL compiler as1              follows:n  L              $ SET COMMAND SYS$SYSROOT:[SYSEXE.DECW$113]DECW$UILCOMPILER.CLD  C              ________________________ Note ________________________a  C              If you want to revert back to the previous UIL commande7              definition, execute the following command:e  ;              $ SET COMMAND SYS$LIBRARY:DECW$UILCOMPILER.CLDs  C              ______________________________________________________   A     4.7 Adding POSIX for OpenVMS Support to DECwindows Transportsh  8     V1.1  Transports specific to DECwindows require code;           modifications to support POSIX for OpenVMS fork()l@           requirements. If you have written a specific transportC           and also plan to implement POSIX for OpenVMS support, you2D           must make changes to your transport source code. This note)           describes the required changes.P       4-12 H  X      I                                                  Programmer Release NotesXI             4.7 Adding POSIX for OpenVMS Support to DECwindows Transports     "         4.7.1 POSIX fork() Routine  F         V1.1  The POSIX fork() routine creates a copy of the currentlyI               executing process, completely cloning P1 and P0 space. Both H               the original process (the parent) and the new process (the@               child) proceed on identical paths from that point.  >               When using the POSIX fork() routine, data is not!               duplicated because:   H               o  Files that are not opened through the POSIX for OpenVMS8                  file system are not known to the child.  H               o  Channels that are not shareable or opened through POSIX8                  for OpenVMS are not known to the child.  H               o  The AST queue of the parent is not copied to the child.  A               Because of these limitations, the POSIX for OpenVMS D               implementation has placed certain demands on protected@               shareable images, including transports specific to               DECwindows:_  E               o  It is the responsibility of each protected shareable <                  image to acknowledge that it can be forked.  E               o  Based on how the child process should function, eachWE                  protected shareable image must handle any cleanup orSG                  duplication of its own data in a routine called a fork                   callback.  G               Specific transports must acknowledge (on the client side)WH               that they can be forked. The SYS$POSIX_FORK_CONTROL systemG               service, described in Section 4.7.2, is provided for thisr               purpose.  D               Specific transports need not perform any cleanup work.  3         4.7.2 SYS$POSIX_FORK_CONTROL System Servicei  F         V1.1  A new SYS$POSIX_FORK_CONTROL system service was added in               VMSaI               Version 5.5 that registers that a protected shareable image H               can be forked. It also registers the address and parameter!               to a fork callback.   D               The execution of the POSIX fork() routine fails if theC               application has been linked with, or has activated, a F               protected shareable image that has not called SYS$POSIX_               FORK_CONTROL.B  I                                                                      4-13     E           Programmer Release NotesA     4.7 Adding POSIX for OpenVMS Support to DECwindows Transports     E           Therefore, in your specific transport's open routine, add aEC           call to the SYS$POSIX_FORK_CONTROL system service similarB           to the following:B  >           $ POSIX_FORK_CONTROL(CNTRL = POSIX$C_SETUP_CALLBACK,B             WHEN = POSIX$M_CALL_IN_CHILD,HANDLER = posix_fork_cb);  A           In this example, the CNTRL parameter indicates that thepB           image is setting up a callback so that it can be forked,B           the WHEN parameter tells when to call the fork callback,A           and the HANDLER parameter gives the address of the forkr           callback.S  B           Other parameters that are not used in this example allowE           for a parameter to be passed to the callback routine and toaD           specify the access mode (maximized to that of the caller).        4.8 Translated Image Support  E           This section discusses restrictions and general information )           about translated-image support.r  6     4.8.1 Running Translated Images on OpenVMS Systems  D   V1.2-3  In versions of OpenVMS Alpha systems prior to Version 1.5,C           translation support was provided to address the followingmC           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 VAX "              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 the (           VAX VMS Version 5.5-2 release.  B           Similarly, translation is supported for images whose useA           of system services and run-time library entry points is D           restricted to those images that existed on the VAX Version!           5.5-2 operating system.m       4-14 s         I                                                  Programmer Release NotessI                                              4.8 Translated Image Supporta    C               If you have installed layered products on your system G               since the VAX Version 5.5-2 release, you may need to make C               additional changes if you rebuild an image to support B               translation. For instance, for applications that areF               included with DECwindows Motif Version 1.2-3 for OpenVMSD               VAX software, you must build images with the OSF MotifB               Release 1.1.3 library or the DECwindows XUI library,B               instead of with the OSF Motif Release 1.2.3 library.  D               The DECwindows Motif Version 1.2-3 for OpenVMS releaseE               includes the same translated-image support file that isRH               provided with the DECwindows Motif Version 1.2 for OpenVMS               Alpha release.  E               DECwindows Motif Version 1.2 for OpenVMS Alpha includes F               support for DECwindows Motif Version 1.1 for OpenVMS VAX0               images on an OpenVMS Alpha system.  H         V1.2  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 Alphae               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 Version D               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 applicationeI               against the OSF/Motif Release 1.1.3 programming environmentfF               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 whensE               you upgrade to DECwindows Motif Version 1.2 for OpenVMS H               VAX.) VAX images built against the OSF/Motif Release 1.1.3G               programming environment can be copied to an OpenVMS Alphao<               system, translated, and executed successfully.    I                                                                      4-15  2  o           Programmer Release Notes      4.8 Translated Image Support    =           You can install translated-image support during the E           DECwindows Motif installation procedure. See the DECwindows @           Motif Version 1.2-3 for OpenVMS Installation Guide for           instructions.h  D           The OSF/Motif Release 1.1.3 shareable images that are usedD           with translated images are different from and incompatible@           with the shareable images used for native images. As a9           result, the following image restrictions apply:   B           o  Do not use both native and translated images that use4              DECwindows Motif software in a process.  =              Either port or translate all the images that usewD              DECwindows Motif software and all images that call each              other.   E           o  Translated images that dynamically activate a DECwindowsC;              Motif image using LIB$FIND_IMAGE_SYMBOL from aa0              translated image are not supported.  ?           For more information on translated-image support, see C           the DECmigrate for OpenVMS AXP Systems Translating Imagesl           guide.  0     4.8.2 DECwindows Motif Toolkit Functionality       V1.1  <           On OpenVMS Alpha systems, DECwindows Motif ToolkitD           functionality is available with the following restriction:B           for the DECwindows Motif product, C modules are compiledE           using the default MEMBER_ALIGNMENT switch in the C compiler D           to maximize performance. It is recommended that you do not9           use the NOMEMBER_ALIGNMENT compile-time switch.   E           If you intend to port a toolkit application that is writtensC           in C, see the VAX C Run-Time Library release notes in the.6           OpenVMS Alpha AXP Version 1.0 Release Notes.       4.9 Cross-Development Tools   E     V1.2  The OpenVMS Alpha Migration Toolkit runs on the OpenVMS VAX E           operating system and supports development for OpenVMS AlphaoE           operating systems. To develop DECwindows Motif applicationsrD           in a multiplatform environment, you need the OpenVMS AlphaD           Migration Toolkit and the DECwindows Motif Version 1.2 for       4-16    1      I                                                  Programmer Release NotesoI                                               4.9 Cross-Development Tools     F               OpenVMS Alpha software. DECwindows Motif Version 1.2 forI               OpenVMS is not part of the OpenVMS Alpha Migration Toolkit.l  C               The following steps explain how to extract DECwindowsnD               Motif files from the save sets on the DECwindows MotifG               Version 1.2 for OpenVMS Alpha kit for use in a multitools                environment.  F                 ________________________ Note ________________________  @                 Because of OSF requirements, you must purchase a>                 DECwindows Motif Version 1.2 license to unpack@                 the DECwindows Motif save sets for multiplatform                 development.F                 ______________________________________________________  D               During the VMSINSTAL installation of the OpenVMS AlphaB               Migration Toolkit, the logical name ALPHA$LIBRARY isF               created. This logical name is used as the destination ofC               the files in the OpenVMS BACKUP commands that follow.e  ?               Unpack DECwindows Motif Version 1.2-3 for OpenVMSgD               Alpha save sets for multiplatform development into the?               ALPHA$LIBRARY directory using the BACKUP command.r  F               o  Use the following commands to unpack the B and C save2                  sets, which contain all bindings:  O                $ BACKUP DWMOTIF_AXP012.B/SAVE/SELECT=[SYSLIB]*.* ALPHA$LIBRARY:eO                $ BACKUP DWMOTIF_AXP012.C/SAVE/SELECT=[SYSLIB]*.* ALPHA$LIBRARY:   G               o  Use the BACKUP command to unpack the language bindingsS.                  from the following save sets:  &                  -  E (MIT C bindings)  (                  -  J (Fortran bindings)  '                  -  L (Pascal bindings)o                    For example:o  >                  $ BACKUP DWMOTIF_AXP012.E/SAVE ALPHA$LIBRARY:>                  $ BACKUP DWMOTIF_AXP012.J/SAVE ALPHA$LIBRARY:>                  $ BACKUP DWMOTIF_AXP012.L/SAVE ALPHA$LIBRARY:  D               o  Use the BACKUP command to unpack the files from the$                  following save set:  0                  -  Q (Translated image support)  I                                                                      4-17I _  E           Programmer Release Notes     4.9 Cross-Development Tools"                  For example:X  O             $ BACKUP DWMOTIF_AXP012.Q/SAVE/SELECT=[SYSLIB]*.IIF  ALPHA$LIBRARY:C  C              Note that you only need the .IIF files from the Q saver              set.   >           The OpenVMS Alpha Migration Toolkit Reference ManualA           provides programming reference information on the toolst:           included in the OpenVMS Alpha Migration Toolkit.  ,     4.10 Compiling Applications Written in C  B     V1.0  During the VAX C layered-product installation procedure,@           you have the option of extracting the VAX C definition>           files (.h files) or leaving the .h files in the textC           library. If you extract the definition files, you can user7           #include control lines of the following form:i             #include <filename.h>o  >           The DECwindows header files assume that the .h files?           were extracted. They contain #include <module_name.h> E           notation for the included files. The DECwindows programmingP3           documentation also makes this assumption.n  C           VAX C should, therefore, be installed using the option to &           extract the library modules.  E           If you have already installed VAX C and you did not extract E           the .h files, the DECwindows sample C programs do not work.sE           To correct this problem, reinstall VAX C and extract the .he           files.  B           With DEC C, the header files do not need to be extractedC           from the text library if you define the DECC$TEXT_LIBRARYf"           logical name as follows:  @           $ DEFINE DECC$TEXT_LIBRARY SYS$LIBRARY:DECC$RTLDEF.TLB  2     4.11 Compiling Applications Written in Fortran       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 definitionsmE           that cause memory layout changes, depending on the compiler            switches used.       4-18 d  c      I                                                  Programmer Release Notes I                            4.11 Compiling Applications Written in Fortran     .               You can do one of the following:  F               o  Use the CDEC$ OPTIONS in the source code so that yourD                  Fortran programs work correctly with the DECwindows*                  Motif run-time libraries:  E                  -  Before you include DECwindows Motif files in yourl9                     program, add the following statement:   8                     CDEC$ OPTIONS /ALIGN=RECORDS=NATURAL  F                  -  Following the INCLUDE statement, add the following                     statement:  %                     CDEC$ END OPTIONS                         For example:  8                     CDEC$ OPTIONS /ALIGN=RECORDS=NATURAL,                     INCLUDE "DECW$MOTIF.FOR"%                     CDEC$ END OPTIONSi  I               o  Use the Fortran compiler switch, /ALIGN=RECORDS=NATURAL,a0                  when you compile your programs.           4.12 CDA Application  I               This section contains programming information about the CDA                application.  9         4.12.1 CDA-Implementing the Drag-and-Drop Featuree  D         V1.2  The drag-and-drop feature, which lets you move or copyH               information between widgets, is implemented in the widgets"               listed in Table 4-4.  -               Table 4-4 Drag-and-Drop Widgets I               ___________________________________________________________   @               Widget            Drag Operation    Drop OperationI               ___________________________________________________________f  ?               XmText            copy and move     copy and movei  ?               XmTextField       copy and move     copy and movee  $               XmLabel           copy  $               XmPushButton      copy  $               XmToggleButton    copy   $               XmList            copy  I                                                                      4-19t E  n           Programmer Release Notes     4.12 CDA Application      C           For information about how to include additional drag-and- B           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.  )     4.12.2 CDA Run-Time Services FeaturesX  A     V1.2  This section describes new programming features in this E           version of the CDA Run-Time Services. See Chapter 2 for new            user features.       4.12.2.1 Version Number   =    V1.2-3 DECwindows Motif Version 1.2-3 for OpenVMS softwareuC           incorporates additional problem resolutions that were not @           provided in the general release of the CDA Version 1.8           product.  B           CDA Version 1.6 was part of the DECwindows Motif Version?           1.1 release. DECwindows Motif Version 1.2 for OpenVMS B           software provides the CDA Run-Time Services component ofE           CDA Version 1.8; DECwindows Motif Version 1.2-3 for OpenVMSr$           incorporates Version 1.8A.  9     4.12.2.2 Changes to the Programming Interface for CDA   ?     V1.2  This section describes the changes to the programming >           interface for this version of CDA Run-Time Services.  E           This version provides a new set of header files that define B           CDA constants, types, and routines using portable namingE           conventions. By using these new naming conventions, you canTC           use a wider variety of C compilers to minimize the amount ;           of system-specific code in your CDA applications.   B           The names of the new set of header files are the same as?           the names of the previous set of header files, except B           that the dollar sign ($)  has been removed. For example,B           the cda$msg.h include file is now called cdamsg.h. Other?           examples include the following: The DDIF$K_DSC_MAJOR_gE           VERSION symbol is now declared as DDIF_K_DSC_MAJOR_VERSION,        4-20 h  x      I                                                  Programmer Release NoteseI                                                      4.12 CDA Applicationg    E               and the CDA$_NORMAL status value is now defined as CDA_                NORMAL.   G               The previous set of header files is also included in thisaI               version, but these files will no longer be updated. Changes F               introduced since the release of DECwindows Motif VersionG               1.1 (for example, the new definitions for audio support),BG               are available only in the new set of header files. To usePH               the new CDA features, change the file names in your source               code.   B               The new set of header files supplements the previousF               set of header files. If you want to write ANSI-compliantG               applications using CDA definitions and CDA Toolkit calls, H               use the new set of header files. However, you can continueH               to use the header files that define symbols containing theH               dollar sign ($) provided you choose a non-ANSI compilation               mode.e  @               By using the previous set of header files, you canC               successfully build existing source code that uses thea*               previous naming conventions.  @               See Table 4-5 for a list of new header file names.  -               Table 4-5 New Header File Namess<               ______________________________________________  '               Previous Name    New Name <               ______________________________________________  '               cda$def.h        cdadef.hm  '               cda$msg.h        cdamsg.h   (               ddif$def.h       ddifdef.h  (               dtif$def.h       dtifdef.h  '               cda$ptp.h        cdaptp.hr  '               cda$typ.h        cdatyp.hh  '               dvr$msg.h        dvrmsg.hr  )               dvr$cc_def.h     dvrccdef.hs  )               dvr$cc_ptp.h     dvrccptp.ha  (               dvr$decw_def.h   dvrwdef.h  (               dvr$decw_ptp.h   dvrwptp.h  I                                                                      4-21                 Programmer Release Notes     4.12 CDA Application    5     4.12.2.3 Changes to External Reference Processingv  E     V1.2  CDA Run-Time Services supports relative file specifications ?           for external references. Relative references are also B           supported: that is, a reference where the directory pathA           is not fully specified but is relative to the directory &           path of the parent document.  -     4.12.2.4 Message for Style Guide Fallbacke  E     V1.2  The following message is displayed when a local style guide.           cannot be found:  B       STYGDEFBK, Fallback to nonlocale-specific style guide: file-
          spec             Level: Informationalf  E          Explanation: Since the locale-specific style guide cannot berD          found, the nonlocale-specific version of the style guide is          used.  6     4.12.2.5 Using Logical Names with CONVERT Commands  A     V1.2  During a document conversion, if a logical name is used B           to specify the directory of the primary document and theA           document file extension is omitted, external referencese=           that contain relative file specifications cause theo           conversion to fail.S  E           This failure occurs because the back-end converter examines1B           the converter processing options, although the front-end?           converter opens the input file. Because the convertereA           software cannot predict what default file extension the2C           front-end converter might apply, it uses the OpenVMS filerE           services to resolve the logical name and to find the actualnD           file specification so that the directory can be parsed and1           extended with a relative specification.n  D           The conversion fails only when the external reference uses)           a format such as the following:              sys$login:mydoc   ?           In this case, the reference will not be resolved. Thei@           reference is resolved in all other cases. For example:             sys$login:mydoc.doc            disk$:[smith]mydoc            disk$:[smith]mydoc.doc       4-22 u  n      I                                                  Programmer Release Notes I                                                      4.12 CDA Applicatione    /         4.12.2.6 Restructuring Shareable Images   C         V1.2  The CDA Viewer includes two shareable images to allowoH               installation on systems where DECwindows is not installed.  C               In DECwindows Motif Version 1.2 for OpenVMS software,tC               shareable images that use the X services are renamed. A               Table 4-6 lists the shareable images in the various1)               versions of the CDA Viewer.   1               Table 4-6 Names of Shareable Images I               ___________________________________________________________e                 CDA 6               Version     Image Name       DescriptionI               ___________________________________________________________   @               Version     CDA$ACCESS       CDA Run-Time Services;               1.6                          shareable image.t  B                           DDIF$VIEWSHR     Callable viewer widget.  @               Version     CDA$ACCESS       CDA Run-Time Services;               1.7                          shareable image.   G                           DDIF$VIEWSHR     The DDIF$DECW_VIEWSHR widget F                           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_VIEWSHR E                                            (character-cell interface) 3                                            widgets.   @               Version     CDA$ACCESS       CDA Run-Time Services;               1.8                          shareable image.i               VersionL               1.8A  G                           DDIF$VIEWSHR12   The DDIF$VIEWSHR12 widget is H                                            a callable viewer widget thatH                                            uses LIB$FIND_IMAGE_SYMBOL toI                                            invoke the DDIF$DECW_VIEWSHR12EE                                            (DECwindows interface) andoF                                            DDIF$CC_VIEWSHR (character-C                                            cell interface) widgets.   I               By using the LIB$FIND_IMAGE_SYMBOL routine to reference the I               entry points to the DDIF$DECW_VIEWSHR, DDIF$DECW_VIEWSHR12, H               and DDIF$CC_VIEWSHR images, an application can dynamically  I                                                                      4-23p M  l           Programmer Release Notes     4.12 CDA Application    B           determine whether it can execute in a given environment.B           The DDIF$VIEW.EXE application now replaces this routine.  @           The previous DDIF$VIEWSHR.EXE shareable image is still>           included to maintain compatibility with applicationsD           linked against it. However, new applications (and previousB           applications that take advantage of new features) should'           use the new shareable images.e       4.13 DECterm Programming  9           This section contains information about DECterm            programming.  )     4.13.1 Page-Movement Escape Sequences2  :     V1.2  The following page-movement escape sequences are!           implemented in DECterm:   1               NP       <CSI> Pn U       Next Pagen5               PP       <CSI> Pn V       Previous PageE>               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.   C              ________________________ Note ________________________   A              DECterm does not support cursor coupling; the cursor_=              is always bound to the current (displayed) page.i  C              ______________________________________________________l       4.13.2 DECCRA Sequence  =     V1.2  DECterm supports the DECCRA (Copy Rectangular Area)o@           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 copyn/           from one off-screen page to another).n           4-24 d         I                                                  Programmer Release Notes I                                                  4.13 DECterm ProgrammingI             4.13.3 DECLFKC SequenceP  F         V1.2  Since DECterm does not have a user interface to redefineA               the F5 (Break) key, the DECLFKC (Local Function KeyuH               Control) sequence redefines the F5 key when "0" (all keys)<               is used to select which key is to be modified.  "         4.13.4 ReGIS Input Cursors  G        V1.2-3 DECterm supports the following input cursors: cross-hair, F               rubber-band line, diamond, and rubber-band rectangle. ToF               select input cursors use the S(C(In)) command. Table 4-7$               shows the values of n.  D               Table 4-7 ReGIS Input Cursors-Cursor styles and ValuesD               ______________________________________________________  .               Cursor Style          Variable nD               ______________________________________________________  +               Cross-hair            Omittedm  %               Cross-hair (default)  0X  %               Diamond               1/  %               Cross-hair            2C  %               Rubber-band line      3t  %               Rubber-band           4                rectangle   F                 ________________________ Note ________________________  C                 If a shape other than the diamond cursor is desiredp=                 when n is equal to 1, define the logical namenB                 DECW$DECTERM_REGIS_CURSOR to be one of the numbers>                 defined in the SYS$LIBRARY:DECW$CURSOR.H file.  F                 ______________________________________________________  )         4.14 DECwindows OSF/Motif Toolkith  <               This section contains information about notes,H               restrictions, and corrections for the DECwindows OSF/Motif               Toolkit.  I                                                                      4-25d m  l           Programmer Release Notes%     4.14 DECwindows OSF/Motif Toolkita    C     4.14.1 Compilation Error When Including Both CURSES.H and XMP.H             Files  E     V1.2  When compiling a C program that includes the files curses.hoE           and XmP.h, or any Motif header file that causes XmP.h to be D           included, such as LabelP.h, a compilation error similar to)           the following may be generated:e             Boolean move;aF           %CC-E-MACREQARGS, Macro reference requires an argument list;!           "move" not substituted. A           At line number 407 in SYS$COMMON:[DECW$INCLUDE]XMP.H;1.   E           This error occurs as a result of the file curses.h definingLC           a macro named "move", which conflicts with a member fieldFC           in an OSF/Motif Release 1.2.2 structure for drag-and-drop            support.  <           This error can be prevented by placing the include;           statement for the file curses.h after the include ;           statements for any DECwindows Motif header files.e  )     4.14.2 Motif Text Widget Translationse  @     V1.0  To implement Digital virtual bindings, it is necessaryB           for Digital to modify the default XmText and XmTextFieldA           translation manager syntax. Specifically, the following !           syntax line is removed:   B           Shift ~Ctrl ~Meta ~Alt <Key>osfDelete:   cut-clipboard()  A           If you use virtual bindings in which the osfCut virtual :           keysym is not bound, no key sequence is bound to=           the cut-clipboard action by default. To work around >           this limitation, override the XmText and XmTextField7           translations in your DECW$XDEFAULTS.DAT file.        4.14.3 Upward Compatibilityt  =     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 imageoA           activation is that the semantics of the Intrinsics havesD           changed in places between the X Toolkit Intrinsics Release=           3 to the MIT X11 Release 4 Intrinsics. A previouslyo       4-26           I                                                  Programmer Release NotesoI                                         4.14 DECwindows OSF/Motif Toolkitd    A               linked XUI application calls through entries in the C               XUI transfer vector that use the X Toolkit Intrinsics E               Release 3 semantics of the Intrinsics. However, as soon C               as that application relinks (or dynamically activatesfC               DECW$DWTLIBSHR), it uses the MIT X Toolkit Intrinsics 4               Release 4 semantics of the Intrinsics.  C               Applications that dynamically activate DECW$DWTLIBSHRmH               should be changed to link directly against DECW$DWTLIBSHR.H               DECW$DWTLIBSHR is now a small, thin-layer, shareable imageF               that dynamically activates automatically the majority ofF               the toolkit code only when necessary. There is no reasonB               for applications to continue to dynamically activate               DECW$DWTLIBSHR.   A               In addition, Digital cannot guarantee binary upwardo?               compatibility in the future for applications that @               dynamically activate the toolkit shareable images.@               DECwindows toolkits (XUI and Motif) are based uponI               standards that Digital does not control. When the standardsuB               make an incompatible change, Digital will change theF               toolkit to follow it. However, the intent is to add codeF               that allows existing executable images to run unchanged.  =         4.14.3.1 Restrictions on Mixing Motif and XUI Widgetse  E         V1.0  Mixing Motif and XUI widgets is restricted. The problem.F               results from the fact that both XUI and Motif have theirA               own Vendor Shell widget class. If an application isDD               linked against XUI and not Motif, the XUI Vendor ShellE               widget class is used in order to maintain compatibility F               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 (usingiG               LIB$FIND_IMAGE_SYMBOL) a shareable image that uses Motif.pH               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 logicalDE               name contains a comma-separated list of image names forCE               which the toolkit is to use the Motif Vendor Shell. The H               value of DECW$USE_XM_VENDOR_SHELL logical name defaults to  I                                                                      4-27D N  A           Programmer Release Notes%     4.14 DECwindows OSF/Motif Toolkit     C           NOTES$MAIN. To add additional image names to this logical $           name, enter the following:  9           $ DEFINE DECW$USE_XM_VENDOR_SHELL "NOTES$MAIN,-e'           _$ yourimage1,yourimage2,..."   <           Note that DECW$USE_XM_VENDOR_SHELL does not affectB           applications that use Motif since they are already using!           the Motif Vendor Shell.D  ?     4.14.4 Compile-Time Incompatibilities in Motif Header Filese  E    V1.2-3 Several macro definitions are removed from the Motif header A           files in the OSF/Motif programming support. The changesa,           affect the following header files:             o  DECW$INCLUDE:XMP.H   3              The following definitions are removed:   5              -  #define XmLONGBITS sizeof(Cardinal)*8d  5              -  #define XmHALFLONGBITS (XmLONGBITS/2)$  C              These macros are replaced in the same header file with !              the following macro:e                -  XmOFFSETBITS  <              Update the code to call the XmOFFSETBITS macro.  !           o  DECW$INCLUDE:TEXTP.Hn  3              The following definitions are removed:   )              -  #define MAXINT 2147483647 9                 /* Biggest number that can fit in long */_  &              -  #define NODELTA MAXINT  D              The definition of MAXINT is operating-system dependent.B              Include this definition in applications in one of the              following ways:  :              -  Include the appropriate system-header file  #              -  Define the constant        4-28 t         I                                                  Programmer Release Notes$I                                           4.15 OSF/Motif Example Programs     '         4.15 OSF/Motif Example Programs   C               This section describes example programs from the Opend?               Softare Foundation (OSF) that are included in the @               DECwindows Motif Version 1.2 for OpenVMS software.  ,         4.15.1 Cut and Paste Example Program  G         V1.2  This example demonstrates the use of the Motif Clipboard.pD               You can cut and paste application-defined data formats(               using the XmClipboard API.  G               Run two cut/paste clients and transfer graph values usingf-               the pull-down and pop-up menus.   &         4.15.2 DNDDemo Example Program  I         V1.2  This example illustrates a typical use of the drag-and-drope               feature.  F               When the example starts, it does not have any valid dropG               sites. It starts with different color rectangles that actLH               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).s  I               o  Press MB1 and drag. You see the "rubber-banding" effect.l  ?               o  Release MB1 after dragging a desired distance.o  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 and G               dragging over to one of the rectangles inside the drawinga%               area and releasing MB2.e  C               To initiate a drag, move the pointer over to the dragV@               source, press BTransfer (which is MB2 by default),D               and start to drag. Notice that the cursor changes to aH               painter's palette in the same color as the color rectangle/               from which the drag is initiated.   ;               While you are dragging, notice the following:   B               o  When dragging over the root window, the drag icon8                  consists of only the painter's palette.  I                                                                      4-29i :  i           Programmer Release Notes#     4.15 OSF/Motif Example Programs     E           o  When dragging over parts of the drawing area where there B              are no rectangles, the drag icon changes to include aB              "DO NOT ENTER!" sign on top of the painter's palette.  @           o  When dragging over any of the rectangles inside theD              drawing area, the "DO NOT ENTER!" sign is replaced with              a painter's brush.   A           To perform a drop, release MB2. If you release MB2 witha?           the pointer over any part of the drawing area outside @           of the rectangles, or anywhere on the root window, the>           drag icon snaps back to the point of drag initiationA           and disappears. This is an indication that the drop you_D           attempted failed. If you release MB2 with the pointer overA           any of the rectangles inside the drawing area, the drag_B           icon disappears into the background; this indicates thatA           the drop was a success. The rectangle on which the drop B           was attempted, becomes filled in with the color that was           dragged.  E           The rectangles inside the drawing area act as drag sources. B           Initiate the drag with the pointer on any rectangle, and?           the cursor changes to a rectangle (either of the samee?           size or a smaller size depending on the X cursor sizeeB           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 time A           you attempt the drop (Ctrl is the modifier key for copy C           in the current implementation). When you drag a rectangleEE           with no modifier key pressed or with the Shift key pressed, B           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 untile@           you press the Ctrl key, which changes the operation to@           Copy. At that time it regains its original solid form.  C              ________________________ Note ________________________E  @              During dragging you can cancel the drag by pressingC              the Cancel key (F11). Also, you can press the Help key C              to get information about whether the drop will succeedM*              and possible drop operations.  C              ______________________________________________________        4-30    F      I                                                  Programmer Release Notes I                                           4.15 OSF/Motif Example Programsr        #         4.15.3 Dogs Example Program   H         V1.1  This example uses the dog and square widgets. It shows howI               to incorporate new widgets into the UIL source by using the $               user-defined function.  ?               The dogs example program allows you to change thelF               DogNwagTime and SquareNmakeSquare resources dynamically.  F               If you have a system with sound generation features, youG               might want to change the bark callback to something otherg               than XBell().n           4.15.3.1 Dog Widget   H         V1.1  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, youaI               must subclassify it, or replace up.bm, down.bm, and bark.bmr)               with more advanced bitmaps.   9               The dog widget has the following resources:   C               o  DogNwagTime: Time in milliseconds between each wag   G               o  DogNbarkTime: Time in milliseconds the bark graphic is                   displayed  E               o  DogNbarkCallback: Callback called by the bark action   <               The dog widget has the following translations:  4               o  osfActivate/Return/Space/MB1 = Bark  !               o  W/MB2 = Wag tailt  0               o  S/Shift-MB2 = Stop wagging tail                 o  osfHelp = Help   I                                                                      4-314 d              Programmer Release Notes#     4.15 OSF/Motif Example Programss         4.15.3.2 Square Widget  ;     V1.1  The square widget (SquareWidget) demonstrates how 9           to subclassify a constraint widget that remainso:           binary compatible with future versions of Motif.;           It uses XmResolveAllPartOffsets()  and associated >           macros and implements all the recommendations in the*           XmResolveAllPartOffsets manpage.  =           The square Widget is a subclass of XmBulletinBoard..@           It forces its children to be square using a constraint           resource.n  C           The square widget has the resource SquareNmajorDimension.p>           This resource determines which dimension is used for>           the new size of the child. Values are SquareWIDTH or           SquareHEIGHT.u  7           The square widget has the constraint resource_A           SquareNmakeSquare. This resource determines whether the E           child is forced to be square or set to its preferred shape.   #     4.15.4 Helloint Example Programm  D     V1.2  This example is a simple UIL/Xm program with a label and a           push button.  D           With this version, you can choose a Kanji, Hebrew, French,+           or English interface at run time.   <           The program uses the file LOCALSTRINGS.UID for all<           language-specific interfaces. To change languages,@           copy one of the LOCALSTRINGS_*.UID files to DECW$USER_?           DEFAULTS:LOCALSTRINGS.UID. Then, use the logical nameCA           LANG or the xnlLanguage resource to set the locale. Set C           the LOCALSTRINGS suffix and the locale name to one of the_           following:  E           ___________________________________________________________   $           Locale      Interface TypeE           ___________________________________________________________E             Japan       Kanji              Hebrew      Hebrew             French      French  &           English     Standard English  D           To define the xnlLanguage resource, add the following line*           to your DECW$XDEFAULTS.DAT file:       4-32 n  M      I                                                  Programmer Release NotesfI                                           4.15 OSF/Motif Example Programsm    !               *xnlLanguage:locale   E               The following fonts are needed for the helloint exampleg               program:  L       ______________________________________________________________________         Locale    Font NamesL       ______________________________________________________________________  L       French    -adobe-helvetica-medium-r-normal-12-120-75-75-p-67-iso8859-1   J       English   -adobe-times-medium-r-normal-14-100-100-100-p-74-iso8859-1  G       Hebrew    -Misc-Fixed-Medium-R-Normal-13-120-75-75-C-80-ISO8859-8.  "       Japan     -*-JISX0208.1983-1  "                 -*-JISX0201.1976-0  F               If you do not have these fonts installed on your system,E               either change the UIL files to reference other fonts orTH               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.w  )         4.15.5 Hellomotif Example Program   H         V1.2  This example is a simple UIL/Xm program with a label and a               push button.  (         4.15.6 Motifanim Example Program  H         V1.1  The motifanim program demonstrates the following OSF/Motif               features:k  E               o  Declaration of icon/bitmap using UIL for portability                   across visualsC  >               o  Exchange of value between UIL and C using Mrm  -               o  Use of the Motif form widgetS  I               o  Background procedure running while the client process is :                  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 read 1               at startup from existing UID files.g  I                                                                      4-33     n           Programmer Release Notes#     4.15 OSF/Motif Example Programse    A           The syntax of all the animation.uid files can add a new B           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:   %           $ SET DEFAULT DECW$EXAMPLESs3           $ motifanim := "$DECW$EXAMPLES:motifanim"t!           $ motifanim -anim planee  E           The files motiflogo.uil, motifanim.uil, and motifanim.c are -           the core components of the program.s  -     4.15.7 Motifgif and Pict Viewing Programsl  0     V1.2  The following .gif files are provided:  ?           o  TOUCAN.GIF, which is a picture of a tropical bird.W  D           o  CHALLENGER.GIF, which is a picture of the space shuttle              Challenger.  A     V1.1  The motifgif and pict programs work together to displaynA           a .gif formatted picture. The motifgif program displaysoC           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  motifgifa  B              The source and executable code in this directory is aA              Motif program driving the display of a .gif picture.t             o  pictt  B              The program called by motifgif that displays a bitmapE              of a .gif picture file. This program used to be xgif bute/              has since been converted to Motif.   5           The following problems exist with motifgif:.  .           o  Resizing a picture does not work.  C           o  The -d option is not used when calling pict, so remoteb@              displays must set the DISPLAY environment variable.       4-34  I                                                  Programmer Release Notes I                                           4.15 OSF/Motif Example Programsg  )         4.15.8 Motifshell Example Programb  D         V1.2  The motifshell program is an example of an environmentC               created using Motif. The purpose of the example is tosD               show how Motif may be used as a standalone environment;               for dispatching other programs and utilities.S  G               The motifshell program is written in C code. There are noc               UIL references.   F                 ________________________ Note ________________________  F                 Displaying a file listing or process status takes someE                 time. These operations are accomplished by spawning a E                 DCL command, capturing the output in a file, and then !                 reading the file.a  ?                 The default font is proportionally spaced. SomeLC                 listings are more readable if a fixed space font isaF                 used, such as Courier. Use the Font option to select a                 different font. F                 ______________________________________________________  '         4.15.9 Periodic Example Program   H         V1.2  The periodic example is a demonstration of the displayableG               widgets in Motif. The program displays Motif widgets in ad$               periodic chart format.  (         4.15.10 Textedit Example Program  F         V1.2  The textedit program is a primitive text editor based onE               the Motif XmText widget that makes use of its XmNsourceEE               resource to allow multiple views of the same underlyinge               text.   I                                                                      4-35M f           Programmer Release Notes#     4.15 OSF/Motif Example Programse8               Table 4-8 describes the View menu options.  )               Table 4-8 View Menu OptionseF               ________________________________________________________  &               Option       DescriptionF               ________________________________________________________  F               Split Pane   Adds a new independently scrollable view of$                            the text.  5               Remove Pane  Removes a designated pane.   H               One Pane     Removes all panes except the designated pane.    A           The designated pane is determined in the following way:g  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 viewT,              with which the user interacted.  =           The designated pane is also the one whose clipboardiB           contents are pasted when Paste is selected from the Edit           Menu.   E           The textedit sources are separated into independent layers. A           Textedit contains the source files listed in Table 4-9.            4-36  I                                                  Programmer Release NotesaI                                           4.15 OSF/Motif Example Programs %       Table 4-9 TextediT Source FilesmA       ___________________________________________________________n  
       File       Name     DescriptionA       ___________________________________________________________s  C       tfile.c      The code to read, write, and remove files. HidesfC                    any operating system or filesystem dependencies.o  E       app.c        Uses tfile.c to provide all the code to manipulate D                    files and their related buffers. This is toolkit-                    dependent.o  ;       tk.c         Isolates dependencies on the Xm Toolkit.   >                    The first half of the file provides utility:                    routines and a toolkit-independent (butC                    application-specific) interface that can be usedrA                    by the toolkit-independent dialog layer of the                     application.r  >                    The second half of the file defines all the@                    callback routines. Many of these update stateD                    internal to this layer; others perform additionalB                    actions. Those actions unambiguously correspondE                    to toolkit-specific action routines defined in theeB                    first half of the file. Otherwise, an upcall isB                    made to the toolkit-independent dialog layer to%                    decide what to do.d  E       dlg.c        Uses tk.c to manage dialog with the user. The codee*                    is toolkit-independent.  ?       textedit. C  Initializes the application and instantiatesw@                    widget hierarchies. The code hides the use of@                    UIL and Mrm from the rest of the application.    F                 ________________________ Note ________________________  :                 Moving and removing files is not currently                 implemented.F                 ______________________________________________________  )         4.15.10.1 Additional Translations   E         V1.2  Users familiar with emacs may want to add the followingn=               translations to their DECW$XDEFAULTS.DAT files:e          I                                                                      4-374 i  :           Programmer Release Notes#     4.15 OSF/Motif Example Programsr    N        *XmText.translations:     Mod1<Btn3Down>: scroll-cursor-vertically()\n\8          Mod1<Btn3Motion>: scroll-cursor-vertically()\n\)        Ctrl<key>a: beginning-of-line()\n\n*        Ctrl<key>b: backward-character()\n\-        Ctrl<key>d: delete-next-character()\n\i#        Ctrl<key>e: end-of-line()\n\e)        Ctrl<key>f: forward-character()\n\         Ctrl<key>g: beep()\n\1        Ctrl<key>h: delete-previous-character()\n\r#        Ctrl<key>i: cut-primary()\n\e*        Ctrl<key>j: newline-and-indent()\n\M        Ctrl<key>k: set-anchor() end-of-line() key-select() cut-clipboard()\n\r&        Ctrl<key>l: redraw-display()\n\        Ctrl<key>m: newline()\n\a!        Ctrl<key>n: next-line()\n\d*        Ctrl<key>o: newline-and-backup()\n\%        Ctrl<key>p: previous-line()\n\ !        Ctrl<key>v: next-page()\n\t%        Ctrl<key>w: cut-clipboard()\n\c'        Ctrl<key>y: paste-clipboard()\n\n*        Ctrl<key>z: scroll-one-line-up()\n\%        Mod1<key>b: backward-word()\n\ (        Mod1<key>d: delete-next-word()\n\$        Mod1<key>f: forward-word()\n\,        Mod1<key>h: delete-previous-word()\n\$        Mod1<key>i: copy-primary()\n\-        Mod1<key>k: delete-to-end-of-line()\n\ %        Mod1<key>v: previous-page()\n\a&        Mod1<key>w: copy-clipboard()\n\,        Mod1<key>z: scroll-one-line-down()\n\/        Mod1 Shift<key>greater: end-of-file()\n\g,        Mod1<key>less: beginning-of-file()\n\)        Mod1<key>]: forward-paragraph()\n\a'        Mod1<key>[: backward-paragraph()l        4.15.11 View Example Program  B     V1.2  The view program is similar to the DCL command TYPE/PAGEB           using Motif with internationalization support. It allows1           you to view files in several languages.k               4-38    t      I                                                  Programmer Release NotesrI                                           4.15 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:t  .               $ SET DEFAULT DECW$USER_DEFAULTS0               $ @DECW$EXAMPLES:FILEVIEW language  E               This command file copies the .UID and .DAT files to thebC               current directory. It sets the appropriate locale ande8               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 work -               area of which is a PanedWindow.r  5               The menu bar has the following entries:   I               o  File-opening and closing files, creating new shells, and                   exiting  >               o  View-controlling the panes in the pane window                 File Menu   ;               The file menu contains the following options:                  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.                  o  Open New Shelld  H                  Creates a secondary shell similar to the primary shell.A                  Files can be viewed in each shell independently.t                 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 closesy(                  the file and the shell.  I                                                                      4-39     i           Programmer Release Notes#     4.15 OSF/Motif Example Programsi               View Menu   7           The view menu contains the following options:              o  New Paneb  4              Creates a new pane in the paned window.             o  Delete Pane  &              Deletes the current pane.             o  Searcho  @              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 innC              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 toF?           end abruptly. The View options do not work correctly.1  #     4.15.12 Xmpiano Example Programm  B     V1.2  The xmpiano program shows how to write a Motif InterfaceC           to Dumb Instruments (MIDI) application. Both a staff, for 3           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 buttonsdC           changes the active note accordingly. The selected note isr1           also displayed as the new mouse cursor.r  A           Though the note selection is limited, it is possible tonD           play sharps as well as naturals. The program interface hasA           not been written to play flats. The staff automatically B           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:             o  Add Voice  E              Connects another display to a new staff. After selectingH>              this command, you are prompted for the display toA              connect. Any music written in the new staff plays to D              this display. Note that pressing the right mouse buttonB              on the new staff shows the name of the display in the       4-40 .  .      I                                                  Programmer Release NoteshI                                           4.15 OSF/Motif Example Programse    G                  menu title. In addition, the menu commands in the menu_A                  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 this D                  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 Voiceo  F                  Plays the voice of the staff in which the right mouseI                  was pressed. If the voice is the same as the local host,nF                  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 mustuI                  be compiled with the -DCHORDS option. Note that this candI                  slow down the application significantly on many servers.e                 o  Play All8  A                  Plays all voices at the same time on each of the $                  specified displays.                 o  Save Voices  ;                  Saves the corresponding voice to a file. AeH                  FileSelectionDialog is displayed to prompt for the nameD                  of the file in which to save the voice. The display5                  connection information is not saved.                  o  Load Voicen  @                  Loads (appends) a previously saved voice to the%                  corresponding staff.r                 o  Quit   +                  Exits the example program.t  D               This version does not allow editing of notes. To edit,F               clear the staff and start again, or read the data from a               saved file.   I                                                                      4-41  E  a           Programmer Release Notes#     4.15 OSF/Motif Example Programso    D           To set the color of the notes, change the foreground colorC           of the application. To do this, use the -fg option on thec$           command line. For example:  .           $ xmpiano :== $DECW$EXAMPLES:xmpiano           $ xmpiano -fg blue  !     4.15.13 Motif Sample Programsa  @     V1.2  Table 4-10 lists sample programs showing various Motif            Toolkit functionality.  *           Table 4-10 Motif Sample ProgramsE           ___________________________________________________________   #           File Name     DescriptionoE           ___________________________________________________________n  &           xmdialogs.c   dialog sampler  $           xmfonts.c     font browser  #           xmeditor.c    text editoru  $           xmlist.c      list example  8           xmprotocol.c  window manager protocols example  1           xmter.c       shape & animation exampleE  /           xmform.c      form attachment exampleC  ;           xmforc.c      form attachment + rowcolumn example   <           xmmap.c       drawingarea + scrolledwindow example  1           xmgetres.c    resource fetching example   ;           xmapdef.c     app defined scrolled window exampleh  =           The following notes apply to these sample programs:w  A           1. The xmfonts program defaults to displaying the fonts,C              whose name length are less than 10 characters. On some @              systems, the font path contains only long XLFD fontB              names. It may be necessary either to set the resourceD              XMFONTS*maxLen to a larger number (80), or to specify a&              numColumns resource of 1.  ?           2. If you run the program xmter with a window manageriA              other than Motif Window Manager, that window manageruC              has to remove all the window decorations (for example,oE              borders). The program xmter directs Motif Window Manager .              to remove the window decorations.       4-42 p         I                                                  Programmer Release Notes I                                           4.15 OSF/Motif Example Programsi    C               3. The xmform program displays a string made of Motif H                  widgets embedded in a Form. Use the following commands:  3                  $ xmform :== $DECW$EXAMPLES:xmforml                   $ xmform string  H                  The variable string is optional. If string is supplied,D                  the available letters for string are F,I,M,O,T. TheD                  string of letters that you use must be in uppercaseG                  and enclosed in quotation marks. If string is omitted,.(                  xmform returns "MOTIF".  A               4. The xmgetres program is an example of how to use G                  XmGetSecondaryResourceData. Use the following commandsh$                  to invoke xmgetres:  7                  $ xmgetres :== $DECW$EXAMPLES:xmgetres '                  $ xmgetres WidgetClass_  H                  The variable WidgetClass is optional. If WidgetClass isH                  omitted, it defaults to a class named "Widget". You canG                  also use the class "All", which displays the resourcesaH                  for all the Xt and the Motif widgets. See the OSF/MotifF                  Programmer's Reference manual for a list of available                   widget classes.  (         4.15.14 Xmtravel Example Program  C         V1.2  The xmtravel example is a front end to a travel agent D               client and flight database. The program is designed toG               illustrate various user-interface design concepts as welld=               as be compliant with the OSF/Motif Style Guide.   G               The program is just an example, many of the functions aree@               either not implemented or use predefined settings.  3         4.15.15 Resource Files for Example Programst  I         V1.2  Many of the example programs have associated resource files C               for defining various display attributes. To use theseeF               files, either copy them from the directory DECW$EXAMPLESI               to your DECW$USER_DEFAULTS directory, or add their contentsN.               to your DECW$XDEFAULTS.DAT file.  A               The list of example programs and the resource files 1               associated with them is as follows:_  I                                                                      4-43  s  p           Programmer Release Notes#     4.15 OSF/Motif Example Programs_  E           ___________________________________________________________   -           Example Program       Resource File E           ___________________________________________________________a  1           DECW$CDPLAYER.EXE     DECW$CDPLAYER.DAT   ,           FILEVIEW.EXE          FILEVIEW.DAT  ,           PERIODIC.EXE          PERIODIC.DAT  -           MOTIFANM.EXE          MOTIFANIM.DAT   +           XMAPDEF.EXE           XMDEMOS.DAT   +           XMDIALOGS.EXE         XMDEMOS.DATe  +           XMEDITOR.EXE          XMDEMOS.DAT.  +           XMFONTS.EXE           XMDEMOS.DATn  +           XMFORC.EXE            XMDEMOS.DATe  +           XMFORM.EXE            XMDEMOS.DAT   +           XMGETRES.EXE          XMDEMOS.DATs  +           XMLIST.EXE            XMDEMOS.DATe  +           XMMAP.EXE             XMDEMOS.DATe  +           XMPROTOCOL.EXE        XMDEMOS.DAT   +           XMTER.EXE             XMDEMOS.DAT   ,           XMTRAVEL.EXE          XMTRAVEL.DAT  D           If a resource file is not found, the example programs run,>           but some of the display attributes may be incorrect.  *     4.15.16 UID Files for Example Programs  D     V1.2  The UID files used by the example programs must be locatedD           in either the current directory or your DECW$USER_DEFAULTSD           directory. If they are not found, the application fails toC           start. The UID files can be copied from the DECW$EXAMPLESl           directory.  '     4.16 DECwindows Extensions to Motif   =           This section contains information about the Digitalo*           extensions to the Motif Toolkit.       4-44    e      I                                                  Programmer Release NotesiI                                       4.16 DECwindows Extensions to Motif     -         4.16.1 DXmCSText Input Method Supporte  C         V1.2  X11 R5 input method support is added to the DXmCSText B               widget. Specify input methods using the vendor shellD               XmNinputMethod resource. However, to maintain backward@               compatibility, the existing input method resources?               DXmNinputMethod and DXmNinputMethodType are still                available.  :         4.16.2 SVN-Horizontal Live Scrolling Not Supported  C         V1.0  Horizontal live scrolling is not yet supported in thet8               Structured Visual Navigation (SVN) widget.  ,         4.16.3 SVN Horizontal Separator Line  H         V1.1  When displaying an application that uses the SVN widget onH               a Sun system running OpenWindows Version 2, the horizontalF               separator line of the SVN widget is not always displayedG               due to a problem with the OpenWindows server. The problem 8               does not exist with OpenWindows Version 3.  5         4.16.4 DXmFormSpaceButtonsEqually Restriction   F         V1.1  The convenience routine DXmFormSpaceButtonsEqually sizesD               and spaces all widgets or gadgets equally if they haveE               a subclass of XmLabel or XmLabelGadget. The results aretB               undefined if a widget or gadget is not a subclass of'               XmLabel or XmLabelGadget.   &         4.17 Display Server Extensions  H               This section contains information about the display server               extensions.   D         4.17.1 Display PostScript (DPS) Server Extension-Color Cells  C         V1.0  You can associate a colormap with a DPS context using E               the DPSCreateContext routine or the setXgcdrawablecolorhB               operator. You can also specify that DPS allocate itsE               own colors from the specified colormap using the actualnF               parameter to DPSCreateContext or the setXgcdrawablecolor               operator.<  G               If you have created the colormap using the AllocAll flag, F               you must not also specify a nonzero value for the actualA               parameter. DPS always allocates colors as shareablee  I                                                                      4-45c (  \           Programmer Release Notes"     4.17 Display Server Extensions    A           and AllocAll forces all possible colormap entries to bec$           allocated as nonshareable.       4.17.2 X Image Extension  E     V1.1  The X Image Extension (XIE) allows image display processing C           using resources on the server side of the X client-servers?           model. XIE eliminates the need to transmit image data>B           repeatedly from the client to the server and also allowsA           data to be transmitted in compressed form, reducing thel           network load.   B           VMS DECwindows Motif Version 1.1 includes the XIE client?           side sharable library (XIE$SHRLIB.EXE) and C language D           header files. These allow applications to communicate with9           any X11 server that supports the XIE extension.c  @           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 is @           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 processingsB           unsigned byte (UdpK_DTypeBU), unaligned bit field (UdpK_B           DTypeVU), and aligned bit field (UdpK_DTypeV) data, with@           a maximum depth of 8 bits per pixel per component. TheB           XIE client library supports these data types, as well asD           unsigned word (UdpK_DTypeWU), and a depth of up to 16 bits"           per pixel per component.  >           The XIE protocol and programming interface are beingC           standardized within the X Consortium for R6, and programs E           that use XIE will probably have to be modified. You can user@           the Image Display Services (IDS) component of DECimage?           Application Services for VMS as an alternative to thesB           XIE library interface. IDS provides a higher level model@           of image display and automatically uses XIE when it is$           available and appropriate.  D           XIE is documented in the DECimage Application Services for>           VMS X Image Extension Programmer's Reference Manual.           4-46 o  o      I                                                  Programmer Release NotessI                                            4.17 Display Server Extensionse    ,         4.17.3 Client Side Extension Library  A         V1.1  Starting with Version 1.1, Xlib added a client sidelE               library that allows VMS clients to issue Shape, XInput,aB               Multibuffer, and shared memory extension requests toD               servers that provide these features. (For example, theD               DECwindows X11 display server for OpenVMS VAX does notB               support the Shape extension while the DECwindows X11B               display server for OpenVMS Alpha system does supportF               Shape.) The name of this library is DECW$XEXTLIBSHR.EXE.  :               You must modify the linking file options for;               client applications that issue Shape, XInput,e>               Multibuffer, or shared memory extension requests?               to link to the Xlib extensions shareable image in E               SYS$LIBRARY:DECW$XEXTLIBSHR.EXE. Add the following linen*               to your linker options file:  /               SYS$LIBRARY:DECW$XEXTLIBSHR/SHARE   D               For more information on Shape, XInput, and MultibufferC               extensions, see the following text files in SYS$HELP:e                    DECW$SHAPE.TXT                    DECW$XINPUT.TXT%                  DECW$MULTIBUFFER.TXTh  .         4.17.4 Shared Memory Extension Support           V1.2  G               On OpenVMS Alpha systems, shared memory extension support F               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,oF               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 isTE               stored in the shared memory segment. Through the use of I               shared memory pixmaps, you can change the contents of theser6               pixmaps without using any Xlib routines.  I                                                                      4-47c o  p           Programmer Release Notes"     4.17 Display Server Extensions    B           These routines are included in the client side extensionA           library. See Section 4.17.3 for details on linking thise           library.  /     4.17.4.1 How to Use Shared Memory Extension   E           Code that uses the shared memory extension must include the !           following header files:s  )           # include "DECW$INCLUDE:Xlib.h"h(           # include "DECW$INCLUDE:shm.h")           # include "DECW$INCLUDE:XShm.h"   ?           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)c!                  Display *displayn  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           ___________________________________________________________   !           Argument    DescriptionvE           ___________________________________________________________k  *           display     The current display.  =                       If the shared memory extension is used,_>                       the return value from either function isB                       True. Otherwise, your program operates using.                       conventional Xlib calls.  ;           major       Major version number of the extension C                       implementation. Returned by XShmQueryVersion.   ;           minor       Minor version number of the extensionsC                       implementation. Returned by XShmQueryVersion.   5           pixmaps     True, if shared memory pixmaps.r       4-48 e         I                                                  Programmer Release NotesaI                                            4.17 Display Server Extensions     ,         4.17.4.2 Using Shared Memory XImages  G               The following sequence shows the process for creating ande*               using shared memory XImages:  ;               1. Create the shared memory XImage structure.   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.e  .               5. Use the shared memory XImage.  G               The following sections explain each step in this process:   >               Step 1-Creating a Shared Memory XImage Structure  G               To create a shared memory XImage, use the XShmCreateImage 6               routine, which has the following format:  L               XImage *XShmCreateImage (display, visual, depth, format, data,1                           shminfo, width, height)o&                      Display *display;$                      Visual *visual;7                      unsigned int depth, width, height;t                       int format;                       char *data;.                      XShmSegmentInfo *shminfo;  I               Most of the arguments are the same as for XCreateImage (See_G               the X Window System for a description of the XCreateImage E               routine.) Note that there are no offset, bitmap_pad, ormG               bytes_per_line arguments. These quantities are set by theoF               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 thish;               structure before the call to XShmCreateImage.r  G               If successful, an XImage structure is returned, which youF/               can use for the subsequent steps.i  I                                                                      4-49,    s           Programmer Release Notes"     4.17 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);O  A           This example assumes that you called your shared memoryiD           XImage structure. A return value of 0 indicates the sharedE           memory allocation has failed. Use the bytes_per_line field,CE           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 IDs*           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,l@           decide how you want the server to attach to the shared?           memory segment, and set the shminfo.readOnly field as            follows:  #           shminfo.readOnly = False;a  C           If you set the structure to True, the server cannot writet7           to this segment, and XShmGetImage calls fail.l  C              ________________________ Note ________________________m  A              The shared memory segment routines are provided withnB              DECwindows Motif Version 1.2 for OpenVMS Alpha. Using?              global sections, these routines emulate the shared--              memory routines on UNIX systems.   C              ______________________________________________________        4-50    e      I                                                  Programmer Release NotesrI                                            4.17 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:r  3               Status XShmAttach (display, shminfo);E  C               If successful, a nonzero status is returned, and yourE&               XImage is ready for use.  3               Step 5-Using the Shared Memory XImage   E               To write a shared memory XImage into an X drawable, use I               the XShmPutImage routine. The XShmPutImage routine uses ther               following format:f  @               XShmPutImage (display, d, gc, image, src_x, src_y,M                                    dest_x, dest_y, width, height, send_event) &                      Display *display;                       Drawable d;                      GC gc;E#                      XImage *image;W6                      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.E  F               The completion event is of the type XShmCompletionEvent,*               which is defined as follows:             typedef struct {2               inttype;              /* of event */E               unsigned long serial; /* # of last request processed */IO               Bool send_event;      /* true if came from a SendEvent request */aI               Display *display;     /* Display the event was read from */U=               Drawable drawable;    /* drawable of request */p4               int major_code;       /* ShmReqCode */7               int minor_code;       /* X_ShmPutImage */ H               ShmSeg shmseg;        /* the ShmSeg used in the request */E               unsigned long offset; /* the offset into ShmSeg used */o            } XShmCompletionEvent;  I                                                                      4-51                 Programmer Release Notes"     4.17 Display Server Extensions    ?           To determine the event type value that is used at runiD           time, use the XShmGetEventBase routine as in the following           example:  O                int CompletionType = XShmGetEventBase (display) + ShmCompletion;i  C              ________________________ Note ________________________u  ?              If you modify the shared memory segment before thel@              arrival of the completion event, the results may be              inconsistent.  C              ______________________________________________________   A           To read image data into a shared memory XImage, use the6@           XShmGetImage routine, which uses the following format:  C           Status XShmGetImage (display, d, image, x, y, plane_mask)r"                  Display *display;                  Drawable d;                  XImage *image;                   int x, y;*                  unsigned long plane_mask;  9           The following table lists each argument and itsd           description.E           ___________________________________________________________o!           Argument    DescriptionnE           ___________________________________________________________   .           display     The display of interest.  *           d           The source drawable.  -           image       The destination XImage.l  :           x           X-offset within the source drawable.  :           y           Y-offset within the source drawable.  5           plane mask  The planes that are to be read.   ?           To destroy a shared memory XImage, first instruct thenD           server to detach from it, then destroy the segment itself.C           The following example illustrates how to destroy a shared            memory Ximage:  (           XShmDetach (display, shminfo);            XDestroyImage (image);"           shmdt (shminfo.shmaddr);.           shmctl (shminfo.shmid, IPC_RMID, 0);       4-52 x  r      I                                                  Programmer Release NotesrI                                            4.17 Display Server Extensionss    ,         4.17.4.3 Using Shared Memory Pixmaps  D               Unlike X images, for which any image format is usable,G               the shared memory extension supports only a single format H               for the data stored in a shared memory pixmap (XYPixmap orF               ZPixmap). This format is independent of the depth of theI               image and independent of the screen. (For 1-bit pixmaps the1$               format is irrelevant.)  D               The XShmPixmapFormat routine returns the shared memoryH               pixmap format for the server. The XShmPixmapFormat routine'               has the following format:o  ,               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 memoryH                  XImages steps 1 through 4 (see Section 4.17.4.2). WhileD                  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 then"                  following format:  K                  Pixmap XShmCreatePixmap (display, d, data, shminfo, width, 9                                           height, depth);a)                         Display *display; #                         Drawable d; #                         char *data;a1                         XShmSegmentInfo *shminfo;_:                         unsigned int width, height, depth;  I                  The arguments are the same as for XCreatePixmap (see theiG                  X Window System) except for two additional parameters, D                  data and shminfo. The data parameter is the pointerD                  to the shared memory segment and is the same as theI                  shminfo.shmaddr field. The shminfo parameter is the sameI+                  as the previous structure.v  I                                                                      4-53                 Programmer Release Notes"     4.17 Display Server Extensions    ?              If successful, a pixmap is returned, which you canrA              manipulate. You can manipulate its contents directly E              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 (see )              step 4 in Section 4.17.4.2).   (     4.17.5 Using Extension Include Files  @     V1.2  To ensure that programs that contain extension includeC           files compile properly, add the logical name DECW$INCLUDEu1           to the C include directory search list.1  @           To add the logical name for VAX C, enter the following           command:  )           $ DEFINE C$INCLUDE DECW$INCLUDEe  @           To add the logical name for DEC C, enter the following           command:  1           $ DEFINE DECC$USER_INCLUDE DECW$INCLUDEm       4.18 Xlib Issues  7           This section contains information about Xlib.a  0     4.18.1 xlibint.h Is Now a Public Header File  E     V1.2  To write application interfaces for your server extensions,aB           DECwindows Motif for OpenVMS provides the OpenVMS header>           file called xlibint.h in the DECW$INCLUDE directory.  .     4.18.2 Command Procedure Builds .PEN Files  ?     V1.0  To allow Pascal programs to inherit environment filesi;           for Xlib and Motif, execute the command procedures@           SYS$LIBRARY:DECW$PEN_BUILD.COM. This command procedureB           generates the DECW$XLIBDEF.PEN and DECW$MOTIF.PEN files.E           The .PEN files compile into Pascal programs faster than the            provided .PAS files.             4-54 u  r      I                                                  Programmer Release Notes I                                                          4.18 Xlib Issues     5         4.18.3 Parameter/Protocol Datasize Mismatches,  G         V1.0  Several Xlib routines accept longword parameters that are I               not sent in their entirety in the X Protocol message to the G               server. In each case, the Xlib routine sends out only the I               least significant 16 bits of the parameter value. This is adI               constraint of the field size within the X Protocol message.lG               Table 4-11 lists routine names and the longword argumentsa2               that are sent only as 16-bit values.  J               Table 4-11 Routine Names and Arguments Sent as 16-Bit ValuesJ               ____________________________________________________________  B               Routine Name                       Routine ArgumentsJ               ____________________________________________________________  @               XAllocColorCells/ALLOC_COLOR_      nplanes,npixels               CELLS   B               XDrawArc/DRAW_ARC                  x,y,width,height,>                                                  angle1,angle2  <               XDrawLine/DRAW_LINE                x1,x2,x3,x4  4               XDrawPoint/DRAW_POINT              x,y  A               XDrawRectangle/DRAW_RECTANGLE      x,y,width,heightN  4               XDrawString/DRAW_STRING            x,y  4               XDrawString16/DRAW_STRING16        x,y  4               XDrawText/DRAW_TEXT                x,y  4               XDrawText16/DRAW_TEXT16            x,y  ;               XFillArc/FILL_ARC                  x,y,width,.E                                                  height,angle1,angle2   A               XFillRectangle/FILL_RECTANGLE      x,y,width,height   ?         4.18.4 XSelectAsyncEvent and XSelectAsyncInput Routinesi  B         V1.1  The XSelectAsyncEvent and XSelectAsyncInput routines=               allocate memory for the storage of AST deliverytF               information. This memory is freed in the following ways:  D               o  If you close a display (XCloseDisplay), all the ASTI                  delivery information associated with all windows on that "                  display is freed.  B               o  If you destroy a window (XDestroyWindow), the AST?                  delivery information for that window is freed.f  I                                                                      4-55e o  i           Programmer Release Notes     4.18 Xlib Issues    E           The AST delivery information for subwindows is not freed by            XDestroyWindow.o  @           If you want to turn off AST notification for all event;           types within a given window and also free the AST ?           delivery information, the client application can calllC           XSelectAsyncEvent or XSelectAsyncInput passing the event_rA           mask argument equal to minus one (all bits set) and the -           ast_routine argument equal to zero.e  $     4.18.5 Xlib Internationalization  D     V1.2  The X Window System Version 11, Release 5 (X11 R5) definesC           a number of services to support writing internationalizede?           X applications. Internationalization of X is based onmA           the concept of a locale. A locale defines the localizedsD           behavior of a program at run time. Locales affect Xlib by:  6           o  Encoding and processing input method text  /           o  Encoding resource files and valuesa  .           o  Encoding and imaging text strings  E           o  Encoding and decoding for interclient text communicatione  ?           The X Window System defines a general methodology and ?           a set of application programming interfaces (APIs) tor?           standardize programming in X. Standards have not been,A           established for implementing these internationalizatione@           features. Currently, the X11 R5 distribution makes twoE           sample implementations of Xlib internationalization support @           available: Xsi and Ximp. In addition, Digital providesC           an implementation called Xi18n. You can select which I18N D           implementation you want. All three implementations provideE           the same functionality through the same set of public APIs,ID           but their underlying processing differs. These differences2           are described in the following sections.  #     4.18.5.1 Vendor Pluggable Layer   @     V1.2  Digital provides a general mechanism called the vendor:           pluggable layer, which allows you to choose your=           own internationalization implementations. Differente>           implementations can be built as standalone shareable;           libraries and can be selected through the logicalo           DECW$XVENDORLAYER.       4-56 S  e      I                                                  Programmer Release NotesiI                                                          4.18 Xlib Issuesr    D               If this logical is not defined, the mechanism searchesG               for an internationalization implementation library in thei               following order:  )                  DECW$XI18NLIBSHR (Xi18n) %                  DECW$XSILIBSHR (Xsi) '                  DECW$XIMPLIBSHR (Ximp)   E               If a shareable library is not found, the default is the F               Xi18n implementations that are already linked with Xlib.  H               The following functions act as interfaces between Xlib andH               the internationalization implementation shareable library:                    XDefaultStringo"                  XwcFreeStringList*                  XwcTextListToTextProperty*                  XmbTextListToTextProperty*                  XwcTextPropertyToTextList*                  XmbTextPropertyToTextList"                  _XrmInitParseInfo"                  _XlcDefaultLoader  F               When creating the Xsi or the Ximp shareable library, youG               need to know the names of the interfaces because they areoE               defined within Xlib. Digital recommends that you rename F               the functions during compilation by adding the following                compilation flags:                 /define=(-6                   "XDefaultString"="_XDefaultString",-<                   "XwcFreeStringList"="_XwcFreeStringList",-L                   "XwcTextListToTextProperty"="_XwcTextListToTextProperty",-L                   "XmbTextListToTextProperty"="_XmbTextListToTextProperty",-L                   "XwcTextPropertyToTextList"="_XwcTextPropertyToTextList",-L                   "XmbTextPropertyToTextList"="_XmbTextPropertyToTextList",-<                   "_XrmInitParseInfo"="__XrmInitParseInfo",-;                   "_XlcDefaultLoader"="__XlcDefaultLoader")g              I                                                                      4-57d y  F           Programmer Release Notes     4.18 Xlib Issues    =     4.18.5.2 Digital Internationalization Xlib Implementationa  >     V1.2  The Digital implementation (Xi18n) provides enhanced@           support and a stable internationalization environment.C           The Digital implementation (Xi18n) provides the followingpD           advantages over the Xsi or Ximp environments provided with           the X distribution:m  E           o  Most European locales and Asian locales are supported by_>              the DECwindows Motif for OpenVMS version of Xlib.  A           o  New locales can easily be supported without changing D              Xlib. New locales can be added by plugging in a locale-D              specific shareable library and a corresponding X locale+              database file for that locale.   ?           o  Encoding of input processing can be different fromlB              output encodings. The output methods create a defaultC              font set and use available font resources installed indD              the X server. The code conversion is transparent to the              user.  >           o  The XIM protocol (protocol between Xlib and inputA              method server) has been proposed to the X ConsortiumS2              for inclusion in the X11 R6 standard.  &     4.18.5.3 Locale in OpenVMS Systems  >     V1.2  DECwindows Motif Version 1.2 for OpenVMS software isE           dependent on a locale environment that conforms to the ANSI D           C library. In the DEC C environment, the set of supporting>           locales does not fully utilize the internationalizedA           Xlib. Therefore, Xlib provides a minimal locale supportsE           environment that allows DECwindows Motif for OpenVMS to run 7           on a host environment without locale support.t  ;           The locale support environment can use the localed>           environment provided by DECC$SHR if it is available;?           otherwise, Xlib uses its internal locale environment.oB           Locales can be set by using the setlocale()  function if*           the locale is supported by Xlib.  @           The following functions and macros are provided in the%           OpenVMS locale environment:f                setlocale              mblen              mbtowco              mbstowcse       4-58           I                                                  Programmer Release Notes I                                                          4.18 Xlib Issuest                      wctombr                  wcstombsi                  MB_LEN_MAXy  E               If you write internationalized applications using theseaD               functions in the locale environment, do the following:  C               o  For Xlib applications, include <X11/Xlocale.h>. If C                  you include <stdlib.h>, you must do so before <X11                   /Xlocale.h>.*  I               o  For Motif applications, <X11/Xlocale.h> is automatically                   included.  9               o  Turn on the following compilation flags:g  E                  /define=(X_LOCALE,X_WCHAR,_WCHAR_T_,XLIB_XPG4_FUNCS)o                                                        I                                                                      4-59  x  l                      I                                                                         5 I         _________________________________________________________________I  I                                               Documentation Release Notesh    ?               This chapter describes the following information:   I               o  Section 5.1, Documentation Release Notes Specific to the C                  DECwindows Motif Version 1.2-3 for OpenVMS Product   H               o  Section 5.2, DECwindows Motif Version 1.2-3 for OpenVMS                  Documentation  H               o  Section 5.3, DECwindows Motif Version 1.2-3 for OpenVMS*                  Documentation Corrections  >               o  Section 5.4, OSF/Motif List of Known Problems  H         5.1 Documentation Release Notes Specific to the DECwindows Motif-             Version 1.2-3 for OpenVMS Product_  C        V1.2-3 The release notes in this chapter are cumulative fromtE               DECwindows Motif Version 1.0 and still apply to Version_I               1.2-3. The following sections contain documentation release E               notes that pertain specifically to the DECwindows Motife0               Version 1.2-3 for OpenVMS release:  H               o  Section 5.2, DECwindows Motif Version 1.2-3 for OpenVMS                  Documentation  H               o  Section 5.3.1.1, Enhancing Information About the Finish                   Printing Option  0               o  Section 5.3.2.2, Tear-Off Menus  0               o  Section 5.3.3.1, Global Symbols  :               o  Section 5.3.4.1, GET_CHAR_STRUCT Function  H               o  Section 5.3.6.1, DXmNlayoutDirection Resource Constants  A               o  Section 5.3.7.1, UIL Source Code for the OpenVMS;&                  DECburger Application  A               o  Section 5.3.7.2, Help Widget Implementation Code   I                                                                       5-1     7         Documentation Release Notes E     5.1 Documentation Release Notes Specific to the DECwindows Motif  )         Version 1.2-3 for OpenVMS Productr    B           o  Section 5.3.7.3, Help Widget Implementation-Callbacks  A           o  Section 5.3.7.4, Using UIL to Create the Help Widgetd  @     5.2 DECwindows Motif Version 1.2-3 for OpenVMS Documentation  E    V1.2-3 Table 5-1 lists DECwindows Motif for OpenVMS documentation.)?           Information for the documents that is not updated for @           the DECwindows Motif Version 1.2-3 for OpenVMS release;           is included in this chapter of the Release Notes.   >           Table 5-1 DECwindows Motif for OpenVMS DocumentationG           _____________________________________________________________m  F           Title                                       Software VersionG           _____________________________________________________________o  C           DECwindows Motif Version 1.2-3 for OpenVMS  Version 1.2-3            Release Notes   C           DECwindows Motif Version 1.2-3 for OpenVMS  Version 1.2-3f           Installation Guide  D           DECwindows Motif for OpenVMS Applications   Version 1.2[1]           Guiden  D           DECwindows Motif for OpenVMS Guide to       Version 1.2[1]           Non-C Bindings  D           Using DECwindows Motif for OpenVMS          Version 1.1[1]           (Digital Press)h  D           DECwindows Motif for OpenVMS Quick          Version 1.2[1]           Reference Card  D           Managing DECwindows Motif for OpenVMS       Version 1.2[1]           Systems   D           Overview of DECwindows Motif for OpenVMS    Version 1.2[1]           Documentation   D           DECwindows Extensions to Motif              Version 1.2[2]  B           [1]Updates to these documents, if any, are noted in this'           chapter of the Release Notes.TD           [2]The recently updated DEC OSF/1 version of this documentA           is provided with the DECwindows Motif Version 1.2-3 for E           OpenVMS documentation kit. The information is applicable to B           the DEC OSF/1 and DECwindows Motif for OpenVMS releases.  E                                              (continued on next page)        5-2            I                                               Documentation Release Notes I              5.2 DECwindows Motif Version 1.2-3 for OpenVMS Documentationl    J               Table 5-1 (Cont.) DECwindows Motif for OpenVMS DocumentationJ               ____________________________________________________________     J               Title                                       Software VersionJ               ____________________________________________________________  H               DECwindows Companion to the OSF/Motif       Version 1.2[2]               Style Guide   H               DECwindows Motif Guide to Application       Version 1.2[2]               Programmingn  H               VMS DECwindows Device Driver Manual         Version 1.0[1]  H               VMS DECwindows Transport Manual             Version 1.0[1]  H               Porting XUI Applications to Motif           Version 1.0[1]  H               VMS DECwindows Guide to Xlib (Release 4)    Version 1.0[1](               Programming: MIT C Binding  H               VMS DECwindows Guide to Xlib (Release 4)    Version 1.0[1]&               Programming: VAX Binding  H               VMS DECwindows Display PostScript System    Version 1.0[1]$               Programming Supplement  C               X Window System (Digital Press)             Release 5rG                                                           Third Editiont  C               X Window System Toolkit (Digital Press)     Release 4F  C               X and Motif Quick Reference Guide (Digital  Release 5i               Press)  E               OSF/Motif Style Guide (Prentice-Hall)       Release 1.2B  E               OSF/Motif Programmer's Guide (Prentice-     Release 1.2N               Hall)i  E               OSF/Motif Programmer's Reference            Release 1.2h               (Prentice-Hall)e  F               [1]Updates to these documents, if any, are noted in this+               chapter of the Release Notes. H               [2]The recently updated DEC OSF/1 version of this documentE               is provided with the DECwindows Motif Version 1.2-3 foreI               OpenVMS documentation kit. The information is applicable to F               the DEC OSF/1 and DECwindows Motif for OpenVMS releases.  I                                                                       5-3s i  f           Documentation Release NoteshL     5.3 DECwindows Motif Version 1.2-3 for OpenVMS Documentation Corrections    @     5.3 DECwindows Motif Version 1.2-3 for OpenVMS Documentation         Corrections   ?           This section contains corrections and enhancements to1=           existing DECwindows Motif Version 1.2-3 for OpenVMS            documentation.  9     5.3.1 DECwindows Motif for OpenVMS Applications Guide   @           This section contains documentation corrections to theA           DECwindows Motif for OpenVMS Applications Guide manual.   B     5.3.1.1 Enhancing Information About the Finish Printing Option  B    V1.2-3 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.3.2 Using DECwindows Motif for OpenVMS  =           This section contains documentation corrections and1@           enhancements to the Using DECwindows Motif for OpenVMS           manual.w  +     5.3.2.1 Using the Drag-and-Drop Feature   @     V1.2  The drag-and-drop feature lets you move or copy screenB           objects. For example, you can move text from buttons and           paste it elsewhere.i  4           To drag and drop text into a new location:  <           1. Select the text to be copied or moved with MB1.  2           2. To move the text, press and hold MB2;-              to copy the text, press and hold               Ctrl/MB2.  )              A move or copy icon appears.   E           3. Drag the icon to the location where you want to drop the "              text and release MB2.  E              If the object is highlighted as you drag the icon across :              it, you can drop the text into that location.       5-4            I                                               Documentation Release NoteslI  5.3 DECwindows Motif Version 1.2-3 for OpenVMS Documentation Correctionsn    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 applicationsfF               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.            5.3.2.2 Tear-Off Menus  F        V1.2-3 The DECwindows Mail application supports tear-off menus.  E         V1.2  The DECwindows Motif applications allow you to tear off D               pull-down and popup menus. Tear-off menus let you keepH               frequently used menus displayed without repeatedly pulling+               them down or popping them up.l  !               To tear off a menu:g  3               1. Display a pull-down or popup menu.f  A                  If the menu is a tear-off menu, a dotted line ise2                  displayed at the top of the menu.  3               2. Click on the dotted line with MB1.   H                  The menu remains active until it is closed or until the.                  parent application is closed.  '               To close a tear-off menu:   F               1. Click on the Window menu button in the tear-off menu.  ,               2. Choose the Close menu item.  G               The following applications do not support tear-off menus:X                 o  CDA Viewer                   o  DECwindows Mail                 o  Notepad                 o  Print Screeno  I                                                                       5-5p e  n           Documentation Release Notes L     5.3 DECwindows Motif Version 1.2-3 for OpenVMS Documentation Corrections    B     5.3.2.3 Adding Target Screen Options to Application Menu Items  B     V1.2  The example "Adding Target Screen Options to Application>           Menu Items" in Using DECwindows Motif for OpenVMS is=           incorrect. To correct the problem, remove the first +           occurrence of the following line:i             $ select_qualifiers:  ,     5.3.2.4 Changing the Startup Environment  C     V1.2  The example "Changing Your Logo" is incorrect. To correct E           the problem, change the following code example in step one:   F           $ COPY SYS$COMMON:[SYSMGR]DECW$PRIVATE_APPS_SETUP.TEMPLATE -E           _$ SYS$SPECIFIC:[SYSMANAGER]DECW$PRIVATE_APPS_SETUP.COM/LOG   2           The code example should read as follows:  F           $ COPY SYS$COMMON:[SYSMGR]DECW$PRIVATE_APPS_SETUP.TEMPLATE -A           _$ SYS$SPECIFIC:[SYSMGR]DECW$PRIVATE_APPS_SETUP.COM/LOG   )     5.3.2.5 Enhancing Startup Performance8  ?     V1.1  Extensive SYLOGIN.COM or LOGIN.COM command procedures ?           slow down application startup. Many of the operations A           performed in a SYLOGIN.COM or LOGIN.COM are meaningless:<           for DECwindows application startup. Therefore, theC           SYLOGIN.COM and LOGIN.COM files should be conditionalized >           for DECwindows application startup performance. WhenE           starting a DECwindows application, a minimum of SYLOGIN.COM_4           and LOGIN.COM commands should be executed.  A           Typically, the commands that should be executed are theyD           redefinition of DECW$USER_DEFAULTS (if present), and otherB           logical name definitions if the user will be referencingC           them from within the context of a DECwindows application.tE           The following code segment can be inserted into SYLOGIN.COM=D           and LOGIN.COM immediately following the commands necessary           for DECwindows:=             $ mode = f$mode() '           $ tt_devname = f$trnlnm("TT")wC           $ session_mgr_login = (mode .eqs. "INTERACTIVE") .and.  -rC                 (f$locate("WSA",tt_devname) .ne. f$len(tt_devname))yI           $ session_detached_process = (mode .eqs. "INTERACTIVE") .and. -rC                 (f$locate("MBA",tt_devname) .ne. f$len(tt_devname))IH           $ if session_mgr_login .or. session_detached_process then exit       5-6a L  e      I                                               Documentation Release Notes I  5.3 DECwindows Motif Version 1.2-3 for OpenVMS Documentation Correctionsu    F               Applications continue to run even if these lines are not;               added to the SYLOGIN.COM and LOGIN.COM files.   3         5.3.2.6 Enhancing Hold-Screen Response Timei  G         V1.1  If the Hold Screen key response time is too slow, add thenE               following lines to your DECW$TERMINAL_DEFAULT.DAT file:h  :               DECW$TERMINAL.main.terminal.syncFrequency: 1=               DECW$TERMINAL.main.terminal.batchScrollCount: 1D  C               Using this resource can affect the performance of thesE               DECterm window. The actual impact on performance varieslE               from site to site. You can trade off scrolling speed tolF               hold-screen response time. A faster hold-screen responseI               results in a slower scrolling speed. The default values forf9               these resources are 10 and 0, respectively.a  ;         5.3.3 Managing DECwindows Motif for OpenVMS Systemsu  B               This section contains documentation enhancements andF               corrections to the Managing DECwindows Motif for OpenVMS               Systems manual.t         5.3.3.1 Global Symbols  F        V1.2-3 The following additional global symbols are available inE               the DECwindows Motif Version 1.2-3 for OpenVMS product:E  '               o  DECW$CONSOLE_SELECTIONw  D                  Specifies how to display operator-messages options.  &               o  DECW$CONSOLE_GEOMETRY  C                  Specifies the value of the -geometry option in thei4                  DECW$MESSAGEPANEL.EXE command line.  A               For information about using these symbols, refer toaF               Section 1.8 in these Release Notes. Refer to the chapterI               "Using DECwindows" in Managing DECwindows Motif for OpenVMSn>               Systems for the complete list of global symbols.            5.3.3.2 Security Options  G         V1.2  In the Session Manager Security Options dialog box, placetG               the node name within quotation marks if the name contains #               any of the following:u  E               o  Reserved characters: space, tab, comma (,) or doublee#                  quotation mark (")   "               o  Double colon (::)  I                                                                       5-7                 Documentation Release Notes L     5.3 DECwindows Motif Version 1.2-3 for OpenVMS Documentation Corrections    @           o  A colon (:) as the final character in the node name  C           Session Manager automatically adds quotation marks to thenC           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 changeF
           it.a  C           Within a quoted string, a double quotation mark should be D           replaced by two double quotation marks (" "). For example,E           the quoted string "DEC:.zko."my node"" should be changed to            the following:  #           ("DEC:.zko.""my node""").   (     5.3.3.3 Displaying a Customized Logo  =     V1.1  By default, if there is no DECwindows Motif license @           registered for the SYSTEM account, DECwindows does not>           display customized login logos. This is a problem onB           systems with DECwindows Motif personal-use licenses thatD           do not include SYSTEM on the list of authorized DECwindows           users.  A           To display a customized logo without a DECwindows Motif A           license for SYSTEM, add the following definition to thec7           SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM file:i  '           $ DECW$LOGINLOGOSUB == "TRUE"m  C              ________________________ Note ________________________3  ;              If the SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM 7              file does not exist, copy it from the files:              SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.TEMPLATE.  C              ______________________________________________________   @           After editing the setup file, restart DECwindows Motif&           using the following command:  -           $ @SYS$MANAGER:DECW$STARTUP RESTART.  =           DECwindows Motif login starts the logo process as a B           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.       5-8  c  n      I                                               Documentation Release NoteshI  5.3 DECwindows Motif Version 1.2-3 for OpenVMS Documentation Correctionsr    5         5.3.3.4 Enabling and Disabling Access Controlo  I         V1.0  DECwindows Motif does not enable access control by default. H               Instead, it uses the access control set by the server. TheE               DECwindows X11 display server enables access control at                startup time.   B               To force the DECwindows Session Manager to enable orF               disable access control explicitly at login time, you can8               define one of the following logical names:  H               $ DEFINE/SYSTEM/EXECUTIVE DECW$LOGIN_ACCESS_CONTROL ENABLE  I               $ DEFINE/SYSTEM/EXECUTIVE DECW$LOGIN_ACCESS_CONTROL DISABLE   E               If the logical name is not defined, or if it is definedeE               to some other value, such as "SERVER", DECwindows loginV:               neither enables nor disables access control.  E               In most cases, it should not be necessary to define theh               logical name.   B         5.3.4 DECwindows Motif for OpenVMS Guide to Non-C Bindings  B               This section contains documentation enhancements andF               corrections to the DECwindows Motif for OpenVMS Guide to               Non-C Bindings._  (         5.3.4.1 GET_CHAR_STRUCT Function  I        V1.2-3 The access related to the char_struct argument for the XLIB_E               GET_CHAR_STRUCT function is incorrectly documented. Thef&               correct access is write.  G         5.3.5 VMS DECwindows Guide to Xlib (Release 4) Programming: VAXr               Bindingf  F         V1.2  Example 1-1 in the VMS DECwindows Guide to Xlib (ReleaseF               4) Programming: VAX Binding is incorrect. To correct theD               problem, change the following two lines in the section+               "Create the WINDOW_1 window":e  B               WINDOW_1X = (X$WIDTH_OF_SCREEN(DPY) - WINDOW_1W) / 2C               WINDOW_1Y = (X$HEIGHT_OF_SCREEN(DPY) - WINDOW_1H) / 2   1               The example should read as follows:   E               WINDOW_1X = (X$WIDTH_OF_SCREEN(SCREEN) - WINDOW_1W) / 2wF               WINDOW_1Y = (X$HEIGHT_OF_SCREEN(SCREEN) - WINDOW_1H) / 2  I                                                                       5-9                 Documentation Release NotesnL     5.3 DECwindows Motif Version 1.2-3 for OpenVMS Documentation Corrections    B           Example 3-1 in the VMS DECwindows Guide to Xlib (ReleaseB           4) Programming: VAX Binding is incorrect. To correct the2           problem, change the following two lines:  I           WINDOW_1X = (X$DISPLAY_WIDTH_OF_SCREEN(SCREEN) - WINDOW_1W) / 2 J           WINDOW_1Y = (X$DISPLAY_HEIGHT_OF_SCREEN(SCREEN) - WINDOW_1H) / 2  -           The example should read as follows:   F           WINDOW_1X = (X$DISPLAY_WIDTH_OF_SCREEN(DPY) - WINDOW_1W) / 2G           WINDOW_1Y = (X$DISPLAY_HEIGHT_OF_SCREEN(DPY) - WINDOW_1H) / 2   (     5.3.6 DECwindows Extensions to Motif  :           This section lists documentation corrections and=           enhancements for the DECwindows Extensions to Motif            document.   2     5.3.6.1 DXmNlayoutDirection Resource Constants  B    V1.2-3 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   =           Note that the following constants are not currently]9           available for the DXmNlayoutDirection resource:              o  DXmLAYOUT_LEFT_UP             o  DXmLAYOUT_RIGHT_UP   ?           The introduction to Table 2-1 is incorrect. Table 2-1bC           describes the effect of the constants DXmLAYOUT_LEFT_DOWNi4           and DXmLAYOUT_RIGHT_DOWN on the functions.  >     V1.2  In Section 2.2 of the DECwindows Extensions to MotifC           manual, the description of DXmChildren indicates that the.A           routine can be used to learn the length of widget_list.w  C           The documentation is incorrect. The sentence should read, E           "You can use the DXmNumChildren routine to learn the lengthd6           of the widget list returned by DXmChildren."       5-10    i      I                                               Documentation Release Notes I  5.3 DECwindows Motif Version 1.2-3 for OpenVMS Documentation Corrections     ?         5.3.7 DECwindows Motif Guide to Application Programming   >               This section lists documentation corrections andH               enhancements for the DECwindows Motif Guide to Application!               Programming manual.n  E         5.3.7.1 UIL Source Code for the OpenVMS DECburger Application   A        V1.2-3 The introduction to the section in Chapter 4 called C               "Creating the Help Widget with UIL", which introduces E               Example 4-6, "UIL Help Widget Implementation," does not E               clearly state that the complete UIL source code for the H               OpenVMS DECburger application is included in DECW$EXAMPLES!               on OpenVMS systems.e  /         5.3.7.2 Help Widget Implementation Codef  H        V1.2-3 In the title of Example 4-7, "Help Widget Implementation-CH               Language Module", DECBURGER.C should be added to the title               as follows:n  ;               "Help Widget Implementation-C Language Module                (DECburger.C)"  4         5.3.7.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)"   3         5.3.7.4 Using UIL to Create the Help Widgett  G        V1.2-3 The title of Section 4.10, "Using the Toolkit Help WidgetaI               Creation Routine," does not accurately reflect the contents C               of this section. The title should read, "Using UIL to &               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:   H               "The code in Example 4-9 is included in DECburger.C but isI               commented and will not be compiled when the example program.               is built."  D               The implementation in this example is not complete; it?               requires some sections from Examples 4-7 and 4-8.o  I                                                                      5-11o n  l           Documentation Release NotestL     5.3 DECwindows Motif Version 1.2-3 for OpenVMS Documentation Corrections    D           To summarize, the documentation should state the following           information:  A           o  Examples 4-6 and 4-7 are UIL code (DECburger.UIL(D))a;              that, when combined, create the DECburger.EXE.s  5           o  Example 4-8 is C code for DECburger.EXE.u  9           o  Example 4-9 is C code for a Toolkit example.t  @     5.3.8 Overview of DECwindows Motif for OpenVMS Documentation  ;     V1.2  Table 2-2 in the Overview of DECwindows Motif forC>           OpenVMS Documentation Version 1.2 indicates that the?           DECwindows Motif Version 1.2 for OpenVMS InstallationgC           Guide is included in the User Kit. This is incorrect. Thei<           installation guide is included with the media kit.  (     5.4 OSF/Motif List of Known Problems  B           Included in the DECwindows Motif for OpenVMS software isA           an OSF file that contains the OSF/Motif known problems.wE           During the installation this file is copied from the kit toa2           SYS$HELP:DECW$MOTIF_OSF_BUGLIST_V12.TXT.                                               5-12 a                       I                                                                         AaI         _________________________________________________________________o  I                                       OSF/Motif Release 1.2 Release Notese    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 discusshE               performance improvements and information about backwardt               compatibility.  I               These Release Notes support the OSF/Motif software providedaG               with the DECwindows Motif for OpenVMS software, DEC OSF/1eC               software, the eXcursion Software Development Kit, and )               ULTRIX Worksystem Software.u  G               For the OSF/Motif Release 1.2.3 update, approximately 425D%               problems were resolved.p  $         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 arG               minimum, to not allow it to degrade below the performanceT'               of OSF/Motif Release 1.1.I  :               Performance testing was done in three areas:  -               o  Aspects obvious to end usersi  !               o  Data space usage                  o  Memory leakager  H               The performance of user-perceptible events such as postingH               and unposting dialog boxes and pop-up menus are comparableI               or better than the performance for OSF/Motif Release 1.1.4. G               A significant improvement was made for scrolling inside a H               Scrolled Text region that contains a large amount of test.  I                                                                       A-1  e  a      '     OSF/Motif Release 1.2 Release NotesY      A.1 Performance Improvements    @           Data space usage has improved throughout the OSF/MotifC           Toolkit, particularly for the Text widget. In some cases, >           data space usage has been reduced by as much as 40%.D           Also, the memory used for the text in a Text widget is nowC           correctly reduced when that text is replaced by a smaller            amount of text.i  C           Memory leakage has been reduced to a minimum for multiplehC           creates and destroys of all Toolkit widgets. Although thepA           Motif tests showed small memory leaks, the OSF believesm?           that this amount of memory is required as part of thee9           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 ofw           memory per instance.       A.2 Backward Compatibility  =           The OSF tested OSF/Motif Release 1.2 for both link-o=           time compatibility as well as visual and behavioral            compatibility.  -     A.2.1 Visual and Behavioral Compatibility   ;           The OSF ran automated tests that compared current C           visuals with those recorded using OSF/Motif Release 1.1.4 E           libraries. Once all differences between the Release 1.2 and E           Release 1.1.4 versions were accounted for, the visuals wereIB           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 andw>           behaviorally compatible with Release 1.1.4. However,@           they have made extensive improvements to the Traversal@           and Geometry Management algorithms that result in some?           differences between those versions. These differences @           reflect efforts to fix defects in the earlier release.  D           For example, one such modification involves the new policyA           in which an initial size set for a manager widget in an A           application is now honored by the Toolkit. In OSF/Motif >           Release 1.1, applications set the initial size for aA           manager widget, but did not, in fact, use that size. Inr?           Release 1.2, Motif now uses that size setting and theg0           initial layout is changed accordingly.       A-2  d  r      I                                       OSF/Motif Release 1.2 Release NoteseI                    A.3 Changes and New Features for OSF/Motif Release 1.2     >         A.3 Changes and New Features for OSF/Motif Release 1.2  G               This section summarizes changes and new features that therI               OSF has made to OSF/Motif Release 1.2. Detailed information A               about these modifications is contained in the MotifwD               reference pages and the Motif Release 1.2 revisions of               following books:  &               o  OSF/Motif Style Guide  -               o  OSF/Motif Programmer's Guideh  F               The following sections discuss the OSF/Motif Release 1.2               enhancements.S  %         A.3.1 General Toolkit Changesn  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 Released.               1.1 are obsolete in Release 1.2:                    ExtObject.h                  Traversal.h                  VaSimple.hO                  VendorE.h                  VendorEP.hp  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 nowuG               make incorrect assumptions for certain keyboards, such as I               those that have the arrow keys defined in the keypad. Otherk;               Motif applications might be affected as well.m  G               You can avoid this problem by creating a file to redefinehI               the bindings for the keys in question and then passing thate*               file to the xmodmap utility.  I                                                                       A-3            '     OSF/Motif Release 1.2 Release Notesa:     A.3 Changes and New Features for OSF/Motif Release 1.2    C           The following example changes the bindings for the keypadyD           keys that match the arrow keys so that only the arrow keysC           are produced, not the keypad numbers. The new definitionstE           allow the application to use modifiers with the arrow keys.d             !n           ! Always force:            !   KP_2 = Downn           !   KP_8 = UpE           !   KP_4 = Left            !   KP_6 = Right           keycode 120 = Down           keycode 76  = Up           keycode 98  = Left           keycode 100 = Right        A.3.3 ANSI C ComplianceE  C           All references to caddr_t have been changed to XtPointer. A           This change affects all callback routines and any other C           routines that reference caddr_t. The OSF made this changefC           so that OSF/Motif Release 1.2 would be compliant with theD           ANSI C specification.   *     A.3.4 Display and Screen Specific Data  E           Motif now has an XmDisplay object that supports per-displayrD           data and resources. An XmScreen object has been added that1           supports per-screen data and resources.        A.3.5 Drag and Dropt  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 ________________________o  A              If you want to use Btn2 to have pop-up menus pop up,oB              drag and drop will not function properly. You need to5              disable drag and drop in such instances.o  C              ______________________________________________________e       A-4c s  n      I                                       OSF/Motif Release 1.2 Release NoteseI                    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 tearable G               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 manager                policy.n  I               Tear-off behavior is enabled by setting the XmNtearOffModelCI               resource to XmTEAR_OFF_ENABLED. (The default is XmTEAR_OFF_                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 XmNtearOffModeldF               resource using the XmRepTypeInstallTearOffModelConverter               function.P  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, G               if a tear-off menu is mapped, the sensitivity of its menuOB               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 in E               operations being enabled at unexpected times. If a usersD               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                  XmListL                  XmScrollBar                  XmText   I                                                                       A-5c e  o      '     OSF/Motif Release 1.2 Release Notesw:     A.3 Changes and New Features for OSF/Motif Release 1.2                  XmTextField       A.3.8 Other Visual Changes  @           OSF/Motif Release 1.2 has made other visual changes as           follows:  A           o  Several pixels have changed in the three-dimensional               beveled look.  A           o  Minor changes have been made to the color generationh=              routines. In particular, the new XmScreen objecto<              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.D  C           o  Motif now adds a location cursor to surround all items C              in a List whenever a List widget has the focus and thel2              current keyboard item is not visible.  C           o  There are minor layout differences because of fixes in !              geometry management.r       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-6e n  h      I                                       OSF/Motif Release 1.2 Release NotesWI                    A.3 Changes and New Features for OSF/Motif Release 1.2l    !         A.3.11 Color Enhancements   B               The following three resources have been added to theC               XmScreen widget so that users can specify the defaultaE               background color and thresholds for shadow calculation:m  "                  XmNlightThreshold!                  XmNdarkThresholde'                  XmNforegroundThresholdn  I               Motif has added the XmChangeColor function that changes the A               background and other colors for a specified widget.b  !         A.3.12 Baseline Alignmenta  G               Motif has added two functions for baseline alignment. The-F               XmWidgetGetBaselines function determines the position ofD               the widget's text baseline. The XmWidgetGetDisplayRectG               function determines the size and position of the bounding"4               box for the widget's character string.  %         A.3.13 Expanded Traversal Setd  C               In OSF/Motif Release 1.2, you can use more widgets to G               support traversal using the keyboard. For example, inside G               a tab group, users can now use the arrow keys to traverse F               to all control descendants that are not contained withinH               a nested tab group and that are eligible to receive focus,E               even if the controls are not direct children of the tab                group.  -         A.3.14 Two-Dimensional Menu Traversal   G               With OSF/Motif Release 1.2, the left, right, up, and downdI               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 they E               are pressed in the rightmost and leftmost column of the %               menupane, respectively.e           A.3.15 Input Focus  A               OSF/Motif Release 1.2 has added the XmNinitialFocusgD               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-7r n  2      '     OSF/Motif Release 1.2 Release Notesi:     A.3 Changes and New Features for OSF/Motif Release 1.2    %     A.3.16 Traversal Access Functionsi  E           OSF/Motif Release 1.2 has added the following new functionsi@           to support better interaction with keyboard traversal:                XmGetFocusWidgetn              XmGetTabGroup              XmGetVisibility              XmIsTraversable              XmIsVisible  C           The XmTrackingLocate function has been modified to do the            following:  7           o  Field all events, not just a button press.   5           o  Return on any keystroke or button press._  0           o  Be called for nonsensitive widgets.  C           In addition, the XmTrackingEvent function has been added. C           This function is similar to XmTrackingLocate, except thatp.           it returns a pointer to the X event.       A.3.17 Virtual Keysc  E           OSF/Motif Release 1.2 has added the XmTranslateKey function D           that allows applications to override the default XtKeyProc'           to handle Motif virtual keys.a  0           Motif defines two new virtual keysyms:                osfPageLeft              osfPageRightt  @           You must have the X11 Release 5 XKeysymDB installed inC           /usr/lib/X11 to use these new virtual keys. Otherwise youiC           get a warning message on application startup. Specify the 6           following information in the XKeysymDB file:  #           osfPageLeft     :1004FF40   #           osfPageUp       :1004FF41.  #           osfPageDown     :1004FF42   #           osfPageRight    :1004FF43   ?           To comply with the OSF/Motif Style Guide, the defaultn>           binding for osfMenu has been changed from <key>F4 to           Shift<key>F10.       A-8  ,         I                                       OSF/Motif Release 1.2 Release Notes I                    A.3 Changes and New Features for OSF/Motif Release 1.2a    D               In X11 Release 5, the HP keysyms in the XKeysymDB fileH               have the prefix hp. This prefix is not reflected in the HPH               bindings file in the /bindings directory. If you are usingD               an X11 Release 5 XKeysymDB file, you might see warningI               messages at application startup. To eliminate these warning1G               messages, add the hp prefix as follows to the appropriated                lines in the file:  3               osfDelete :         <key>hpDeleteChar   3               osfInsert :         <key>hpInsertChar   3               osfPrimaryPaste :   <key>hpInsertLinee  3               osfQuickPaste :     <key>hpDeleteLine   G               OSF/Motif Release 1.2 has a new client, xmbind, that setsiD               up the virtual bindings for use by Motif applications.D               Since virtual binding is automatically set up at MotifG               Window Manager (MWM) startup, you only need to use xmbindeE               if MWM is not used or if you need to change the virtual .               bindings without restarting MWM.  A               Virtual bindings can now be specified by individual A               vendors. If there is no .motifbind file in the homeeE               directory, you can use the xmbind.alias file to providedI               a mapping from the server vendor name to the bindings file. H               You can set up user vendor bindings as well as system-wide               vendor bindings.  "         A.3.18 Resource Management  G               OSF/Motif Release 1.2 has the following new functions for ,               managing representation types:  "                  XmRepTypeRegister$                  XmRepTypeAddReverse$                  XmRepTypeValidValue'                  XmRepTypeGetRegisteredt                  XmRepTypeGetIdB%                  XmRepTypeGetNameListh#                  XmRepTypeGetRecorde  C               These functions are useful for developers who want tosG               define new resource converters that use an enumerated set.               of values.  I                                                                       A-9i R  a      '     OSF/Motif Release 1.2 Release Notesi:     A.3 Changes and New Features for OSF/Motif Release 1.2    1     A.3.19 Changes for CUA and Windows Compliance   D           In OSF/Motif Release 1.2, pressing the Return key or using@           the key bound to osfActivate (usually the Enter key onB           the numeric keypad) no longer activates a button that isD           outside a menu. For example, pressing such a key no longer@           pops up an OptionMenu or activates a ToggleButton in a           dialog box.a  E           If your application has a default button associated with anaA           XmBulletinBoard, pressing Return (except in a multiline ?           XmText), Ctrl/Return, or the key bound to osfActivatehA           while the focus is in the XmBulletinBoard now activatest           the default button.   4     A.4 Changes and Enhancements to Specific Widgets  A           This section summarizes the changes to specific widgets 2           that were made in OSF/Motif Release 1.2.       A.4.1 XmClipboarde  B           OSF made several corrections to the XmClipboard function>           parameters. These changes are binary compatible with@           earlier releases of Motif. However, in some instances,@           you might see warning messages when you recompile yourA           applications. The modifications involved changing (charaD           *) to XtPointer, int to long, and (int *) to (long *). The@           related functions affected by these modifications are:             o  XmClipboardCopy  "           o  XmClipboardCopyByName  $           o  XmClipboardInquireCount  %           o  XmClipboardInquireFormatf  &           o  XmClipboardRegisterFormat              o  XmClipboardRetrieve  !           o  XmClipboardStartCopyd  &           o  XmClipboardWithdrawFormat       A-10 S  o      I                                       OSF/Motif Release 1.2 Release Notes I                          A.4 Changes and Enhancements to Specific Widgets.             A.4.2 XmCommand:  @               In OSF/Motif Release 1.2, a correction was made toE               XmCommandGetChild so that it now accepts XmDIALOG_WORK_V5               AREA as a value for the child argument.m           A.4.3 XmList  H               To enchance 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 enableo?           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 time               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  usePPositioni  >              Uses the values of on, off, or nonzero to control:              whether program-specified positions are used.  (     A.5.3 New and Enhanced MWM Functions  B           OSF/Motif Release 1.2 has the following new and enhanced           MWM functions:             o  f.lower  A              Includes a within argument to move the window within C              the application stacking order, but retains the parentu>              window below the children rule. The function also>              includes a freeFamily argument to move the windowA              absolutely without regard to its local family stack. C              Both modifiers move the window within the local family 5              stack, but do not move the family stack..             o  f.minimize   9              Can now be used from an icon in an icon box.o             o  f.raise       A-16 t  v      I                                       OSF/Motif Release 1.2 Release Notes I                                     A.5 Motif Window Manager Enhancements     E                  Includes a within argument to move the window within G                  the application stacking order, but retains the parentwB                  window below the children rule. The function alsoB                  includes a freeFamily argument to move the windowE                  absolutely without regard to its local family stack.0G                  Both modifiers move the window within the local family 9                  stack, but do not move the family stack.e                 o  f.raise_lower  E                  Includes a within argument to move the window within1G                  the application stacking order, but retains the parentoB                  window below the children rule. The function alsoB                  includes a freeFamily argument to move the windowE                  absolutely without regard to its local family stack.eG                  Both modifiers move the window within the local familyl9                  stack, but do not move the family stack.                  o  f.restore  I                  Restores a window to its previous state. Double clicking H                  on a root icon is bound to this function rather than to                  f.normalize.   $               o  f.restore_and_raise  I                  Restores a window to its previous state and raises it to H                  the top of the window stack. Double clicking on an iconH                  in an icon box is bound to this function rather than to                  f.normalize.e                 o  f.screen   G                  Traverses to the screen specified by arg. Legal values D                  for arg are: next, prev, last, or a specific screen                  number.           A.5.4 New MWM Action  ;               OSF/Motif Release 1.2 has one new MWM action:a                 o  <Alt> <Esc>  F                  This key combination behaves similarly to f.next_key,G                  except that the window is always raised, regardless off-                  the value of focusAutoRaise.,  I                                                                      A-17t s  e      '     OSF/Motif Release 1.2 Release Notes .     A.6 Changes to the User Interface Language    .     A.6 Changes to the User Interface Language  E           OSF/Motif Release 1.2 has the following changes in the Usera#           Interface Language (UIL):   B           o  There is a new command flag, -s, that enables the use@              of setlocale and the creation of localized Compound              Strings.   C              ________________________ Note ________________________B  @              There is a serious problem in parsing double quotedC              strings with the -s flag. If you need to use this flag A              for parsing double quoted strings, you must obtain a                patch from the OSF.  C              ______________________________________________________   C           o  New UIL syntax now supports font sets and font tables.i  @           o  New UIL syntax now supports wide character strings.  B           o  Support has been added for using widget references as              callback tags.e  D           o  New UIL syntax specifies the resources of automatically              created children.  C           o  Syntax changes to the Widget Meta-Language (WML) allow D              for the definition of automatically created children of              composite widgets.B  >           o  UIL can now use the -wmd file flag to read binary@              databases (WML files) that contain WML information.  ,           o  Mrm includes two new functions:  *              -  MrmOpenHierarchyPerDisplay  E                 This function is the same as the old MrmOpenHierarchy >                 function, except that in the new function, the?                 display is passed as an explicit argument. Thisa3                 function replaces MrmOpenHierarchy.t  %              -  MrmFetchBitmapLiteral   C                 This function fetches a bitmap literal with a depthm                 of 1.        A-18 s  h                            F      _________________________________________________________________  F                                                                  Index      0      A                                 Cardfiler:      _______________________________     XUI version,  2-5*      Access control,  2-3              CDA@        enabling and disabling, 5-9       applications,  2-5, 2-8F      AccessX support                        dynamic font support,  2-69        keyboard enhancements, 2-43          packing,  2-9 <      Ada bindings                           unpacking,  2-10D        Release 1.1.3, 4-8                   WRITE$FONT logical name,2      Answerback message                        2-7F        DECterm, 2-17                     changes to external reference<      Applications                           processing, 4-229        compiling Fortran, 4-18           converters,  1-7 B        for DECwindows Motif, 2-4         converting Asian-language;      Auto Repeat setting                    text files, 1-7 8        changing in DECterm, 2-15         DECfonts,  2-13  E                                          defining logical names,  1-6 B      B______________________________     Display Options...,  2-13  B      Bindings support                    Display PostScript,  2-126        languages, 4-8                    drag-and-drop?      Bookreader                             implementing,  4-19 F        draft-quality printing, 2-4       internationalization support,/        using comments in the                1-5nD          DECW$BOOKSHELF file,  2-4       logical names with convert,0                                             4-227      C______________________________     message,  2-12 D      Calendar                            packing and unpacking error:        after installing, 2-4                messages, 2-11A        double clicking becomes           paper size button,  2-13 B          disabled,  2-4                  PostScript documentation,/        small message dialog box,            2-8 4          2-4                             programmingA                                             external referencing, 3                                                4-22 D                                             interface changes,  4-20  F                                                                Index-1                   =     CDA                                Compiling applications =       programming (cont'd)              See also Applicationse6          logical names with convert     Fortran,  4-18  E             , 4-22                     Compound Document Architectureb/          release notes,  4-19           See CDA 3          restructuring of shareable    Console port 8             images, 4-23                selecting,  1-285          style guide message,  4-22    Console Window ?       restructuring of shareable        console messages,  1-28 ?          images, 4-23                   controlling the initial 9       specifying an options file,          position, 1-29 A          1-5                            defining a global symbol,f/       style guide message,  4-22           1-29 D       Version 1.8A enhancements,        displaying console messages,/          4-20                              1-28DD       viewing PostScript files with        DISABLE (default),  1-28,2          errors, 2-13                         1-298       Watch Progress,  2-13                ENABLE,  1-298     C header files,  4-18                  values,  1-288     Clock                                  WINDOW,  1-287       DECsound for Clock,  2-13         invoking,  1-28m?     Color Customizer,  3-2              selecting the Alternatel=       auto shadowing toggle button,        Console port, 1-28 7          3-8                           Copyright noticee?       building,  3-3                    displaying in a DECterm 6       command summary,  3-4                window, 1-4>       DECterms unaffected,  3-7        Cross-development toolsB       mapping color resources and       OpenVMS Migration Toolkit,/          color cells, 3-6                  4-16rB       modifying DECW$LOGIN.COM,         unpacking save sets,  4-17@          3-4                           Cross-hair cursor support9       running,  3-3                     See Input cursors 5       supported                        Cursor support           applications,  3-2,9          displays,  3-2                 See Input cursors   "       using on multi-head systems,F          3-8                           D______________________________  /       xsetroot_cust demo,  3-8         Debuggere?     Command files                       using in DECterm,  3-17rB       for checking version,  3-13      DEC CDA Base Services, 4-20;     Compatibility                      DECchart applicationrA       shareable images,  4-26           invoking from the Sessionp  8                                            Manager, 2-31       Index-2                    :         DECnet/OSI full names support,    DECterm (cont'd)C           1-4                               system management, 3-15nC         DECsound                            terminal emulator, 2-18 E          notes,  2-14                       user font selection, 2-16 D          prerequisites,  2-14               using the debugger, 3-17E          restrictions,  2-14                virtual terminal support, 2         DECterm                               3-17  7          See also Input cursors           DECW$CDPLAYER.E          answerback message,  2-17          required privileges, 2-23T?          automatic window positioning,    DECW$CONSOLE_GEOMETRYc>             3-16                            global symbol, 5-7@          changing the Auto Repeat         DECW$CONSOLE_SELECTION>             setting,  2-15                  global symbol, 5-7E          DECCRA sequence,  4-24           DECW$INCLUDE:TEXTP.H header 1          DECLFKC sequences,  4-25            fileaD          default font size,  2-23           definition changes, 4-28H          diagnostic crash file,  2-22     DECW$INCLUDE:XMP.H header fileA          diagnostic crash messages,         See also Header files 9             2-22                            changes, 4-28 ?          displaying the copyright           removed definitionsmC             notice,  1-4                       XmHALFLONGBITS, 4-28t?          escape sequences,  2-15               XmLONGBITS, 4-28o8          finish printing option,  5-4     DECW$LOGIN.DATI          graphics,  2-20                    customizing the login screen,e2          hold-screen response time,           3-104             3-16, 5-7                     DECW$UTILS?          initialization,  2-20, 2-21        global symbols, 3-9tH          local echo,  2-17                DECwindows Extensions to Motif3          logicals,  3-15                     , 4-44 F          page-movement sequences,         DECwindows OSF/Motif Toolkit7             4-24                            See Toolkit_?          positioning,  2-15               DECwindows transports ?          /PROCESS problem,  2-19            POSIX support, 4-12XC          programming issues,  4-24        Development support,  4-2 6          ReGIS input cursors,  1-4,       Dialog boxesA             4-25                            changing the position A          ReGIS locator report,  2-23           Set Password, 3-11sB          reporting window size,  1-3           Start Session, 3-119          resizing the terminal,  1-3      Digital writers_D          resource usage,  2-22              sending comments to, iiiC          screen print services,  2-19     Display PostScript Server <          scrolling through the               Extension, 4-45             keyboard,  1-3#          seven-bit printer support,              2-18  I                                                                   Index-3  l  t                   Display serverF       shared memory extension,         F______________________________  @          4-47                          Feedback on documentationC       shared memory pixmaps,  4-53      sending comments to Digital 7       shared memory XImages,  4-49         writers, iii /       supporting AccessX,  2-43        FileView A     Documentation                       application startup,  3-9 <       sending comments to Digital       private logos,  2-340          writers, iii                   removingB     Documentation titles and               LinkWorks Manager verb,2        versions                               2-31@       DECwindows Motif for OpenVMS,        LinkWorks Setup verb,2          5-2                                  2-31=     Drag-and-drop                      Finish printing option 5       using,  2-2, 4-19, 5-4            DECterm,  5-4d5     DXmCSText widget                   Font resourcesX2       input method support,  4-45       See Mosaic.     DXmFormSpaceButtonsEqually         FortranE        routine                          compiling applications,  4-18)9       sizing and spacing widgets,      Full names supporti4          4-45                           DECnet,  1-4;     DXmLAYOUT_LEFT_DOWN constant       Functional resourcese#       DXmNlayoutDirection resource,t2          5-10                           See Mosaic       DXmLAYOUT_LEFT_UP constantF       DXmNlayoutDirection resource,    G______________________________  ?          5-10                          GET_CHAR_STRUCT functioni4     DXmLAYOUT_RIGHT_DOWN constant       access,  5-95       DXmNlayoutDirection resource,    Global symbolsmC          5-10                           DECW$CONSOLE_GEOMETRY,  5-7gD     DXmLAYOUT_RIGHT_UP constant         DECW$CONSOLE_SELECTION,  5-7#       DXmNlayoutDirection resource, F          5-10                          H______________________________3     DXmNlayoutDirection resource       Header filesaC       constants,  5-10                  DECW$INCLUDE:TEXTP.H,  4-28n  A     E                                   DECW$INCLUDE:XMP.H,  4-28s7     _______________________________     languages,  4-8m+     Escape sequences                   Help <       DECterm,  2-15                    invoking through theD                                            workspace Help menu, 2-28@                                        Hold-screen response time7                                         enhancing,  5-7        Index-4     A              7         Home page                         Logical namesoG          See also Mosaic                    defining in the CDA Viewer, 1          creating,  1-10                      1-6a5                                           Login logos B         I______________________________     customizing, 3-13, 5-86         Input cursors                     Login screenA          cross-hair,  4-25                  changing colors, 3-11 =          cross-hair support,  1-4           customizing, 3-10pC          diamond,  4-25                        DECW$LOGIN.DAT, 3-10e/          rubber-band line,  4-25          LogosoG          rubberband-line support,  1-4      modifying the Digital logo,N2          rubber-band rectangle,  4-25         3-11  +          selecting,  4-25                 M I         Internationalization              _______________________________n.          converting files,  1-5           MailB          viewing files,  1-5                color customizer, 2-25F         Internet                            enhanced performance, 2-24B          See also Mosaic                    keyboard actions, 2-24H          browsing,  1-9                        activating pushbuttons inD                                                  dialog boxes,  2-24G         K______________________________        highlighting selections,m5         Keyboard                                 2-24 7          enhancements for disabled          performanceiG             users,  2-43                       turning on the word-wrapo>          scrolling in DECterm,  1-3              option,  2-25F                                             selecting arrow buttons in@         L                                     Read window,  2-25E         _______________________________     setting input focus, 2-25 D         Languages                           tear-off menus, 1-4, 2-3E          available in the Session           using the message button,t2             Manager Language Options          2-252             dialog box,  2-32             MessagesI         LinkWorks Manager                   System Menu Bar: Pseudo Mouse B          removing                             not available,  3-15G             from FileView,  2-31          Migration Toolkit for OpenVMSeG             from Session Manager,           See Cross-development toolse1                2-31                       MIT X11 @          removing from Session Manager      Release 3 Intrinsics=             ,  2-31                            messages, 4-26o@          support removed,  2-24             Release 4 Intrinsics=         Local echo                             messages, 4-26 0          DECterm,  2-17                   Mosaic  7                                             configuringr9                                                processing   I                                                                   Index-5                    ;     Mosaic                             Motif Window Manager <       configuring                       customizing (cont'd)>          processing (cont'd)               colors on multihead  ;             Audio files,  1-11                systems, 2-29s:             GIF files,  1-11               icon box,  2-28@             MIME files,  1-11              icon placement,  2-28<             MPEG files,  1-11           invoking Help,  2-28A             multimedia files,  1-11     modal dialog boxes,  2-28aC             PostScript files,  1-11     moving the icon box off the 7       creating a home page,  1-10          screen, 2-28 9       determining an external           restarting,  2-26 C          viewer, 1-11                   running earlier versions of ;       external view setup                  DECwindows, 2-26eE          examples,  1-12                starting an application as an 5       file location,  1-10                 icon, 2-27vD       firewall,  1-26                   supporting customization forD       font resources,  1-24                monochrome monitors, 2-27E       functional resources,  1-13       truncated icon titles,  2-28, /       mappings,  1-12                      2-29 @       NoProxy resource                  using an icon box,  2-27*          restrictions,  1-27           MWM@       providing as the Internet         See Motif Window Manager          browser, 1-9l       proxy gateway resources,F          1-26                          N______________________________  8       restrictions,  1-26              Node name display8       setting Mosaic X resources,       disabling,  3-12.          1-12                          Notepad@       starting,  1-10                   linking with the Release>          an external program,  1-11        1.1.3 Toolkit, 2-29       supporting the NoProxyF          resource, 1-27                O______________________________3       supporting the ProxyGateway      Options file 8          resource, 1-26                 specifying,  1-58       visual resources,  1-22          OSF/Motif Toolkit8     Motif and XUI widgets               See also Toolkit7       mixing,  4-27                     examples,  4-29c:     Motif Window Manager                   cutpaste,  4-299       centering lines for multiline        dnddemo,  4-29t6          icon titles, 2-29                 Dogs,  4-31;       color customizer,  2-25                 widget,  4-31o:       configuration file,  2-26            helloint,  4-32<       customizing                          hellomotif,  4-33;          colors,  2-27                     MOTIFANIM,  4-33        Index-6n o  s              =         OSF/Motif Toolkit                 POLYCENTER Software A          examples (cont'd)                   Installation utilityx<             MOTIFGIF,  4-34                 description, 1-2D             motif samples,  4-42            using to install OpenVMSG             motifshell,  4-35                 Version 6.2 systems,  1-3 7             periodic,  4-35               POSIX support G             pict,  4-34                     DECwindows transports, 4-12 I             PICT,  4-34                     SYS$POSIX_FORK_CONTROL system <             resource files for example        service,  4-13I                programs,  4-43              using the POSIX fork routine, 2             Square widget,  4-32              4-132             textedit,  4-35               Printing;             uid files for example           Bookreader, 2-4y6                programs,  4-44            Print Screen>             view,  4-38                     default icon, 2-301             xmpiano,  4-40                ProcesscA             xmtravel,  4-43                 creating with virtual E          known problems,  5-12                terminal support,  3-17AH         Overlay support                   Programming environments,  4-2F          See also Window manager          Programming support and XUI,0          colormap                            4-8  A             avoiding potential            Proxy gateway resourcesD6                problems,  1-31              See Mosaic9          modifying applications,  1-31    Public profiles F          sharing overlay colormaps          creating files for layered=             with the Window Manager,          products,  2-34 5             1-31                          Pushbuttons ;                                             DECwindows Mail I         P______________________________        activating in dialog boxes 8         Paint                                    ,  2-24  +          creating private colormaps,      RtI             2-30                          ________________________________=          enhancing performance during     ReGIS input cursors B             basic operations,  2-30         See also Input cursors8         Parameter datasize                  DECterm, 1-43          mismatches,  4-55                Resources ;         Pascal programming                  See also Mosaico6          .PEN files,  4-54                  font, 1-24<         PEN files                           functional, 1-13?          using with Pascal programs,        proxy gateway, 1-26 C             4-54                            setting in Mosaic, 1-12   8                                             visual, 1-22  I                                                                   Index-7                    ?     Rubberband-line cursor support     Start Session dialog boxcD       See Input cursors                 changing the position,  3-11  C     Run-time support,  4-2             Structured Visual NavigationC  /                                         See SVNt=     S______________________________    SVN (Structured Visuall  4     Symbols                              Navigation)B     Save sets                           horizontal separator line,/       unpacking using the BACKUP           4-45 5          commands, 4-17                 widget,  4-45 D     Security options,  5-7             SYS$POSIX_FORK_CONTROL system0       Session Manager,  2-33             service3     Sending comments to Digital         registeringlD        writers, iii                        addresses and parameters,2     Session Manager                           4-13E       color customizer,  2-33              protected shareable imagest4       DECchart application,  2-31             , 4-136       known problems                   System menu bar7          private logos,  2-34           messages,  3-154       language options,  2-32-F       removing                         T______________________________5          LinkWorks Manager verb,       Tear-off menuso=             2-31                        DECwindows Mail,  1-4 3          LinkWorks Setup verb,          using,  5-52;             2-31                        using in Mail,  2-3 /       security options,  2-33          Terminalg6       stopping a process,  2-34         resizing,  1-3.     Set Password dialog box            Toolkit;       changing the position,  3-11      compatibility,  4-3 >     Seven-bit printer support              naming in OSF/MotifC       DECterm,  2-18                          Release 1.2.2 and X11kE     Shareable images                          R5 Shareable Libraries, 1       compatibility,  4-26                    4-5 C       upward compatibility,  4-26          using _Xm routines,  4-4 A     Shareable linkage                   compilation errors,  4-26 E       installing images,  1-30          compiling C modules using the C     Shared memory                          MEMBER_ALIGNMENT switch, /       creating and using XImages,          4-16e@          4-49                           description of OSF/MotifE       extension support,  4-47             Release 1.2.3 environment,        pixmaps,  4-53.     Start Session                          1-1E       blue login screen,  3-2           description of Release 1.2.3, .                                            A-12                                         extensionsB                                            DXmCSText widget,  4-45       Index-8     t              =         Toolkit (cont'd)                  Window Dump utilityuE          locale error message,  2-3         dump to print file (xpr),e2          mixing Motif and XUI Widgets,        2-358             4-27                          Window ManagerA          modifying XmText and               overlay support, 1-31 5             XmTextField translation       Window size F             manager syntax,  4-26           reporting for DECterm, 1-3  &          OSF/Motif Release 1.2.3,  4-2I          release 1.1.3 applications       X______________________________   B             abort,  2-45                  X Image extension,  4-46.          saving programming               XlibF             environments,  4-8              Digital international XlibC         Toolkit shareable images              implementation,  4-58C6          See Shareable images               extensionsH         Translated-image support, 4-14         client side library, 4-47F          running on OpenVMS systems,        Internationalization, 4-568             4-14                            locale, 4-584         Translations                        routinesI          unsupported with XmText               files for Pascal programs, 5             Widget,  2-45                        4-54tG         Transports                             parameter datasize, 4-55 >          POSIX support,  4-12                  xlibint.h, 4-54F                                                XSelectAsyncEvent, 4-55F         U                                      XSelectAsyncInput, 4-55H         _______________________________     vendor pluggable layer, 4-56A         UIL source code                   XmNinputMethod resourceoF          documentation,  5-11               using the shell to specify  B                                               input methods,  4-457         V______________________________   XmText WidgetoE         Version checking command files      unsupported translations, 2           ,  3-13                             2-45C         Virtual terminal support          XSelectAsyncEvent routine C          creating a process,  3-17          allocating memory, 4-55sC         Visual resources                  XSelectAsyncInput routine C          See Mosaic                         allocating memory, 4-55   '         W______________________________            Widgets1          See also Motif and XUI              widgets,  4-27!          sizing and spacing using &             DXmFormSpaceButtonsEqually             ,  4-45c  I                                                                   Index-9 