Compaq DECwindows Motif for OpenVMS _______________________________________ Release Notes April 2001 This manual describes new features, software problems, corrections, restrictions, and documentation changes that pertain to Compaq DECwindows Motif for OpenVMS, Version 1.2-6. Revision/Update Information: This manual supersedes the DECwindows Motif Version 1.2-5 for OpenVMS Release Notes. Operating System: OpenVMS Alpha Version 6.2, 7.1-2, 7.2-1, or 7.3 OpenVMS VAX Version 6.2, 7.1, 7.2, or 7.3 VMS Version 5.5-2 Software Version: Compaq DECwindows Motif for OpenVMS Alpha, Version 1.2-6 Compaq DECwindows Motif for OpenVMS VAX, Version 1.2-6 Compaq Computer Corporation Houston, Texas ________________________________________________________________ April 2001 © 2001 Compaq Computer Corporation COMPAQ, VAX, VMS, the Compaq logo, and the DIGITAL logo Registered in U.S. Patent and Trademark Office. Motif, OSF/1, and UNIX are registered trademarks of The Open Group. All other product names mentioned herein may be the trademarks or registered trademarks of their respective companies. Confidential computer software. Valid license from Compaq or authorized sublicensor required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this publication is subject to change without notice and is provided "AS IS" WITHOUT WARRANTY OF ANY KIND. THE ENTIRE RISK ARISING OUT OF THE USE OF THIS INFORMATION REMAINS WITH THE RECIPIENT. IN NO EVENT SHALL COMPAQ BE LIABLE FOR ANY DIRECT, CONSEQUENTIAL, INCIDENTAL, SPECIAL, PUNITIVE, OR OTHER DAMAGES WHATSOEVER (INCLUDING WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, OR LOSS OF BUSINESS INFORMATION), EVEN IF COMPAQ HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING SHALL APPLY REGARDLESS OF THE NEGLIGENCE OR OTHER FAULT OF EITHER PARTY AND REGARDLESS OF WHETHER SUCH LIABILITY SOUNDS IN CONTRACT, NEGLIGENCE, TORT, OR ANY OTHER THEORY OF LEGAL LIABILITY, AND NOTWITHSTANDING ANY FAILURE OF ESSENTIAL PURPOSE OF ANY LIMITED REMEDY. The limited warranties for Compaq products are exclusively set forth in the documentation accompanying such products. Nothing herein should be construed as constituting a further or additional warranty. ZK6470 The Compaq OpenVMS documentation set is available on CD- ROM. _________________________________________________________________ Contents Preface................................................... xv 1 Introduction 1.1 Features of This Release...................... 1-1 2 General User Release Notes 2.1 General DECwindows Motif Environment.......... 2-1 2.1.1 Changes and Enhancements.................. 2-1 2.1.1.1 Enhanced Web Browser Support............ 2-1 2.1.1.2 Color Customizer Example Program........ 2-3 2.1.1.2.1 Supported Displays..................... 2-3 2.1.1.2.2 Supported Applications................. 2-4 2.1.1.2.3 Building the Color Customizer on OpenVMS Systems........................ 2-4 2.1.1.2.4 Running the Color Customizer........... 2-5 2.1.1.2.5 Modifying the DECW$LOGIN.COM File...... 2-5 2.1.1.2.6 Command Interface Summary ............. 2-6 2.1.1.2.7 Changing the Mapping Between Color Resources and Color Cells.............. 2-7 2.1.1.2.8 DECterm Windows Not Affected........... 2-9 2.1.1.2.9 Changing the Default Value of the Automatic Shadowing Toggle Button...... 2-9 2.1.1.2.10 Using the Customizer on Multihead Systems................................ 2-9 2.1.1.2.11 Using the XSETROOT_CUST.EXE Demonstration Program.................. 2-10 2.1.1.3 Window Dump to Print File (xpr) Utility................................. 2-10 2.1.1.4 Keyboard Enhancements for Disabled Users (Alpha Only)............................ 2-18 2.1.1.4.1 Sticky Keys............................ 2-18 iii 2.1.1.4.2 Mouse Keys............................. 2-18 2.1.1.4.3 Toggle Keys............................ 2-18 2.1.1.4.4 Repeat Keys............................ 2-19 2.1.1.4.5 Slow Keys.............................. 2-19 2.1.1.4.6 Bounce Keys............................ 2-19 2.1.1.4.7 Time Out............................... 2-19 2.1.1.5 Drag and Drop Support................... 2-19 2.1.2 Problems and Restrictions................. 2-20 2.1.2.1 Support Discontinued for Display PostScript.............................. 2-20 2.1.2.2 Unsupported Translations by the Motif XmText Widget........................... 2-20 2.1.2.3 Limited Supported for Tear-Off Menus.... 2-22 2.1.2.4 Printing from Applications Linked Against OSF/Motif Release 1.1.3......... 2-22 2.1.2.5 Access Control Not Explicitly Enabled by Default................................. 2-22 2.2 New Desktop Environment (Alpha Only).......... 2-23 2.2.1 Changes and Enhancements.................. 2-23 2.2.1.1 Screen Saver and Screen Lock Support.... 2-23 2.2.1.2 Full List of Language Variants Displayed............................... 2-24 2.2.1.3 File/Shred Menu Item Handles Multilevel Directories............................. 2-24 2.2.1.4 Display Icon Files from the Find Set Dialog Box.............................. 2-24 2.2.1.5 Selecting Screens on Application Launch.................................. 2-25 2.2.1.6 Front Panel Icons Support MB3 Operations.............................. 2-25 2.2.1.7 Detached Processes...................... 2-26 2.2.1.8 Viewing Reference Pages................. 2-26 2.2.2 Corrections............................... 2-27 2.2.2.1 Session Manager Exits Properly When Saving a Session From an Nonprivileged Account................................. 2-27 2.2.2.2 File Manager Allows Access to Files and Directories That Use ACLs............... 2-28 2.2.2.3 Screen Lock Functions Properly on Multihead Systems ...................... 2-28 2.2.2.4 Can Set Default Display on Multihead Systems................................. 2-28 iv 2.2.2.5 Can Remove the Calendar Icon From a Subpanel................................ 2-28 2.2.2.6 Can Switch Between Workspaces........... 2-29 2.2.2.7 Login Screen Positioned Properly in 640x480 Display Mode.................... 2-29 2.2.2.8 Invalid Characters in a Username or Password No Longer Halt Login........... 2-29 2.2.2.9 Welcome Message Updated................. 2-29 2.2.3 Problems and Restrictions................. 2-29 2.2.3.1 Desktop Applications Disappear When Setting a Home Session.................. 2-30 2.2.3.2 DECwrite Icon Does Not Open DECwrite Program................................. 2-30 2.2.3.3 Viewing TIF Files with dximageview...... 2-30 2.2.3.4 Text Editor Supports Standalone Mode Only.................................... 2-31 2.2.3.5 Text Editor Does Not Support Spell Checking................................ 2-31 2.2.3.6 Text Editor Tab Width is Larger Than Eight Characters........................ 2-31 2.2.3.7 File Names Displayed in UNIX Format..... 2-31 2.2.3.8 Delay When Exiting a Session with Open TPU Windows............................. 2-31 2.2.3.9 Front Panel Clock is an Icon Only....... 2-32 2.2.3.10 ToolTalk Actions Not Supported.......... 2-32 2.2.3.11 Session Manager Save/Restore Limitations............................. 2-32 2.2.3.12 File Manager Limitations................ 2-33 2.2.3.13 Login and Pause Screen Text Field Restrictions............................ 2-34 2.2.3.13.1 Control Characters Not Recognized When Entering Username...................... 2-34 2.2.3.13.2 Return Key Used to Move Between Login Text Fields............................ 2-34 2.2.3.13.3 First Character Discarded When Entering Pause Screen Password.................. 2-34 2.2.3.13.4 Text on the Welcome Screen is Not Displayed.............................. 2-35 2.2.3.14 Using SET DISPLAY/CREATE in DECterm Windows................................. 2-35 2.2.3.15 Font Selection Limitations.............. 2-35 2.2.3.16 Default Workspace Limitations........... 2-35 v 2.2.3.17 Alt + Space Key Does Not Post the Window Menu ................................... 2-36 2.3 Traditional DECwindows Desktop Environment.... 2-36 2.3.1 Problems and Restrictions................. 2-36 2.3.1.1 Alt + Space Key Does Not Post the Window Menu.................................... 2-36 2.4 Bookreader.................................... 2-37 2.4.1 Changes and Enhancements.................. 2-37 2.4.1.1 Bookreader Printing Improved............ 2-37 2.4.2 Corrections............................... 2-37 2.4.2.1 Last Login State Properly Restored (New Desktop Only)........................... 2-37 2.4.2.2 Can Open DECW$BOOK Files Directly from FileView (Alpha Only)................... 2-37 2.4.2.3 Can Specify DECW$BOOKSHELF Files with Blank Lines............................. 2-38 2.4.3 Problems and Restrictions................. 2-38 2.4.3.1 Support for Display PostScript Removed................................. 2-38 2.4.3.2 Including Comment Characters in the DECW$BOOKSHELF File..................... 2-38 2.5 CDA........................................... 2-38 2.5.1 Changes and Enhancements.................. 2-39 2.5.1.1 Dynamic Font Support.................... 2-39 2.5.1.2 WRITE$FONTS Logical Name................ 2-39 2.5.1.3 Enhanced Display Performance............ 2-40 2.5.1.4 Pack and Unpack Applications............ 2-40 2.5.1.4.1 Pack Application Syntax................ 2-41 2.5.1.4.2 Unpack Application Syntax.............. 2-42 2.5.1.4.3 Error Messages......................... 2-43 2.5.1.5 Paper Size Button Renamed............... 2-44 2.5.1.6 New CDA Viewer Error Message............ 2-44 2.5.2 Problems and Restrictions................. 2-44 2.5.2.1 Support for Display PostScript Removed................................. 2-44 2.6 Clock......................................... 2-45 2.6.1 Changes and Enhancements.................. 2-45 2.6.1.1 DECsound Alarm Capability............... 2-45 2.6.2 Corrections............................... 2-45 2.6.2.1 DECW$CLOCK.EXE Process Increments Correctly............................... 2-45 2.7 DECterm....................................... 2-45 vi 2.7.1 Changes and Enhancements.................. 2-46 2.7.1.1 Improved Batch Scrolling................ 2-46 2.7.1.2 New Default Font Sizes.................. 2-46 2.7.1.3 DECterm Resource File Name.............. 2-47 2.7.1.4 Escape Sequences........................ 2-47 2.7.1.5 Scrolling Through the Keyboard.......... 2-48 2.7.1.6 Reporting the DECterm Window Size....... 2-48 2.7.1.7 Resizing the Terminal................... 2-48 2.7.1.8 Timeout for Displaying the Copyright Notice.................................. 2-48 2.7.2 Corrections............................... 2-48 2.7.2.1 Can Specify Non-Standard Font Sets...... 2-49 2.7.2.2 Device Output Files Used by Multiple DECterm Windows Updated Correctly....... 2-49 2.7.2.3 Print Operations That Exceed Quota Generate a Warning Message.............. 2-49 2.7.2.4 Button and Menubar Background Colors Set Properly (New Desktop Only)............. 2-50 2.7.3 Problems and Restrictions................. 2-50 2.7.3.1 Maximum Number of DECterm Windows....... 2-50 2.7.3.2 Changing the Auto Repeat Setting........ 2-50 2.7.3.3 Positioning DECterm Windows............. 2-51 2.7.3.4 User Font Selection..................... 2-51 2.7.3.5 Local Echo.............................. 2-52 2.7.3.6 Answerback Message...................... 2-52 2.7.3.7 Seven-Bit Printer Support............... 2-53 2.7.3.8 Printing to an Attached Printer......... 2-53 2.7.3.9 DECterm Graphics........................ 2-54 2.7.3.10 DECterm Resource Usage.................. 2-54 2.7.3.11 Diagnostic Crash File and Messages...... 2-55 2.7.3.12 VT330 and VT340 Terminal Emulation...... 2-55 2.7.3.13 CREATE/TERMINAL/DETACHED/PROCESS........ 2-56 2.7.3.14 ReGIS Locator Report.................... 2-57 2.8 DECW$CDPLAYER................................. 2-58 2.8.1 Problems and Restrictions................. 2-58 2.8.1.1 Required Privileges..................... 2-58 2.9 DECwindows Mail............................... 2-58 2.9.1 Corrections............................... 2-58 2.9.1.1 Can Drag Messages Between Folders While Text is Selected in an Alternate vii Window.................................. 2-58 2.9.1.2 Can Send Multiple Messages from the DECnotes Interface...................... 2-59 2.9.1.3 Can Pick Inbox on Receipt of New Mail (Alpha Only)............................ 2-59 2.9.1.4 Window Color Options Displayed Correctly (New Desktop Only)...................... 2-59 2.9.2 Problems and Restrictions................. 2-59 2.9.2.1 Support Removed for Display PostScript.............................. 2-59 2.9.2.2 Pasting Messages from the Directory Window.................................. 2-60 2.9.2.3 Responses to Keyboard Actions........... 2-60 2.9.2.4 Using the Color Customizer with DECwindows Mail......................... 2-60 2.10 Extended File Specification (EFS) Support..... 2-61 2.10.1 Changes and Enhancements.................. 2-61 2.10.1.1 File Selection Popup Window............. 2-61 2.10.1.2 FileView Application (DECwindows Desktop Only)................................... 2-61 2.10.1.3 File Manager Application (New Desktop Only)................................... 2-62 2.10.1.4 The Programming Libraries............... 2-62 2.10.2 Corrections............................... 2-62 2.10.2.1 File Manager Corrections for EFS (New Desktop Only)........................... 2-62 2.10.3 Problems and Restrictions................. 2-63 2.10.3.1 File Manager Problems with EFS (New Desktop Only)........................... 2-63 2.10.3.2 Translated Image Support (TIS) Library (Alpha Only)............................ 2-64 2.11 Notepad....................................... 2-65 2.11.1 Problems and Restrictions................. 2-65 2.11.1.1 Notepad Is Linked with the OSF/Motif Release 1.1.3 Toolkit................... 2-65 2.12 Paint......................................... 2-65 2.12.1 Problems and Restrictions................. 2-65 2.12.1.1 Private Colormaps....................... 2-65 2.12.1.2 Slow Performance of Some Paint Operations.............................. 2-66 2.13 Print Screen.................................. 2-66 2.13.1 Problems and Restrictions................. 2-66 2.13.1.1 PostScript Output Problem............... 2-66 viii 2.14 Session Manager and FileView ................. 2-67 2.14.1 Corrections............................... 2-67 2.14.1.1 Can Create DECterm Windows from the Qualifiers Dialog Box (DECwindows Desktop Only)........................... 2-67 2.14.2 Problems and Restrictions................. 2-67 2.14.2.1 Invoking DECchart from the Session Manager Applications Menu............... 2-68 2.14.2.2 Security Options........................ 2-69 2.14.2.3 Using the Color Customizer with Session Manager................................. 2-70 2.14.2.4 Input Focus Change When Starting Private Logo.................................... 2-70 2.14.2.5 Stopping a Session Manager Process...... 2-70 2.15 Window Manager................................ 2-71 2.15.1 Changes and Enhancements.................. 2-71 2.15.1.1 DECwindows XUI Applications............. 2-71 2.15.2 Problems and Restrictions................. 2-71 2.15.2.1 Using the Color Customizer with DECwindows Motif Window Manager......... 2-71 2.15.2.2 Configuration File...................... 2-72 2.15.2.3 Restarting Motif Window Manager......... 2-72 2.15.2.4 Customizing Color-Related Resources for Monochrome Monitors..................... 2-72 2.15.2.5 Moving the Icon Box Off Screen.......... 2-73 2.15.2.6 Customizing Colors on Multihead Systems................................. 2-73 2.15.2.7 Multiline Icon Title Not Centered ...... 2-73 3 System Manager Release Notes 3.1 Installation and Upgrade Information.......... 3-1 3.1.1 Changes and Enhancements.................. 3-1 3.1.1.1 DMA Disabled by Default (Alpha Only).... 3-1 3.1.1.2 DECW$GETPARAMS.COM Modified to Accept Large GBLPAGES Values (Alpha Only)...... 3-1 3.1.1.3 Previously Optional Files Moved......... 3-2 3.1.1.4 Using Shareable Linkages to Install Images (Alpha Only)..................... 3-3 3.1.1.5 Version Checking Available for Command Files................................... 3-4 ix 3.1.2 Problems and Restrictions................. 3-5 3.1.2.1 Check System Parameters Prior to Upgrade................................. 3-5 3.1.2.2 Upgrade Problem After Installing Required PCSI ECO....................... 3-6 3.1.2.3 Reboot Recommended After Installation... 3-7 3.1.2.4 Installation Verification Procedure Error in UIL Compiler................... 3-7 3.2 System Startup Information.................... 3-9 3.2.1 Changes and Enhancements.................. 3-10 3.2.1.1 Starting DECwindows Independently of OpenVMS................................. 3-10 3.2.2 Problems and Restrictions................. 3-10 3.2.2.1 Problem With Delayed DECwindows Startup (Alpha Only)............................ 3-10 3.2.2.2 Color Problem in DECwindows Login Screen.................................. 3-13 3.3 System and Environment Tuning Information..... 3-13 3.3.1 Changes and Enhancements.................. 3-13 3.3.1.1 Displaying an Expanded Welcome Message (New Desktop Only)...................... 3-13 3.3.1.2 Setting the File Manager Refresh Rate (New Desktop Only)...................... 3-14 3.3.1.3 System Tuning for Non-VGA Devices....... 3-14 3.3.1.4 Define DECW$UTILS Global Symbol When Moving DECW$EXAMPLES Global Symbol...... 3-17 3.3.1.5 Customizing the Login Screen............ 3-18 3.3.1.5.1 Customizing the Compaq Logo and Login Screen Colors.......................... 3-18 3.3.1.5.2 Changing Positions of the Start Session and Set Password Dialog Boxes.......... 3-19 3.3.1.5.3 Disabling a Node Name Display in the Start Session Dialog Box............... 3-20 3.3.1.6 Displaying Customized Login Logos....... 3-20 3.3.2 Problems and Restrictions................. 3-20 3.3.2.1 System Hangs With Some Graphics Cards... 3-21 3.3.2.2 Performance Problem with Certain Keymaps................................. 3-21 3.4 Console Window................................ 3-22 3.4.1 Changes and Enhancements.................. 3-23 3.4.1.1 Displaying Console Messages............. 3-23 3.5 DECterm....................................... 3-25 x 3.5.1 Changes and Enhancements.................. 3-25 3.5.1.1 Supported DECterm Logical Names......... 3-25 3.5.1.2 Automatic Window Positioning............ 3-26 3.5.1.3 Improving Hold Screen Response Time..... 3-27 3.5.1.4 Using the Debugger...................... 3-27 3.5.1.5 Virtual Terminal Support................ 3-27 3.5.2 Problems and Restrictions................. 3-28 3.5.2.1 DECterm Window Shrinking Problem........ 3-28 3.6 Session Manager and FileView.................. 3-28 3.6.1 Changes and Enhancements.................. 3-28 3.6.1.1 Implications of the Message, "System Menu Bar: Pseudo Mouse Not Available"... 3-28 3.6.1.2 Detached Processes Created by Default... 3-29 3.6.2 Problems and Restrictions................. 3-30 3.6.2.1 DTSESSION Logging Problem (New Desktop Only)................................... 3-30 3.7 Window Manager................................ 3-30 3.7.1 Changes and Enhancements.................. 3-30 3.7.1.1 Overlay Support......................... 3-30 4 Programmer Release Notes 4.1 OSF/Motif Toolkit Support..................... 4-1 4.2 Run-Time and Programming Environment Support....................................... 4-2 4.2.1 Changes and Enhancements.................. 4-3 4.2.1.1 Available Language Bindings............. 4-3 4.2.1.2 Running Translated Images on OpenVMS Systems................................. 4-4 4.2.2 Problems and Restrictions................. 4-6 4.2.2.1 Support for Display PostScript Removed................................. 4-6 4.2.2.1.1 Impact on DECwindows Motif Applications........................... 4-7 4.2.2.1.2 Impact on Java Applications............ 4-8 4.2.2.2 Using Multithreading and Upcalls (Alpha Only)................................... 4-8 4.2.2.3 Problems Using the DECW$INCLUDE:INTRINSIC.H File........... 4-8 4.2.2.4 DECW$WML.EXE Looks in Current Directory For DECW$WML_TOKENS.DAT................. 4-9 4.2.2.5 DECW$COMPARE_VERSIONS Command File Limitation.............................. 4-9 xi 4.2.2.6 Use of _Xm Routines..................... 4-9 4.2.2.7 Compiling Applications Written in Fortran (Alpha Only).................... 4-10 4.2.2.8 Compiling Applications Written in C..... 4-10 4.3 CDA........................................... 4-11 4.3.1 Changes and Enhancements.................. 4-11 4.3.1.1 Drag-and-Drop Feature Available......... 4-11 4.3.1.2 Changes to the Programming Interface.... 4-12 4.3.1.3 Changes to External Reference Processing.............................. 4-13 4.3.1.4 Message for Style Guide Fallback........ 4-14 4.3.1.5 Using Logical Names with CONVERT Commands................................ 4-14 4.3.1.6 Restructuring Shareable Images.......... 4-15 4.4 DECterm....................................... 4-17 4.4.1 Changes and Enhancements.................. 4-17 4.4.1.1 ReGIS Input Cursors..................... 4-17 4.4.1.2 Page-Movement Escape Sequences.......... 4-18 4.4.1.3 DECCRA Sequence......................... 4-18 4.4.1.4 DECLFKC Sequence........................ 4-18 4.4.2 Corrections............................... 4-18 4.4.2.1 CREATE/TERM/WAIT SHOW PROCESS No Longer Disrupts SYS$INPUT...................... 4-19 4.5 DECTPU for DECwindows Motif................... 4-19 4.5.1 Problems and Restrictions................. 4-19 4.5.1.1 Small Display Monitors and DECTPU....... 4-19 4.6 DECwindows Extensions to Motif................ 4-20 4.6.1 Changes and Enhancements.................. 4-20 4.6.1.1 SVN Widget Supports Extended Selection............................... 4-20 4.6.1.2 DXmCSText Input Method Support.......... 4-20 4.6.2 Problems and Restrictions................. 4-20 4.6.2.1 DXmFormSpaceButtonsEqually Restriction............................. 4-20 4.6.2.2 SVN Widget Does Not Support Horizontal Live Scrolling.......................... 4-21 4.6.3 Corrections............................... 4-21 4.6.3.1 Calling DXmSvnDeleteEntries after DXmSvnAddEntries........................ 4-21 4.7 Display Server Extensions..................... 4-21 xii 4.7.1 Changes and Enhancements.................. 4-21 4.7.1.1 Shared Memory Extension Support (Alpha Only)................................... 4-21 4.7.1.1.1 How to Use Shared Memory Extension..... 4-22 4.7.1.1.2 Using Shared Memory XImages............ 4-23 4.7.1.1.3 Using Shared Memory Pixmaps............ 4-27 4.7.1.2 Specifying Extension Include Files...... 4-28 4.7.1.3 X Image Extension Support............... 4-28 4.7.1.4 Client Side Extension Library Available............................... 4-29 4.8 Internationalization.......................... 4-30 4.8.1 Changes and Enhancements.................. 4-30 4.8.1.1 Using the CDA Viewer to View Asian-Language Text..................... 4-30 4.8.1.1.1 Specifying an Options File............. 4-30 4.8.1.1.2 Defining Logical Names................. 4-31 4.8.1.2 Converting Files That Contain Asian-Language Characters............... 4-32 4.9 XNL Library................................... 4-34 4.9.1 Changes and Enhancements.................. 4-34 4.9.1.1 xnl_parsedatetime....................... 4-34 4.9.1.2 xnl_langinfo............................ 4-34 4.10 Xlib.......................................... 4-34 4.10.1 Changes and Enhancements.................. 4-35 4.10.1.1 X11 Environment Variable Parsing........ 4-35 4.10.1.2 UIDPATH Environment Variable............ 4-35 4.10.1.3 New Default Format for XtResolvePathname....................... 4-36 4.10.1.4 XtAppMainLoop Routine................... 4-36 4.10.1.5 Locale Support in OpenVMS Systems....... 4-36 4.10.1.6 Xlib Internationalization............... 4-37 4.10.1.6.1 Vendor Pluggable Layer................. 4-38 4.10.1.6.2 Compaq Internationalization Xlib Implementation......................... 4-39 4.10.1.7 XSelectAsyncEvent and XSelectAsyncInput Routines ............................... 4-39 4.10.1.8 Command Procedure Builds .PEN Files..... 4-40 4.10.2 Corrections............................... 4-40 4.10.2.1 UNIX Filename Emulation (Alpha Only).... 4-40 4.10.2.2 XmTextField Widget Switches Focus Correctly............................... 4-40 4.10.2.3 XrmoptionStickyArg Produces Correct Results................................. 4-40 xiii 4.10.2.4 PAllHints Macro Corrected............... 4-41 4.10.3 Problems and Restrictions................. 4-41 4.10.3.1 XtOpenDisplay Routine and Case Sensitivity............................. 4-41 4.10.3.2 Parameter/Protocol Datasize Mismatches.............................. 4-41 5 Documentation Release Notes 5.1 Getting Started With the New Desktop.......... 5-1 5.1.1 File Specification Incorrect.............. 5-1 5.2 DECwindows Motif for OpenVMS Applications Guide......................................... 5-1 5.2.1 Enhancing Information About the Finish Printing Option........................... 5-2 5.3 Using DECwindows Motif for OpenVMS............ 5-3 5.3.1 Using the Drag-and-Drop Feature........... 5-3 5.3.2 Using Tear-Off Menus...................... 5-3 5.3.3 Adding Target Screen Options to Application Menu Items.................... 5-4 5.3.4 Changing the Startup Environment.......... 5-4 5.3.5 Enhancing Startup Performance............. 5-5 5.3.6 Enhancing Hold-Screen Response Time....... 5-5 5.4 Managing DECwindows Motif for OpenVMS Systems....................................... 5-6 5.4.1 Global Symbols............................ 5-6 5.4.2 Security Options.......................... 5-6 5.4.3 Displaying a Customized Logo.............. 5-7 5.4.4 Enabling and Disabling Access Control..... 5-8 5.5 DECwindows Motif for OpenVMS Guide to Non-C Bindings...................................... 5-8 5.5.1 GET_CHAR_STRUCT Function.................. 5-8 5.6 VMS DECwindows Guide to Xlib (Release 4) Programming: VAX Binding...................... 5-8 5.7 DECwindows Extensions to Motif................ 5-9 5.7.1 DXmNlayoutDirection Resource Constants.... 5-9 5.8 DECwindows Motif Guide to Application Programming................................... 5-10 5.8.1 UIL Source Code for the OpenVMS DECburger Application............................... 5-10 5.8.2 Help Widget Implementation Code........... 5-10 5.8.3 Help Widget Implementation-Callbacks...... 5-10 5.8.4 Using UIL to Create the Help Widget....... 5-11 xiv A OSF/Motif Release 1.2 Release Notes A.1 Performance Improvements...................... A-1 A.2 Backward Compatibility........................ A-2 A.2.1 Visual and Behavioral Compatibility....... A-2 A.3 Changes and New Features for OSF/Motif Release 1.2........................................... A-3 A.3.1 General Toolkit Changes................... A-3 A.3.1.1 Include File Changes.................... A-3 A.3.2 Change in XT Translations................. A-3 A.3.3 ANSI C Compliance......................... A-4 A.3.4 Display and Screen Specific Data.......... A-4 A.3.5 Drag and Drop............................. A-4 A.3.6 Tear-Off Menus............................ A-5 A.3.7 Insensitive Visuals....................... A-5 A.3.8 Other Visual Changes...................... A-6 A.3.9 Titles for Frames......................... A-6 A.3.10 Audible Warning........................... A-6 A.3.11 Color Enhancements........................ A-7 A.3.12 Baseline Alignment........................ A-7 A.3.13 Expanded Traversal Set.................... A-7 A.3.14 Two-Dimensional Menu Traversal............ A-7 A.3.15 Input Focus............................... A-7 A.3.16 Traversal Access Functions................ A-8 A.3.17 Virtual Keys.............................. A-8 A.3.18 Resource Management....................... A-9 A.3.19 Changes for CUA and Windows Compliance.... A-10 A.4 Changes and Enhancements to Specific Widgets....................................... A-10 A.4.1 XmClipboard............................... A-10 A.4.2 XmCommand................................. A-11 A.4.3 XmList.................................... A-11 A.4.4 XmMessageBox.............................. A-12 A.4.5 XmRowColumn and Menus..................... A-12 A.4.6 XmScrollBar............................... A-12 A.4.7 XmScrolledWindow.......................... A-13 A.4.8 XmSelectionBox, XmFileSelectionBox........ A-13 A.4.9 XmText.................................... A-13 A.4.10 XmTextField............................... A-14 A.4.11 XmToggleButton, XmToggleButtonGadget...... A-15 A.5 Motif Window Manager Enhancements............. A-15 A.5.1 Changes to MWM............................ A-15 A.5.2 New and Enhanced MWM Resources............ A-15 A.5.3 New and Enhanced MWM Functions............ A-16 xv A.5.4 New MWM Action............................ A-17 A.6 Changes to the User Interface Language........ A-18 B OSF/Motif Toolkit Information B.1 OSF/Motif Release 1.2.2 and X11 Release 5 Shareable Libraries........................... B-1 B.2 OSF/Motif Release 1.1.3 Programming Support and XUI....................................... B-4 B.3 DECwindows OSF/Motif Toolkit.................. B-9 B.3.1 Callable OSF/Motif UIL Compiler (Alpha Only)..................................... B-9 B.3.2 Motif Text Widget Translations............ B-9 B.3.3 Upward Compatibility...................... B-10 B.3.3.1 Restrictions on Mixing Motif and XUI Widgets................................. B-11 B.3.4 Compile-Time Incompatibilities in Motif Header Files.............................. B-11 B.4 OSF/Motif Example Programs.................... B-12 B.4.1 Cut and Paste Example Program............. B-12 B.4.2 DNDDemo Example Program................... B-12 B.4.3 Dogs Example Program...................... B-14 B.4.3.1 Dog Widget.............................. B-15 B.4.3.2 Square Widget........................... B-15 B.4.4 Helloint Example Program.................. B-16 B.4.5 Hellomotif Example Program................ B-17 B.4.6 Motifanim Example Program................. B-17 B.4.7 Motifgif and Pict Viewing Programs........ B-18 B.4.8 Motifshell Example Program................ B-19 B.4.9 Periodic Example Program.................. B-19 B.4.10 Textedit Example Program.................. B-19 B.4.10.1 Additional Translations................. B-21 B.4.11 View Example Program...................... B-22 B.4.12 Xmpiano Example Program................... B-24 B.4.13 Motif Sample Programs..................... B-27 B.4.14 Xmtravel Example Program.................. B-28 B.4.15 Resource Files for Example Programs....... B-28 B.4.16 UID Files for Example Programs............ B-29 B.5 OSF/Motif List of Known Problems.............. B-29 xvi C Using the NCSA Mosaic Browser (VMS 5.5-2 Only) C.1 Starting Mosaic Software...................... C-2 C.2 Creating a Home Page.......................... C-3 C.3 Configuring Mosaic to Process Multimedia Files......................................... C-3 C.4 Customizing the Mosaic Browser................ C-5 C.5 Restrictions for Using Mosaic from Behind a Firewall...................................... C-19 C.5.1 ProxyGateway Resource..................... C-19 C.5.2 NoProxy Resource.......................... C-20 Index Examples 3-1 Error Messages Displayed Due to Low Memory in Granularity Hints Region............... 3-11 Tables 1-1 Directory of Changes for Compaq DECwindows Motif for OpenVMS, Version 1.2-6.......... 1-1 2-1 Supported Web Browsers.................... 2-1 2-2 Window Dump to Print File Options......... 2-12 3-1 Previously Optional Files Now Required.... 3-2 3-2 Recommended Quotas for System Tuning...... 3-14 3-3 Moving the Compaq Logo and Changing Login Screen Colors ............................ 3-18 3-4 Changing Position of the Start Session and Set Password Dialog Boxes................. 3-19 3-5 Logical Names Supported by DECterm........ 3-25 4-1 Drag-and-Drop Widgets..................... 4-11 4-2 New Header File Names..................... 4-13 4-3 Names of Shareable Images................. 4-15 4-4 ReGIS Input Cursors-Cursor styles and Values.................................... 4-17 4-5 Asian Language Codes for Options Files.... 4-31 4-6 Logical Names for Specifying Text Encoding.................................. 4-32 xvii 4-7 Languages and Associated Basic Fonts...... 4-33 4-8 Routine Names and Arguments Sent as 16-Bit Values.................................... 4-41 B-1 Names of Shareable Libraries Based on R5........................................ B-2 B-2 Names of Shareable Libraries Based on OSF/Motif Release 1.2.2................... B-2 B-3 Directories for Previous XUI or Motif Programming Environment................... B-7 B-4 View Menu Options......................... B-20 B-5 Textedit Source Files..................... B-20 B-6 Motif Sample Programs..................... B-27 C-1 Functional Resources...................... C-6 C-2 Visual Resources.......................... C-16 C-3 Font Resources............................ C-17 C-4 Proxy Gateway Resources................... C-19 xviii _________________________________________________________________ Preface These release notes describe features, software problems, corrections, restrictions, and documentation changes that pertain to the Compaq DECwindows Motif for OpenVMS, Version 1.2-6 software. The notes in this manual are cumulative from DECwindows Motif Version 1.0 and indicate any undocumented items that still pertain to the Compaq DECwindows Motif for OpenVMS, Version 1.2-6 software. Margin notes indicate the first version of the DECwindows Motif product to which each release note applies. Intended Audience This manual is intended for system managers, users, and programmers who work with the DECwindows Motif software. Document Structure This manual is structured as follows: o Chapter 1 highlights the features, enhancements, and changes that comprise Compaq DECwindows Motif for OpenVMS, Version 1.2-6. o Chapter 2 contains general user release notes for all users. o Chapter 3 contains release notes intended for system managers. o Chapter 4 contains release notes intended for application and system programmers. o Chapter 5 describes additions and corrections to the documentation set. xv o Appendix A contains a subset of the release notes for OSF/Motif Release 1.2. o Appendix B contains release notes for the DECwindows OSF/Motif Toolkit. o Appendix C contains information on starting, using, and customizing the NCSA Mosaic browser on VMS 5.5-2 systems. Related Documents For additional information on the OpenVMS System Software Group (OSSG) products and services, access the following OpenVMS World Wide Web address: http://www.openvms.compaq.com Reader's Comments Compaq welcomes your comments on this manual. Please send comments to either of the following addresses: Internet openvmsdoc@compaq.com Mail Compaq Computer Corporation OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Rd. Nashua, NH 03062-2698 How To Order Additional Documentation Use the following World Wide Web address to order additional documentation: http://www.openvms.compaq.com:8000/ Conventions In this manual, references to OpenVMS are synonymous with the Compaq OpenVMS Operating System. Unless otherwise specified, references to OpenVMS Clusters, VMSclusters, or clusters in this document are synonymous with Compaq OpenVMS Clusters. xvi All uses of DECwindows and DECwindows Motif refer to the Compaq DECwindows Motif for OpenVMS software. Additionally, all uses of DECwindows XUI (X User Interface) refer to the DECwindows product prior to DECwindows Motif Version 1.0. The following conventions are also used in this manual: Ctrl/x A sequence such as Ctrl/x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button. In examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.) In the HTML version of this document, this convention appears as brackets, rather than a box. . . . Horizontal ellipsis points in examples indicate one of the following possibilities: o Additional optional arguments in a statement have been omitted. o The preceding item or items can be repeated one or more times. o Additional parameters, values, or other information can be entered. . Vertical ellipsis points indicate the . omission of items from a code example . or command format; the items are omitted because they are not important to the topic being discussed. ( ) In command format descriptions, parentheses indicate that you must enclose the choices in parentheses if you choose more than one. xvii [ ] In command format descriptions, brackets indicate optional elements. You can choose one, none, or all of the options. (Brackets are not optional, however, in the syntax of a directory name in an OpenVMS file specification or in the syntax of a substring specification in an assignment statement.) [|] In command format descriptions, vertical bars separating items inside brackets indicate that you choose one, none, or more than one of the options. { } In command format descriptions, braces indicate required elements; you must choose one of the options listed. text style This text style represents the introduction of a new term or the name of an argument, an attribute, or a reason. In the HTML version of this document, this convention appears as italic text. italic text Italic text emphasizes important information and indicates complete titles of manuals and variables. Variables include information that varies in system messages (Internal error number), in command lines (/PRODUCER=name), and in command parameters in text (where dd represents the predefined code for the device type). UPPERCASE TEXT Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege. xviii Monospace type indicates code examples and Monospace type interactive screen displays. In the C programming language, monospace type in text identifies the following elements: keywords, the names of independently compiled external functions and files, syntax summaries, and references to variables or identifiers introduced in an example. - A hyphen at the end of a command format description, command line, or code line indicates that the command or statement continues on the following line. numbers All numbers in text are assumed to be decimal unless otherwise noted. Nondecimal radixes-binary, octal, or hexadecimal-are explicitly indicated. xix 1 _________________________________________________________________ Introduction This chapter summarizes the features and enhancements included in Compaq DECwindows Motif for OpenVMS, Version 1.2-6 and provides information regarding the recommended migration paths and the current support policy. 1.1 Features of This Release Compaq DECwindows Motif for OpenVMS, Version 1.2-6 is a maintenance release that delivers a full range of changes and enhancements to your desktop. From faster batch scrolling to support for the Common Desktop Environment (CDE) screen saver and lock extensions, these changes are intended to provide you with a more efficient, flexible DECwindows Motif environment that is further in line with the current OSF/Motif, MIT X11 Release 5 (X11 R5), and CDE standards. Table 1-1 lists the specific changes, enhancements, and corrections implemented in this release of DECwindows Motif and the section in which they are described. Table 1-1 Directory of Changes for Compaq DECwindows Motif __________for_OpenVMS,_Version_1.2-6_______________________ Title________________________________Section_______________ Global Changes Enhanced Web Browser Support Section 2.1.1.1 New Desktop Changes (continued on next page) 1-1 Introduction 1.1 Features of This Release Table 1-1 (Cont.) Directory of Changes for Compaq DECwindows Motif for OpenVMS, Version __________________1.2-6____________________________________ Title________________________________Section_______________ Screen Saver and Screen Lock Section 2.2.1.1 Support Full List of Language Variants Section 2.2.1.2 Displayed File/Shred Menu Item Handles Section 2.2.1.3 Multilevel Directories Display Icon Files from the Find Section 2.2.1.4 Set Dialog Box Session Manager Exits Properly Section 2.2.2.1 When Saving a Session From an Nonprivileged Account File Manager Allows Access to Files Section 2.2.2.2 and Directories That Use ACLs Screen Lock Functions Properly on Section 2.2.2.3 Multihead Systems Can Set Default Display on Section 2.2.2.4 Multihead Systems Can Remove the Calendar Icon From a Section 2.2.2.5 Subpanel Can Switch Between Workspaces Section 2.2.2.6 Login Screen Positioned Properly in Section 2.2.2.7 640x480 Display Mode Welcome Message Updated Section 2.2.2.9 DECwindows Motif Application Changes Bookreader: Last Login State Section 2.4.2.1 Properly Restored (New Desktop Only) (continued on next page) 1-2 Introduction 1.1 Features of This Release Table 1-1 (Cont.) Directory of Changes for Compaq DECwindows Motif for OpenVMS, Version __________________1.2-6____________________________________ Title________________________________Section_______________ Bookreader: Can Open DECW$BOOK Section 2.4.2.2 Files Directly from FileView (Alpha Only) Bookreader: Can Specify Section 2.4.2.3 DECW$BOOKSHELF Files with Blank Lines Clock: DECW$CLOCK.EXE Process Section 2.6.2.1 Increments Correctly DECterm: Improved Batch Scrolling Section 2.7.1.1 DECterm: Can Specify Non-Standard Section 2.7.2.1 Font Sets DECterm: Device Output Files Used Section 2.7.2.2 by Multiple DECterm Windows Updated Correctly DECterm: Print Operations That Section 2.7.2.3 Exceed Quota Generate a Warning Message DECterm: Button and Menubar Section 2.7.2.4 Background Colors Set Properly (New Desktop Only) DECterm: CREATE/TERM/WAIT SHOW Section 4.4.2.1 PROCESS No Longer Disrupts SYS$INPUT DECwindows Mail: Can Drag Messages Section 2.9.1.1 Between Folders While Text is Selected in an Alternate Window DECwindows Mail: Can Send Multiple Section 2.9.1.2 Messages from the DECnotes Interface DECwindows Mail: Can Pick Inbox on Section 2.9.1.3 Receipt of New Mail (Alpha Only) (continued on next page) 1-3 Introduction 1.1 Features of This Release Table 1-1 (Cont.) Directory of Changes for Compaq DECwindows Motif for OpenVMS, Version __________________1.2-6____________________________________ Title________________________________Section_______________ DECwindows Mail: Window Color Section 2.9.1.4 Options Displayed Correctly (New Desktop Only) Session Manager/FileView: Can Section 2.14.1.1 Create DECterm Windows from the Qualifiers Dialog Box (DECwindows Desktop Only) DECwindows Extensions to Motif and Xlib Changes SVN Widget Supports Extended Section 4.6.1.1 Selection X11 Environment Variable Parsing Section 4.10.1.1 UIDPATH Environment Variable Section 4.10.1.2 New Default Format for Section 4.10.1.3 XtResolvePathname UNIX Filename Emulation (Alpha Section 4.10.2.1 Only) XmTextField Widget Switches Focus Section 4.10.2.2 Correctly XrmoptionStickyArg Produces Correct Section 4.10.2.3 Results PAllHints Macro Corrected Section 4.10.2.4 Callable OSF/Motif UIL Compiler Section B.3.1 (Alpha Only) Installation and Tuning Changes DMA Disabled by Default (Alpha Section 3.1.1.1 Only) (continued on next page) 1-4 Introduction 1.1 Features of This Release Table 1-1 (Cont.) Directory of Changes for Compaq DECwindows Motif for OpenVMS, Version __________________1.2-6____________________________________ Title________________________________Section_______________ DECW$GETPARAMS.COM Modified to Section 3.1.1.2 Accept Large GBLPAGES Values (Alpha Only) Displaying an Expanded Welcome Section 3.3.1.1 Message (New Desktop Only) Setting the File Manager Refresh Section 3.3.1.2 Rate_(New_Desktop_Only)____________________________________ 1-5 2 _________________________________________________________________ General User Release Notes This chapter contains information about DECwindows Motif for general users. 2.1 General DECwindows Motif Environment This section contains release notes that pertain to the general DECwindows Motif user environment. This includes common changes, corrections, and restrictions that apply to both the New Desktop and the traditional DECwindows desktop environments. 2.1.1 Changes and Enhancements The following notes describe important changes and enhancements made to the general DECwindows Motif environment. 2.1.1.1 Enhanced Web Browser Support V1.2-6 Compaq DECwindows Motif for OpenVMS, Version 1.2-6 users have several web browser alternatives depending on the version of the OpenVMS operating system that they are running. Table 2-1 shows the current options. Table_2-1_Supported_Web_Browsers___________________________ OpenVMS OpenVMS Platform Version _____________________________________________ ______________VAX_________________Alpha____________________ 5.5-2 NCSA Mosaic 4.2 - (continued on next page) 2-1 General User Release Notes 2.1 General DECwindows Motif Environment Table_2-1_(Cont.)_Supported_Web_Browsers___________________ OpenVMS OpenVMS Platform Version _____________________________________________ ______________VAX_________________Alpha____________________ 6.2 Netscape Navigator Netscape Navigator Gold Gold 3.03 3.03 7.1, 7.1-2, Netscape Navigator Netscape Navigator Gold 7.2, 7.2-1, Gold 3.03 3.03 and_7.3___________________________Mozilla__________________ The following sections provide additional details regarding the individual web browsers and their current level of support. Mozilla The OpenVMS development team has ported the Mozilla browser to the OpenVMS Alpha platform. The latest version of this browser, which is based on Netscape 6, is available from the following Compaq OpenVMS web page: http://www.openvms.compaq.com/openvms/products/ips/register_mozilla.html This page contains installation and running instructions for Mozilla, as well as information about hardware and software prerequisites, system parameters, account quotas, and problem reporting. Netscape Navigator Netscape Navigator Gold Version 3.03 is the current web browser for most versions and platforms of the OpenVMS software. However, support for this browser is expected to end one year after the official release of the Mozilla browser. Compaq will continue to provide the Netscape Navigator Gold software on an "as is," unsupported basis for use on OpenVMS VAX systems and on those OpenVMS Alpha systems that do not support the Mozilla browser. See Table 2-1 for the current list of web browsers supported on OpenVMS systems. You can obtain the Netscape Navigator Gold software from the following Compaq OpenVMS web page: http://www.openvms.compaq.com/openvms/internetnetworks.html 2-2 General User Release Notes 2.1 General DECwindows Motif Environment NCSA Mosaic Compaq provides the National Center for Supercomputing Applications (NCSA) Mosaic Version 2.4 browser on an "as- is, unsupported basis for systems running VMS Version 5.5-2. The software for the Mosaic browser is located in the DECW$UTILS directory and is installed as part of the DECwindows Motif product installation. For detailed information about starting, using, and customizing the NCSA Mosaic browser, see Appendix C. Spyglass Enhanced Mosaic The Spyglass Enhanced Mosaic browser is no longer provided with the DECwindows Motif software and is no longer supported. Note that starting with DECwindows Motif Version 1.2-5, the product installation procedure removes the Spyglass Enhanced Mosaic software. If you are currently using this browser and plan to upgrade your system to DECwindows Motif Version 1.2-5 or later, refer to Table 2-1 to select an alternate browser. 2.1.1.2 Color Customizer Example Program V1.2 The color customizer example program allows you to dynamically control the colors of your workstation environment. Window, icon, and window manager colors can be changed individually or as part of a palette switch. You can control mapping between resources and color cells, as well as the size and contents of the palette set. Also, automatic shadowing with the standard Motif shadowing algorithms is supported. 2.1.1.2.1 Supported Displays The color customizer supports any display using pseudocolor or grayscale visuals. This includes most 4- and 8-plane workstation displays. 2-3 General User Release Notes 2.1 General DECwindows Motif Environment 2.1.1.2.2 Supported Applications The color customizer can affect the colors of any 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. ________________________ Note ________________________ If the color customizer is used to control the colors of applications that have their own color customization dialog boxes (like the Session Manager, Window Manager, and DECwindows Mail), those application-specific color customization dialog boxes may not reflect the correct current color values while the customizer is running the application. This is normal; use the customizer instead of the application- specific dialog box to change these color values. ______________________________________________________ 2.1.1.2.3 Building the Color Customizer on OpenVMS Systems To build the color customizer on OpenVMS systems, perform the following steps: 1. Copy the files to a private directory. For example: $ SET DEFAULT SYS$LOGIN $ CREATE/DIRECTORY [.CUSTOMIZER] $ SET DEFAULT [.CUSTOMIZER] $ COPY DECW$EXAMPLES:CUSTOM.C [] $ COPY DECW$EXAMPLES:CUSTOM.UIL [] $ COPY DECW$EXAMPLES:CUSTOMIMAGE.DAT [] $ COPY DECW$EXAMPLES:XSETROOT_CUST.C [] $ COPY DECW$EXAMPLES:BUILD_CUSTOMIZER.COM [] 2. Build the customizer using the following command: $ @BUILD_CUSTOMIZER.COM This command procedure creates the following output files: CUSTOM.UID CUSTOM.EXE XSETROOT_CUST.EXE 2-4 General User Release Notes 2.1 General DECwindows Motif Environment 2.1.1.2.4 Running the Color Customizer To run the color customizer, perform the following steps: 1. Copy the files CUSTOM.UID and CUSTOM.EXE, which were created during the customizer build, to the directory where the customizer will be run. A typical location is the directory SYS$LOGIN or the directory DECW$USER_ DEFAULTS. 2. Copy the files CUSTOM.DAT and DXMDEFAULTS.DAT from the directory DECW$EXAMPLES to the same location as you copied the files in step 1. The same typical locations apply. 3. Run the executable file CUSTOM.EXE as follows: $ RUN CUSTOM ________________________ Note ________________________ Only the colors of applications invoked after the customizer starts will be affected. For this reason, start the customizer as the first X application during the login process. ______________________________________________________ 2.1.1.2.5 Modifying the DECW$LOGIN.COM File As noted in Section 2.1.1.2.4, the color customizer should be the first X application started during the login process. Do this by starting it as a subprocess from within the DECW$LOGIN.COM file. Add a command to wait approximately 10 seconds between customizer startup and the startup of other applications. For example, add the following lines to the DECW$LOGIN.COM file: $! Starting the color customizer $ DISPLAY = F$LOGICAL("DECW$DISPLAY") $ SPAWN/NOWAIT/OUTPUT='DISPLAY' RUN SYS$LOGIN:CUSTOM.EXE $ WAIT 0:0:10 See Using DECwindows Motif for OpenVMS and Managing DECwindows Motif for OpenVMS Systems for more information on the file DECW$LOGIN.COM. 2-5 General User Release Notes 2.1 General DECwindows Motif Environment 2.1.1.2.6 Command Interface Summary A box containing a list of available palettes is in the leftmost section of the Color Customizer window. Click on the desired palette to see the colors take affect. Below the palettes are two arrays of colored buttons, representing the dynamically allocated color cells for normal and shadow colors. To find out what resources are affected by a color cell, click and hold the arrow button next to the color cell. ________________________ Hint ________________________ As a shortcut, you can click on the screen facsimile in the rightmost corner of the dialog box. If the portion you click on is colored by one of the resource values controlled by the customizer, the pop-up window for the appropriate color button is displayed. ______________________________________________________ To modify a single color cell, click on the corresponding color button. A colormix widget pops up; as you modify the color, these modifications are reflected in your workstation environment. Use the colormix widget reset button to return to the starting color at any time. You can also change the color cell you are modifying by clicking on a different color button while the colormix widget is displayed. The automatic shadowing option causes shadow and select colors to be automatically updated when their corresponding background colors are changed. The standard Motif shadowing algorithms are used for these calculations. Use the File menu to modify, add, and delete color palettes as follows: o To modify an existing palette, select the palette, change the colors, and choose Save Palette from the File menu. o To add a new palette, select an existing palette, modify the colors as necessary, and choose Save Palette As... from the File menu. A message box prompts you for the name of the new palette. 2-6 General User Release Notes 2.1 General DECwindows Motif Environment o To delete a palette, select the palette and choose Delete Palette from the File menu. Changes made through the File menu automatically update the CUSTOM.DAT file, which contains the resource defaults. The File menu Exit button causes the customizer application to exit. A warning dialog is displayed first. Note that the color cells allocated by the customizer (and used by the currently running applications) will be deallocated. After the customizer exits, if the colors of the currently running applications are not correct, the applications should be restarted to restore normal colors. Usually, there is no need to exit the color customizer; it is typically kept running at all times, like the Session Manager. 2.1.1.2.7 Changing the Mapping Between Color Resources and Color Cells The file DXMDEFAULTS.DAT allows you to control how many dynamic color cells are allocated and what resources are affected. This file contains resource specifications like the following: *background: DXmDynamicWindowBackground *foreground: DXmDynamicWindowForeground *topShadowColor: DXmDynamicWindowTopShadow When the customizer is started, the file DXMDEFAULTS.DAT is written to a property on the root window. Any application that is subsequently run and that uses the correct X Toolkit Library merges these resources with its normal resource database. Resource specifications in this file take precedence over specifications with equivalent resource names in other resource default files. The resource values within the file DXMDEFAULTS.DAT have a special format. For each unique color value in this file that begins with the string "DXmDynamic", a color button is created in the color customizer. If 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" for purposes of automatic shadowing. If a color value named 2-7 General User Release Notes 2.1 General DECwindows Motif Environment "DXmDynamicScreenBackground" is encountered, the color cell allocated is used by the customizer to set the root window background color. You can edit the file DXMDEFAULTS.DAT and define resources to use the same color cells. You can have separate dynamic color cells, for scrollbar widgets or for your DECwindows Mail application, for example, by adding the following lines to the file DXMDEFAULTS.DAT: Mail*background: DXmDynamicMyMailBackground Mail*foreground: DXmDynamicMyMailForeground Mail*topShadowColor: DXmDynamicMyMailTopShadow Mail*bottomShadowColor: DXmDynamicMyMailBottomShadow Adding the previous lines to the file DXMDEFAULTS.DAT and restarting the customizer causes four new color cells to be allocated and four new color buttons to be added to the customizer interface. These buttons are assigned default color values (usually black or white) for each palette. These defaults can then be modified for each palette through the customizer interface. ________________________ Note ________________________ The text of the DXMDEFAULTS.DAT file is read and parsed by the color customizer. The parsing algorithm does not allow comments, incorrect spacing, or incorrect resource specifications. If this file or the CUSTOM.DAT resource file become corrupt, the customizer cannot start correctly. To resolve the problem, copy the versions of CUSTOM.DAT and DXMDEFAULTS.DAT from the DECW$EXAMPLES directory into your login directory. ______________________________________________________ 2-8 General User Release Notes 2.1 General DECwindows Motif Environment 2.1.1.2.8 DECterm Windows Not Affected The color customizer does not affect the colors of DECterm windows. To change the colors of DECterm windows, copy the DECterm resource specifications from the file DXMDEFAULTS.DAT and add them to the DECterm resource defaults file DECW$USER_ DEFAULTS:DECW$TERMINAL_DEFAULT.DAT. For example, add the following lines to the DECterm resource defaults file: . . . DECW$TERMINAL.main.terminal.background: DXmDynamicTerminalBackground DECW$TERMINAL.main.terminal.foreground: DXmDynamicTerminalForeground This allows the DECterm window colors to be customized with the color customizer. 2.1.1.2.9 Changing the Default Value of the Automatic Shadowing Toggle Button The default value of the automatic shadowing toggle button is set using the Custom.autoShadow resource in the CUSTOM.DAT file as follows: Custom.autoShadowing: False The default value is True. 2.1.1.2.10 Using the Customizer on Multihead Systems The color customizer affects only applications started on the same screen as the customizer. On multihead systems, 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 is invoked once and affects all applications regardless of where they are started. This mode is invoked by modifying the Custom.multiScreen resource in the CUSTOM.DAT file as follows: Custom.multiScreen: True The default value is False. 2-9 General User Release Notes 2.1 General DECwindows Motif Environment 2.1.1.2.11 Using the XSETROOT_CUST.EXE Demonstration Program The XSETROOT_CUST.EXE demonstration program, created during the customizer build, is a modified version of the MIT utility program xsetroot that is used to set a bitmap on the root window. The XSETROOT_ CUST.EXE program uses DXmDynamicScreenBackground and DXmDynamicScreenForeground as the background and foreground colors of the specified bitmap. If your DXMDEFAULTS.DAT file contains entries for these two dynamic colors, then use the customizer to dynamically modify the colors of your bitmap. For example: $ XSETROOT_CUST :== "$SYS$LOGIN:XSETROOT_CUST.EXE" $ XSETROOT_CUST -BITMAP your_xbm_file.XBM 2.1.1.3 Window Dump to Print File (xpr) Utility V1.2 The Window Dump to Print File utility prints an X Window dump using the xpr program. The xpr program receives as input a window dump file produced by the Window Dump utility (xwd) and formats it for output on the following printers: o PostScript o DIGITAL LN03 or LA100 o IBM PP3812 page printer o HP LaserJet (or other PCL printers) o HP PaintJet To use the xpr program, define xpr as a user-defined command: $ xpr == "$DECW$UTILS:XPR" You must specify an input file. The xpr program prints the largest possible representation of the window on the output page. Options allow the user to add headers and trailers, specify margins, adjust the scale and orientation, and append multiple window dumps to a single output file. 2-10 General User Release Notes 2.1 General DECwindows Motif Environment Use the following command format: $ xpr input_file [options...] Options include: -append filename -noff -output filename -compact -device {ln03 | la100 | ps | lw | pp | ljet | pjet | pjetxl} -dump -gamma correction -gray {2 | 3 | 4} -height inches -width inches -header string -trailer string -landscape -portrait -left inches -top inches -noposition -nosixopt -plane n -psfig -render type -report -rv -scale scale -slide -split n-pages Table 2-2 defines the available options. 2-11 General User Release Notes 2.1 General DECwindows Motif Environment Table_2-2_Window_Dump_to_Print_File_Options________________ Option___________Description_______________________________ -device devtype Specifies the device on which the file is printed. Currently supported devices: la100 DIGITAL LA100. ln03 DIGITAL LN03. ljet HP LaserJet series and other monochrome PCL devices such as ThinkJet, QuietJet, RuggedWriter, HP series, and HP-series printers. pjet HP PaintJet (color mode). pjetxl HP PaintJet XL Color Graphics Printer (color mode). pp IBM PP3812. ps PostScript printer. lw LaserWriter is equivalent to - device ps and is provided only for backwards compatibility. The default is PostScript. -scale scale Affects the size of the window on the page. The PostScript, LN03, and HP printers can translate each bit in a window pixel map into a grid of a specified size. For example, each bit might translate into a 3x3 grid. This would be specified by -scale 3. By default, a window is printed with the largest scale that will fit onto the page for the specified orientation. -height inches Specifies the maximum height of the page. -width inches Specifies the maximum width of the page. -left inches Specifies the left margin in inches. Fractions are allowed. By default the window is centered in the page. (continued on next page) 2-12 General User Release Notes 2.1 General DECwindows Motif Environment Table_2-2_(Cont.)_Window_Dump_to_Print_File_Options________ Option___________Description_______________________________ -top inches Specifies the top margin for the picture in inches. Fractions are allowed. -header string Specifies a header string to be printed above the window. -trailer string Specifies a trailer string to be printed below the window. -landscape Forces the window to be printed in landscape mode. By default, a window is printed so that its longest side follows the long side of the paper. -portrait Forces the window to be printed in portrait mode. By default a window is printed so that its longest side follows the long side of the paper. -plane number Specifies which bit plane to use in an image. The default is to use the entire image and map values into black and white based on color intensities. -gray Uses a 2x2, 3x3, or 4x4 gray scale conversion on a color image, rather than mapping to strictly black and white. This doubles, triples, or quadruples the effective width and height of the image. -rv Forces the window to print in reverse video. -compact Uses run-length encoding for compact representation of windows with white pixels. -output Specifies an output file name. filename -append Specifies a file name previously produced filename by xpr to which the window is to be appended. (continued on next page) 2-13 General User Release Notes 2.1 General DECwindows Motif Environment Table_2-2_(Cont.)_Window_Dump_to_Print_File_Options________ Option___________Description_______________________________ -noff When specified in conjunction with - append, the window appears on the same page as the previous window. -split n-pages Allows the user to split a window onto several pages. This might be necessary for very large windows that would otherwise cause the printer to overload and print the page in an obscure manner. -psfig Suppresses translation of the PostScript picture to the center of the page. -density dpi Indicates dot-per-inch density to be used by the HP printer. -cutoff level Changes the intensity level where colors are mapped to either black or white for monochrome output on a LaserJet printer. The level is expressed as percentage of full brightness. Fractions are allowed. -noposition Causes header, trailer, and image positioning command generation to be bypassed for LaserJet, PaintJet and PaintJet XL printers. -gamma Changes the intensity of the colors correction printed by the PaintJet XL printer. The correction is a floating-point value in the range 0.00 to 3.00. Consult the operator's manual to determine the correct value for the specific printer. -render Allows the PaintJet XL printer to algorithm render the image with the best quality versus performance tradeoff. Consult the operator's manual to determine the available algorithms. (continued on next page) 2-14 General User Release Notes 2.1 General DECwindows Motif Environment Table_2-2_(Cont.)_Window_Dump_to_Print_File_Options________ Option___________Description_______________________________ -slide filename Allows overhead transparencies to be printed using the PaintJet and PaintJet _________________XL_printers.______________________________ The program contains the following limitations: o Support for PostScript output currently cannot use the -append, -noff, or -split options. o The -compact option is only supported for PostScript output. It compresses white space but not black space, so it is not useful for reverse-video windows. o For color images, map directly to PostScript image support. Program limitations with an LN03 printer: o The current version of xpr can print most X Windows that are not larger than two-thirds of the screen. 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 incorrectly print large or complex windows. The two most common errors encountered are "band too complex" and "page memory exceeded" and are described as follows: - "band too complex" A window may have a particular six pixel row that contains too many changes (from black to white to black). This causes the printer to drop part of the line and possibly drop parts of the page. The printer flashes the number "1" on its front panel when this problem occurs. A possible solution to this problem is to increase the scale of the picture or to split the picture onto two or more pages. - "page memory exceeded" 2-15 General User Release Notes 2.1 General DECwindows Motif Environment This occurs if the picture contains too much black space, or if the picture contains complex half-tones, such as the background color of a display. When this problem occurs, the printer automatically splits the picture onto two or more pages. The number "5" may flash on its front panel. As a possible solution to the problem, it might be necessary to either cut and paste or to rework the application to produce a less complex picture. Program limitations with a LA100 printer: o The picture is always printed in portrait mode. o The scale is ignored. o The scale factor will be different in the horizontal and vertical directions. Program limitations with an HP printer: o If the -density option is not specified, 300 dots-per- inch (dpi) is assumed for the ljet device and 90-dpi for the pjet device. The LaserJet printer supports 300-, 150-, 100-, and 75-dpi. Consult the operator's manual to determine the densities supported by other printers. o If the -scale option is not specified, the image is expanded to fit the printable page area. o The default printable page area is 8x10.5 inches. Other paper sizes can be accommodated using the -height and -width options. o Note that a 1024x768 image fits the default printable area when processed at 100-dpi with scale=1; the same image can also be printed using 300-dpi with scale=3, but it requires more data to be transferred to the printer. o The xpr program may be tailored for use with monochrome PCL printers other than the LaserJet. To print on a ThinkJet (HP 2225A) printer, invoke xpr as follows: xpr -density 96 -width 6.667 filename To print black-and-white output on a PaintJet printer, invoke xpr as follows: 2-16 General User Release Notes 2.1 General DECwindows Motif Environment xpr -density 180 filename o The monochrome intensity of a pixel is computed as 0.30*R + 0.59*G + 0.11*B. If the computed intensity of a pixel is less than the -cutoff level, it prints white. This maps light-on-dark display images to black-on-white hard copy. The default cutoff intensity is 50% of full brightness. For example, specifying -cutoff 87.5 means that a pixel will be displayed as black if the computed intensity is less than 85% of full brightness. o A LaserJet printer must be configured with sufficient memory to print the image. To print a full page at 300- dpi, approximately 2 MB of printer memory is required. o Color images are produced on the PaintJet printer at 90-dpi. The PaintJet is limited to 16 colors from its 330 color palette on each horizontal print line. The xpr program issues a warning message if more than 16 colors are encountered on a line. Xpr programs the PaintJet for the first 16 colors encountered on each line and uses the nearest matching programmed value for other colors on the line. o Specifying the -rv option on the PaintJet printer causes black and white to be interchanged on the output image. No other colors are changed. o Multiplane images must be recorded by xwd in ZPixmap format. Single-plane (monochrome) images may be in either XYPixmap or ZPixmap format. o Some PCL printers do not recognize image positioning commands. Output for these printers is not centered on the page, and header and trailer strings may not appear where expected. o The -gamma and -render options are supported only on the PaintJet XL printers. o The -slide option is not supported on LaserJet printers. o The -split option is not supported on HP printers. o The -gray option is not supported on HP or IBM printers. 2-17 General User Release Notes 2.1 General DECwindows Motif Environment 2.1.1.4 Keyboard Enhancements for Disabled Users (Alpha Only) V1.2 On OpenVMS Alpha systems starting with DECwindows Motif Version 1.2 for OpenVMS, the AccessX extension provides features to help disabled users interact with workstations. These features make it easier to use the keyboard and mouse. You can interact with workstations by entering commands and manipulating menus and dialog boxes. However, with AccessX features, performing these input operations is even easier. A client application is provided to enable and customize the AccessX features. To run this application, enter the following commands: $ SET DEFAULT DECW$EXAMPLES $ RUN AccessX Online help is available by selecting the Help menu option. AccessX offers the features described in the following sections. 2.1.1.4.1 Sticky Keys The Sticky Keys feature allows you to perform multikey operations with one hand, one finger, or a mouth stick. You can use this feature to enter uppercase letters or punctuation characters without having to hold down the Shift key while pressing the character key. This feature also makes it easier to enter control characters such as Ctrl/C. 2.1.1.4.2 Mouse Keys The Mouse Keys feature lets you map actions that you would perform with a mouse to keys on the numeric keyboard or other keys that you specify. With this feature, you can use one finger or a mouth stick to move the cursor to different areas of the screen, manipulate menus, and select, cut, and paste text. 2.1.1.4.3 Toggle Keys The Toggle Keys feature provides audio feedback when the Shift Lock (Caps Lock) key is pressed. This feature helps users who might have difficulty seeing the keyboard light indicator for the Shift Lock key or users who are using a keyboard that does not provide light indicators for any keyboard settings. 2-18 General User Release Notes 2.1 General DECwindows Motif Environment 2.1.1.4.4 Repeat Keys The Repeat Keys feature allows you to adjust the auto-repeat keyboard mechanism speed or to turn it off entirely. With this feature turned on, you can set your keyboard so that holding down a key for a longer than average time does not cause a repeat entry of that character. 2.1.1.4.5 Slow Keys The Slow Keys feature makes the keys less likely to respond 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 light keystrokes that are held only for a moment. 2.1.1.4.6 Bounce Keys The Bounce Keys feature eliminates the problem of pressing a key and then accidentally pressing it again before moving to another key. You can set this feature to tell the computer not to process a second pressing of a key unless a certain length of time elapses between each pressing. 2.1.1.4.7 Time Out The Time Out feature shuts off the AccessX features on a workstation after a specified period of time. If you are sharing a workstation and have set AccessX features, the settings are automatically turned off before the next use. To retain the AccessX settings at all times, you can turn off the Time Out feature. 2.1.1.5 Drag and Drop Support V1.2 All DECwindows Motif applications except Notepad support the drag-and-drop feature. DECwindows Mail supports the drag-and-drop feature in all windows except the main message area, where DECwindows Mail has its own drag-and- drop; you can use MB2 to move messages around with the SVN interface. The drag-and-drop feature lets you move or copy screen objects; this feature is provided primarily for programmers who choose to incorporate drag-and-drop into their applications. For example, you can move text from a text entry area and paste it elsewhere. Refer to Section 5.3.1 for instructions on using drag and drop. 2-19 General User Release Notes 2.1 General DECwindows Motif Environment 2.1.2 Problems and Restrictions The following notes describe the known problems and restrictions that currently exist in the general DECwindows Motif environment. 2.1.2.1 Support Discontinued for Display PostScript Starting August 1, 1998, Compaq discontinued support for Adobe Display PostScript software. Compaq took this action because Adobe Systems Incorporated discontinued its former ongoing support for Display PostScript. This action has had a varying degree of impact on the behavior of those DECwindows Motif applications that used the Adobe Display PostScript software. For example, starting with DECwindows Motif Version 1.2-6, Bookreader can no longer display graphics in PostScript format. For information about the effects of this action on specific DECwindows applications, see the following release notes: o Bookreader, Section 2.4.3.1 o CDA, Section 2.5.2.1 o DECwindows mail, Section 2.9.2.1 To learn about the possible impact to user-written and third-party applications designed for the DECwindows Motif environment, see Section 4.2.2.1. 2.1.2.2 Unsupported Translations by the Motif XmText Widget V1.2-3 By default, the Motif XmText widget does not support the following translations for Versions 1.1, 1.2, and 1.2-3 of the DECwindows Motif product: F12: beginning-of-line() F13: delete-previous-word() Ctrl e: end-of-line() Ctrl j: delete-previous-word() Ctrl h: beginning-of-line() Ctrl r: redraw-display() Ctrl u: delete-to-start-of-line() ~Ctrl ~Meta ~Shift Altspace: self-insert() 2-20 General User Release Notes 2.1 General DECwindows Motif Environment These translations are preferred by OpenVMS users to ensure consistency with the DCL command line interface. The DECwindows Motif Session Manager defines translations so that they can be used by applications that are displayed to an OpenVMS display server. If you display your applications on a different display server (for example, on a PC or Compaq Tru64 UNIX workstation), these translations are not functional. To enable these translations, add the following lines to your applications default file (for example, DECW$USER_ DEFAULTS:app_name.DAT or to the file DECW$USER_ DEFAULTS:XDEFAULTS.DAT): *XmText.translations: #override \n\ F12: beginning-of-line()\n\ F13: delete-previous-word()\n\ Ctrle: end-of-line()\n\ Ctrlj: delete-previous-word()\n\ Ctrlh: beginning-of-line()\n\ Ctrlr: redraw-display()\n\ Ctrlu: delete-to-start-of-line()\n\ ~Ctrl ~Meta ~Shift Altspace: self-insert()\n You can copy the text for these translations from the file DECW$SYSTEM_DEFAULTS:DECW$LOGIN.DAT. Enabling these translations does not affect the standard Motif translations, such as Alt-right for end-of-line or Ctrl-right for end-of-word. ________________________ Note ________________________ If you add lines to the file DECW$USER_ DEFAULTS:XDEFAULTS.DAT file, startup performance for all applications is slightly degraded. ______________________________________________________ 2-21 General User Release Notes 2.1 General DECwindows Motif Environment 2.1.2.3 Limited Supported for Tear-Off Menus V1.2-3 The following applications do not support tear-off menus: o CDA Viewer o Notepad o Print Screen Refer to Section 5.3.2 for instructions on tearing off a menu and closing a tear-off menu. 2.1.2.4 Printing from Applications Linked Against OSF/Motif Release 1.1.3 V1.2 Applications that are linked against OSF/Motif Release 1.1.3 may end abruptly when you attempt to print on systems that do not have print queues. Any layered products that linked against the OSF/Motif Release 1.1.3 libraries and use the standard DECwindows print dialog ("print widget") are also affected. As a possible solution, either avoid displaying the DECwindows print dialog, or define a print queue on your system. The print queue does not have to be connected to a printer to accept print jobs. Assign a name to the print queue that indicates the print queue is not connected to a printer, for example, NULL_PRINTER. 2.1.2.5 Access Control Not Explicitly Enabled by Default V1.0 DECwindows Motif does not enable access control by default. Instead, the product uses access control set by the server. The DECwindows X11 display server enables access control at startup time. To force the DECwindows Session Manager to enable or disable access control explicitly at login time, you can define one of the following logical names: $ DEFINE/SYSTEM/EXECUTIVE DECW$LOGIN_ACCESS_CONTROL ENABLE $ DEFINE/SYSTEM/EXECUTIVE DECW$LOGIN_ACCESS_CONTROL DISABLE 2-22 General User Release Notes 2.1 General DECwindows Motif Environment If the logical name is not defined or if it is defined to some other value, such as "SERVER", DECwindows login neither enables nor disables access control. In most cases, it should not be necessary to define the logical name. 2.2 New Desktop Environment (Alpha Only) Compaq DECwindows Motif for OpenVMS, Version 1.2-6 product incorporates the Common Desktop Environment (CDE) Motif 1.0 Toolkit (OSF/Motif Release 1.2.5) and is based on Release 5 of the X Window System Intrinsics. As with previous releases, Compaq DECwindows Motif for OpenVMS, Version 1.2-6 continues to provide run-time support for the XUI user interface and Toolkit. Application development is supported for the CDE Motif 1.0 Toolkit. On Alpha systems, the New Desktop is derived from the Common Desktop Environment (CDE). The user interface that was provided in previous versions of DECwindows Motif is referred to as the DECwindows desktop. The system manager can choose to install either the New Desktop or the DECwindows desktop, or both. In addition, the user can select which desktop is started during the DECwindows startup procedure. This section contains release notes that pertain to the New Desktop environment. 2.2.1 Changes and Enhancements The following notes describe changes and enhancements made to the New Desktop environment. 2.2.1.1 Screen Saver and Screen Lock Support V1.2-6 New Desktop now supports the Screen Saver Extension (MIT- SCREEN-SAVER), which is available systems running on OpenVMS Alpha Version 7.1 or greater. This extension enables you to use the following features, which are available from the Style Manager Screen dialog box: o Screen saver-Prevents screen burn-in by displaying one or more screen savers after a specific timeout period. 2-23 General User Release Notes 2.2 New Desktop Environment (Alpha Only) You can set both the timeout period and the amount of time each screen saver is displayed onscreen. Sample screen savers are available from CDE$SYSTEM_ DEFAULTS:[EXAMPLES.DTSCREEN]. To learn how to create additional screen savers and make them available to the Style Manager, see Getting Started With the New Desktop. o Screen lock-Secures your current New Desktop session(s) by locking the Front Panel after a specific timeout period. Once locked, a user must enter the account password of the home session password to unlock the desktop. For more information on using the screen saver and screen lock components of the Style Manager, see the online help for the Style Manager application. 2.2.1.2 Full List of Language Variants Displayed V1.2-6 The Login Screen has been modified to recognize all available language variants. Now when you select the Language item from the Options menu, all available language variants are listed and ready for selection. This enables you to login and create a localized New Desktop session that displays the Front Panel, desktop, and menu items according to the options associated with the selected variant. 2.2.1.3 File/Shred Menu Item Handles Multilevel Directories V1.2-6 The File Manager now allows you to delete items that contain one or more subdirectories. Once dragged or placed into the Trash Can using the Select/Put In Trash option, you can select File/Shred to quickly dispose of the item and its contents, including any underlying subdirectories and files. 2.2.1.4 Display Icon Files from the Find Set Dialog Box V1.2-6 When defining or editing an application icon with Create Action application, you can now view and select from a list of available icon files in the associated Find Set dialog box. 2-24 General User Release Notes 2.2 New Desktop Environment (Alpha Only) 2.2.1.5 Selecting Screens on Application Launch V1.2-5 You can graphically select the screen on which a new application is displayed when launched from either the Front Panel, the File Manager, or the Application Manager. By default, the new application appears on the current screen (that is, the screen containing the mouse pointer). The feature allows you to drop an application icon from the File Manager or Application Manager onto one of the numbered screen controls of the Set Default Screen window. This starts the application on the selected screen without changing the current screen. The Set Default Screen window is activated as before by selecting the "Set Default Screen" application in the Application Manager's Desktop Tools folder. You can start a separate instance of the Set Default Screen window on each screen. The highlighting of the default screen is synchronized across all instances of the Set Default Screen window. 2.2.1.6 Front Panel Icons Support MB3 Operations V1.2-4 The New Desktop Front Panel supports mouse button 3 (MB3) operations. When the cursor is placed over a Front Panel icon and you press MB3, a subpanel or menu appears. The menu items are as follows: o Top item-The label of the menu. o Second item-The application that starts if you single click on the icon. o Third item-Add or delete a subpanel, depending on whether a subpanel already exists for the control panel. _______________________ Caution _______________________ If the third item is "Delete Subpanel", this change is difficult to reverse without reinstalling the kit. ______________________________________________________ 2-25 General User Release Notes 2.2 New Desktop Environment (Alpha Only) 2.2.1.7 Detached Processes V1.2-4 When you start an application (from the Front Panel or dtfile), a new detached process is created with a process name constructed from the user name, $CDE, and a three- digit numeric identifier. For example, user SMITH starts an application whose process name is SMITH$CDE001. The next assigned process name would be SMITH$CDE002, unless SMITH$CDE001 has already terminated and is available for reuse. 2.2.1.8 Viewing Reference Pages V1.2-4 DECwindows contains a collection of help files for the New Desktop called reference pages (also known as manpages). Reference pages are divided into sections and, on OpenVMS, the file extension indicates the section. Sections distributed with the release include the following: ___________________________________________________________ Section_Purpose_____________Extension______________________ 1 Applications filename.1 3 Libraries/programminfilename.3 4 Programming filename.4 5 Include file filename.5 ________formats____________________________________________ A version of dthelpview has been set up with the appropriate action definition for manpage viewing. The process logical MANPATH has been defined to point to the CDE$SYSTEM_DEFAULTS:[MAN] directory that contains all of the reference page files. You can use either of the following methods to start dthelpview and display reference pages: 2-26 General User Release Notes 2.2 New Desktop Environment (Alpha Only) Method 1 To start dthelpview from DECterm and view a reference page called dtaction.1: 1. At the DCL level or in a LOGIN.COM file, define dthelpview as a foreign command by entering the following: $ dthelpview :== - _"$ sys$sysdevice:[sys0.syscommon.cde$defaults.system.bin]dthelpview.exe" 2. At the DCL level, enter: $ dthelpview -"manPage" dtaction.1 Method 2 To start dthelpview from Application Manager and view the reference page called dtaction.1: 1. Start Application Manager. 2. Double click on the Man Page Viewer icon located in the Desktop Apps application group. A dialog box appears. 3. Enter the reference page to be viewed and click on OK. 2.2.2 Corrections The following notes describe the resolution of any problems specific to the New Desktop environment that previously resulted in an error or required a workaround. 2.2.2.1 Session Manager Exits Properly When Saving a Session From an Nonprivileged Account V1.2-6 Starting and exiting a New Desktop session from an account that does not have rename privileges to the files in the SYS$LOGIN:[.DT] directory no longer causes the Session Manager to hang. This problem has been corrected; the Session Manager exits the session properly and returns you to the Login Screen. 2-27 General User Release Notes 2.2 New Desktop Environment (Alpha Only) 2.2.2.2 File Manager Allows Access to Files and Directories That Use ACLs V1.2-6 Previously, the File Manager application denied nonprivileged users access to files and directories even though access was granted through access control list (ACL). This problem has been corrected; dtfile allows the user to access the file or directory as specified by the related ACL entry. 2.2.2.3 Screen Lock Functions Properly on Multihead Systems V1.2-6 When running New Desktop on a multihead system, using lock screen with the Use Backgrounds For Lock option enabled was not behaving properly. It was possible to lock the screen from a remote system and then display an application over the background on the locked workstation. This problem has been corrected. 2.2.2.4 Can Set Default Display on Multihead Systems V1.2-6 Previously, the following problems occurred when the default display was set to a value other than 0 on a multihead system: o File Manager (DTFILE.EXE) continued to display on screen 0. o xrdb -q returned values only for screen 0. These problems have been fixed; all applications and return values either appear on or are related to the correct display device. 2.2.2.5 Can Remove the Calendar Icon From a Subpanel V1.2-6 Previously, removing the Calendar icon from a subpanel caused the Window Manager to crash. This problem has been corrected; you can safely delete the icon from any application subpanel. 2-28 General User Release Notes 2.2 New Desktop Environment (Alpha Only) 2.2.2.6 Can Switch Between Workspaces V1.2-6 Previously, changing workspaces resulted in a system crash as soon as the user clicked on a window in the new workspace to bring it into focus. This problem has been corrected; you can toggle between two or more workspaces. 2.2.2.7 Login Screen Positioned Properly in 640x480 Display Mode V1.2-6 The Login Screen has been recentered so that it allows ample space for both operator message and login text on Compaq Alpha systems that use the screen resolution of 640 x 480 (such as those containing Cirrus graphics cards). 2.2.2.8 Invalid Characters in a Username or Password No Longer Halt Login V1.2-6 Entering one or more invalid characters (such as a space) in either the Username or Password text field of the Login Screen no longer halts the login process by causing the Login Screen to disapper. This problem has been fixed. If any invalid characters are detected, a warning message is displayed that prompts you to correct the username and password text before proceeding. 2.2.2.9 Welcome Message Updated V1.2-6 Previously, the welcome message in the Login Screen did not display a host name when the DECnet network transport was not configured. This problem has been corrected. If TCP/IP is the network transport, the TCP/IP host name is displayed. If neither transport is configured, a default message of "Welcome to OpenVMS" is displayed. 2.2.3 Problems and Restrictions The following notes describe known problems and restrictions that currently exist in the New Desktop environment. 2-29 General User Release Notes 2.2 New Desktop Environment (Alpha Only) 2.2.3.1 Desktop Applications Disappear When Setting a Home Session V1.2-6 In the Style Manager, selecting Startup and then Set Home Session can cause applications that you previously started using the Application Manager to disappear. This can happen if you start these applications with the Application Manager and then close the Application Manager before setting your home session. The workaround is to keep the Application Manager window open. 2.2.3.2 DECwrite Icon Does Not Open DECwrite Program V1.2-5 DECwindows does not include the DECwrite program. However, DECwindows does include the DECwrite icon on the New Desktop. If the DECwrite product has not been installed, clicking on the DECwrite icon results in the following error messages: > RCV'D (pid 000000CA): %DCL-W-IVVERB, unrecognized command verb - check validity and spelling -> RCV'D (pid 000000CA): \DECWRITE\ -> RCV'D (pid 000000CA): TESTER logged out at 29-JUL-1998 17:56:44.63 If the DECwrite product is installed and you still get this error, ensure that DECwrite is started in SYSTARTUP_ VMS.COM. 2.2.3.3 Viewing TIF Files with dximageview V1.2-4 When using dximageview to view TIF formatted files from the CDE$SYSTEM_DEFAULTS:[APPCONFIG.HELP.C.GRAPHICS] directory, the following warning messages are displayed: TIFFOpen: Warning, unknown field with tag 34209 (0x85a1) ignored. TIFFOpen: XResolution: Rational with zero denominator (num = 200). Note this error only occurs with the TIF files in CDE$SYSTEM_DEFAULTS:[APPCONFIG.HELP.C.GRAPHICS]; it is only a warning. The file is still displayed correctly by the image viewer. 2-30 General User Release Notes 2.2 New Desktop Environment (Alpha Only) 2.2.3.4 Text Editor Supports Standalone Mode Only V1.2-4 The reference page for Text Editor describes a client/server implementation of the Text Editor. This release of the Text Editor supports the -"standAlone" option only and is not built as a client/server application. 2.2.3.5 Text Editor Does Not Support Spell Checking V1.2-4 The Text Editor application, which is part of the New Desktop, is described in Chapter 10 of the Common Desktop Environment: User's Guide. The spell-checking function described in the section "To Correct Misspelled Words" is not implemented in this version of the Text Editor. 2.2.3.6 Text Editor Tab Width is Larger Than Eight Characters V1.2-4 The Text Widget upon which the New Desktop Text Editor is based does not set the size of a tab to exactly the width of eight (8) characters; it is usually slightly larger. When displaying text with a combination of spaces and tabs, text may not appear vertically aligned. 2.2.3.7 File Names Displayed in UNIX Format V1.2-4 In the Application Manager Find dialog box and in error messages reported by the Help Viewer, file names are displayed in UNIX format rather than in standard OpenVMS format. For example, SYS$SYSROOT:[SYSMGR]LOGIN.COM appears as /sys$sysroot/sysmgr/login.com. 2.2.3.8 Delay When Exiting a Session with Open TPU Windows V1.2-4 Users will experience a one-minute delay for each DECwindows Text Processing utility (TPU) window displayed when exiting the session or when saving a home session. 2-31 General User Release Notes 2.2 New Desktop Environment (Alpha Only) The DECwindows interface for TPU (EVE editor) requires notification if its state needs to be saved, but it does not respond to that notification sent by Session Manager. The New Desktop Session Manager waits one minute for a response before continuing, resulting in the delay. 2.2.3.9 Front Panel Clock is an Icon Only V1.2-4 The New Desktop Front Panel Clock is an animated icon that displays the current system time using an analog display. The icon has no other function and does not support single- click or double-click operations. 2.2.3.10 ToolTalk Actions Not Supported V1.2-4 Creation of ToolTalk Action definitions in the Action Definition files (*.dt) as described in the Common Desktop Environment: Advanced User's and System Administrator's Guide is not supported. Although some ToolTalk actions exist in the Action Definition files installed with this product, modification of these actions is not supported and could cause some New Desktop functions to fail. 2.2.3.11 Session Manager Save/Restore Limitations V1.2-4 The Session Manager supplied with the New Desktop supports the WM_SAVE_YOURSELF protocol for the following DECwindows applications: Bookreader, DECterm, and Calendar. Applications that have been written to take advantage of this protocol can: o Save their state when the user exits a session. o Restore a state when the user starts a new session. The New Desktop applications support save/restore, but many existing DECwindows Motif applications have not been modified to support the WM_SAVE_YOURSELF protocol. The impact of this difference between existing and new applications can be seen during a logout/login sequence as follows: o Applications supporting save/restore create a main window if they were running when the user logged out. 2-32 General User Release Notes 2.2 New Desktop Environment (Alpha Only) o Applications that do not support save/restore do not automatically restart. An example of an existing DECwindows Motif application that supports save/restore is DECwindows Mail. 2.2.3.12 File Manager Limitations V1.2-4 The File Manager application has the following limitations: o If you specify a folder (directory) name, which is strictly a logical name, and the logical name translates to a search list, only the first directory encountered in the search list is displayed. For example, the SYS$SYSTEM logical represents both SYS$SPECIFIC:[SYSEXE] and SYS$COMMON:[SYSEXE]. If you present a view of SYS$SYSTEM, only the files in SYS$SPECIFIC:[SYSEXE] display. This is because SYS$SPECIFIC:[SYSEXE] precedes SYS$COMMON:[SYSEXE] in the search list. o When displaying a directory whose name includes a search-listed device, all directories in the search path are displayed. If more than one directory with the same name exists in the search path, an icon appears for each instance of that directory. If more than one file with the same name exists in the search path, the behavior depends on whether the Show Top Version Only filter option has been selected. If selected, only one icon of the file with the highest version is displayed. If not selected, all versions from all locations are displayed. However, if more than one of the files has the same version number, any action to any of the files with that version applies to the first occurrence of the file in the search path. For example, suppose the files SYS$SPECIFIC: [SYSMGR]TOOLS.DIR;1 and SYS$COMMON:[SYSMGR]TOOLS.DIR;1 both exist in a system. If a user switches to the directory SYS$SYSROOT:[SYSMGR], two icons represent the file TOOLS.DIR. Operations performed on either of the two icons work identically. New files are created in the first directory in the search path. In addition, some actions for these icons may not work properly. 2-33 General User Release Notes 2.2 New Desktop Environment (Alpha Only) To work around this problem, specify explicit directory names when a conflict occurs, for example, SYS$SPECIFIC:[SYSMGR] or SYS$COMMON:[SYSMGR]. 2.2.3.13 Login and Pause Screen Text Field Restrictions V1.2-4 The following sections provide information about the Login Screen and Pause Screen text fields. 2.2.3.13.1 Control Characters Not Recognized When Entering Username The New Desktop does not support entering control characters in the login Username text field. If entered, these characters are discarded. This differs from the DECwindows login Username text field which supports such key sequences as: o Ctrl/U, Ctrl/J, or F13 (deletes to beginning of the line) o Ctrl/H or F11 (positions to the beginning of the line) o Ctrl/E (positions at the end of the line) The New Desktop does support Ctrl/U, which when typed while entering a password at login or when unpausing the screen, erases any characters entered up to that point. 2.2.3.13.2 Return Key Used to Move Between Login Text Fields Because the Username text field and Password text field are different dialog boxes in the New Desktop, press the Return key to move the cursor from the Username text field to the Password text field. The Tab key does not move the cursor to the next text field; rather, this action highlights the OK button. 2.2.3.13.3 First Character Discarded When Entering Pause Screen Password If the workstation is paused and the Password dialog box is not displayed, the first character typed is ignored. This differs from the DECwindows pause screen, which always accepts any characters typed. When using the New Desktop, use a nontyping key, such as Shift, or move the mouse to redisplay the Pause dialog box before entering your password. If you are unsure of what you have already typed, you can use Ctrl/U to erase the Password text field. 2-34 General User Release Notes 2.2 New Desktop Environment (Alpha Only) 2.2.3.13.4 Text on the Welcome Screen is Not Displayed If the 100-dpi fonts are not included in the X server's font path, the welcome text is not displayed on the blue welcome screen that appears immediately after logging in. This may also occur if you are displaying your session on a remote X server. 2.2.3.14 Using SET DISPLAY/CREATE in DECterm Windows V1.2-4 From a privileged account, if you use the SET DISPLAY command from within a DECterm window without the /CREATE qualifier, it changes the display used for any application created from that point forward. It also redefines the display on which the login box appears after logging out. Always use the /CREATE qualifier when setting the display from a DECterm if you have not set the display already. 2.2.3.15 Font Selection Limitations V1.2-4 On the New Desktop, Style Manager contains a control that displays a dialog box used to select font size. Selecting a new font size affects only New Desktop applications and does not affect existing DECwindows Motif applications. 2.2.3.16 Default Workspace Limitations V1.2-4 The New Desktop provides a default backdrop for the four default workspaces. You can change or even select Nobackdrop using the Backdrop control located in Style Manager. When no backdrop is selected, you cannot drag icons and place them on the backdrop of the desktop. If you drag an icon and release it, it snaps back to File Manager or Application Manager. Icons that were dropped on the background before Nobackdrop was selected remain and function correctly. 2-35 General User Release Notes 2.2 New Desktop Environment (Alpha Only) 2.2.3.17 Alt + Space Key Does Not Post the Window Menu V1.2-4 The New Desktop maps the key binding Alt+space key to the Compose Character function by default. This provides a method for character composition on keyboards which do not supply a specific Compose Character key. To use this feature, follow these steps: 1. Copy CDE$SYSTEM_DEFAULTS:[CONFIG.lang]SYS.DTWMRC to DISK$:[LOGIN.DT]DTWMRC.DAT. 2. In the Keys DtKeyBindings section, uncomment the following line: Altspace icon|window f.post_wmenu 3. Restart the Workspace Manager. 2.3 Traditional DECwindows Desktop Environment This section contains release notes that pertain to the traditional DECwindows Desktop environment only. 2.3.1 Problems and Restrictions The following notes describe known problems and restrictions that currently exist in the traditional DECwindows Desktop environment. 2.3.1.1 Alt + Space Key Does Not Post the Window Menu V1.2-4 DECwindows Motif maps the key binding Alt+space key to the Compose Character function by default. This provides a method for character composition on keyboards which do not supply a specific Compose Character key. To use this feature, follow these steps: 1. Copy DECW$SYSTEM_DEFAULTS:DECW$MWM_RC.DAT to DECW$USER_ DEFAULTS:DECW$MWM_RC.DAT. 2. In the Keys DtKeyBindings section, uncomment the line: Altspace icon|window f.post_wmenu 3. Restart the Window Manager. 2-36 General User Release Notes 2.4 Bookreader 2.4 Bookreader This section contains release notes pertaining to the Bookreader application. 2.4.1 Changes and Enhancements The following notes describe changes and enhancements made to the Bookreader application. 2.4.1.1 Bookreader Printing Improved V1.2-4 The Bookreader application allows only draft-quality printing for books or topics. However, the Bookreader print function has been improved to eliminate such problems as missing lines and words, figures being overwritten by text, and poor leading of lines. 2.4.2 Corrections The following notes describe the resolution of problems that previously resulted in an error or required a workaround. 2.4.2.1 Last Login State Properly Restored (New Desktop Only) V1.2-6 Each time you start a New Desktop session, Bookreader remembers and properly restores its application state as it existed during your most recent New Desktop session. Previously, the application state and its position on the desktop was only partially restored. 2.4.2.2 Can Open DECW$BOOK Files Directly from FileView (Alpha Only) V1.2-6 Highlighting a Bookreader filename (.DECW$BOOK) in FileView and then starting Bookreader from the Applications menu now opens and displays the specified book. Previously, only the main Bookreader window was displayed containing the default library. Note that this problem existed on the OpenVMS Alpha platform only. 2-37 General User Release Notes 2.4 Bookreader 2.4.2.3 Can Specify DECW$BOOKSHELF Files with Blank Lines V1.2-6 Bookreader allows you to select and open DECW$BOOKSHELF files that contain either a blank line or that are not terminated by a front slash (\). The parsing of DECW$BOOKSHELF files has been improved so that this action no longer results in an access violation. 2.4.3 Problems and Restrictions The following notes describe problems and restrictions that currently pertain to the Bookreader application. 2.4.3.1 Support for Display PostScript Removed V1.2-6 With the removal of the support for Display PostScript from the current version of DECwindows Motif, Bookreader no longer supports the display of PostScript artwork in online manuals. When Bookreader detects PostScript artwork, it displays a full-size figure window with an large "X" overlayed with an error message box containing the following message: Unable to display PostScript(R) graphic. This feature is no longer available. There is no workaround. 2.4.3.2 Including Comment Characters in the DECW$BOOKSHELF File V1.2-3 If you include a comment character (! or #) in the last line of the DECW$BOOKSHELF file, Bookreader fails with a reserved operand fault. As a workaround, ensure that you do not add comment characters to the last line of the file. 2.5 CDA V1.2 This section contains release notes that pertain to the Compound Document Architecture (CDA) Run-Time Services and CDA Viewer components of DECwindows Motif. 2-38 General User Release Notes 2.5 CDA 2.5.1 Changes and Enhancements The following notes describe changes and enhancements made to the the CDA Run-Time Services and CDA Viewer application. 2.5.1.1 Dynamic Font Support V1.2 As well as supporting a static-table for the fonts supported by the DECfonts Typeface Collection Version 1.2, this version of CDA Run-Time Services includes support for dynamic font lookup. This enables the CDA Viewer to use new fonts as they are installed on the system. Dynamic font support is implemented using the WRITE$FONTS.INI file, which you can maintain using the Font utility provided with either DECwrite or DECpresent. If a document contains a font not found in the static tables, the CDA Viewer tries to open the WRITE$FONTS.INI file and search for the font. If the font is not found or if the system does not contain a WRITE$FONTS.INI file, the viewer uses a fallback font. 2.5.1.2 WRITE$FONTS Logical Name V1.2 The default location for the WRITE$FONTS.INI file is SYS$LIBRARY, but, if the logical name WRITE$FONTS is defined, the CDA Viewer uses the logical name definition to search for the WRITE$FONTS.INI file. Full path support is included, so any of the following definitions are valid: ___________________________________________________________ WRITE$FONTS Logical Name__________________Resulting_File_______________________ Undefined SYS$LIBRARY:WRITE$FONTS.INI DISK:[DIRECTORY] DISK:[DIRECTORY]WRITE$FONTS.INI SYS$LOGIN: SYS$LOGIN:WRITE$FONTS.INI .TMP SYS$LIBRARY:WRITE$FONTS.TMP DISK:[DIRECTORY]FILE__DISK:[DIRECTORY]FILE.INI_____________ 2-39 General User Release Notes 2.5 CDA 2.5.1.3 Enhanced Display Performance V1.2 The current version of CDA Run-Time Services includes a performance enhancement that decreases the time it takes to display the first page of a CDA document. Other applications that use the CDA Viewer to view documents (for example, DECwindows Mail) also benefit from this enhancement. The CDA Viewer enables this performance enhancement feature by default. You can disable the feature as follows: $ DEFINE CDA_QUICK_FIRST_PAGE FALSE The CDA Viewer might not display some documents correctly when this feature is enabled. If you encounter such a problem, disable the feature and invoke the CDA Viewer again. 2.5.1.4 Pack and Unpack Applications V1.2 CDA Run-Time Services includes two standalone applications that can be used for transferring CDA documents across a network. The CDA Pack application packages a CDA document along with all of its externally referenced files into a single file that can be copied between systems or mailed to other users. The CDA Unpack application reads a file that is packaged by the CDA Pack application and creates a copy of the original document file and all its externally referenced files. These applications allow you to copy CDA documents between systems without copying externally referenced files separately or correcting external file reference information after copying documents. To use these applications, add the following lines to your LOGIN.COM file (or add the lines to the SYS$MANAGER:SYLOGIN.COM file): $ PACK == "$SYS$SYSTEM:CDA$PACK.EXE" $ UNPACK == "$SYS$SYSTEM:CDA$UNPACK.EXE" These lines enable you to use the symbols PACK and UNPACK to invoke the Pack and Unpack applications, respectively. 2-40 General User Release Notes 2.5 CDA 2.5.1.4.1 Pack Application Syntax The CDA Pack application creates a single output file that contains the contents of a .DDIF or .DTIF input file. 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: $ PACK input-file-spec output-file-spec The following sections explain the format of the PACK command. input-file-spec Specifies the name of the primary .DDIF or .DTIF input file. output-file-spec Specifies the name of the output file that is created by the PACK application. If you do not specify a device or directory, the output file is created in the current default directory. Qualifiers: /[NO]SKIP_MISSING Controls whether the Pack application continues processing if it cannot find one or more of the files that are listed as external references in the input file. The names of any missing files are sent to SYS$ERROR when the Pack application is completed. If you specify /NOSKIP_MISSING, the Pack application does not create an output file if any of the externally referenced files are missing. The default is /SKIP_MISSING. /[NO]CONTROLLED_COPY Controls whether the output file includes only those external references that specify COPY_REFERENCE as the value of the ERF_CONTROL item in the input file. If you specify /NOCONTROLLED_COPY, the Pack application includes all referenced files, regardless of the value of the ERF_ CONTROL item. The default is /NOCONTROLLED_COPY. 2-41 General User Release Notes 2.5 CDA /ALWAYS_ENCODE Controls whether an output file is created when there are no external references in the input file, or if none of the externally referenced files are found. The default is not to create an output file in these cases. If an output file is not created for these reasons, the Pack application returns the CDA_W_NOOUTFIL status code. For example: $ PACK MYFILE.DDIF TEST.PACK 2.5.1.4.2 Unpack Application Syntax The CDA Unpack application unpacks an input file created by the Pack application. The output files are the .DDIF or .DTIF file that is packed by the Pack application, as well as a file for each external reference in the .DDIF or .DTIF file. The Unpack application sends a list of created files to SYS$ERROR. The format of the UNPACK command is as follows: $ UNPACK input-file-spec The following sections explain the format of the UNPACK command. input-file-spec Specifies the name of the input file that is created by the Pack application. Qualifier: /OUTPUT=output-file-spec Specifies the file name and location of the files created by the Unpack application. If you specify an output file name without a directory name, the Unpack application creates the main .DDIF or .DTIF file with the file name you specify in the current default directory. It also creates all externally referenced files in the current default directory. 2-42 General User Release Notes 2.5 CDA If you specify a directory name without a file name, the Unpack application creates the main .DDIF or .DTIF file and all externally referenced files in the specified directory. The main .DDIF or .DTIF file has the same name as the file packed by the Pack application. If you specify a directory name and a file name, the Unpack application creates the main .DDIF or .DTIF file and all the externally referenced files, in the specified directory. The main .DDIF or .DTIF file has the file name you specify. For example: $ UNPACK TEST.PACK Output file DISK$:[SMITH]MYFILE.DDIF created. Output file DISK$:[SMITH]FIGURE_1.DDIF created. $ UNPACK TEST.PACK/OUTPUT=[SMITH.UNPACK] Output file DISK$:[SMITH.UNPACK]MYFILE.DDIF created. Output file DISK$:[SMITH.UNPACK]FIGURE_1.DDIF created. $ UNPACK TEST.PACK/OUTPUT=[SMITH.UNPACK]NEW_FILE.DDIF Output file DISK$:[SMITH.UNPACK]MYFILE.DDIF renamed NEW_FILE.DDIF Output file DISK$:[SMITH.UNPACK]FIGURE_1.DDIF created. 2.5.1.4.3 Error Messages This section describes messages associated with the CDA Pack and Unpack applications. FILESPEC, Missing filespec: file-name Severity: Informational Explanation: The Pack application cannot locate an external file included as an external reference in the .DDIF or .DTIF file or in one of the files referenced in the .DDIF or .DTIF file. NOOUTFIL, No output file was created. Severity: Warning Explanation: The Pack application cannot find external references in the .DDIF or .DTIF document to be packed, and you did not specify the /ALWAYS_ENCODE qualifier. 2-43 General User Release Notes 2.5 CDA OUTFILE, Output file created: file-name Severity: Informational Source: CDA_UNPACK Explanation: The Unpack application created the specified file while unpacking a file created by the Pack application. 2.5.1.5 Paper Size Button Renamed V1.2 In the CDA Viewer, the name of the Paper Size button in the Open dialog box was changed to Display Options. However, the function invoked by the button was not changed. 2.5.1.6 New CDA Viewer Error Message V1.2 The CDA Viewer issues the following message if it is unable to create the application context: DRMCTXFAIL, DVR could not create application context, aborting Level: Error Explanation: The CDA Viewer ends because an attempt to create the application context using the Resource Manager failed, which is usually caused by insufficient memory. User Action: Reduce the system load and start the application again. 2.5.2 Problems and Restrictions The following notes describe known problems and restrictions that currently exist with either the CDA Run-Time Services or the CDA Viewer application. 2.5.2.1 Support for Display PostScript Removed V1.2-6 With the removal of the support for Display PostScript from the current version of DECwindows Motif, CDA no longer supports the display of PostScript source. The PostScript option has been removed from the CDA Viewer. If you attempt to view a PostScript file from the character cell interface CDA viewer, the viewer displays the following message: %CDA-E-UNSUPFMT, unsupported document format. There is no workaround. 2-44 General User Release Notes 2.6 Clock 2.6 Clock This section contains release notes pertaining to the Clock application. 2.6.1 Changes and Enhancements The following notes describe changes and enhancements made to the Clock application. 2.6.1.1 DECsound Alarm Capability V1.2 The Clock application includes an alarm feature that can be used if your system supports DECsound. On systems without sound capabilities, you can select only the keyboard bell. When you choose Alarm from the Options menu, a pop-up window appears. This pop-up window allows you to set the alarm time, choose the sound to be played, and indicate an alarm message. To see if your system supports this feature, invoke one of the sounds located in the DECW$EXAMPLES directory (for example, BELLS.AUD). 2.6.2 Corrections The following notes describe the resolution of problems with the Clock application that previously resulted in an error or required a workaround. 2.6.2.1 DECW$CLOCK.EXE Process Increments Correctly V1.2-6 The Clock application now consistently increments hour and minute values correctly. Previously, the DECW$CLOCK.EXE process generated two timer queue entries (XtTimeout) at the end of each 61-minute period to increment both the minute and hour values. Due to scheduling issues, these duplicate entries sometimes resulted in a time loss. The expiration value for XtTimeout has been adjusted to eliminate this problem. 2.7 DECterm This section contains information about the DECterm application. 2-45 General User Release Notes 2.7 DECterm 2.7.1 Changes and Enhancements The following notes describe recent changes and enhancements made to the DECterm application. 2.7.1.1 Improved Batch Scrolling V1.2-6 The overall performance of batch scrolling has been improved allowing you to moving through long files or multiscreen output quicker and easier. Now when you change the value of the Batch Scroll Lines option in the Display Options dialog box, the resulting display performance is visibly quicker. 2.7.1.2 New Default Font Sizes V1.2-4 In previous releases, the default DECterm font size for the "big" and "little" fonts were chosen by point size. This depended on whether 75 or 100 dpi fonts were installed first in the font path. Starting with DECwindows Motif Version 1.2-4 for OpenVMS, DECterm chooses its default fonts by pixel size. The following table shows the two behaviors. ___________________________________________________________ Prior Releases Since Version 1.2-4 Default Font Size (in_pixels)___________100___75[1]_______100___75___________ Big font 25 18 18 18 Little font 18 14 14 14 [1]75_dpi_fonts_or_100_dpi_fonts_on_a_15-inch_monitor______ ___________________________________________________________ In addition, on 100-dpi displays DECterm now uses the big font by default. This results in DECterm using the same font size (18 pixels) on 100-dpi displays as it did in prior releases. On displays that are less than 325 mm wide, DECterm also now uses a bigger default font. Follow these steps to use the same font as in previous releases (14 pixels): 1. From the Options menu, select the Window... item. 2-46 General User Release Notes 2.7 DECterm 2. Choose Little Font. Click on Apply. 3. If the new default font is too small, click on the Big Font button and change the pixel size in the Other text entry field from 18 to 25. 2.7.1.3 DECterm Resource File Name V1.2-4 In this release, the locale of the display is used to create the file name of the DECterm resource file. For example, if the locale is set to "ja_JP", then the default resource file name becomes DECW$TERMINAL_DEFAULT_JA_JP.DAT. However, DECterm continues to use the old resource file name until the user selects Save Options at least once in the particular locale. The default resource file name for DECterm continues to be DECW$TERMINAL_DEFAULT.DAT if the locale: o Is "C" o Starts with "en_US" o Contains "8859-1" 2.7.1.4 Escape Sequences V1.2-3 The DECterm application supports all ReGIS input cursors: o Crosshair o Diamond o Rubber-band line o Rubber-band rectangle For a shape other than the diamond cursor when n is equal to 1, define the logical name DECW$TERM_REGIS_CURSOR as one of the numbers defined in the SYS$LIBRARY:DECW$CURSOR file. V1.2 The following escape sequences are supported by DECterm: o All page movement sequences (NP, PP, PPA, PPB, and PPR). o One rectangular area operation sequence (DECCRA). o The DECLFKC sequence. 2-47 General User Release Notes 2.7 DECterm o The ReGIS command S(C(In)) supports the rubber-band rectangle cursor and the diamond cursor. See Section 4.4.1.1, ReGIS Input Cursors for additional information about escape sequences in DECwindows Motif software. See Chapter 4 for details and restrictions on the use of these sequences. 2.7.1.5 Scrolling Through the Keyboard V1.2-3 You can scroll through the keyboard by pressing the Ctrl key and arrow keys or by pressing the Prev or Next key on the editing keypad. 2.7.1.6 Reporting the DECterm Window Size V1.2-3 When you enable the Show Feedback option in the Workspace Options dialog box of the Window Manager and you resize a DECterm window, the size of the window is reported in characters instead of pixels. 2.7.1.7 Resizing the Terminal V1.2-3 If you maximize the DECterm window when you enable the Auto Resize Terminal window option, the window is expanded to its nearest cell boundary; the window does not necessarily occupy the entire screen. The Restore options continue to function appropriately. 2.7.1.8 Timeout for Displaying the Copyright Notice V1.2-3 If keyboard or mouse activity does not take place for 10 seconds after the copyright notice is displayed on the terminal, the notice disappears from the DECterm screen. 2.7.2 Corrections The following notes describe the resolution of problems with the DECterm application that previously resulted in an error or required a workaround. 2-48 General User Release Notes 2.7 DECterm 2.7.2.1 Can Specify Non-Standard Font Sets V1.2-6 In the Window Options dialog box, you can now specify a subset of the standard font set listed for Big Font, Little Font, and Standard German Font. For example, select Little Font and click Other. In the text entry box, replace the standard size and display options with alternate values from the current font set, as follows: o Original specification: -bitstream-terminal-*-*-*--18-*-*-*-*-*-*-* o Modified specification: -bitstream-terminal-*-r-narrow--36-*-*-*-*-*-*-* For additional information about specifying fonts, see Section 2.7.3.4. For information regarding the fonts available on your system, contact your system manager. 2.7.2.2 Device Output Files Used by Multiple DECterm Windows Updated Correctly V1.2-6 Redirecting the printer or window output of multiple DECterm windows to the same device file now produces separate versions of the file-one for each DECterm session. Previously, when performing an OPEN/READ INPUT command on this device file, an error occured, and after closing the file, only one version was created for all open sessions. 2.7.2.3 Print Operations That Exceed Quota Generate a Warning Message V1.2-6 DECterm print operations that exceed the available disk quota now generate following warning message: write to printer failed, write returned -1 2-49 General User Release Notes 2.7 DECterm 2.7.2.4 Button and Menubar Background Colors Set Properly (New Desktop Only) V1.2-6 The colors of the DECterm cascade buttons and menubar items are now consistent with other desktop applications when you use the Style Manager to activate the More Colors for Desktop option. 2.7.3 Problems and Restrictions The following notes describe the known problems and restrictions that currently exist with the DECterm application. 2.7.3.1 Maximum Number of DECterm Windows V1.2-4 A DECterm controller can create a maximum of 23 DECterm windows. This occurs because DECterm needs an event flag for each terminal window to use. There are 23 event flags that DECterm can use. (Event flag 0 and event flags 24-32 are not available for DECterm to use.) If you need more than 23 DECterm windows, then you must create a new controller. To create a new controller, enter the following command: $ MCR DECW$TERMINAL Note that the window from which this command is executed cannot be used for anything else because this command does not return until the last DECterm window is closed. After starting the controller with this method, the user can create another 23 DECterm windows with the DCL command CREATE/TERMINAL. 2.7.3.2 Changing the Auto Repeat Setting V1.2-3 You cannot change the Auto Repeat setting in the DECterm Keyboard Options dialog box. Instead, change the setting in the Keyboard dialog box in the Session Manager. 2-50 General User Release Notes 2.7 DECterm 2.7.3.3 Positioning DECterm Windows V1.2-3 If the resource Mwm*clientAutoPlace is set to True, DECterm windows are not displayed where the DECW$TERMINAL.x and DECW$TERMINAL.y resources are specified. As a workaround, set this resource to False and restart MWM. 2.7.3.4 User Font Selection V1.2 DECterm allows you to select available fonts from the Options/Window dialog box. A different font can be selected to replace the default Big Font, default Little Font, or default German Standard Font. In the Options/Window dialog box, you can select the default font or enter the name of a font into a text field and select that font. When the Big Font, Little Font, or German Standard Font is selected and the Other toggle button for the font is selected, DECterm attempts to locate and use the font name supplied in the adjacent text field. For information on font naming conventions or fonts available on your system, consult your system manager. ________________________ Note ________________________ Not all fonts work properly with DECterm. DECterm emulates a character-cell terminal, and, therefore, expects the fonts to be monospaced (each glyph 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, and condensed characters. Also, DECterm fonts include special characters, such as the Line Drawing and the DIGITAL Technical character sets. A DECterm font family is identified by the font naming convention. Use of fonts that do not have all the related font family variations, fonts that do not have the needed special characters, or font families that do not adhere to the DECterm font family naming conventions, 2-51 General User Release Notes 2.7 DECterm may not result in an optimal display or otherwise perform as expected. ______________________________________________________ On OpenVMS systems, Version 6.1 or higher, the VT330 font has been made available. The VT330 font is based on the 10x20 font used in the VT330 and VT340 terminals. Use this font on a system where they are available by entering the following font-name strings in the font-name text field: -DEC-VT330-*-*-*--20-*-*-*-c-*-*-* 2.7.3.5 Local Echo V1.2 DECterm supports a local echo mode. In the Options/General dialog box, select Local Echo, which causes all character sequences generated locally to be echoed on the display and passed to the remote host. This feature is useful when connected to a host that does not echo typed characters. 2.7.3.6 Answerback Message V1.2 A user interface is available to enter answerback messages. This answerback message field is for compatibility with Compaq terminals. The answerback field is a buffer that contains up to thirty characters. The answerback field in earlier Compaq terminals contained a message used to identify itself to the host system. For DECterm windows, the answerback field can be used to store a sequence of characters that you can use for any repetitive purpose. A field is provided in the Options/General dialog box to enter answerback text. Click on the answerback field and enter your text. To enter control characters, encode the control character as a two-digit hex ASCII code, preceded by a number sign (#). For example, when you enter #0D in the answerback field, DECterm responds with a carriage return. If two consecutive number sign characters are entered (##), a single number sign is transmitted. 2-52 General User Release Notes 2.7 DECterm If anything other than a valid two-digit hex code or another number sign is detected after an initial number sign, the number sign is treated as a normal text character. Refer to any ASCII table for a complete list of characters. The answerback text can also be concealed. When the Conceal Answerback button is enabled, the answerback message is concealed. To deselect the Conceal Answerback button, click on the answerback text field, which erases the previous answerback message. 2.7.3.7 Seven-Bit Printer Support V1.2 When the 7-Bit Printer button is selected in the Options/Printer dialog box, DECterm modifies printed text to be compatible with printers that do not support 8-bit characters. This includes modifying control sequence introducer (CSI) strings to use the format Escape-Left Bracket rather than the single 8-bit CSI character. When the 8-Bit Printer button is selected, DECterm allows the use of 8-bit characters when printing. This mode can cause problems for older printers if they can not interpret 8-bit characters. The default is 8-Bit. 2.7.3.8 Printing to an Attached Printer V1.1 Printing to a port device requires you to have read and write privileges on that port. You cannot print by allocating the device, since the controller requires access to the device. Instead, set the device to WORLD:RW. For example, to use the printer port on a VAX 3100 system, enter the following command from a privileged account or include the command in the system startup file: $ SET PROTECTION=WORLD:RW TTA3:/DEVICE 2-53 General User Release Notes 2.7 DECterm 2.7.3.9 DECterm Graphics V1.1 The following information is specific to DECterm graphics: o In some cases, a private colormap is created in DECterm. This private colormap is created when ReGIS or Sixel graphics are displayed in the window and a sufficient number of colors from the default colormap cannot be allocated. The result is that when the DECterm window has input focus, the colormap changes for the entire workstation. The default colormap is four colors on a four-plane or monochrome system and 16 colors on color systems with more than four planes. To restore a DECterm window to the default colormap, select Clear Display from the Commands menu to clear the window. Then select Reset Terminal from the Commands menu to reset the terminal. o Only graphics, not text, are written to the graphics backing store. When part of a window has to be redrawn in DECterm, the graphics portion of the window is drawn first, then the text is overlaid. As a result, the redrawn window might not look the same as the original picture. o ReGIS addresses the entire window, not just 24 rows and 80 columns, so the aspect ratio between text and graphics might not always be the same as on the VT330 or VT340 terminal. o The following ReGIS features are not implemented: - Command Display mode - Scrolling - Output cursors 2.7.3.10 DECterm Resource Usage V1.1 You cannot create more terminal windows than your system resources and quotas allow. If you have insufficient resources, a dialog box is displayed with a message indicating that no additional DECterm windows can be created. 2-54 General User Release Notes 2.7 DECterm To reduce the memory requirement of each DECterm window and create additional terminal windows, decrease the number of Record Lines Off Top in the Display dialog box and decrease the number of columns for each DECterm window. Once the resource limit is reached, log out of all DECterm windows that are running on the host system before you increase the number of terminal windows. 2.7.3.11 Diagnostic Crash File and Messages V1.1 DECterm produces a diagnostic file when a status code of fatal is returned. The DECTERM_ERROR.LOG file is produced in the login directory when the DECterm application exits abnormally. If you have a problem with the DECterm application, submit a copy of this log file to your Compaq service representative. However, under certain circumstances, a log file is generated even when no problem is encountered. Therefore, the appearance of a log file as an isolated event should not be cause for a problem report. You can enable additional levels of diagnostic messages by defining either a logical name or a symbol named DECTERM_ DIAG. When defined, enhanced diagnostics are displayed by the DECterm images. Use this mode only for diagnosing problems; it causes Session Manager message windows to be generated for each new DECterm created from the Session Manager. DECterm diagnostics can be captured in a file by defining the logical name DECW$TERMINAL_OUTPUT to point to a file. 2.7.3.12 VT330 and VT340 Terminal Emulation V1.0 DECterm incorporates some of the features of the VT330- and VT340-series video terminals, such as ReGIS and Sixel graphics. DECterm does not provide complete VT330 and VT340 terminal emulation. The following restrictions apply to DECterm: o User-loadable characters (DRCS), local mode, and control representation mode (CRM) are not implemented. 2-55 General User Release Notes 2.7 DECterm o The checkerboard character (character 97 in the DIGITAL Special Graphic character set) is used as an error character in place of the reverse question mark. o DECterm uses replace mode as the default for Sixel drawing on servers with eight planes or less. On servers with more than eight planes, DECterm uses overlay mode; replace mode is not functional on those servers. 2.7.3.13 CREATE/TERMINAL/DETACHED/PROCESS V1.0 The /PROCESS=procnam qualifier does not work when used in conjunction with the /DETACHED qualifier, unless there is already a process running on the system where its process name is equal to the user name. To work around this problem, use the following command procedure: $! CREATE_TERM_PROC.COM $! $! Invoke as SPAWN/NOWAIT @CREATE_TERM_PROC procname $! $ SET NOON $! $! Set Process name to username $! $ X = F$CONTEXT("PROCESS", PID, "PRCNAM", "''F$PROCESS()'","EQL") $ NAME = F$EDIT(F$GETJPI(X,"USERNAME"),"COLLAPSE") $ SET PROCESS/NAME="''NAME'" $ CREATE/TERMINAL/DETACHED/PROCESS="''P1'" $! $! Allow new process to RUN LOGINOUT before exiting subprocess $ WAIT 00:00:10 If the /PROCESS=procnam qualifier specifies a process name that is already in use, the DECterm is created but creation of the process inside the DECterm fails. In this case, the DCL command CREATE/TERMINAL returns the following error message: Duplicate process name 2-56 General User Release Notes 2.7 DECterm 2.7.3.14 ReGIS Locator Report V1.0 When DECterm sends a ReGIS locator report in response to the R(P(I)) command, or in multiple input mode and the locator position is outside the addressable area, DECterm sends a locator report with the coordinates omitted. For example, press the A key to generate the report: A[], where is a carriage return (ASCII code 13). 2-57 General User Release Notes 2.8 DECW$CDPLAYER 2.8 DECW$CDPLAYER This section contains information about the DECW$CDPLAYER application. 2.8.1 Problems and Restrictions The following notes describe the known problems and restrictions that currently exist with the DECW$CDPLAYER application. 2.8.1.1 Required Privileges V1.1 The DECW$CDPLAYER application in the DECW$EXAMPLES directory requires PHY_IO and DIAGNOSE privileges to operate the compact-disc player hardware. Either your process or the image must have these privileges. 2.9 DECwindows Mail This section contains information about the DECwindows Mail application. 2.9.1 Corrections The following notes describe the resolution of problems with the DECwindows Mail application that previously resulted in an error or required a workaround. 2.9.1.1 Can Drag Messages Between Folders While Text is Selected in an Alternate Window V1.2-6 You can now drag one or more mail messages between folders in DECwindows mail after selecting a range of text in another application window, such as a DECterm window. Previously, this action caused a selection conflict when the user returned to the Mail application and attempted to drag the highlighted messages to a new folder. This problem has been corrected. 2-58 General User Release Notes 2.9 DECwindows Mail 2.9.1.2 Can Send Multiple Messages from the DECnotes Interface V1.2-6 You can now send multiple mail messages from the DECnotes interface to DECmail. This action no longer results in an access violation. 2.9.1.3 Can Pick Inbox on Receipt of New Mail (Alpha Only) V1.2-6 You can use the Pick menu to select messages from the Inbox while new messages are being received. This action no longer causes the application to crash. 2.9.1.4 Window Color Options Displayed Correctly (New Desktop Only) V1.2-6 Previously, when attempting to change colors in DECwindows Mail, the five window color options in the lower portion of the Window dialog box were unreadable (displayed as black text on black background). This problem has been corrected; all options are now displayed in the appropriate colors. 2.9.2 Problems and Restrictions The following notes describe known problems and restrictions that currently exist with the DECwindows Mail application. 2.9.2.1 Support Removed for Display PostScript V1.2-6 With the removal of the support for Display PostScript from the current version of DECwindows Motif, DECWmail no longer supports the display of messages that are exclusively PostScript code. In previous versions, DECWmail sensed the presence of a mail message containing PostScript and used Display PostScript to display the message. Currently, when DECWmail detects a messages that is exclusively PostScript code, it displays the following error message: [This PostScript® message cannot currently be displayed.] 2-59 General User Release Notes 2.9 DECwindows Mail As a workaround, use the Extract option in the File menu, (deselect the "Include Header Information" button in the Extract dialog box), and print the extracted file. 2.9.2.2 Pasting Messages from the Directory Window V1.2-4 In DECwindows Mail, if the user selects one or more messages in the directory window using MB1 and then clicks on MB2 in another window (such as a DECterm window), the entire contents of the selected messages is pasted into the other window. The selected messages are highlighted in the directory window, however the text of the selected and pasted message is not highlighted in the Read window. 2.9.2.3 Responses to Keyboard Actions V1.2-3 Enhancements in the DECwindows Mail application to comply more closely with OSF/Motif style conventions cause some changes with application responses to keyboard actions. Note the following changes. If you use the Tab key to advance through text entry boxes in the Create/Send window, the current field is no longer highlighted. To select a field, use one of the standard Motif actions, such as double or triple clicking MB1, or use the Shift+Alt - > key sequence. In several dialog boxes, press either the Select key or the space bar to activate a pushbutton through the keyboard. Note that the Return key and the Enter key are bound to other widgets in the dialog box. Alternatively, you can continue to click MB1 to activate a pushbutton. 2.9.2.4 Using the Color Customizer with DECwindows Mail V1.2 If you use the color customizer sample program provided in the directory DECW$EXAMPLES to control DECwindows Mail colors, the DECwindows Mail color customization dialog boxes used to modify those colors may not reflect the correct current color values. This is normal behavior; use the color customizer instead of the DECwindows Mail color customization dialog boxes to change these values. Alternatively, exit from the color customizer and restart 2-60 General User Release Notes 2.9 DECwindows Mail DECwindows Mail. See Section 2.1.1.2 for more information about the color customizer. 2.10 Extended File Specification (EFS) Support In general, DECwindows Motif supports the Extended File Specifications (EFS) option provided in OpenVMS Alpha Version 7.2. The interface either supports the new ODS-5 file names or provides an error message indicating that the particular component does not support the new names. 2.10.1 Changes and Enhancements The following notes describe those changes and enhancements made to the DECwindows Motif environment in support of EFS. 2.10.1.1 File Selection Popup Window V1.2-5 The standard file selection popup window used by most DECwindows Motif applications fully supports ODS-5 style file names. The window supports deep directories, case preservation, and extended-length file names. The window supports entry of file names using the extended file name character and displays files using the extended file name character set using the circumflex character (^). See the OpenVMS Guide to Extended File Support for more specific information about using deep directories and the extended file name character set. 2.10.1.2 FileView Application (DECwindows Desktop Only) V1.2-5 With an ODS-5 volume, the FileView application supports deep directories, case preservation, and extended-length file names. FileView supports entry of file names using the extended file name character and displays files using the extended file name character set using the circumflex character (^). See the OpenVMS Guide to Extended File Support for more specific information about using deep directories and the extended file name character set. Any custom FileView command extensions must be modified to support EFS. 2-61 General User Release Notes 2.10 Extended File Specification (EFS) Support 2.10.1.3 File Manager Application (New Desktop Only) V1.2-5 The File Manager application supports case preservation and creates files with the extended file name character set, but does not support any operations on its files. The File Manager application supports deep directories and extended-length file names with the following restriction. As indicated in the OpenVMS Guide to Extended File Support, ODS-5 volumes allow file names up to 236 8-bit characters in length and deep directory structures if the total file specification does not exceed 512 8-bit characters in length. The current version of the File Manager supports extended-length file names and deep directory structures with the additional restriction that a total file specification cannot exceed 235 8-bit characters in length. Exceeding this limit causes an error message for some menu items. 2.10.1.4 The Programming Libraries V1.2-5 The programming libraries fully support deep directories and extended-length file names. However, the libraries do not support case preservation or the extended file name character set. 2.10.2 Corrections The following notes describe the resolution of all EFS problems that previously resulted in an error or required a workaround. 2.10.2.1 File Manager Corrections for EFS (New Desktop Only) V1.2-6 o The "Selected/Copy to" menu item supports case preservation. The files are copied correctly with their case preserved. o The "Selected/Copy to" menu item no longer causes an error with file names that exceed 235 characters. o The "Selected/Change Permissions" menu works on files with file names that exceed 235 characters. Permission can now be changed on files with long file names. 2-62 General User Release Notes 2.10 Extended File Specification (EFS) Support 2.10.3 Problems and Restrictions The following notes describe the known problems and restrictions that currently exist with EFS in the DECwindows Motif environment. 2.10.3.1 File Manager Problems with EFS (New Desktop Only) V1.2-5 o The "Selected/Move to" menu item does not support case preservation. The files are moved correctly, but case is not preserved. o The File Manager currently does not support case preservation when you create file names that contain special characters. For example, "Special^&Characters" will be converted to "SPECIAL^&CHARACTERS.;1". o The "Selected/Put in Trash" menu item does not work on ODS-5 volumes marked for EFS (Extended File Specifications). This applies only to folders with extended file names. An error message similar to the following is displayed: File Manipulation Error Cannot create "sys$sysroot:[sysmgr.dt.trash]qwertyuiopasdfghjklzxcvbnm- QWERTYUIOPASDFGHJKLZXCVBNM.LONG_NAME;1" The most common cause is that you do not have the correct permissions for the involved files or folders. To view permissions, select the object and then select "Change Permissions..." from the Selected or popup menu. These files can be deleted at the DCL level. o Dragging a file or folder with an extended file name to Trash causes an error message. On an ODS-2 volume you can drag a file or folder with a short file name to Trash and still be able to restore it. On an ODS-5 volume you can drag a file or folder with a short name to Trash, but you cannot restore even files with short names from an ODS-5 volume. These files can be deleted at the DCL level. 2-63 General User Release Notes 2.10 Extended File Specification (EFS) Support o The "File/New Folder" menu item can handle the creation of a folder when the path length exceeds 255 characters, but the folder cannot be displayed (it is hidden). These files can be viewed at the DCL level. o The "File/Find/File" menu item cannot find a file with file name that exceeds 235 characters if the full file name has been entered in the dialog's form field. To avoid the problem, use wildcards to conduct the search. o The "Selected/Purge" menu item does not work for long file names on ODS-5 volumes marked for EFS (Extended File Specifications). "Short" file names do not present this problem. An error similar to the following is displayed: File Manipulation Error Cannot create "sys$sysroot:[sysmgr.dt.trash]qwertyuiopasdfghjklzxcvbnm- QWERTYUIOPASDFGHJKLZXCVBNM.LONG_NAME;1" The most common cause is that you do not have the correct permissions for the involved files or folders. To view permissions, select the object and then select "Change Permissions..." from the Selected or popup menu. These files with long file names can still be purged at the DCL level. o Updated protection settings are not displayed when invoking "Fileview/Command/Protection," although the settings have actually been updated. However, the new settings can be verified by either issuing a DCL command or invoking "Fileview/Command/Show File." 2.10.3.2 Translated Image Support (TIS) Library (Alpha Only) V1.2-5 The translated image support (TIS) library has not been updated to support EFS. 2-64 General User Release Notes 2.11 Notepad 2.11 Notepad This section contains information about the Notepad application. 2.11.1 Problems and Restrictions The following notes describe known problems and restrictions that currently exist with the Notepad application. 2.11.1.1 Notepad Is Linked with the OSF/Motif Release 1.1.3 Toolkit V1.2-3 The Notepad application is linked with the OSF/Motif Release 1.1.3 Toolkit. Notepad is not modified to link with the OSF/Motif Release 1.2.3 Toolkit, which is provided with the Compaq DECwindows Motif for OpenVMS, Version 1.2-6 product. The following restrictions apply: o OSF/Motif Release 1.2 drag-and-drop functionality is not supported. As a workaround, use the standard clipboard operations (Cut, Copy, and Paste) to transfer text into Notepad. o OSF/Motif Release 1.2 tear-off menus are not supported. 2.12 Paint This section contains information about the Paint application. 2.12.1 Problems and Restrictions The following notes describe known problems and restrictions that currently exist with the Paint application. 2.12.1.1 Private Colormaps V1.1 If your workstation does not have sufficient colormap entries to view or edit a color image, Paint creates a private colormap. When this happens, the Paint image retains its colors, but the colors on the rest of the workstation are modified. To restore the colors to their 2-65 General User Release Notes 2.12 Paint original values, give another window input focus by clicking on it. 2.12.1.2 Slow Performance of Some Paint Operations V1.0 On GPX systems, Paint might appear slow even when performing basic operations such as drawing a brush stroke. This is because the pixmap is being swapped into the pixmap memory in order to paint the object. If Paint performance is slow, click on the Pencil tool and draw a point in the image area. This should improve performance following the initial Pencil click. When editing images (especially color images), you can resize the image area using the Picture Size... entry from the Options menu. Resize to the least possible image area to significantly reduce the amount of required pixmap memory. 2.13 Print Screen This section contains information about the Print Screen utility. 2.13.1 Problems and Restrictions The following notes describe known problems and restrictions that currently exist with the Print Screen utility. 2.13.1.1 PostScript Output Problem V1.2-5 When using the Print Screen application to produce PostScript output on some printers, part of the output may be lost. Usually, the upper and left portion is missing when printing in landscape mode and the lower and left portion is missing when printing in portrait mode. This problem is caused by differences between PostScript printers. To correct this problem, DECwindows Motif Version 1.2-5 for OpenVMS added support for four resources that can be specified in DECW$PRINTSCREEN.DAT: 2-66 General User Release Notes 2.13 Print Screen PrintScreen.plxtranslate PrintScreen.plytranslate PrintScreen.plxscale PrintScreen.plyscale These resources control the size and position of the PostScript image on the page. The plxtranslate and plytranslate resources control the x and y offsets of the image in inches from the origin. The plxscale and plyscale resources are an x and y scale factor to allow the entire image to be displayed on the page after the origin is moved. 2.14 Session Manager and FileView This section contains information about the Session Manager and FileView applications. 2.14.1 Corrections The following notes describe the resolution of problems with either the Session Manager or FileView application that previously resulted in an error or required a workaround. 2.14.1.1 Can Create DECterm Windows from the Qualifiers Dialog Box (DECwindows Desktop Only) V1.2-6 Creating DECterm windows from the DECterm Qualifiers dialog box now creates a single window each time you select the Apply or OK button. Previously, this action created duplicate instances of the window, which occasionally caused Session Manager to fail. 2.14.2 Problems and Restrictions The following notes describe known problems and restrictions that currently exist in either the Session Manager or FileView applications. 2-67 General User Release Notes 2.14 Session Manager and FileView 2.14.2.1 Invoking DECchart from the Session Manager Applications Menu V1.2-3 If you invoke the DECchart application from the Session Manager applications menu, your session can fail. As a workaround to this problem, edit the file VUE$LIBRARY:DECCHART$VUE.COM to incorporate the following text: $! $! Copyright (c) 1989, 1991 Digital Equipment Corporation. $! All rights reserved. $! $! Command procedure to run DECchart from the User Executive $! in DECwindows $! $ vue$suppress_output_popup $! $! See if we should skip the dialog box $! $ vue$get_symbol vue$show_hidden_dialogs $ vue$read show_hidden_dialogs $ $ if show_hidden_dialogs then goto select_qualifiers $ vue$get_qualifiers $ goto do_chart $ $select_qualifiers: $ vue$popup_qualifiers $ $ $do_chart: $ $ vue$popup_progress_box 8 $ vue$read vue$command $ $ if "''vue$command'" .eqs. "DETACHED_APPLY" then goto $ select_qualifiers $ $ 'vue$command $ $ decchart :== $sys$system:decchart$motif.exe $ vue$get_next_selection 2-68 General User Release Notes 2.14 Session Manager and FileView $ vue$read selection $ decchart 'selection $ $ vue$check_verb_loop $ vue$read loop $ if "''loop'" .eqs. "TRUE" then goto select_qualifiers The only change is to relocate the following line from the beginning of the VUE$LIBRARY:DECCHART$VUE.COM file: $ vue$popup_progress_box 8 This statement causes the Progress Box to pop up after the qualifiers are processed. 2.14.2.2 Security Options V1.2 In the Session Manager Security Options dialog box, place the node name within quotation marks if the name contains any of the following: o Reserved characters: space, tab, comma (,) or double quotation mark (") o Double colon (::) o A colon (:) as the final character in the node name Session Manager automatically adds quotation marks to the node name if they are needed, unless the node name begins with a double quotation mark. If the node name begins with a double quotation mark, Session Manager assumes that the user has already quoted the node name and does not change it. Within a quoted string, a double quotation mark should be replaced by two double quotation marks (""). For example, the quoted string "DEC:.zko."my node"" should be changed to the following: ("DEC:.zko.""my node"""). 2-69 General User Release Notes 2.14 Session Manager and FileView 2.14.2.3 Using the Color Customizer with Session Manager V1.2 If you are using the color customizer example program provided in the directory DECW$EXAMPLES to control Session Manager colors, the Session Manager color customization dialog boxes used to modify those colors may not reflect the correct current color values. This is normal behavior; use the color customizer instead of the Session Manager color customization dialog boxes to change these values. Alternatively, exit the color customizer and restart your session. See Section 2.1.1.2 for more information about the color customizer. 2.14.2.4 Input Focus Change When Starting Private Logo V1.0 If you are logging into DECwindows and using a private logo command file, input focus might revert unexpectedly to the Username field when the private logo starts up. 2.14.2.5 Stopping a Session Manager Process V1.0 Stopping the Session Manager process can have serious consequences for nonprivileged workstation users. DECwindows must be restarted to avoid the following problems: o A nonprivileged user cannot start a new Session Manager or create a new login box. o If the session is paused, the Pause cover window is deleted and unauthorized users can access windows on that workstation. o The workstation can also become unusable if the Session Manager process is terminated by the job controller (for example, when the user's access hours, which might be from 8 a.m. to 5 p.m., are exceeded). As a possible solution, restart DECwindows on each workstation in a batch job that runs during off-hours. 2-70 General User Release Notes 2.14 Session Manager and FileView If you stop the Session Manager process, restart DECwindows (if you have system manager privileges) with the following command: $ @SYS$MANAGER:DECW$STARTUP RESTART 2.15 Window Manager This section contains information about the DECwindows Motif Window Manager. 2.15.1 Changes and Enhancements The following notes describe changes and enhancements made to the DECwindows Motif Window Manager. 2.15.1.1 DECwindows XUI Applications V1.0 The resource Mwm*useDECMode allows previous versions of DECwindows XUI applications to behave correctly with the Motif Window Manager. In particular, this resource is used to control focus, window placement, multiline icons, and the window's initial state (normal or minimized). 2.15.2 Problems and Restrictions The following notes describe known problems and restrictions that currently exist with the DECwindows Motif Window Manager. 2.15.2.1 Using the Color Customizer with DECwindows Motif Window Manager V1.2 If you are using the color customizer provided in the DECW$EXAMPLES directory to control Motif Window Manager colors, the Motif Window Manager customization dialog boxes used to modify those colors may not reflect the correct current color values. This is normal behavior; use the color customizer instead of the Motif Window Manager color customization dialog boxes to change these values. Alternatively, exit the color customizer and then restart Motif Window Manager. See Section 2.1.1.2 for more information about the color customizer. 2-71 General User Release Notes 2.15 Window Manager 2.15.2.2 Configuration File V1.0 The configuration file DECW$MWM_RC.DAT defines how the Window Manager uses the function keys. Most of the accelerators use the form Alt key (or Compose Character key) and function key, for example Alt+F7. If any application needs to use these keys, you must either comment them out by placing an exclamation point (!) at the beginning of the line, or create new keyboard bindings. Then change Mwm*keyBindings:DefaultKeyBindings in the MWM resource file to point to the new bindings. With the Motif binding, you can no longer use the Alt+spacebar or the Compose Character+spacebar to bring up the Window menu because it interferes with Compose Character sequences in DECterm. Use Shift+F11 to bring up the Window menu. To reenable Alt+space, select the appropriate option in the Workspace Options dialog box and apply the current settings. You can also remove the comment for the default button bindings for Alt+space in the DECW$MWM_RC.DAT file. 2.15.2.3 Restarting Motif Window Manager V1.0 The file SYS$MANAGER:DECW$MWM.COM is used for information on how to restart the Window Manager. By default, it is always restarted on all the screens that are available. However, if you are not starting the Window Manager from the Session Manager, then the Window Manager might not have been initially started on all the available screens. You can modify this file to change the way the window is restarted for your system. 2.15.2.4 Customizing Color-Related Resources for Monochrome Monitors V1.0 The Motif Window Manager does not support full customization of color-related resources for monochrome monitors in the Options dialog box. In order to change the colors, you might need to modify the pixmap resources by directly editing the DECW$MWM_BW.DAT resource file. For 2-72 General User Release Notes 2.15 Window Manager example, to change the color of the active window's title background, you must change the Mwm*activeBackgroundPixmap resource. Some values include 25_foreground, 50_foreground, 75_foreground, and unspecified pixmap. In addition, by default, the title text is created with a white background. To use the same color as the rest of the title, set the Mwm*cleanText resource to FALSE. 2.15.2.5 Moving the Icon Box Off Screen V1.0 If you move the icon box to the edge of the screen and then resize it using the keyboard, you can move it off the screen. To retrieve the icon box, press Alt+Tab until you reach that window and then press Shift Escape (F11) to bring up the Window menu for that window. You can then move the window back onto the screen. 2.15.2.6 Customizing Colors on Multihead Systems V1.0 If you have a multihead system with different monitor types (color, monochrome, or gray-scale), you can customize the colors only by using the Options dialog box on the monitors that match the type of your main monitor (screen 0). To customize the other monitors, you must either log in to a system with that monitor type or directly edit the resource files. 2.15.2.7 Multiline Icon Title Not Centered V1.0 The Window Manager does not center all the lines of a multiline icon title. 2-73 3 _________________________________________________________________ System Manager Release Notes This chapter contains system manager release notes. 3.1 Installation and Upgrade Information This section describes important considerations related to the DECwindows Motif installation and upgrade procedures. 3.1.1 Changes and Enhancements The following notes describe changes and enhancements made to the DECwindows Motif installation and upgrade procedures. 3.1.1.1 DMA Disabled by Default (Alpha Only) V1.2-6 In support of the PowerStorm 3D30 or 4D20 (TGA2) graphics cards shipped with most Compaq AlphaServer systems, Direct Memory Access (DMA) is now disabled by default. During DECwindows Motif installation, the startup file DECW$DEVICE_CONFIG_GY.COM sets the logical DECW$FFBDODMA to a value of 0 (disabled). 3.1.1.2 DECW$GETPARAMS.COM Modified to Accept Large GBLPAGES Values (Alpha Only) V1.2-6 The procedure DECW$GETPARAMS.COM has been modified to treat large GBLPAGES values (those exceeding the 2 GB pagelet limit imposed by SYSGEN) as unsigned longwords. Previously, values that exceeded this limit were parsed as signed comparisons, which prevented DECwindows from starting. 3-1 System Manager Release Notes 3.1 Installation and Upgrade Information 3.1.1.3 Previously Optional Files Moved V1.2-4 The files listed in Table 3-1 from the optional areas have been moved into the required files areas. These files are now installed by default. Table_3-1_Previously_Optional_Files_Now_Required_________________ File_Name_________________________________File_Function__________ [SYSHLP.EXAMPLES.DECW]ICO.EXE Programming example image [SYSHLP.EXAMPLES.DECW.UTILS]BITMAP.EXE MIT utility image [SYSHLP.EXAMPLES.DECW.UTILS]ATOBM.EXE MIT utility image [SYSHLP.EXAMPLES.DECW.UTILS]BMTOA.EXE MIT utility image [SYSHLP.EXAMPLES.DECW.UTILS]XDPYINFO.EXE MIT utility image [SYSHLP.EXAMPLES.DECW.UTILS]XEV.EXE MIT utility image [SYSHLP.EXAMPLES.DECW.UTILS]XLSATOMS.EXE MIT utility image [SYSHLP.EXAMPLES.DECW.UTILS]XLSFONTS.EXE MIT utility image [SYSHLP.EXAMPLES.DECW.UTILS]XLSWINS.EXE MIT utility image [SYSHLP.EXAMPLES.DECW.UTILS]XMAG.EXE MIT utility image [SYSHLP.EXAMPLES.DECW.UTILS]XMBIND.EXE MIT utility image [SYSHLP.EXAMPLES.DECW.UTILS]XMODMAP.EXE MIT utility image [SYSHLP.EXAMPLES.DECW.UTILS]XPR.EXE MIT utility image [SYSHLP.EXAMPLES.DECW.UTILS]XPROP.EXE MIT utility image [SYSHLP.EXAMPLES.DECW.UTILS]XRDB.EXE MIT utility image [SYSHLP.EXAMPLES.DECW.UTILS]XREFRESH.EXE MIT utility image [SYSHLP.EXAMPLES.DECW.UTILS]XSET.EXE MIT utility image [SYSHLP.EXAMPLES.DECW.UTILS]XSETROOT.EXE MIT utility image [SYSHLP.EXAMPLES.DECW.UTILS]XWD.EXE MIT utility image [SYSHLP.EXAMPLES.DECW.UTILS]XWININFO.EXE MIT utility image [SYSHLP.EXAMPLES.DECW.UTILS]XWUD.EXE______MIT_utility_image______ 3-2 System Manager Release Notes 3.1 Installation and Upgrade Information 3.1.1.4 Using Shareable Linkages to Install Images (Alpha Only) V1.2-4 On OpenVMS Alpha systems, using shareable linkages to install images on Compaq DECwindows Motif for OpenVMS software offers the following advantages: o Enhanced startup performance by decreasing image- activation time o Conserved memory usage by decreasing the total of memory pages used by the image By default, the following images are installed using shareable linkages on Alpha systems: o DECW$XLIBSHR.EXE (Xlib) o DECW$XTLIBSHRR5.EXE (Xt Intrinsics) o DECW$XMLIBSHR12.EXE (Motif Toolkit) o DECW$MRMLIBSHR12.EXE (Motif Resource Manager) o DECW$DXMLIBSHR12.EXE (Compaq Extensions to the Motif Toolkit) o CDE$UNIX_ROUTINES.EXE (UNIX emulation routines) These images are installed using the /SHARE=ADDRESS_DATA option. Note that if you accept the default, these images cannot be replaced during a restart of DECwindows Motif software. As a result, when you restart DECwindows Motif, the images are not replaced and the following message is displayed: Shared linkage sections are in use on this system and no images will be reinstalled. If you are restarting DECwindows to reinstall images then you must reboot the system. To replace new images installed with this option, reboot the system. Note that you can disable shared-linkage sections by defining the logical name DECW$IGNORE_SHARE_ ADDRESS in the SYSTARTUP_VMS.COM command procedure. 3-3 System Manager Release Notes 3.1 Installation and Upgrade Information 3.1.1.5 Version Checking Available for Command Files V1.0 The Compaq DECwindows Motif for OpenVMS kit contains version-checking command procedures that layered products can use during their installation procedure. The following three files are placed in the SYS$UPDATE directory during the installation of Compaq DECwindows Motif for OpenVMS: o DECW$GET_IMAGE_VERSION.COM A command procedure that extracts the image identification string from an image and places it into a user-defined symbol. o DECW$COMPARE_VERSIONS.COM A command procedure that compares two image identification strings and assigns a value to a user- defined symbol with these possible results: - Facility codes do not match. - Identifiers are the same. - Second identifier is older than the first. - Second identifier is newer then the first. o DECW$VERSIONS.COM A command procedure used to display the versions of several components of the DECwindows Motif layered product and the X11 display server. The DECW$VERSIONS.COM procedure uses the DECW$GET_IMAGE_ VERSION.COM command procedure to obtain the image idents of each file. Use the following command to display the versions on sys$output: 3-4 System Manager Release Notes 3.1 Installation and Upgrade Information $ @SYS$UPDATE:DECW$VERSIONS * ________________________________________________________ Component_____________Description_______________________ DECwindows ident Xlib shareable image DECwindows server Server DIX file DECwindows transport Transport common DECwindows Xlib Xlib shareable image DECwindows OSF/Motif OSF/Motif Xm Toolkit Toolkit DECwindows DECwindows FileView applications DECwindows OSF/Motif UIL compiler programming_____________________________________________ The output from the command procedure shows DW, the version number, and the date the image is created. For example: DW V1.2-4960312 is version 1.2-4 and was created on March 12, 1996. 3.1.2 Problems and Restrictions The following notes describe known problems and restrictions that currently exist with the DECwindows Motif installation and upgrade process. 3.1.2.1 Check System Parameters Prior to Upgrade V1.2-6 If you are upgrading to Compaq DECwindows Motif for OpenVMS, Version 1.2-6 from a system running Version 1.2-4 or earlier, be sure to adjust the NPAGEDYN, GBLPAGES, and FREE_GBLPAGES system parameters to the following minimum values prior to installation: ___________________________________________________________ Parameter________Minimum_Value_____________________________ NPAGEDYN 1,998,848 3-5 System Manager Release Notes 3.1 Installation and Upgrade Information ___________________________________________________________ Parameter________Minimum_Value_____________________________ GBLPAGES 150,000 FREE_GBLPAGES_______20,000_________________________________ Otherwise, the installation procedure terminates and prompts you to run AUTOGEN to set these parameters to the appropriate values. 3.1.2.2 Upgrade Problem After Installing Required PCSI ECO V1.2-5 For systems running OpenVMS Alpha Version 7.1-2 or OpenVMS VAX Version 7.2 or earlier, you must install a POLYCENTER Software Installation (PCSI) utility ECO (see the Compaq DECwindows Motif for OpenVMS Installation Guide). After installing the required PCSI utility ECO, your system will use the new features provided by this version of the PCSI utility. If a layered product is installed that makes use of this new functionality, then it may not be possible to revert back to an older version of the utility. The restriction occurs because there may be records in the software product database that the older version of the utility will not be able to interpret. This scenario occurs if you install the PCSI ECO, then install DECwindows Motif, and later install certain upgrades to the OpenVMS operating system. The steps below describe the situations when this will occur: 1. Install the PCSI ECO kit onto an OpenVMS Version 6.2, 6.2-1H1, 6.2-1H2, 6.2-1H3, 7.1, 7.1-1H1, or 7.1-1H2 system. 2. Install the DECwindows Motif Version 1.2-6 software. 3. Upgrade to (or reinstall) OpenVMS Version 6.2, 6.2-1H1, 6.2-1H2, 6.2-1H3, 7.1, 7.1-1H1, or 7.1-1H2. Upgrading to any of the OpenVMS versions listed in item 3 may fail (or other PRODUCT command operations on the product database may fail) with one of the following errors: %SYSTEM-F-ACCVIO, access violation, ... %PCSI-E-UNSDOCENC, unsupported product document encoding version 3-6 System Manager Release Notes 3.1 Installation and Upgrade Information To prevent these failures after installing the PCSI ECO and DECwindows Motif, perform the following steps: 1. Remove DECwindows Motif using the following command: $ PRODUCT REMOVE DWMOTIF 2. Upgrade to (or reinstall) OpenVMS Version 6.2, 6.2-1H1, 6.2-1H2, 6.2-1H3, 7.1, 7.1-1H1, or 7.1-1H2. 3. Reinstall the PCSI ECO. 4. Reinstall DECwindows Motif. This workaround is not needed if you upgrading to OpenVMS Alpha Version 7.2-1 or higher, or if you are upgrading to OpenVMS VAX Version 7.2 or higher. These versions (and all later versions) already include the new functionality added by the PCSI ECO. 3.1.2.3 Reboot Recommended After Installation V1.2-4 Although system parameters are correct, it may be necessary to reboot the system after installing the Compaq DECwindows Motif for OpenVMS software. If the DECwindows login box does not appear after you install DECwindows Motif and restarting DECwindows Motif with the command @SYS$MANAGER:DECW$STARTUP RESTART, you will need to reboot the system. 3.1.2.4 Installation Verification Procedure Error in UIL Compiler V1.2-5 If you installed a previous version of DECwindows (for example, V1.2-4) without using the PCSI_INSTALLATION.COM procedure, you might get this error. Enter the following code into a command file and run it. This will check for .CLD files. If it finds any, it deletes them: $ VAX = 1 $ Alpha = 2 $ ARCH = F$Getsyi("ARCH_TYPE") $! $! See if the user wants the New Desktop to be the default desktop. $! $ if ARCH .ne. Alpha then goto skip_new_desktop $ type sys$input 3-7 System Manager Release Notes 3.1 Installation and Upgrade Information The New Desktop is a graphical user interface that is derived from the Common Desktop Environment (CDE). It offers the following features not available with the traditional DECwindows desktop: o Multiple workspaces for greater flexibility in managing windows on the screen. o An icon-based File Manager to make it easier to manipulate files from the graphical user interface. o Enhanced support for the drag-and-drop feature, which is fully supported in the new File Manager and Application Manager applications. o New Image Viewer and Icon Editor applications. Both the New Desktop and the DECwindows desktop provide the same underlying X and Motif libraries and the same DECterm, Bookreader, Mail, and Calendar applications. $ inquire/nopunct answer - "Do you want the New Desktop to be your default desktop ([y]/n)?" $ if answer .eqs. "" then answer = "yes" $ ! $ ! Create the decw$default_desktop.com file on the destination device. $ ! $ dest = "sys$sysdevice:[vms$common]" $ sysmgr_dir = f$search(dest+"SYSMGR.DIR") $ sysmgr_node = f$parse(sysmgr_dir,,,"NODE") $ sysmgr_device = f$parse(sysmgr_dir,,,"DEVICE") $ sysmgr_directory = f$parse(sysmgr_dir,,,"DIRECTORY") - "]" + ".SYSMGR]" $ dname = sysmgr_node + sysmgr_device + sysmgr_directory + - "DECW$DEFAULT_DESKTOP.COM" $ if f$search(dname) .nes. "" then delete 'dname';* $ open/write/error=dopenerr dfile 'dname' $ if answer $ then write dfile "$ DECW$START_NEW_DESKTOP == ""TRUE""" $ else write dfile "$ DECW$START_NEW_DESKTOP == ""FALSE""" $ endif $ close dfile $ set protection=(sy:rwed,ow:rwed,gr:re,wo:re) 'dname' $ goto skip_new_desktop $dopenerr: $ write sys$output "" $ write sys$output " WARNING: Can't create ''dname'" $ write sys$output "" $skip_new_desktop: 3-8 System Manager Release Notes 3.1 Installation and Upgrade Information $! $! Update [SYSLIB]DCLTABLES.EXE with new verbs $! $ create_new_dcltable: $ IF f$search("SYS$SYSROOT:[SYSLIB]DECW$UILCOMPILER.CLD") .EQS. "" - THEN GOTO skip_uil $ SET COMMAND/tables=SYS$COMMON:[SYSLIB]DCLTABLES.EXE - /output=SYS$COMMON:[SYSLIB]DCLTABLES.EXE - SYS$SYSROOT:[SYSLIB]DECW$UILCOMPILER.CLD $!$ skip_uil: $ IF f$search("SYS$COMMON:[SYSLIB]ddif$view.cld") .EQS. "" THEN GOTO skip_view $ SET COMMAND/tables=SYS$COMMON:[SYSLIB]DCLTABLES.EXE - /output=SYS$COMMON:[SYSLIB]DCLTABLES.EXE - SYS$COMMON:[SYSLIB]ddif$view.cld $! $skip_view: $ IF f$search("SYS$COMMON:[SYSLIB]pswrap.cld") .EQS. "" THEN GOTO skip_pswrap $ SET COMMAND/tables=SYS$COMMON:[SYSLIB]DCLTABLES.EXE - /output=SYS$COMMON:[SYSLIB]DCLTABLES.EXE - SYS$COMMON:[SYSLIB]pswrap.cld $skip_pswrap: $! $! Install the DCLTABLES $! $ set noon $ INSTALL LIST SYS$LIBRARY:DCLTABLES $ status = $status $ if status .eq. %X10000001 !%SYSTEM-S-NORMAL $ then $ INSTALL REPLACE SYS$LIBRARY:DCLTABLES/OPEN/HEADER_RESIDENT/SHARED $ endif $ set on 3.2 System Startup Information This section describes important considerations related to the startup of the Compaq DECwindows Motif for OpenVMS software. 3-9 System Manager Release Notes 3.2 System Startup Information 3.2.1 Changes and Enhancements The following notes describe changes and enhancements made to the DECwindows Motif system startup and login mechanisms. 3.2.1.1 Starting DECwindows Independently of OpenVMS V1.2-4 If DECwindows is not started during OpenVMS startup, it can be started later by running SYS$MANAGER:DECW$STARTUP.COM from a system account. Perform the following steps: 1. Define the logical name DECW$IGNORE_DECWINDOWS with a value of TRUE in SYS$STARTUP:SYSTARTUP_VMS.COM. 2. Reboot the system. 3. When system startup has completed, press Return and log in to the workstation console. 4. After logging in, start DECwindows by invoking the SYS$MANAGER:DECW$STARTUP.COM command procedure, as in the following example: $ @SYS$MANAGER:DECW$STARTUP ________________________ Note ________________________ Once DECW$STARTUP.COM has completed, you must log out of the console in order for DECwindows to start. ______________________________________________________ 3.2.2 Problems and Restrictions The following notes describe known problems and restrictions that exist with the current DECwindows Motif system startup and login mechanisms. 3.2.2.1 Problem With Delayed DECwindows Startup (Alpha Only) V1.2-4 On OpenVMS Alpha systems, error messages similar to those shown in Example 3-1 are displayed when: o Shareable address linkage is being used (the default setting). 3-10 System Manager Release Notes 3.2 System Startup Information o DECwindows is not started as part of system startup but is started later. These error messages are generated because there is not enough memory in the granularity hints region to install images resident. The images are installed nonresident, without shared address linkage, so DECwindows startup can complete. However, the performance and memory advantages of using shared address linkage are lost. The amount of memory in the granularity hints region is determined by the system parameter GH_RSRVPGCNT. In DECwindows Motif Version 1.2-3 for OpenVMS and earlier versions, this parameter was set to 512, which allowed DECwindows to start at any time with shared address linkage. However, this also consumed a large amount of physical memory. To prevent memory from being wasted, OpenVMS temporarily increases the size of the granularity hints region during system startup and releases the unused memory once startup has completed. Starting with DECwindows Motif Version 1.2-4 for OpenVMS DECwindows Motif takes advantage of this by allowing GH_RSRVPGCNT to remain at its default value of zero. DECwindows images can be installed resident and with shared address linkage as long as DECwindows is started during system startup, as it is by default. Example 3-1 Error Messages Displayed Due to Low Memory in Granularity Hints Region %INSTALL-I-FAIL, failed to create shared linkage entry for DISK$ALPHASYS: RCV'D (pid nnnnnnnn): RCV'D (pid nnnnnnnn %SYSTEM-F-EXBUFOBJLM, exceeded systemwide buffer object page limit (MAXBOBMEM) -> RCV'D (pid nnnnnnnn): RCV'D (pid nnnnnnnn SYSTEM logged out at dd-mmm-yyyy hh:mm:ss At the present time, there is no workaround for this problem other than using fewer windows (increasing the MAXBOBMEM value doesn't fix the problem). If you experience this problem, you may want to keep a DECterm window free so that you can perform a graceful system reboot. Otherwise, you will need to perform a hard reboot. 3.3.2.2 Performance Problem with Certain Keymaps V1.2-5 There is a performance problem when using the Austrian- German keymap (AUSTRIAN_GERMAN_LK401AG_TW). The problem can also occur with other keyboard and/or language changes, when the user selects a sequence of keyboard maps/languages which force the Mode_switch modifier into the mod4 or mod5 entry in the keyboard modifier map. This happens in response to the user selecting a keyboard map in the "Keyboard Options" popup that uses the Mode_switch modifier. To verify the position of the Mode_switch modifier in the keyboard modifier map, use the following commands: $ XMODMAP :== $DECW$UTILS:XMODMAP.EXE $ XMODMAP xmodmap: up to 3 keys per modifier, (keycodes in parentheses): 3-21 System Manager Release Notes 3.3 System and Environment Tuning Information shift Shift_R (0xab), Shift_L (0xae) lock Caps_Lock (0xb0) control Control_L (0xaf) mod1 Alt_L (0xac), Alt_R (0xb2) mod2 Mode_switch (0xb1) mod3 Multi_key (0xad) mod4 Mode_switch (0x7a) mod5 Help (0x7c) As a workaround, change the modifier mapping after selecting the keyboard map by using the DECW$UTILS:XMODMAP.EXE utility. 1. Create a file, which when passed to XMODMAP, clears the keyboard modifier map and remaps the Mode_switch to a lower entry in the keyboard modifier map: clear shift clear lock clear control clear mod1 clear mod2 clear mod3 clear mod4 clear mod5 add shift = Shift_R Shift_L add lock = Caps_Lock add control = Control_L add mod1 = Alt_R Alt_L add mod2 = Multi_key add mod3 = Mode_switch add mod5 = Help 2. Pass the file to XMODMAP using the following commands: $ XMODMAP :== $DECW$UTILS:XMODMAP.EXE $ XMODMAP XMODMAPRC.DAT 3.4 Console Window This section contains information about the Console Window application. 3-22 System Manager Release Notes 3.4 Console Window 3.4.1 Changes and Enhancements The following notes describe changes and enhancements made to the Console Window application. 3.4.1.1 Displaying Console Messages V1.2-3 DECwindows Motif Version 1.2-3 for OpenVMS introduced the feature of displaying console messages in the Console Window application. Previous versions of DECwindows Motif displayed the console window by default. ________________________ Note ________________________ The new default for displaying console messages starting with the DECwindows Motif Version 1.2-3 for OpenVMS 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 for 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. ______________________________________________________ Specify how to display messages by defining the global symbol DECW$CONSOLE_SELECTION in the customized startup 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 Window application. This is a new application starting with the DECwindows Motif Version 1.2-3 for OpenVMS software. If you specify the WINDOW value, the Console Window is displayed in the lower right corner of the login screen by default and continues to be displayed after the user logs in to the system. 3-23 System Manager Release Notes 3.4 Console Window The Console Window application shares the same executable file and looks similar to the Message Window. However, a menu bar is not displayed in the Console Window; it reads its resources from the DECW$CONSOLE.DAT file instead of from the DECW$MESSAGEPANEL.DAT file. Internally, the Console Window is invoked by running the DECW$MESSAGEPANEL.EXE executable with the command line option -console. To control the initial position of the Console Window and the classes of OPCOM output that are enabled, you can the define the following global symbol in the file SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM: DECW$CONSOLE_GEOMETRY This symbol specifies the value of the -geometry option in the DECW$MESSAGEPANEL.EXE command line; this command is used to start the Console Window application. The default value is "-0-0", which specifies the location of the window in the lower right corner of the screen. To position the window at the lower left corner of the screen, for example, add the following line to the command file SYS$MANAGER:DECW$PRIVATE_APPS_ SETUP.COM: $ DECW$CONSOLE_GEOMETRY == "+0-0" o DISABLE (default) Disables broadcasts to the OPA0: device. Console messages are not displayed. o ENABLE Displays console messages in the console window. The console window is a six-line display area at the top of the workstation screen. ________________________ Note ________________________ Although ENABLE was the default value in previous releases of DECwindows Motif, it is recommended that you do not use this option with DECwindows Motif Version 1.2-3 for OpenVMS and later versions. Displaying console messages by default in the console 3-24 System Manager Release Notes 3.4 Console Window window can corrupt the contents of the workstation display. ______________________________________________________ Refer to Managing DECwindows Motif for OpenVMS Systems for information about defining global symbols in the file SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM. 3.5 DECterm This section contains information about DECterm system management issues. 3.5.1 Changes and Enhancements The following notes describe changes and enhancements that effect the management of the DECterm application. 3.5.1.1 Supported DECterm Logical Names V1.1 Table 3-5 describes the logical names that are supported by DECterm. If you do not define these logical names in your LOGIN.COM file, the controller uses the default files. Table_3-5_Logical_Names_Supported_by_DECterm_____________________ Logical_Name______________________Description____________________ DECTERM_DIAG Enables diagnostic messages. DECTERM_SHOW_PARSING Shows characters as they are parsed. DECTERM_CHECK_MEMORY Enables strict memory checking. FAKE_VM_REAL_FREE_OFF Must be set to 1 if DECTERM_ CHECK_MEMORY is defined. +DECW$DECTERM_ERROR Name of error log file; default is DECTERM_ERROR.LOG. DECW$DECTERM_OUTPUT Name of diagnostic output file; default is SYS$OUTPUT. +VAX_specific____________________________________________________ (continued on next page) 3-25 System Manager Release Notes 3.5 DECterm Table_3-5_(Cont.)_Logical_Names_Supported_by_DECterm_____________ Logical_Name______________________Description____________________ DECW$DECTERM_REGIS_CURSOR Specifies which cursor to use for ReGIS. DECW$TERMINAL_NODENAME Node name used by controller if it cannot find another name. DECW$DECTERM_CTRL_SSRWAIT Sets the SSRWAIT flag for the controller. DECW$DECTERM_CTRL_PSWAPM Sets the PSWAPM quota for the controller. DECW$DECTERM_CTRL_WSEXTENT Sets the WSEXTENT quota for the controller. DECW$DECTERM_CTRL_WSQUOTA Sets the WSQUOTA quota for the controller. DECW$DECTERM_DISABLE_QUOTA_ Turns off quota checking. CHECKING DECW$DECTERM_MEM_DIAG Shows controller quota __________________________________calculations.__________________ 3.5.1.2 Automatic Window Positioning V1.1 A resource has been defined to manage repositioning a DECterm window when a resize operation forces part of the window off the screen. If a DECterm window is enlarged by using the Options/Window dialog box or by entering a SET TERMINAL/PAGE=nn or SET TERMINAL/WIDTH=nn command, the controller moves the newly resized DECterm window so that it can be viewed in its entirety. If you prefer DECterm not to move, add the following line to your DECW$TERMINAL_ DEFAULT.DAT file: DECW$TERMINAL.main.terminal.autoAdjustPosition: off 3-26 System Manager Release Notes 3.5 DECterm 3.5.1.3 Improving Hold Screen Response Time V1.1 If the hold screen key response time is too slow, add the following lines to your DECW$TERMINAL_DEFAULT.DAT file: DECW$TERMINAL.main.terminal.syncFrequency: 1 DECW$TERMINAL.main.terminal.batchScrollCount: 1 Using this resource can affect the performance of the DECterm window. The actual impact on performance varies from site to site. You can trade off scrolling speed to hold-screen response time. A faster hold-screen response results in a slower scrolling speed. The default values for these resources are 10 and 0, respectively. 3.5.1.4 Using the Debugger V1.0 To redirect the output from the debugger to a DECterm window, enter the following command: $ CREATE/TERMINAL/NOPROCESS/DEFINE=xxx This command creates a DECterm without an associated process but with a logical name of xxx that points to the terminal. This procedure enables you to direct output to a DECterm window other than the window where the application is currently running. To redirect the output, enter the following commands: $ DEFINE /USER DBG$INPUT xxx: $ DEFINE /USER DBG$OUTPUT xxx: $ RUN /DEBUG application.EXE 3.5.1.5 Virtual Terminal Support V1.0 To create a process that uses a virtual terminal, enter the following command: $ CREATE/TERMINAL/NOPROCESS Then establish focus to the newly created DECterm, press Return, and log in. Note that the /DEFINE qualifier is not required. 3-27 System Manager Release Notes 3.5 DECterm 3.5.2 Problems and Restrictions The following notes describe known problems and restrictions that currently effect the management of the DECterm application. 3.5.2.1 DECterm Window Shrinking Problem V1.2-5 If the XUI window manager is in use, "Auto Resize Terminal" is on, and you used the mouse to resize the DECterm window, the DECterm window shrinks. To workaround this problem, add the following line to the DECterm resource file DECW$TERMINAL_DEFAULT.DAT: DECW$TERMINAL.main.terminal.useWMHints: false If you make this change, be aware that the window manager will report the size of the DECterm window in pixels rather than character cells. Also, if you maximize a DECterm window, it might not properly restore to its previous size. However, it will no longer shrink. 3.6 Session Manager and FileView This section describes important considerations related to the Session Manager and FileView applications. 3.6.1 Changes and Enhancements The following notes describe changes and enhancements that effect the management of the Session Manager and FileView applications. 3.6.1.1 Implications of the Message, "System Menu Bar: Pseudo Mouse Not Available" V1.2-3 "System Menu Bar: Pseudo Mouse not available" is an informational message that is included in the user's DECW$USER_DEFAULTS:DECW$SM.LOG file when you run a session. It is not an error message. The message occurs when the OpenVMS Session Manager is run remotely to a non-OpenVMS server. The OpenVMS server provides pseudomouse mode, a mode that allows you to use arrow keys to move the mouse cursor. 3-28 System Manager Release Notes 3.6 Session Manager and FileView 3.6.1.2 Detached Processes Created by Default V1.1 Applications created by FileView and Session Manager are detached processes. The implication is that during application startup, SYS$MANAGER:SYLOGIN.COM and SYS$LOGIN:LOGIN.COM command procedures are executed. Any command executed by these command procedures which reads from SYS$INPUT reads data intended to be used by FileView or Session Manager for the application startup. This prevents the application from starting. Examples of such commands are INQUIRE, READ/PROMPT, and SET TERMINAL/INQUIRE. Extensive SYLOGIN.COM or LOGIN.COM command procedures slow down application startup. Many of the operations performed in a SYLOGIN.COM or LOGIN.COM are meaningless for DECwindows application startup. Therefore, the SYLOGIN.COM and LOGIN.COM files should be conditionalized for DECwindows application startup performance. When starting a DECwindows application, only a minimum of SYLOGIN.COM and LOGIN.COM commands should be executed. Typically, the commands that should be executed are the redefinition of DECW$USER_DEFAULTS (if present), and other logical name definitions if the user will be referencing them from within the context of a DECwindows application. The following code segment can be inserted into SYLOGIN.COM and LOGIN.COM immediately following the commands necessary for DECwindows: $ mode = f$mode() $ tt_devname = f$trnlnm("TT") $ session_mgr_login = (mode .eqs. "INTERACTIVE") .and. - (f$locate("WSA",tt_devname) .ne. f$len(tt_devname)) $ session_detached_process = (mode .eqs. "INTERACTIVE") .and. - (f$locate("MBA",tt_devname) .ne. f$len(tt_devname)) $ if session_mgr_login .or. session_detached_process then exit Applications continue to run even if these lines are not added to the SYLOGIN.COM and LOGIN.COM files. 3-29 System Manager Release Notes 3.6 Session Manager and FileView 3.6.2 Problems and Restrictions The following notes describe known problems and restrictions that currently effect the management of the Session Manager application. 3.6.2.1 DTSESSION Logging Problem (New Desktop Only) V1.2-5 In some cases, DTSESSION continues to log errors to its log file until all free disk space is filled. These errors could occur, for example, if DECW$DISPLAY is set to an incorrect value, or if CDE$SYSTEM_ DEFAULTS:[BIN]DTSCREEN.EXE is not properly installed. If the New Desktop's Session Manager (DTSESSION) is unable to start the Screen Saver (DTSCREEN), it logs an error to the log file device:[user.DT]ERRORLOG. DTSESSION logs this error at a user-settable interval controlled by the Style Manager's "Time Per Background" parameter. To workaround this problem, increase the "Time Per Background" parameter to the maximum (120 minutes), or exit the New Desktop when you are done with it, rather than locking the screen. 3.7 Window Manager This section contains information about Window Manager system management issues. 3.7.1 Changes and Enhancements The following notes describe changes and enhancements that effect the management of the DECwindows Motif Window Manager application. 3.7.1.1 Overlay Support V1.2-3 The latest version of the Window Manager (MWM) is modified to support overlays and utilize additional planes of memory, which are available on some 3D graphics accelerators. The Window Manager places borders and banners for all the windows into these extra planes of memory and thereby reduces the number of expose events for your applications that use overlays. 3-30 System Manager Release Notes 3.7 Window Manager You may need to modify your existing applications that use overlays to avoid potential problems with the colormap. Compaq recommends that you set up your system to share the overlay colormap with the Window Manager, as the hardware supports only one colormap for the overlay planes. See the associated documentation for your 3D graphic accelerator to determine if overlays are supported. Setting Up the Overlay Colormap To modify your applications to share the overlay colormap with the Window Manager, query the server property name SERVER_OVERLAY_COLORMAPS. When you make the query, the server returns the 32-bit value for the overlay Colormap ID. 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 and SYS$COMMON:[SYSMGR]DECW$MWM.COM. Change the following line in each file: $ mwm -multiscreen Edit this line by adding the -Overlay command-line option as follows: $ mwm -multiscreen "-Overlay" Note that if you create and install your own colormap, the following problems can result: o Colors flash on the screen when the colormap is changed. o Border and banner colors also change when you change the colors of your colormap. Restrictions The following restrictions apply when you enable the Window Manager to use overlays: o The Window Manager supports only single-screen systems and does not function correctly with multiple graphics devices (multihead). o If you select a Matte Size value other than "None" from the Window Manager options list, the Matte color may not be correct; that is, the color does not match the selection and is occasionally transparent. 3-31 System Manager Release Notes 3.7 Window Manager o If you select "Show feedback when moving or resizing 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 window borders and banners. o Window borders are occasionally and randomly displayed in clear or black. If this problem occurs, select the restart option from the Workspace menu to restart the Window Manager. 3-32 4 _________________________________________________________________ Programmer Release Notes This chapter contains programmer release notes. 4.1 OSF/Motif Toolkit Support V1.2-6 The Compaq DECwindows Motif for OpenVMS, Version 1.2-6 release is based on the CDE Motif 1.0 Toolkit (OSF/Motif Release 1.2.5) and X11 Release 5. V1.2-5 The DECwindows Motif Version 1.2-5 for OpenVMS release is based on the CDE Motif 1.0 Toolkit (OSF/Motif Release 1.2.5) and X11 Release 5. V1.2-4 The DECwindows Motif Version 1.2-4 for OpenVMS release was based on the CDE Motif 1.0 Toolkit (OSF/Motif Release 1.2.5) and X11 Release 5. V1.2-3 The DECwindows Motif Version 1.2-3 for OpenVMS release was based on the OSF/Motif Release 1.2.3 Toolkit (with extensions for the Common Desktop Environment (CDE)) and X11 Release 5 (R5). V1.2 The DECwindows Motif Version 1.2 for OpenVMS release was based on the OSF/Motif Release 1.2.2 Toolkit and MIT X11 Release 5 (R5). V1.1 The DECwindows Motif Version 1.1 for OpenVMS release was based on the OSF/Motif Release 1.1.3 Toolkit and MIT X11 Release 4 (R4). 4-1 Programmer Release Notes 4.1 OSF/Motif Toolkit Support V1.0 The DECwindows Motif Version 1.0 for OpenVMS release was based on the OSF/Motif Release 1.1.1 Toolkit and MIT X11 Release 4 (R4). Note that although DECwindows Motif Version 1.1 applications will continue to run without modification with current version of DECwindows Motif for OpenVMS, only those applications that have been built against the OSF/Motif Release 1.2.2 Toolkit can take advantage of Version 1.2 features, such as drag-and-drop functionality and tear-off menus. See Appendix B additional information related to the OSF/Motif Toolkit. 4.2 Run-Time and Programming Environment Support V1.2-4 The following run-time and programming environments are provided with the Compaq DECwindows Motif for OpenVMS software: o Run-time support is provided for the CDE Motif 1.0 Toolkit (OSF/Motif Release 1.2.5), OSF/Motif Release 1.1.3 Toolkit, and the XUI Toolkits. o Development support is provided for the CDE Motif 1.0 Toolkit only. However, you can choose during installation to save the OSF/Motif Release 1.1.3 programming files that existed on your system prior to the DECwindows Motif Version 1.2-4 for OpenVMS product. Refer to the Compaq DECwindows Motif for OpenVMS Installation Guide for details about saving the OSF/Motif Release 1.1.3 programming environment. - If you install the software using the VMSINSTAL procedure and choose to save these programming files, the files are moved to subdirectories and can be accessed for programming. 4-2 Programmer Release Notes 4.2 Run-Time and Programming Environment Support - If you install the software using the POLYCENTER Software Installation utility and if programming support for the OSF/Motif Release 1.1.3 Toolkit is present, then you can choose to save the header files and UIL compiler that were used to develop OSF/Motif Release 1.1.3 applications. If selected, the installation procedure creates a subdirectory called [.DECW$113], and the previous programming files are moved into the new subdirectory. See the Compaq DECwindows Motif for OpenVMS Installation Guide for additional information about saving the Release 1.1.3 programming environment. o Application development with the Compaq DECwindows Motif for OpenVMS product is supported for Compaq C++ as well as for updated Motif language bindings for Ada, Pascal, Fortran, and C. Language bindings for Ada are available in the Compaq Ada Version 3.5A for OpenVMS (VAX and Alpha) layered products. 4.2.1 Changes and Enhancements The following notes describe changes and enhancements related to the DECwindows Motif development environment. 4.2.1.1 Available Language Bindings V1.2-3 Fortran, Pascal, C, and C++ language bindings are provided to support software development for the following DECwindows components: o Xlib (Release 5) o Xt (Release 5) o Xm (Release 1.2.3) o Mrm (Release 1.2.3) o DXm 4-3 Programmer Release Notes 4.2 Run-Time and Programming Environment Support 4.2.1.2 Running Translated Images on OpenVMS Systems V1.2-3 In versions of OpenVMS Alpha systems prior to Version 1.5, translation support was provided to address the following problems for users who migrated to OpenVMS Alpha systems: o Lack of full-language programming support o Unavailability of source code for recompilation o Difficulty recompiling code that depended on VAX architecture features 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 maintained to support language features that are available as of the VMS Version 5.5-2 release. Similarly, translation is supported for images whose use of system services and run-time library entry points is restricted to those images that existed on the VMS Version 5.5-2 operating system. If you have installed layered products on your system since the VMS Version 5.5-2 release, you may need to make additional changes if you rebuild an image to support translation. For instance, for applications that are included with Compaq DECwindows Motif for OpenVMS VAX software, you must build images with the OSF Motif Release 1.1.3 library or the DECwindows XUI library, instead of with the OSF Motif Release 1.2.3 library. The Compaq DECwindows Motif for OpenVMS, Version 1.2-6 release includes the same translated-image support file that was provided with the DECwindows Motif Version 1.2 for OpenVMS Alpha release. DECwindows Motif Version 1.2 for OpenVMS Alpha includes support for DECwindows Motif Version 1.1 for OpenVMS VAX images on an OpenVMS Alpha system. V1.2 4-4 Programmer Release Notes 4.2 Run-Time and Programming Environment Support The DECwindows Motif Version 1.2 for OpenVMS Alpha release does not include support for running translated DECwindows Motif Version 1.2 for OpenVMS VAX images on OpenVMS Alpha systems. If you want to run an application against DECwindows Motif Version 1.2 shareable images on an OpenVMS Alpha system, build it (compile and link) on an OpenVMS Alpha system. You cannot obtain a Version 1.2 translated image by building your application against the DECwindows Motif Version 1.2 shareable images on an OpenVMS VAX system, copying the resulting image file to an OpenVMS Alpha system, and translating it (using DECmigrate). If you cannot build your application on an OpenVMS Alpha system and need to obtain a translated image with DECmigrate, you should continue to build your application against the OSF/Motif Release 1.1.3 programming environment provided in the DECwindows Motif Version 1.1 for OpenVMS VAX product. (Note that you are given the option to save your OSF/Motif Release 1.1.3 programming environment when you upgrade to DECwindows Motif Version 1.2 for OpenVMS VAX.) VAX images built against the OSF/Motif Release 1.1.3 programming environment can be copied to an OpenVMS Alpha system, translated, and executed successfully. You can install translated-image support during the DECwindows Motif installation procedure. See the DECwindows Motif Version 1.2-4 for OpenVMS Installation Guide for instructions. The OSF/Motif Release 1.1.3 shareable images that are used with translated images are different from and incompatible with the shareable images used for native images. As a result, the following image restrictions apply: o Do not use both native and translated images that use DECwindows Motif software in a process. Either port or translate all the images that use DECwindows Motif software and all images that call each other. o Translated images that dynamically activate a DECwindows Motif image using LIB$FIND_IMAGE_SYMBOL from a translated image are not supported. 4-5 Programmer Release Notes 4.2 Run-Time and Programming Environment Support For more information on translated-image support, see the DECmigrate for OpenVMS AXP Systems Translating Images guide. 4.2.2 Problems and Restrictions The following notes describe problems and restrictions that currently exist in the DECwindows Motif development environment. 4.2.2.1 Support for Display PostScript Removed V1.2-6 Starting August 1, 1998, Compaq discontinued its support for the Display PostScript software licensed by Adobe Systems Incorporated. Compaq took this action because Adobe ended their former ongoing support of Display PostScript. Due to this decision, Compaq is contractually obligated to remove all Display PostScript capability from the DECwindows Motif software. This includes all related translated-image support and any functionality described in the following programming reference manuals: o VMS DECwindows Display PostScript System Programming Supplement o Display PostScript System: Perspective for Software Developers o Display PostScript System: Client Library Reference Manual o Display PostScript System: Color Extensions o Display PostScript System: pswrap Reference Manual o PostScript Document Structuring Conventions Specification Version 2.1 Currently, there is no workaround. See the following sections for more information on the potential impact to applications in the DECwindows Motif environment. 4-6 Programmer Release Notes 4.2 Run-Time and Programming Environment Support 4.2.2.1.1 Impact on DECwindows Motif Applications Removing Display PostScript from DECwindows Motif impacts any application that relies on its capabilities to present and display graphics and documents in PostScript format. Unfortunately, this includes not only those applications developed by Compaq, such as the CDA Viewer, but also any third-party, user-written, or translated VAX applications that depend on one or more of the following files and libraries. These items are no longer a part the product kit and are removed from your system when upgrading from a previous version of DECwindows Motif client software. o PSWRAP command (DCL) o Display PostScript (XDPS) libraries [SYSLIB]XDPS$DPSBINDINGSSHR.EXE [SYSLIB]XDPS$DPSCLIENTSHR.EXE [SYSLIB]XDPS$DPSLIBSHR.EXE o Display PostScript header files and sample programs o Translated-Image Support (TIS) files [SYSLIB]XDPS$DPSBINDINGSSHR_TV_SUPPORT.EXE [SYSLIB]XDPS$DPSCLIENTSHR_TV_SUPPORT.EXE [SYSLIB]XDPS$DPSLIBSHR_TV_SUPPORT.EXE [SYSLIB]CDA$ACCESS_TV_SUPPORT.EXE [SYSLIB]DDIF$VIEWSHR_TV_SUPPORT.EXE [SYSLIB]DECW$BKRSHR__TV_SUPPORT.EXE [SYSLIB]DECW$MAILSHR_TV_SUPPORT.EXE The actual effect of removing Display PostScript depends on the extent to which it was implemented in the application. Applications that call the PSWRAP command, may fail only at the point where the command is invoked. However, applications that link against one or more of the XDPS libraries or TIS images will fail to function entirely due to unresolved links at run time. As a result, you may need to modify those portions of DECwindows Motif applications that rely on these files to run successfully in the Compaq DECwindows Motif for OpenVMS, Version 1.2-6 environment. 4-7 Programmer Release Notes 4.2 Run-Time and Programming Environment Support 4.2.2.1.2 Impact on Java Applications The Java Development Kit (JDK) for OpenVMS Version 1.2.2-1 contains two shareable images (JAVA$FONT_MANAGER_SHR.EXE and JAVA$FONT_MANAGER_G_SHR.EXE) that link against the Display PostScript (XPDS) libraries. As a result, all Java applications built with this kit that use Display PostScript capabilities will fail in the DECwindows Version 1.2-6 environment. Note that this restriction only applies to the Version 1.2.2-1 kit. The Java machine for the 1.1* series, as well as all releases of the JDK subsequent to Version 1.2.2-1, are not dependent on the Adobe Display PostScript software or its libraries. 4.2.2.2 Using Multithreading and Upcalls (Alpha Only) V1.2-6 The transports used to communicate to the DECwindows Server do not currently support the use of multiple kernel threads. Consequently, DECwindows Motif client applications that use multiple kernel threads multiple threads with upcalls enabled are not supported. This restriction applies even if the application restricts DECwindows calls to a single thread. 4.2.2.3 Problems Using the DECW$INCLUDE:INTRINSIC.H File V1.2-5 The DECwindows header file, DECW$INCLUDE:INTRINSIC.H, redefines the globalref macro to be extern when using the DEC C compiler, even when the /STANDARD=VAXC compiler switch is specified. This could have a wide impact on user applications. This redefinition in INTRINSIC.H is required because DECwindows needs to ensure that references to data located in the DECwindows shared images by user-written applications use the same extern model that was used when the DECwindows shared images were compiled. To workaround this problem, rather than having your application use globalref and globaldef for its own variables, use the following preprocessor directive: #pragma extern_model strict_refdef 4-8 Programmer Release Notes 4.2 Run-Time and Programming Environment Support This workaround has the advantage of being strictly ANSI compliant. This pragma directive is described in the DEC C User's Guide for OpenVMS Systems manual. 4.2.2.4 DECW$WML.EXE Looks in Current Directory For DECW$WML_TOKENS.DAT 1.2-4 The program SYS$SYSTEM:DECW$WML.EXE can be used to customize the parsing of UIL files. It reads a list of tokens from the file DECW$WML_TOKENS.DAT. In previous versions of DECwindows Motif, this tokens file was always read from SYS$LIBRARY. However, starting with DECwindows Motif Version 1.2-4 for OpenVMS, DECW$WML.EXE first looks for this file in the current directory before looking for it in SYS$LIBRARY. This allows a customized tokens file to be used. 4.2.2.5 DECW$COMPARE_VERSIONS Command File Limitation 1.2-4 The DECW$COMPARE_VERSIONS command file compares version identifications using two-digit years. Therefore, it will not compare version identifiers correctly for images generated in the year 2000 and later with version identifiers for images generated before the year 2000. 4.2.2.6 Use of _Xm Routines V1.2 The OSF/Motif Toolkit libraries contain many undocumented routines, which are prefixed with _Xm. These routines are intended to be used only by the standard Motif widgets. OSF reserves the right to modify the API or functionality of these routines, or to delete them altogether in future releases. _______________________ Caution _______________________ Compaq supplies access to the _Xm routines by copying them into the shareable image transfer vector for the OSF/Motif Release 1.2.2 Toolkit. Compaq does not document or support these routines or guarantee their continued existence in future releases. Application 4-9 Programmer Release Notes 4.2 Run-Time and Programming Environment Support developers who use these routines do so at their own risk. ______________________________________________________ 4.2.2.7 Compiling Applications Written in Fortran (Alpha Only) V1.1 On OpenVMS Alpha systems, some of the include files used for writing DECwindows Motif applications in Fortran, such as the DECW$MOTIF.FOR file, contain structure definitions that cause memory layout changes, depending on the compiler switches used. You can do one of the following: o Use the CDEC$ OPTIONS in the source code so that your Fortran programs work correctly with the DECwindows Motif run-time libraries: - Before you include DECwindows Motif files in your program, add the following statement: CDEC$ OPTIONS /ALIGN=RECORDS=NATURAL - Following the INCLUDE statement, add the following statement: CDEC$ END OPTIONS For example: CDEC$ OPTIONS /ALIGN=RECORDS=NATURAL INCLUDE "DECW$MOTIF.FOR" CDEC$ END OPTIONS o Use the Fortran compiler switch, /ALIGN=RECORDS=NATURAL, when you compile your programs. 4.2.2.8 Compiling Applications Written in C 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 text library. If you extract the definition files, you can use #include control lines of the following form: #include 4-10 Programmer Release Notes 4.2 Run-Time and Programming Environment Support The DECwindows header files assume that the .h files were extracted. They contain #include notation for the included files. The DECwindows programming documentation also makes this assumption. VAX C should, therefore, be installed using the option to extract the library modules. If you have already installed VAX C and you did not extract the .h files, the DECwindows sample C programs do not work. To correct this problem, reinstall VAX C and extract the .h files. With DEC C, the header files do not need to be extracted from the text library if you define the DECC$TEXT_LIBRARY logical name as follows: $ DEFINE DECC$TEXT_LIBRARY SYS$LIBRARY:DECC$RTLDEF.TLB 4.3 CDA This section contains programming information about the CDA application and run-time services. 4.3.1 Changes and Enhancements The following notes describe changes and enhancements made to the CDA application and run-time services. 4.3.1.1 Drag-and-Drop Feature Available V1.2 The drag-and-drop feature, which lets you move or copy information between widgets, is implemented in the widgets listed in Table 4-1. Table_4-1_Drag-and-Drop_Widgets____________________________ Widget____________Drag_Operation____Drop_Operation_________ XmText copy and move copy and move XmTextField copy and move copy and move XmLabel copy (continued on next page) 4-11 Programmer Release Notes 4.3 CDA Table_4-1_(Cont.)_Drag-and-Drop_Widgets____________________ Widget____________Drag_Operation____Drop_Operation_________ XmPushButton copy XmToggleButton copy XmList____________copy_____________________________________ For information about how to include additional drag-and- drop functionality in applications and for an example of a drag-and-drop program, see the Open Software Foundation: OSF/Motif Programmer's Guide, Revision 1.2 manual. 4.3.1.2 Changes to the Programming Interface V1.2 This section describes the changes to the programming interface for this version of CDA Run-Time Services. This version provides a new set of header files that define CDA constants, types, and routines using portable naming conventions. By using these new naming conventions, you can use a wider variety of C compilers to minimize the amount of system-specific code in your CDA applications. The names of the new set of header files are the same as the names of the previous set of header files, except that the dollar sign ($) has been removed. For example, the cda$msg.h include file is now called cdamsg.h. Other examples include the following: The DDIF$K_DSC_MAJOR_ VERSION symbol is now declared as DDIF_K_DSC_MAJOR_VERSION, and the CDA$_NORMAL status value is now defined as CDA_ NORMAL. The previous set of header files is also included in this version, but these files will no longer be updated. Changes introduced since the release of DECwindows Motif Version 1.1 (for example, the new definitions for audio support), are available only in the new set of header files. To use the new CDA features, change the file names in your source code. 4-12 Programmer Release Notes 4.3 CDA The new set of header files supplements the previous set of header files. If you want to write ANSI-compliant applications using CDA definitions and CDA Toolkit calls, use the new set of header files. However, you can continue to use the header files that define symbols containing the dollar sign ($) provided you choose a non-ANSI compilation mode. By using the previous set of header files, you can successfully build existing source code that uses the previous naming conventions. See Table 4-2 for a list of new header file names. Table_4-2_New_Header_File_Names____________________________ Previous_Name____New_Name__________________________________ cda$def.h cdadef.h cda$msg.h cdamsg.h ddif$def.h ddifdef.h dtif$def.h dtifdef.h cda$ptp.h cdaptp.h cda$typ.h cdatyp.h dvr$msg.h dvrmsg.h dvr$cc_def.h dvrccdef.h dvr$cc_ptp.h dvrccptp.h dvr$decw_def.h dvrwdef.h dvr$decw_ptp.h___dvrwptp.h_________________________________ 4.3.1.3 Changes to External Reference Processing V1.2 CDA Run-Time Services supports relative file specifications for external references. Relative references are also supported: that is, a reference where the directory path is not fully specified but is relative to the directory path of the parent document. 4-13 Programmer Release Notes 4.3 CDA 4.3.1.4 Message for Style Guide Fallback V1.2 The following message is displayed when a local style guide cannot be found: STYGDEFBK, Fallback to nonlocale-specific style guide: file- spec Level: Informational Explanation: Since the locale-specific style guide cannot be found, the nonlocale-specific version of the style guide is used. 4.3.1.5 Using Logical Names with CONVERT Commands V1.2 During a document conversion, if a logical name is used to specify the directory of the primary document and the document file extension is omitted, external references that contain relative file specifications cause the conversion to fail. This failure occurs because the back-end converter examines the converter processing options, although the front-end converter opens the input file. Because the converter software cannot predict what default file extension the front-end converter might apply, it uses the OpenVMS file services to resolve the logical name and to find the actual file specification so that the directory can be parsed and extended with a relative specification. 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. The reference is resolved in all other cases. For example: sys$login:mydoc.doc disk$:[smith]mydoc disk$:[smith]mydoc.doc 4-14 Programmer Release Notes 4.3 CDA 4.3.1.6 Restructuring Shareable Images V1.2 The CDA Viewer includes two shareable images to allow installation on systems where DECwindows is not installed. In DECwindows Motif Version 1.2 for OpenVMS software, shareable images that use the X services were renamed. Table 4-3 lists the shareable images in the various versions of the CDA Viewer. Table_4-3_Names_of_Shareable_Images________________________ CDA Version_____Image_Name_______Description___________________ Version CDA$ACCESS CDA Run-Time Services 1.6 shareable image. DDIF$VIEWSHR Callable viewer widget. Version CDA$ACCESS CDA Run-Time Services 1.7 shareable image. DDIF$VIEWSHR The DDIF$DECW_VIEWSHR widget DDIF$DECW_ is a callable viewer widget VIEWSHR that uses the LIB$FIND_IMAGE_ DDIF$CC_VIEWSHR SYMBOL routine to invoke the DDIF$DECW_VIEWSHR (DECwindows interface) and DDIF$CC_VIEWSHR (character-cell interface) widgets. Version CDA$ACCESS CDA Run-Time Services 1.8A or shareable image. later DDIF$VIEWSHR12 The DDIF$VIEWSHR12 widget is a callable viewer widget that uses LIB$FIND_IMAGE_SYMBOL to invoke the DDIF$DECW_VIEWSHR12 (DECwindows interface) and DDIF$CC_VIEWSHR (character- _____________________________cell_interface)_widgets.______ By using the LIB$FIND_IMAGE_SYMBOL routine to reference the entry points to the DDIF$DECW_VIEWSHR, DDIF$DECW_VIEWSHR12, and DDIF$CC_VIEWSHR images, an application can dynamically 4-15 Programmer Release Notes 4.3 CDA determine whether it can execute in a given environment. The DDIF$VIEW.EXE application now replaces this routine. The previous DDIF$VIEWSHR.EXE shareable image is still included to maintain compatibility with applications linked against it. However, new applications (and previous applications that take advantage of new features) should use the new shareable images. 4-16 Programmer Release Notes 4.4 DECterm 4.4 DECterm This section contains information about DECterm programming. 4.4.1 Changes and Enhancements The following notes describe changes and enhancements made to the DECterm application. 4.4.1.1 ReGIS Input Cursors V1.2-3 DECterm supports the following input cursors: cross-hair, rubber-band line, diamond, and rubber-band rectangle. To select input cursors use the S(C(In)) command. Table 4-4 shows the values of n. Table_4-4_ReGIS_Input_Cursors-Cursor_styles_and_Values_____ Cursor_Style__________Variable_n___________________________ Cross-hair Omitted Cross-hair (default) 0 Diamond 1 Cross-hair 2 Rubber-band line 3 Rubber-band 4 rectangle__________________________________________________ ________________________ Note ________________________ If a shape other than the diamond cursor is desired when n is equal to 1, define the logical name DECW$DECTERM_REGIS_CURSOR to be one of the numbers defined in the SYS$LIBRARY:DECW$CURSOR.H file. ______________________________________________________ 4-17 Programmer Release Notes 4.4 DECterm 4.4.1.2 Page-Movement Escape Sequences V1.2 The following page-movement escape sequences are implemented in DECterm: NP Pn U Next Page PP Pn V Previous Page PPA Pn P Page Position Absolute PPB Pn R Page Position Backward PPR Pn Q Page Position Relative Note that "Pn" is the number of pages to move; the exception is PPA, where "Pn" is the actual page number. ________________________ Note ________________________ DECterm does not support cursor coupling; the cursor is always bound to the current (displayed) page. ______________________________________________________ 4.4.1.3 DECCRA Sequence V1.2 DECterm supports the DECCRA (Copy Rectangular Area) sequence in a limited way. The entire page needs to be copied at once, and either the source or the destination page must be the current page (for example, you cannot copy from one off-screen page to another). 4.4.1.4 DECLFKC Sequence V1.2 Since DECterm does not have a user interface to redefine the F5 (Break) key, the DECLFKC (Local Function Key Control) sequence redefines the F5 key when "0" (all keys) is used to select which key is to be modified. 4.4.2 Corrections The following notes describe the resolution of any problems specific to the DECterm application that previously resulted in an error or required a workaround. 4-18 Programmer Release Notes 4.4 DECterm 4.4.2.1 CREATE/TERM/WAIT SHOW PROCESS No Longer Disrupts SYS$INPUT V1.2-6 Issuing the CREATE/TERMINAL/WAIT SHOW PROCESS command from a command procedure no longer disrupts the definition of SYS$INPUT. 4.5 DECTPU for DECwindows Motif This section contains information about DECTPU for DECwindows Motif programming. 4.5.1 Problems and Restrictions The following notes describe known problems and restrictions that currently exist with the DECTPU for DECwindows Motif. 4.5.1.1 Small Display Monitors and DECTPU V1.0 When running DECTPU for DECwindows Motif on small display monitors, the main window can be less than fully visible. To correct this condition, follow these steps: 1. Add the following resources to your DECTPU X resource file: Tpu.Tpu$MainWindow.X: 0 Tpu.Tpu$MainWindow.Y: 0 Tpu.Tpu$MainWindow.Rows: 21 Tpu*condensedFont: on Tpu*fontSetSelection: 1 2. Copy the resource file from SYS$LIBRARY:EVE.DAT and add the previous lines. 3. Use the logical name TPU$DEFAULTS to point at the new resource file. The following example invokes the EVE DECwindows Motif user interface using the X resource file names eve_ small_window.dat in your login directory to edit the file LOGIN.COM. $ DEFINE TPU$DEFAULTS SYS$LOGIN:EVE_SMALL_WINDOW.DAT $ EDIT/TPU/INTER=DECWINDOWS LOGIN.COM 4-19 Programmer Release Notes 4.6 DECwindows Extensions to Motif 4.6 DECwindows Extensions to Motif This section contains information about the extensions to the Motif Toolkit. 4.6.1 Changes and Enhancements The following notes describe changes and enhancements made to the DECwindows Extensions to Motif. 4.6.1.1 SVN Widget Supports Extended Selection V1.2-6 The Structured Visual Navigation (SVN) widget now allows users to extend a range of selection using the Shift+Down- Arrow key sequence. Note that this change has also been applied to the sample program SVNMSAMPLE.C. 4.6.1.2 DXmCSText Input Method Support V1.2 X11 R5 input method support is added to the DXmCSText widget. Specify input methods using the vendor shell XmNinputMethod resource. However, to maintain backward compatibility, the existing input method resources DXmNinputMethod and DXmNinputMethodType are still available. 4.6.2 Problems and Restrictions The following notes describe known problems and restrictions that currently exist with the DECwindows Extensions to Motif. 4.6.2.1 DXmFormSpaceButtonsEqually Restriction V1.1 The convenience routine DXmFormSpaceButtonsEqually sizes and spaces all widgets or gadgets equally if they have a subclass of XmLabel or XmLabelGadget. The results are undefined if a widget or gadget is not a subclass of XmLabel or XmLabelGadget. 4-20 Programmer Release Notes 4.6 DECwindows Extensions to Motif 4.6.2.2 SVN Widget Does Not Support Horizontal Live Scrolling V1.0 Horizontal live scrolling is not supported in the SVN widget. 4.6.3 Corrections The following notes describe the resolution of any problems specific to the DECwindows Extensions to Motif that previously resulted in an error or required a workaround. 4.6.3.1 Calling DXmSvnDeleteEntries after DXmSvnAddEntries V1.2-6 Calling the DXmSvnDeleteEntries routine after a call to the DXmSvnAddEntries routine no longer causes the related application to crash. 4.7 Display Server Extensions This section contains information about the display server extensions. 4.7.1 Changes and Enhancements The following notes describe changes and enhancements made to the display server extensions. 4.7.1.1 Shared Memory Extension Support (Alpha Only) V1.2 On OpenVMS Alpha systems, shared memory extension support provides the capability to share memory XImages. This is a version of the XImage interface where the actual image data is stored in a shared-memory segment. Consequently, the image does not need to be moved through the Xlib interprocess communication channel. For large images, use of this extension can result in dramatic performance increases. Support for shared memory pixmaps is also provided. Shared memory pixmaps are two-dimensional arrays of pixels in a format specified by the X server, where the image data is stored in the shared memory segment. Through the use of shared memory pixmaps, you can change the contents of these pixmaps without using any Xlib routines. 4-21 Programmer Release Notes 4.7 Display Server Extensions These routines are included in the client side extension library. See Section 4.7.1.4 for details on linking this library. 4.7.1.1.1 How to Use Shared Memory Extension Code that uses the shared memory extension must include the following header files: # include "DECW$INCLUDE:Xlib.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. In some cases, such as running over the network, the extension does not work. To check if the shared memory extension is available on your system, call one of the following routines: Status XShmQueryExtension (display) Display *display Status XShmQueryVersion (display, major, minor, pixmaps) Display *display; int *major, *minor; Bool *pixmaps The following table lists each argument and its description. ___________________________________________________________ Argument____Description____________________________________ display The current display. If the shared memory extension is used, the return value from either function is True. Otherwise, your program operates using conventional Xlib calls. major Major version number of the extension implementation. Returned by XShmQueryVersion. minor Minor version number of the extension implementation. Returned by XShmQueryVersion. pixmaps_____True,_if_shared_memory_pixmaps.________________ 4-22 Programmer Release Notes 4.7 Display Server Extensions 4.7.1.1.2 Using Shared Memory XImages The following sequence shows the process for creating and using shared memory XImages: 1. Create the shared memory XImage structure. 2. Create a shared memory segment to store the image data. 3. Attach the shared memory segment. 4. Inform the server about the shared memory segment. 5. Use the shared memory XImage. The following sections explain each step in this process: Step 1-Creating a Shared Memory XImage Structure To create a shared memory XImage, use the XShmCreateImage routine, which has the following format: XImage *XShmCreateImage (display, visual, depth, format, data, shminfo, width, height) Display *display; Visual *visual; unsigned int depth, width, height; int format; char *data; XShmSegmentInfo *shminfo; Most of the arguments are the same as for XCreateImage (See the X Window System for a description of the XCreateImage routine.) Note that there are no offset, bitmap_pad, or bytes_per_line arguments. These quantities are set by the server, and your code needs to abide by them. Unless you have already allocated the shared memory segment (see step 2), you pass in NULL for the data pointer. The argument shminfo is a pointer to a structure of type XShmSegmentInfo. Allocate one of these structures so that it has a lifetime at least as long as that of the shared memory XImage. There is no need to initialize this structure before the call to XShmCreateImage. If successful, an XImage structure is returned, which you can use for the subsequent steps. 4-23 Programmer Release Notes 4.7 Display Server Extensions Step 2-Creating the Shared Memory Segment Create the shared memory segment after the creation of the XImage because the XImage returns information that indicates how much memory to allocate. The following example illustrates how to create the segment: shminfo.shmid = shmget (IPC_PRIVATE, image->bytes_per_line * image->height, IPC_CREAT|0777); This example assumes that you called your shared memory XImage structure. A return value of 0 indicates the shared memory allocation has failed. Use the bytes_per_line field, not the width you used to create the XImage, as they may be different. Note that the shared memory ID returned by the system is stored in the shminfo structure. The server needs that ID to attach itself to the segment. Step 3-Attaching the Shared Memory Segment Attach the shared memory segment to your process as in the following example: shminfo.shmaddr = image->data = shmat (shminfo.shmid, 0, 0); The address returned by shmat is stored in both the XImage structure and the shminfo structure. To finish supplying arguments in the shminfo structure, decide how you want the server to attach to the shared memory segment, and set the shminfo.readOnly field as follows: shminfo.readOnly = False; If you set the structure to True, the server cannot write to this segment, and XShmGetImage calls fail. ________________________ Note ________________________ The shared memory segment routines are provided with DECwindows Motif. Using global sections, these routines emulate the shared memory routines on UNIX systems. ______________________________________________________ 4-24 Programmer Release Notes 4.7 Display Server Extensions Step 4-Informing the Server About the Shared Memory Segment Tell the server to attach to your shared memory segment as in the following example: Status XShmAttach (display, shminfo); If successful, a nonzero status is returned, and your XImage is ready for use. Step 5-Using the Shared Memory XImage To write a shared memory XImage into an X drawable, use the XShmPutImage routine. The XShmPutImage routine uses the following format: XShmPutImage (display, d, gc, image, src_x, src_y, dest_x, dest_y, width, height, send_event) Display *display; Drawable d; GC gc; XImage *image; int src_x, src_y, dest_x, dest_y; unsigned int width, height; Bool send_event; The interface is identical to the XPutImage routine (see the X Window System), except for one additional parameter, send_event. If this parameter is passed as True, the server generates a completion event when the image write is complete. This allows your program to know when it is safe to begin manipulating the shared memory segment again. The completion event is of the type XShmCompletionEvent, which is defined as follows: typedef struct { inttype; /* of event */ unsigned long serial; /* # of last request processed */ Bool send_event; /* true if came from a SendEvent request */ Display *display; /* Display the event was read from */ Drawable drawable; /* drawable of request */ int major_code; /* ShmReqCode */ int minor_code; /* X_ShmPutImage */ ShmSeg shmseg; /* the ShmSeg used in the request */ unsigned long offset; /* the offset into ShmSeg used */ } XShmCompletionEvent; 4-25 Programmer Release Notes 4.7 Display Server Extensions To determine the event type value that is used at run time, use the XShmGetEventBase routine as in the following example: int CompletionType = XShmGetEventBase (display) + ShmCompletion; ________________________ Note ________________________ If you modify the shared memory segment before the arrival of the completion event, the results may be inconsistent. ______________________________________________________ To read image data into a shared memory XImage, use the XShmGetImage routine, which uses the following format: Status XShmGetImage (display, d, image, x, y, plane_mask) Display *display; Drawable d; XImage *image; int x, y; unsigned long plane_mask; The following table lists each argument and its description. ___________________________________________________________ Argument____Description____________________________________ display The display of interest. d The source drawable. image The destination XImage. x X-offset within the source drawable. y Y-offset within the source drawable. plane_mask__The_planes_that_are_to_be_read.________________ To destroy a shared memory XImage, first instruct the server to detach from it, then destroy the segment itself. 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-26 Programmer Release Notes 4.7 Display Server Extensions 4.7.1.1.3 Using Shared Memory Pixmaps Unlike X images, for which any image format is usable, the shared memory extension supports only a single format for the data stored in a shared memory pixmap (XYPixmap or ZPixmap). This format is independent of the depth of the image and independent of the screen. (For 1-bit pixmaps the format is irrelevant.) The XShmPixmapFormat routine returns the shared memory pixmap format for the server. The XShmPixmapFormat routine has the following format: int XShmPixmapFormat (display) Display *display; Your application can only use shared memory pixmaps in the format returned by the XShmPixmapFormat routine (including bits-per-pixel). To create a shared memory pixmap do the following: o Create a shared memory segment and shminfo structure exactly the same way as is listed for shared memory XImages steps 1 through 4 (see Section 4.7.1.1.2). While it is not necessary to create an XImage first (step 1), doing so incurs little overhead and provides an appropriate bytes_per_line value to use. o Call the XShmCreatePixmap routine, which has the following format: Pixmap XShmCreatePixmap (display, d, data, shminfo, width, height, depth); Display *display; Drawable d; char *data; XShmSegmentInfo *shminfo; unsigned int width, height, depth; The arguments are the same as for XCreatePixmap (see the X Window System) except for two additional parameters, data and shminfo. The data parameter is the pointer to the shared memory segment and is the same as the shminfo.shmaddr field. The shminfo parameter is the same as the previous structure. 4-27 Programmer Release Notes 4.7 Display Server Extensions If successful, a pixmap is returned, which you can manipulate. You can manipulate its contents directly through the shared memory segment. Shared memory pixmaps are destroyed with the XFreePixmap routine, although you should detach and destroy the shared memory segment (see step 4 in Section 4.7.1.1.2). 4.7.1.2 Specifying Extension Include Files V1.2 To ensure that programs that contain extension include files compile properly, add the logical name DECW$INCLUDE to the C include directory search list. To add the logical name for VAX C, enter the following command: $ DEFINE C$INCLUDE DECW$INCLUDE To add the logical name for DEC C, enter the following command: $ DEFINE DECC$USER_INCLUDE DECW$INCLUDE 4.7.1.3 X Image Extension Support V1.1 Starting with DECwindows Motif Version 1.1 for OpenVMS, DECwindows Motif supports the X Image Extension (XIE). XIE allows image display processing using resources on the server side of the X client-server model. XIE eliminates the need to transmit image data repeatedly from the client to the server and also allows data to be transmitted in compressed form, reducing the network load. DECwindows Motif includes the XIE client side sharable library (XIE$SHRLIB.EXE) and C language header files. These allow applications to communicate with any X11 server that supports the XIE extension. An XIE program uses a structure called the XIEImage to describe image data on the client side. This general mechanism describes data that the destination server is incapable of processing. Consult the documentation for the server system for information on what data types and sizes are supported. Unless the documentation specifies different limits, the server is capable of processing unsigned byte (UdpK_DTypeBU), unaligned bit field (UdpK_ 4-28 Programmer Release Notes 4.7 Display Server Extensions DTypeVU), and aligned bit field (UdpK_DTypeV) data, with a maximum depth of 8 bits per pixel per component. The XIE client library supports these data types, as well as unsigned word (UdpK_DTypeWU), and a depth of up to 16 bits per pixel per component. The XIE protocol and programming interface are being standardized within the X Consortium for R6, and programs that use XIE will probably have to be modified. You can use the Image Display Services (IDS) component of DECimage Application Services for VMS as an alternative to the XIE library interface. IDS provides a higher level model of image display and automatically uses XIE when it is available and appropriate. 4.7.1.4 Client Side Extension Library Available V1.1 Starting with DECwindows Motif Version 1.1 for OpenVMS, Xlib added a client side library that allows OpenVMS clients to issue Shape, XInput, Multibuffer, and shared memory extension requests to servers that provide these features. (For example, the DECwindows X11 display server for OpenVMS VAX does not support the Shape extension while the DECwindows X11 display server for OpenVMS Alpha system does support Shape.) The name of this library is DECW$XEXTLIBSHR.EXE. You must modify the linking file options for client applications that issue Shape, XInput, Multibuffer, or shared memory extension requests to link to the Xlib extensions shareable image in SYS$LIBRARY:DECW$XEXTLIBSHR.EXE. Add the following line to your linker options file: SYS$LIBRARY:DECW$XEXTLIBSHR/SHARE For more information on Shape, XInput, and Multibuffer extensions, see the following text files in SYS$HELP: DECW$SHAPE.TXT DECW$XINPUT.TXT DECW$MULTIBUFFER.TXT 4-29 Programmer Release Notes 4.8 Internationalization 4.8 Internationalization This section contains release notes pertaining to internationalization and localization. 4.8.1 Changes and Enhancements The following notes describe changes and enhancements made to internationalization and localization support. These changes enable users to view and convert files that contain Asian-language characters. 4.8.1.1 Using the CDA Viewer to View Asian-Language Text V1.2-3 You can use the CDA Viewer in two ways to view text files that contain Asian characters: o Specify an options file to the CDA Viewer application. o Define logical names at the DCL command level or in a LOGIN.COM file. Refer to the DECwindows Motif for OpenVMS Applications Guide for information about using the CDA Viewer. 4.8.1.1.1 Specifying an Options File Specify an options file by including a one-line entry in the file in the following format: TEXT TEXT_ENCODING text_encoding_value o TEXT is the format. o TEXT_ENCODING is the option you specify to CDA. o text_encoding_value is the value of the codeset. (See Table 4-5 for a list of values.) Table 4-5 shows the languages, codesets, and text-encoding values. 4-30 Programmer Release Notes 4.8 Internationalization Table_4-5_Asian_Language_Codes_for_Options_Files___________ Language_________Codeset__________Text_Encoding_Value______ Japanese DEC Kanji DEC_KANJI Japanese Super DEC Kanji SDECKANJI Traditional DEC Hanyu DEC_HANYU Chinese Simplified DEC Hanzi DEC_HANZI Chinese Korean___________DEC_Korean_______DEC_HANGUL_______________ The following table shows examples of one-line entries. ___________________________________________________________ Options_File_____________One-Line_Entry____________________ HANYU.CDA$OPTIONS TEXT TEXT_ENCODING DEC_HANYU HANZI.CDA$OPTIONS TEXT TEXT_ENCODING DEC_HANZI HANGUL.CDA$OPTIONS_______TEXT___TEXT_ENCODING___DEC_HANGUL_ To view the EXAMPLES_CUSTOMERS.TXT file that contains Japanese text in DEC Kanji, use your editor to create an options file called KANJI.CDA$OPTIONS. Add the following one-line entry to the file: TEXT TEXT_ENCODING DEC_KANJI When you access the file through the Options File dialog box with the CDA Viewer, the EXAMPLES_CUSTOMERS.TXT file is viewable in the DEC Kanji codeset (Japanese language). 4.8.1.1.2 Defining Logical Names The second option to enable viewing files in Asian 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 Table 4-6 shows the logical names and associated encoding values. 4-31 Programmer Release Notes 4.8 Internationalization Table_4-6_Logical_Names_for_Specifying_Text_Encoding_______ DDIF$READ_TEXT_GL_____DDIF$READ_TEXT_GR_____Encoding_Value_ LATIN1 MCS MCS LATIN1 LATIN1 ISO Latin-1 LATIN1 KATAKANA ASCII-Kana LATIN1 KANJI DEC Kanji ROMAN MCS Roman-MCS ROMAN LATIN1 Roman ROMAN KANJI Roman-Kanji ROMAN KATAKANA Roman-Kana LATIN1 HANZI DEC Hanzi LATIN1 HANGUL DEC Hangul LATIN1________________HANYU_________________DEC_Hanyu______ You can define the logical names on the DCL command line or in your LOGIN.COM file. For example: $ DEFINE DDIF$READ_TEXT_GL LATIN1 $ DEFINE DDIF$READ_TEXT_GR KANJI Note that this example defines the text encoding for DEC Kanji (see Table 4-6). 4.8.1.2 Converting Files That Contain Asian-Language Characters V1.2-3 You can convert an Asian-language text file to another format by specifying an options file or by defining the logical names DDIF$READ_TEXT_GL and DDIF$READ_TEXT_GR as discussed in Section 4.8.1.1.1 and Section 4.8.1.1.2. The format for converting a document from TEXT to another format is as follows: $ CONVERT/DOCUMENT/OPTION=language.CDA$OPTIONS filename.TXT/FORMAT=TEXT - _$ filename.output_extension/FORMAT=output_format For example, to convert a traditional Chinese language text file to a DDIF file, enter the following command line: $ CONVERT/DOCUMENT/OPTION=HANYU.CDA$OPTIONS - _$ GUIDELINES_PERSONNEL.TXT/FORMAT=TEXT GUIDELINES_PERSONNEL.DDIF 4-32 Programmer Release Notes 4.8 Internationalization Note that this command line does not include the /FORMAT=DDIF qualifier; DDIF is the default. The output file, GUIDELINES_PERSONNEL.DDIF, contains language data. You can also create Asian language PostScript files from a DDIF, DTIF, or text (ASCII) file. For example, to convert a DDIF file to PostScript (.PS) format, enter the following command: $ CONVERT/DOCUMENT filename.DDIF filename.PS/FORMAT=PS ________________________ Note ________________________ Convert only DDIF and DTIF files that contain language data to Asian language PostScript format. ______________________________________________________ When you print an Asian language PostScript file on a PostScript printer, ensure that the required language fonts are available on the printer. Otherwise, the PostScript file defaults to a basic set of fonts. If these fonts do not exist, the PostScript file defaults to Courier fonts. Table 4-7 shows the languages and their associated basic fonts. Table_4-7_Languages_and_Associated_Basic_Fonts_____________ Language______________Basic_Fonts__________________________ Japanese Ryumin-Light-EUC-H or Ryumin-Light- Hankaku Hanyu Sung-Light-CNS11643, Sung-Light-DTSCS Hangul Munjo Hanzi_________________XiSong-GB2312-80_____________________ ________________________ Note ________________________ Vertical writing is not supported by the CDA converters. All vertical text is printed horizontally. ______________________________________________________ 4-33 Programmer Release Notes 4.9 XNL Library 4.9 XNL Library This section contains information about the XNL library. 4.9.1 Changes and Enhancements The following notes describe changes and enhancements made to the XNL library. 4.9.1.1 xnl_parsedatetime V1.2-5 xnl_parsedatetime (and its VAX binding, XNL$PARSE_DATE_ TIME) accepts two-digit or four-digit years in the input argument XmString s (which is the date-time string to be parsed). Valid years in the two-digit format are in the range 70 to 99, which mean the years from 1970 to 1999. Values from 00 to 69 are invalid. Year 2000 and later must be specified in the four-digit format. 4.9.1.2 xnl_langinfo V1.2-5 xnl_langinfo (and its VAX binding, XNL$LANGINFO) returns a string for date-time formatting when D_FMT or D_T_FMT is specified in the item argument. In the locales listed below, this function returns a formatting string containing %y. This formatting string should be used carefully after the year 2000, as %y indicates the two-digit year format. o es_ES Spanish o fr_BE French Belgium o fr_CA French Canada o iw_IL Hebrew o no_NO Norwegian 4.10 Xlib This section contains information about Xlib. 4-34 Programmer Release Notes 4.10 Xlib 4.10.1 Changes and Enhancements The following notes describe changes and enhancements made to the Xlib. 4.10.1.1 X11 Environment Variable Parsing V1.2-6 Xlib now accepts the equivalent X11 Release 5 (X11 R5) forms of the following environment variables: ___________________________________________________________ OpenVMS_Form______X11_R5_Form______________________________ DECW$DISPLAY DISPLAY DECW$RESOURCE_ RESOURCE_NAME NAME_______________________________________________________ On startup, if the OpenVMS variable is not defined, Xlib then checks for the X11 R5 equivalent before returning a status value. 4.10.1.2 UIDPATH Environment Variable V1.2-6 When opening a hierarchy, Xlib searches the DECW$USER_ DEFAULTS and DECW$SYSTEM_DEFAULTS areas for the User Interface Definition (UID) file. On UNIX systems and according to X11 R5 specifications, the search path is defined using the UIDPATH variable and its fallbacks. Now, Xlib also checks for the UIDPATH variable if the UID file is not found using either of the OpenVMS variables state above. This variable references a UNIX-style pathname (for example, /foo/bar) and allows the substitutions strings as specified by X11 standards. For more information on the UIDPATH variable, see the OSF/Motif Programmer's Reference. ________________________ Note ________________________ The UIDPATH variable does not work with OpenVMS directory specifications. Use the DECW$xxx_DEFAULTS logicals to specify OpenVMS-style search paths. ______________________________________________________ 4-35 Programmer Release Notes 4.10 Xlib 4.10.1.3 New Default Format for XtResolvePathname V1.2-6 In XtResolvePathname, the default pathname is required to have certain properties when either no other path information is present in the call, or when it is referenced by the environment variable XFILESEARCHPATH. The former default OpenVMS format of the pathname consisted of a type-name-suffix substitution. The modified pathname now reflects the 6-part fallback, as specified by X11 Release 5. The new pathname behavior is enabled by setting the DECW$VSW_COMPLIANT variable, as follows: $ DEFINE DECW$VSW_COMPLIANT 1 4.10.1.4 XtAppMainLoop Routine V1.2-5 Previously, if a program entered its event loop, (for example, by calling XtAppMainLoop) without having opened a display or specified a timer or event flag for the program to wait for (by calling XtAppAddTimeout or XtAppAddInput), Xlib terminated the program with the following error message: X Toolkit Error: Error in XMultiplexInput Starting with DECwindows Motif Version 1.2-5 for OpenVMS, if there is nothing to wait for, Xlib stalls waiting for input instead of terminating with an error status. To allow Xlib to process events at a later time, applications should provide some means of regaining control, such as specifying an event flag by calling XtAppAddInput. 4.10.1.5 Locale Support in OpenVMS Systems V1.2-4 The locale support provided in DECwindows Motif Version 1.2-4 for OpenVMS is compatible with the locale support in the DEC C Run-Time Library. If you write internationalized applications using these functions in the locale environment, do the following: 4-36 Programmer Release Notes 4.10 Xlib o For Xlib applications, include . If you include , you must do so before . o For Motif applications, is automatically included. o Turn on the following compilation flags: /define=(X_LOCALE,X_WCHAR,_WCHAR_T_,XLIB_XPG4_FUNCS) 4.10.1.6 Xlib Internationalization V1.2 The X Window System Version 11, Release 5 (X11 R5) defines a number of services to support writing internationalized X applications. Internationalization of X is based on the concept of a locale. A locale defines the localized behavior of a program at run time. Locales affect Xlib by: o Encoding and processing input method text o Encoding resource files and values o Encoding and imaging text strings o Encoding and decoding for interclient text communication The X Window System defines a general methodology and a set of application programming interfaces (APIs) to standardize programming in X. Standards have not been established for implementing these internationalization features. Currently, the X11 R5 distribution makes two sample implementations of Xlib internationalization support available: Xsi and Ximp. In addition, Compaq provides an implementation called Xi18n. You can select which I18N implementation you want. All three implementations provide the same functionality through the same set of public APIs, but their underlying processing differs. These differences are described in the following sections. 4-37 Programmer Release Notes 4.10 Xlib 4.10.1.6.1 Vendor Pluggable Layer Compaq provides a general mechanism called the vendor pluggable layer, which allows you to choose your own internationalization implementations. Different implementations can be built as standalone shareable libraries and can be selected through the logical DECW$XVENDORLAYER. If this logical is not defined, the mechanism searches for an internationalization implementation library in the following order: DECW$XI18NLIBSHR (Xi18n) DECW$XSILIBSHR (Xsi) DECW$XIMPLIBSHR (Ximp) If a shareable library is not found, the default is the Xi18n implementations that are already linked with Xlib. The following functions act as interfaces between Xlib and the internationalization implementation shareable library: XDefaultString XwcFreeStringList XwcTextListToTextProperty XmbTextListToTextProperty XwcTextPropertyToTextList XmbTextPropertyToTextList _XrmInitParseInfo _XlcDefaultLoader When creating the Xsi or the Ximp shareable library, you need to know the names of the interfaces because they are defined within Xlib. Compaq recommends that you rename the functions during compilation by adding the following compilation flags: /define=(- "XDefaultString"="_XDefaultString",- "XwcFreeStringList"="_XwcFreeStringList",- "XwcTextListToTextProperty"="_XwcTextListToTextProperty",- "XmbTextListToTextProperty"="_XmbTextListToTextProperty",- "XwcTextPropertyToTextList"="_XwcTextPropertyToTextList",- "XmbTextPropertyToTextList"="_XmbTextPropertyToTextList",- "_XrmInitParseInfo"="__XrmInitParseInfo",- "_XlcDefaultLoader"="__XlcDefaultLoader") 4-38 Programmer Release Notes 4.10 Xlib 4.10.1.6.2 Compaq Internationalization Xlib Implementation The Compaq implementation (Xi18n) provides enhanced support and a stable internationalization environment. The Compaq implementation (Xi18n) provides the following advantages over the Xsi or Ximp environments provided with the X distribution: o Most European locales and Asian locales are supported by the DECwindows Motif version of Xlib. o New locales can easily be supported without changing Xlib. New locales can be added by plugging in a locale- specific shareable library and a corresponding X locale database file for that locale. o Encoding of input processing can be different from output encodings. The output methods create a default font set and use available font resources installed in the X server. The code conversion is transparent to the user. 4.10.1.7 XSelectAsyncEvent and XSelectAsyncInput Routines V1.1 The XSelectAsyncEvent and XSelectAsyncInput routines allocate memory for the storage of AST delivery information. This memory is freed in the following ways: o If you close a display (XCloseDisplay), all the AST delivery information associated with all windows on that display is freed. o If you destroy a window (XDestroyWindow), the AST delivery information for that window is freed. The AST delivery information for subwindows is not freed by XDestroyWindow. If you want to turn off AST notification for all event types within a given window and also free the AST delivery information, the client application can call XSelectAsyncEvent or XSelectAsyncInput passing the event_ mask argument equal to minus one (all bits set) and the ast_routine argument equal to zero. 4-39 Programmer Release Notes 4.10 Xlib 4.10.1.8 Command Procedure Builds .PEN Files V1.0 To allow Pascal programs to inherit environment files for Xlib and Motif, execute the command procedure SYS$LIBRARY:DECW$PEN_BUILD.COM. This command procedure generates the DECW$XLIBDEF.PEN and DECW$MOTIF.PEN files. The .PEN files compile into Pascal programs faster than the provided .PAS files. 4.10.2 Corrections The following notes describe the resolution of any problems specific to Xlib that previously resulted in an error or required a workaround. 4.10.2.1 UNIX Filename Emulation (Alpha Only) V1.2-6 Previously, UNIX-style filenames with embedded path syntax "../" within functions such as XtResolvePathname and MrmOpenHierarchy were not handled correctly. While this syntax is highly unusual, it can occur when both the filename and the pathname contain a relative path specification. This problem has been corrected; UNIX-style filenames with this embedded syntax are parsed as expected. 4.10.2.2 XmTextField Widget Switches Focus Correctly V1.2-6 A crash no longer occurs when the losingFocus callback peforms an XtSetValues() on an XmTextField routine. 4.10.2.3 XrmoptionStickyArg Produces Correct Results V1.2-6 Problems with the XrmoptionStickyArg routine have been corrected; this routine no longer returns incorrect results when referenced from the command line. 4-40 Programmer Release Notes 4.10 Xlib 4.10.2.4 PAllHints Macro Corrected V1.2-6 The value of the PAllHints macro in XUTILS.H has been corrected. 4.10.3 Problems and Restrictions The following notes describe problems and restrictions that currently pertain to Xlib. 4.10.3.1 XtOpenDisplay Routine and Case Sensitivity V1.2-6 In some cases the application name in XtOpenDisplay comes from argv[0], which represents the name of the application on the command line. Be aware that case sensitivity must be preserved in such environments as when referencing ODS-5 system with case preservation enabled or when passing a user-defined argv list. 4.10.3.2 Parameter/Protocol Datasize Mismatches V1.0 Several Xlib routines accept longword parameters that are not sent in their entirety in the X Protocol message to the server. In each case, the Xlib routine sends out only the least significant 16 bits of the parameter value. This is a constraint of the field size within the X Protocol message. Table 4-8 lists routine names and the longword arguments that are sent only as 16-bit values. Table_4-8_Routine_Names_and_Arguments_Sent_as_16-Bit_Values Routine_Name_______________________Routine_Arguments_______ XAllocColorCells/ALLOC_COLOR_ nplanes,npixels CELLS XDrawArc/DRAW_ARC x,y,width,height, angle1,angle2 (continued on next page) 4-41 Programmer Release Notes 4.10 Xlib Table 4-8 (Cont.) Routine Names and Arguments Sent as 16- __________________Bit_Values_______________________________ Routine_Name_______________________Routine_Arguments_______ XDrawLine/DRAW_LINE x1,x2,x3,x4 XDrawPoint/DRAW_POINT x,y XDrawRectangle/DRAW_RECTANGLE x,y,width,height XDrawString/DRAW_STRING x,y XDrawString16/DRAW_STRING16 x,y XDrawText/DRAW_TEXT x,y XDrawText16/DRAW_TEXT16 x,y XFillArc/FILL_ARC x,y,width, height,angle1,angle2 XFillRectangle/FILL_RECTANGLE______x,y,width,height________ 4-42 5 _________________________________________________________________ Documentation Release Notes This chapter describes corrections to the DECwindows Motif documentation. 5.1 Getting Started With the New Desktop This section contains documentation corrections to the Getting Started With the New Desktop manual. 5.1.1 File Specification Incorrect V1.2-5 A file specification for a command procedure in Getting Started With the New Desktop (part number AA-QUW1A-TE) is incorrect. The file specification appears in Section 3.4.9, paragraph 5, as follows: "Optional DECwindows applications, such as DECwindows Notes, may not provide any information and therefore are not restarted. For such cases, there is a command procedure called disk$:[user.DT]SESSIONETC.COM that you can use to start any applications that cannot be restarted automatically. This procedure is analogous to the DECW$LOGIN.COM procedure in the traditional DECwindows environment." The correct file specification is: disk$:[user.DT.SESSIONS]SESSIONETC.COM 5.2 DECwindows Motif for OpenVMS Applications Guide This section contains documentation corrections to the DECwindows Motif for OpenVMS Applications Guide manual. 5-1 Documentation Release Notes 5.2 DECwindows Motif for OpenVMS Applications Guide 5.2.1 Enhancing Information About the Finish Printing Option V1.2-3 The section called "Printing Information" in the chapter on DECterm provides information about the Print menu. To further clarify the information in the Finish Printing section, note the following: Selecting the Finish Printing option on the Print menu closes the print job and toggles Auto Print mode back to Normal Print mode. 5-2 Documentation Release Notes 5.3 Using DECwindows Motif for OpenVMS 5.3 Using DECwindows Motif for OpenVMS This section contains documentation corrections and enhancements to the Using DECwindows Motif for OpenVMS manual. 5.3.1 Using the Drag-and-Drop Feature V1.2 The drag-and-drop feature lets you move or copy screen objects. For example, you can move text from buttons and paste it elsewhere. To drag and drop text into a new location: 1. Select the text to be copied or moved with MB1. 2. To move the text, press and hold MB2; to copy the text, press and hold Ctrl/MB2. A move or copy icon appears. 3. Drag the icon to the location where you want to drop the text and release MB2. If the object is highlighted as you drag the icon across it, you can drop the text into that location. Drag-and-drop is provided primarily for programmers to incorporate the feature into their applications. The DECwindows Motif Version 1.2 for OpenVMS applications support the drag-and-drop feature, with the exception of Notepad. DECwindows Mail supports drag-and-drop in all windows except the main message area, where DECwindows Mail has its own drag-and-drop feature; you can use MB2 to move messages around with the SVN interface. 5.3.2 Using Tear-Off Menus V1.2-3 The DECwindows Mail application supports tear-off menus. V1.2 The DECwindows Motif applications allow you to tear off pull-down and popup menus. Tear-off menus let you keep frequently used menus displayed without repeatedly pulling them down or popping them up. 5-3 Documentation Release Notes 5.3 Using DECwindows Motif for OpenVMS To tear off a menu: 1. Display a pull-down or popup menu. If the menu is a tear-off menu, a dotted line is displayed at the top of the menu. 2. Click on the dotted line with MB1. The menu remains active until it is closed or until the parent application is closed. To close a tear-off menu: 1. Click on the Window menu button in the tear-off menu. 2. Choose the Close menu item. The following applications do not support tear-off menus: o CDA Viewer o DECwindows Mail o Notepad o Print Screen 5.3.3 Adding Target Screen Options to Application Menu Items V1.2 The example "Adding Target Screen Options to Application Menu Items" in Using DECwindows Motif for OpenVMS is incorrect. To correct the problem, remove the first occurrence of the following line: $ select_qualifiers: 5.3.4 Changing the Startup Environment V1.2 The example "Changing Your Logo" is incorrect. To correct the problem, change the following code example in step one: $ COPY SYS$COMMON:[SYSMGR]DECW$PRIVATE_APPS_SETUP.TEMPLATE - _$ SYS$SPECIFIC:[SYSMANAGER]DECW$PRIVATE_APPS_SETUP.COM/LOG The code example should read as follows: $ COPY SYS$COMMON:[SYSMGR]DECW$PRIVATE_APPS_SETUP.TEMPLATE - _$ SYS$SPECIFIC:[SYSMGR]DECW$PRIVATE_APPS_SETUP.COM/LOG 5-4 Documentation Release Notes 5.3 Using DECwindows Motif for OpenVMS 5.3.5 Enhancing Startup Performance V1.1 Extensive SYLOGIN.COM or LOGIN.COM command procedures slow down application startup. Many of the operations performed in a SYLOGIN.COM or LOGIN.COM are meaningless for DECwindows application startup. Therefore, the SYLOGIN.COM and LOGIN.COM files should be conditionalized for DECwindows application startup performance. When starting a DECwindows application, a minimum of SYLOGIN.COM and LOGIN.COM commands should be executed. Typically, the commands that should be executed are the redefinition of DECW$USER_DEFAULTS (if present), and other logical name definitions if the user will be referencing them from within the context of a DECwindows application. The following code segment can be inserted into SYLOGIN.COM and LOGIN.COM immediately following the commands necessary for DECwindows: $ mode = f$mode() $ tt_devname = f$trnlnm("TT") $ session_mgr_login = (mode .eqs. "INTERACTIVE") .and. - (f$locate("WSA",tt_devname) .ne. f$len(tt_devname)) $ session_detached_process = (mode .eqs. "INTERACTIVE") .and. - (f$locate("MBA",tt_devname) .ne. f$len(tt_devname)) $ if session_mgr_login .or. session_detached_process then exit Applications continue to run even if these lines are not added to the SYLOGIN.COM and LOGIN.COM files. 5.3.6 Enhancing Hold-Screen Response Time V1.1 If the Hold Screen key response time is too slow, add the following lines to your DECW$TERMINAL_DEFAULT.DAT file: DECW$TERMINAL.main.terminal.syncFrequency: 1 DECW$TERMINAL.main.terminal.batchScrollCount: 1 Using this resource can affect the performance of the DECterm window. The actual impact on performance varies from site to site. You can trade off scrolling speed to hold-screen response time. A faster hold-screen response results in a slower scrolling speed. The default values for these resources are 10 and 0, respectively. 5-5 Documentation Release Notes 5.4 Managing DECwindows Motif for OpenVMS Systems 5.4 Managing DECwindows Motif for OpenVMS Systems This section contains documentation enhancements and corrections to the Managing DECwindows Motif for OpenVMS Systems manual. 5.4.1 Global Symbols V1.2-3 The following additional global symbols are available in the Compaq DECwindows Motif for OpenVMS product: o DECW$CONSOLE_SELECTION Specifies how to display operator-messages options. o DECW$CONSOLE_GEOMETRY Specifies the value of the -geometry option in the DECW$MESSAGEPANEL.EXE command line. For information about using these symbols, refer to Section 3.4.1.1 in these Release Notes. Refer to the chapter "Using DECwindows" in Managing DECwindows Motif for OpenVMS Systems for the complete list of global symbols. 5.4.2 Security Options V1.2 In the Session Manager Security Options dialog box, place the node name within quotation marks if the name contains any of the following: o Reserved characters: space, tab, comma (,) or double quotation mark (") o Double colon (::) o A colon (:) as the final character in the node name Session Manager automatically adds quotation marks to the node name if they are needed, unless the node name begins with a double quotation mark. If the node name begins with a double quotation mark, Session Manager assumes that the user has already quoted the node name and does not change it. 5-6 Documentation Release Notes 5.4 Managing DECwindows Motif for OpenVMS Systems Within a quoted string, a double quotation mark should be replaced by two double quotation marks (" "). For example, the quoted string "DEC:.zko."my node"" should be changed to the following: ("DEC:.zko.""my node"""). 5.4.3 Displaying a Customized Logo V1.1 By default, if there is no DECwindows Motif license registered for the SYSTEM account, DECwindows does not display customized login logos. This is a problem on systems with DECwindows Motif personal-use licenses that do not include SYSTEM on the list of authorized DECwindows users. To display a customized logo without a DECwindows Motif license for SYSTEM, add the following definition to the SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM file: $ DECW$LOGINLOGOSUB == "TRUE" ________________________ Note ________________________ If the SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM file does not exist, copy it from the file SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.TEMPLATE. ______________________________________________________ After editing the setup file, restart DECwindows Motif using the following command: $ @SYS$MANAGER:DECW$STARTUP RESTART DECwindows Motif login starts the logo process as a subprocess instead of as a detached process. The license check sees that the logo process is a child of the login process and that the X connection is opened. 5-7 Documentation Release Notes 5.4 Managing DECwindows Motif for OpenVMS Systems 5.4.4 Enabling and Disabling Access Control V1.0 DECwindows Motif does not enable access control by default. Instead, it uses the access control set by the server. The DECwindows X11 display server enables access control at startup time. To force the DECwindows Session Manager to enable or disable access control explicitly at login time, you can define one of the following logical names: $ DEFINE/SYSTEM/EXECUTIVE DECW$LOGIN_ACCESS_CONTROL ENABLE $ DEFINE/SYSTEM/EXECUTIVE DECW$LOGIN_ACCESS_CONTROL DISABLE If the logical name is not defined, or if it is defined to some other value, such as "SERVER", DECwindows login neither enables nor disables access control. In most cases, it should not be necessary to define the logical name. 5.5 DECwindows Motif for OpenVMS Guide to Non-C Bindings This section contains documentation enhancements and corrections to the DECwindows Motif for OpenVMS Guide to Non-C Bindings. 5.5.1 GET_CHAR_STRUCT Function V1.2-3 The access related to the char_struct argument for the XLIB GET_CHAR_STRUCT function is incorrectly documented. The correct access is write. 5.6 VMS DECwindows Guide to Xlib (Release 4) Programming: VAX Binding V1.2 Example 1-1 in the VMS DECwindows Guide to Xlib (Release 4) Programming: VAX Binding is incorrect. To correct the problem, change the following two lines in the section "Create the WINDOW_1 window": WINDOW_1X = (X$WIDTH_OF_SCREEN(DPY) - WINDOW_1W) / 2 WINDOW_1Y = (X$HEIGHT_OF_SCREEN(DPY) - WINDOW_1H) / 2 5-8 Documentation Release Notes 5.6 VMS DECwindows Guide to Xlib (Release 4) Programming: VAX Binding The example should read as follows: WINDOW_1X = (X$WIDTH_OF_SCREEN(SCREEN) - WINDOW_1W) / 2 WINDOW_1Y = (X$HEIGHT_OF_SCREEN(SCREEN) - WINDOW_1H) / 2 Example 3-1 in the VMS DECwindows Guide to Xlib (Release 4) Programming: VAX Binding is incorrect. To correct the problem, change the following two lines: WINDOW_1X = (X$DISPLAY_WIDTH_OF_SCREEN(SCREEN) - WINDOW_1W) / 2 WINDOW_1Y = (X$DISPLAY_HEIGHT_OF_SCREEN(SCREEN) - WINDOW_1H) / 2 The example should read as follows: WINDOW_1X = (X$DISPLAY_WIDTH_OF_SCREEN(DPY) - WINDOW_1W) / 2 WINDOW_1Y = (X$DISPLAY_HEIGHT_OF_SCREEN(DPY) - WINDOW_1H) / 2 5.7 DECwindows Extensions to Motif This section lists documentation corrections and enhancements for the DECwindows Extensions to Motif document. 5.7.1 DXmNlayoutDirection Resource Constants 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 available for the DXmNlayoutDirection resource: o DXmLAYOUT_LEFT_UP o DXmLAYOUT_RIGHT_UP The introduction to Table 2-1 is incorrect. Table 2-1 describes the effect of the constants DXmLAYOUT_LEFT_DOWN and DXmLAYOUT_RIGHT_DOWN on the functions. V1.2 5-9 Documentation Release Notes 5.7 DECwindows Extensions to Motif In Section 2.2 of the DECwindows Extensions to Motif manual, the description of DXmChildren indicates that the routine can be used to learn the length of widget_list. The documentation is incorrect. The sentence should read, "You can use the DXmNumChildren routine to learn the length of the widget list returned by DXmChildren." 5.8 DECwindows Motif Guide to Application Programming This section lists documentation corrections and enhancements for the DECwindows Motif Guide to Application Programming manual. 5.8.1 UIL Source Code for the OpenVMS DECburger Application V1.2-3 The introduction to the section in Chapter 4 called "Creating the Help Widget with UIL", which introduces Example 4-6, "UIL Help Widget Implementation," does not clearly state that the complete UIL source code for the OpenVMS DECburger application is included in DECW$EXAMPLES on OpenVMS systems. 5.8.2 Help Widget Implementation Code V1.2-3 In the title of Example 4-7, "Help Widget Implementation-C Language Module", DECBURGER.C should be added to the title as follows: "Help Widget Implementation-C Language Module (DECburger.C)" 5.8.3 Help Widget Implementation-Callbacks V1.2-3 The title of Example 4-8 should read as follows: "Help Widget Implementation-Callbacks (DECburger.C continued)" 5-10 Documentation Release Notes 5.8 DECwindows Motif Guide to Application Programming 5.8.4 Using UIL to Create the Help Widget V1.2-3 The title of Section 4.10, "Using the Toolkit Help Widget Creation Routine," does not accurately reflect the contents of this section. The title should read, "Using UIL to Create the Help Widget". The introductory paragraph to Example 4-9 in the section called "Using the Toolkit Help Widget Creation Routine" is incomplete. The information should state the following: "The code in Example 4-9 is included in DECburger.C but is commented and will not be compiled when the example program is built." The implementation in this example is not complete; it requires some sections from Examples 4-7 and 4-8. To summarize, the documentation should state the following information: o Examples 4-6 and 4-7 are UIL code (DECburger.UIL(D)) that, when combined, create the DECburger.EXE. o Example 4-8 is C code for DECburger.EXE. o Example 4-9 is C code for a Toolkit example. 5-11 A _________________________________________________________________ OSF/Motif Release 1.2 Release Notes The release notes in this document are based on Chapter 3 of the OSF/Motif Release Notes for Release 1.2 and include a few other notes relevant to programmers developing OSF/Motif applications. Most of the notes describe changes made for OSF/Motif Release 1.2. The first two notes discuss performance improvements and information about backward compatibility. These release notes support the OSF/Motif software currently provided with the Compaq DECwindows Motif for OpenVMS product. A.1 Performance Improvements The Open Software Foundation set as its goal for OSF/Motif Release 1.2 to improve performance where possible and, at a minimum, to not allow it to degrade below the performance of OSF/Motif Release 1.1. Performance testing was done in three areas: o Aspects obvious to end users o Data space usage o Memory leakage The performance of user-perceptible events such as posting and unposting dialog boxes and pop-up menus are comparable or better than the performance for OSF/Motif Release 1.1.4. A significant improvement was made for scrolling inside a Scrolled Text region that contains a large amount of test. Data space usage has improved throughout the OSF/Motif Toolkit, particularly for the Text widget. In some cases, data space usage has been reduced by as much as 40%. Also, the memory used for the text in a Text widget is now A-1 OSF/Motif Release 1.2 Release Notes A.1 Performance Improvements correctly reduced when that text is replaced by a smaller amount of text. Memory leakage has been reduced to a minimum for multiple creates and destroys of all Toolkit widgets. Although the Motif tests showed small memory leaks, the OSF believes that this amount of memory is required as part of the startup overhead and is not a true memory leak. The OSF did find some memory leaks that they plan to fix in a future release. Three widgets-File Selection Box, Command, and Drawn Button - leak approximately 500 bytes of memory per instance. A.2 Backward Compatibility The OSF tested OSF/Motif Release 1.2 for both link- time compatibility as well as visual and behavioral compatibility. A.2.1 Visual and Behavioral Compatibility The OSF ran automated tests that compared current visuals with those recorded using OSF/Motif Release 1.1.4 libraries. Once all differences between the Release 1.2 and Release 1.1.4 versions were accounted for, the visuals were rerecorded using Release 1.2 visuals. These new recorded visuals were used in all subsequent tests. The OSF believes that Motif Release 1.2 is visually and behaviorally compatible with Release 1.1.4. However, they have made extensive improvements to the Traversal and Geometry Management algorithms that result in some differences between those versions. These differences reflect efforts to fix defects in the earlier release. For example, one such modification involves the new policy in which an initial size set for a manager widget in an application is now honored by the Toolkit. In OSF/Motif Release 1.1, applications set the initial size for a manager widget, but did not, in fact, use that size. In Release 1.2, Motif now uses that size setting and the initial layout is changed accordingly. A-2 OSF/Motif Release 1.2 Release Notes A.3 Changes and New Features for OSF/Motif Release 1.2 A.3 Changes and New Features for OSF/Motif Release 1.2 This section summarizes changes and new features that the OSF has made to OSF/Motif Release 1.2. Detailed information about these modifications is contained in the Motif reference pages and the Motif Release 1.2 revisions of following books: o OSF/Motif Style Guide o OSF/Motif Programmer's Guide The following sections discuss the OSF/Motif Release 1.2 enhancements. A.3.1 General Toolkit Changes This section discusses the changes made to the overall OSF/Motif Release 1.2 Toolkit. A.3.1.1 Include File Changes The following header files that were in OSF/Motif Release 1.1 are obsolete in Release 1.2: ExtObject.h Traversal.h VaSimple.h VendorE.h VendorEP.h A new public header file, XmAll.h, has been added to OSF/Motif Release 1.2. This header file includes all the documented header files. A.3.2 Change in XT Translations As a result of fixing a problem in the XT translation code (Patch 25 for X11 R5), the translations in Xt are now handled strictly and no longer accept any possible match as they did before. This change has caused a change in the behavior of the QATS and Motif VTS test suites, which now make incorrect assumptions for certain keyboards, such as those that have the arrow keys defined in the keypad. Other Motif applications might be affected as well. You can avoid this problem by creating a file to redefine the bindings for the keys in question and then passing that file to the xmodmap utility. A-3 OSF/Motif Release 1.2 Release Notes A.3 Changes and New Features for OSF/Motif Release 1.2 The following example changes the bindings for the keypad keys that match the arrow keys so that only the arrow keys are produced, not the keypad numbers. The new definitions allow the application to use modifiers with the arrow keys. ! ! Always force: ! KP_2 = Down ! KP_8 = Up ! KP_4 = Left ! KP_6 = Right keycode 120 = Down keycode 76 = Up keycode 98 = Left keycode 100 = Right A.3.3 ANSI C Compliance All references to caddr_t have been changed to XtPointer. This change affects all callback routines and any other routines that reference caddr_t. The OSF made this change so that OSF/Motif Release 1.2 would be compliant with the ANSI C specification. A.3.4 Display and Screen Specific Data Motif now has an XmDisplay object that supports per-display data and resources. An XmScreen object has been added that supports per-screen data and resources. A.3.5 Drag and Drop OSF/Motif Release 1.2 supports the drag and drop metaphor for data interchange. The drag-and-drop specification has been fully implemented. See the Release 1.2 version of the OSF/Motif Programmer's Guide for information on the drag and drop interface. ________________________ Note ________________________ If you want to use Btn2 to have pop-up menus pop up, drag and drop will not function properly. You need to disable drag and drop in such instances. ______________________________________________________ A-4 OSF/Motif Release 1.2 Release Notes A.3 Changes and New Features for OSF/Motif Release 1.2 A.3.6 Tear-Off Menus With tear-off menus, the user can retain menus on the display area for subsequent selections. Each tearable menupane is a tear-off button. When the mouse drag button is pressed on the tear-off button, the pane tears off and can be dragged and then placed by releasing the mouse drag button. The window manager surrounds the tear-off menupane with a menu button and a title. Shifting focus to a torn- off menu's windowpane follows the standard window manager policy. Tear-off behavior is enabled by setting the XmNtearOffModel resource to XmTEAR_OFF_ENABLED. (The default is XmTEAR_OFF_ DISABLED). Note that there is no resource converter preregistered by XmNtearOffModel. To allow the tear-off function to be enabled through the resource database, an application must register its own resource converter for the XmNtearOffModel resource using the XmRepTypeInstallTearOffModelConverter function. The converter is not automatically installed because many applications use map or cascading callbacks to dynamically set the sensitivity of items within their menus. However, if a tear-off menu is mapped, the sensitivity of its menu items must be changed immediately to reflect changes in other application states. Existing applications are unlikely to change menu item sensitivity in this manner. Thus, allowing their menus to be torn off could result in operations being enabled at unexpected times. If a user activates one of these menu items, the application can crash or the persistent data can be corrupted. A.3.7 Insensitive Visuals Motif provides visual indications to show whether a component can respond to input from users. Labels and buttons have had this behavior in previous Motif releases. In OSF/Motif Release 1.2, this behavior has been extended to the following widgets: XmArrowButton XmList XmScrollBar XmText A-5 OSF/Motif Release 1.2 Release Notes 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: o Several pixels have changed in the three-dimensional beveled look. o Minor changes have been made to the color generation routines. In particular, the new XmScreen object contains resources that allow for tailoring the generation of default colors. Some of the default values for thresholds have been adjusted to produce more contrast on color monitors. o Motif now adds a location cursor to surround all items in a List whenever a List widget has the focus and the current keyboard item is not visible. o There are minor layout differences because of fixes in geometry management. A.3.9 Titles for Frames In OSF/Motif Release 1.2, you can specify a Title widget in a Frame widget. The release has added the following 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, that can specify whether an audible cue should accompany a warning message. Text widgets determine the value for this resource from the value of XmNaudibleWarning. A-6 OSF/Motif Release 1.2 Release Notes A.3 Changes and New Features for OSF/Motif Release 1.2 A.3.11 Color Enhancements The following three resources have been added to the XmScreen widget so that users can specify the default background color and thresholds for shadow calculation: XmNlightThreshold XmNdarkThreshold XmNforegroundThreshold Motif has added the XmChangeColor function that changes the background and other colors for a specified widget. A.3.12 Baseline Alignment Motif has added two functions for baseline alignment. The XmWidgetGetBaselines function determines the position of the widget's text baseline. The XmWidgetGetDisplayRect function determines the size and position of the bounding box for the widget's character string. A.3.13 Expanded Traversal Set In OSF/Motif Release 1.2, you can use more widgets to support traversal using the keyboard. For example, inside a tab group, users can now use the arrow keys to traverse to all control descendants that are not contained within a nested tab group and that are eligible to receive focus, even if the controls are not direct children of the tab group. A.3.14 Two-Dimensional Menu Traversal With OSF/Motif Release 1.2, the left, right, up, and down traversal arrows now navigate within a menupane. The up and down arrow keys wrap between columns. The right and left arrow keys post the previous or next menupane when they are pressed in the rightmost and leftmost column of the menupane, respectively. A.3.15 Input Focus OSF/Motif Release 1.2 has added the XmNinitialFocus resource to the Manager class. This resource specifies the first widget to receive input focus. This resource can only specify a widget; it is ignored for all pop-up menus, menubars, option menus, and pull-down menus. A-7 OSF/Motif Release 1.2 Release Notes A.3 Changes and New Features for OSF/Motif Release 1.2 A.3.16 Traversal Access Functions OSF/Motif Release 1.2 has added the following new functions to support better interaction with keyboard traversal: XmGetFocusWidget XmGetTabGroup XmGetVisibility XmIsTraversable XmIsVisible The XmTrackingLocate function has been modified to do the following: o Field all events, not just a button press. o Return on any keystroke or button press. o Be called for nonsensitive widgets. In addition, the XmTrackingEvent function has been added. This function is similar to XmTrackingLocate, except that it returns a pointer to the X event. A.3.17 Virtual Keys OSF/Motif Release 1.2 has added the XmTranslateKey function that allows applications to override the default XtKeyProc to handle Motif virtual keys. Motif defines two new virtual keysyms: osfPageLeft osfPageRight You must have the X11 Release 5 XKeysymDB installed in /usr/lib/X11 to use these new virtual keys. Otherwise you get a warning message on application startup. Specify the following information in the XKeysymDB file: osfPageLeft :1004FF40 osfPageUp :1004FF41 osfPageDown :1004FF42 osfPageRight :1004FF43 To comply with the OSF/Motif Style Guide, the default binding for osfMenu has been changed from F4 to ShiftF10. A-8 OSF/Motif Release 1.2 Release Notes A.3 Changes and New Features for OSF/Motif Release 1.2 In X11 Release 5, the HP keysyms in the XKeysymDB file have the prefix hp. This prefix is not reflected in the HP bindings file in the /bindings directory. If you are using an X11 Release 5 XKeysymDB file, you might see warning messages at application startup. To eliminate these warning messages, add the hp prefix as follows to the appropriate lines in the file: osfDelete : hpDeleteChar osfInsert : hpInsertChar osfPrimaryPaste : hpInsertLine osfQuickPaste : hpDeleteLine OSF/Motif Release 1.2 has a new client, xmbind, that sets up the virtual bindings for use by Motif applications. Since virtual binding is automatically set up at Motif Window Manager (MWM) startup, you only need to use xmbind if MWM is not used or if you need to change the virtual bindings without restarting MWM. Virtual bindings can now be specified by individual vendors. If there is no .motifbind file in the home directory, you can use the xmbind.alias file to provide a mapping from the server vendor name to the bindings file. You can set up user vendor bindings as well as system-wide vendor bindings. A.3.18 Resource Management OSF/Motif Release 1.2 has the following new functions for managing representation types: XmRepTypeRegister XmRepTypeAddReverse XmRepTypeValidValue XmRepTypeGetRegistered XmRepTypeGetId XmRepTypeGetNameList XmRepTypeGetRecord These functions are useful for developers who want to define new resource converters that use an enumerated set of values. A-9 OSF/Motif Release 1.2 Release Notes A.3 Changes and New Features for OSF/Motif Release 1.2 A.3.19 Changes for CUA and Windows Compliance In OSF/Motif Release 1.2, pressing the Return key or using the key bound to osfActivate (usually the Enter key on the numeric keypad) no longer activates a button that is outside a menu. For example, pressing such a key no longer pops up an OptionMenu or activates a ToggleButton in a dialog box. If your application has a default button associated with an XmBulletinBoard, pressing Return (except in a multiline XmText), Ctrl/Return, or the key bound to osfActivate while the focus is in the XmBulletinBoard now activates the default button. A.4 Changes and Enhancements to Specific Widgets This section summarizes the changes to specific widgets that were made in OSF/Motif Release 1.2. A.4.1 XmClipboard 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 your applications. The modifications involved changing (char *) to XtPointer, int to long, and (int *) to (long *). The related functions affected by these modifications are: o XmClipboardCopy o XmClipboardCopyByName o XmClipboardInquireCount o XmClipboardInquireFormat o XmClipboardRegisterFormat o XmClipboardRetrieve o XmClipboardStartCopy o XmClipboardWithdrawFormat A-10 OSF/Motif Release 1.2 Release Notes A.4 Changes and Enhancements to Specific Widgets A.4.2 XmCommand In OSF/Motif Release 1.2, a correction was made to XmCommandGetChild so that it now accepts XmDIALOG_WORK_ AREA as a value for the child argument. A.4.3 XmList To enhance its capabilities for managing lists, OSF/Motif Release 1.2 includes the following new functions: o XmListAddItemsUnselected o XmListDeletePositions o XmListGetKbdItemPos o XmListIsPosSelected o XmListPosToBounds o XmListReplaceItemsUnselected o XmListReplaceItemsPosUnselected o XmListReplacePositions o XmListSetKbdItemPos o XmListUpdateSelectedList o XmListYToPos The XmList widget includes a new translation: o 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. ________________________ Note ________________________ This action was mistakenly named ListScrollCursorVisible in OSF/Motif Release 1.2. The name will be corrected in a later release of Motif. ______________________________________________________ A-11 OSF/Motif Release 1.2 Release Notes A.4 Changes and Enhancements to Specific Widgets The XmNvisibleItemCount resource has been modified so that the default value is dynamic, and is based on the item count and the height. In OSF/Motif Release 1.2, if the selectedItems and selectedItemCount resources for a list are set in a resource file, the location cursor appears over the last item in the selectedItems list, not the first selected item. A.4.4 XmMessageBox In OSF/Motif Release 1.2, MessageBox supports the addition of one MenuBar, one work area, and multiple PushButton children. A new dialog type, XmDIALOG_TEMPLATE, creates a MessageBox that contains only a Separator. The application provides additional children. XmCreateTemplateDialog creates an XmDIALOG_TEMPLATE XmMessageBox inside a DialogShell. A.4.5 XmRowColumn and Menus OSF/Motif Release 1.2 adds a new resource, XmNentryVerticalAlignment, that specifies the vertical alignment style. Another resource, XmNunpostBehavior has been added to the XmScreen object. This resource can be set to enable external button events to be replayed after a menu is unposted. A.4.6 XmScrollBar In OSF/Motif Release 1.2, XmScrollBar includes a new translation: o Cancels the current slider drag. A-12 OSF/Motif Release 1.2 Release Notes A.4 Changes and Enhancements to Specific Widgets A.4.7 XmScrolledWindow OSF/Motif Release 1.2 adds the function, XmScrollVisible, that scrolls an automatic scrolled window to make a partially or completely obscured widget visible. Another resource, XmNtraverseObscuredCallback, has been added that specifies a list of callbacks that are called when a traversal event is requested to a nonvisible widget. A new callback structure, XmTraverseObscuredCallbackStruct, has been added to support this callback. A.4.8 XmSelectionBox, XmFileSelectionBox In OSF/Motif Release 1.2, the XmSelectionBox and XmFileSelectionBox widgets support the addition of MenuBar and PushButton children, as well as a work area child. A new resource, XmNchildPlacement, controls the location of the work area child. The value, XmDIALOG_TEMPLATE, has been added to the XmNdialogType resource. By default, XmSelectionBoxDialog and its subclasses use XmTextField instead of XmText. You can revert to the earlier behavior by defining USE_TEXT_IN_DIALOGS when your application builds XmSelectionBox or any of its subclasses. A.4.9 XmText OSF/Motif Release 1.2 has added two functions to XmText for making update changes to the widget: XmTextDisableRedisplay and XmTextEnableRedisplay. Two other functions facilitate string manipulation: XmTextFindString and XmTextGetSubstring. In Release 1.2, the destination cursor now follows the insert cursor and is no longer independently drawn. XmText includes three new translations: o Deletes any non-null primary selection. o Deletes any non-null primary selection. o A-13 OSF/Motif Release 1.2 Release Notes A.4 Changes and Enhancements to Specific Widgets Continues a selection action by scrolling after a time delay. XmText includes two new actions: o scroll-cursor-vertically() Scrolls the cursor vertically based on a y position. o toggle-overstrike() Switches between insert and overstrike modes. ________________________ Note ________________________ There is a potential problem in both XmText and XmTextField with rendering strings in fonts or font sets that contain characters whose ascenders can rise above the font ascent. If the text containing these characters is highlighted, any overlapping descenders in the previous line may be overwritten by the ascenders in the succeeding line. ______________________________________________________ A.4.10 XmTextField OSF/Motif Release 1.2, the XmTextField widget has a new resource, XmNfocusCallback, that specifies the callbacks to 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. XmTextField includes two new translations: o Deletes any non-null primary selection. o Deletes any non-null primary selection. A-14 OSF/Motif Release 1.2 Release Notes A.4 Changes and Enhancements to Specific Widgets A.4.11 XmToggleButton, XmToggleButtonGadget In OSF/Motif Release 1.2, setting XmNfillOnSelect to be true when XmNindicatorOn is false now causes the background of a set XmToggleButton to be filled with XmNselectColor. The default value for XmNfillOnSelect is dynamic so that it matches the state of XmNindicatorOn. A.5 Motif Window Manager Enhancements This section highlights the enhancements to the Motif Window Manager (MWM). A.5.1 Changes to MWM OSF/Motif Release 1.2 incorporates the following enhancements to MWM: o An internationalized .mwmrc file o Internationalized dialog messages o A built-in default root menu o Support for the continuation character (\) in the .mwmrc file o Search capability with XBMLANGPATH for bitmap files o Support for pop-down and replay event behavior in mwm menus o Documentation of the widget names used by mwm o Support for scrolled window traversal to scrolled-off children in the icon box o Support for treating the and key modifiers as two distinct modifiers o Support for the SHAPE nonrectangular window extension A.5.2 New and Enhanced MWM Resources The OSF/Motif Release 1.2 window manager includes the following new or enhanced resources: o feedbackGeometry Sets the position of the move/resize feedback window. The default position is the center of the screen. A-15 OSF/Motif Release 1.2 Release Notes A.5 Motif Window Manager Enhancements o frameBorderWidth Now bases its default value on the size and resolution of the screen. o iconPlacement Now takes the addition value, tight, which specifies automatic icon placement with no gaps between icons. o maximumClientSize Can now take the values vertical and horizontal. o moveOpaque Controls whether an image of the window or just an outline of the window is moved. o resizeBorderWidth Now bases its default value on the size and resolution of the screen. o usePPosition Uses the values of on, off, or nonzero to control whether program-specified positions are used. A.5.3 New and Enhanced MWM Functions OSF/Motif Release 1.2 has the following new and enhanced MWM functions: o f.lower Includes a within argument to move the window within the application stacking order, but retains the parent window below the children rule. The function also includes a freeFamily argument to move the window absolutely without regard to its local family stack. Both modifiers move the window within the local family stack, but do not move the family stack. o f.minimize Can now be used from an icon in an icon box. o f.raise A-16 OSF/Motif Release 1.2 Release Notes A.5 Motif Window Manager Enhancements Includes a within argument to move the window within the application stacking order, but retains the parent window below the children rule. The function also includes a freeFamily argument to move the window absolutely without regard to its local family stack. Both modifiers move the window within the local family stack, but do not move the family stack. o f.raise_lower Includes a within argument to move the window within the application stacking order, but retains the parent window below the children rule. The function also includes a freeFamily argument to move the window absolutely without regard to its local family stack. Both modifiers move the window within the local family stack, but do not move the family stack. o f.restore Restores a window to its previous state. Double clicking on a root icon is bound to this function rather than to f.normalize. o f.restore_and_raise Restores a window to its previous state and raises it to the top of the window stack. Double clicking on an icon in an icon box is bound to this function rather than to f.normalize. o f.screen Traverses to the screen specified by arg. Legal values 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: o This key combination behaves similarly to f.next_key, except that the window is always raised, regardless of the value of focusAutoRaise. A-17 OSF/Motif Release 1.2 Release Notes A.6 Changes to the User Interface Language A.6 Changes to the User Interface Language OSF/Motif Release 1.2 has the following changes in the User Interface Language (UIL): o There is a new command flag, -s, that enables the use of setlocale and the creation of localized Compound Strings. ________________________ Note ________________________ There is a serious problem in parsing double quoted strings with the -s flag. If you need to use this flag for parsing double quoted strings, you must obtain a patch from the OSF. ______________________________________________________ o New UIL syntax now supports font sets and font tables. o New UIL syntax now supports wide character strings. o Support has been added for using widget references as callback tags. o New UIL syntax specifies the resources of automatically created children. o Syntax changes to the Widget Meta-Language (WML) allow for the definition of automatically created children of composite widgets. 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 This function is the same as the old MrmOpenHierarchy function, except that in the new function, the display is passed as an explicit argument. This function replaces MrmOpenHierarchy. - MrmFetchBitmapLiteral This function fetches a bitmap literal with a depth of 1. A-18 B _________________________________________________________________ OSF/Motif Toolkit Information This appendix contains information about notes, restrictions, and corrections related to the OSF/Motif and DECwindows OSF/Motif Toolkits. B.1 OSF/Motif Release 1.2.2 and X11 Release 5 Shareable Libraries V1.2 Because the OSF/Motif Release 1.2.2 Toolkit and the OSF/Motif Release 1.1.3 Toolkit are not binary compatible, applications must link with one toolkit or the other. Applications based on OSF/Motif Release 1.2.2 can only link against OSF/Motif 1.2.2-based and X11 R5-based shareable libraries. Applications based on OSF/Motif Release 1.1.3 can only link against OSF/Motif 1.1.3-based and X11 R4- based shareable libraries. To provide both OSF/Motif Release 1.2.2-based and OSF/Motif Release 1.1.3-based shareable libraries, the Release 1.1.3- based libraries have the same file names as in DECwindows Motif Version 1.1, and the Release 1.2.2-based libraries contain a suffix of either "R5" or "12". Shareable libraries that work with either the OSF/Motif Release 1.1.3 Toolkit or the OSF/Motif Release 1.2.2 Toolkit do not have a suffix. These libraries are as follows: V1.2-6 o CDA$ACCESS.EXE o DECW$D2DXLIBSHR.EXE o DECW$XEXTLIBSHR.EXE o DECW$XLIBSHR.EXE o XIE$SHRLIB.EXE B-1 OSF/Motif Toolkit Information B.1 OSF/Motif Release 1.2.2 and X11 Release 5 Shareable Libraries Shareable libraries that are linked with Release 5 (R5) of the Xt Toolkit have a suffix of "R5". Libraries based on the XUI Toolkit have no R5 equivalent libraries and should not be included in a linker options file based on X11 R5 or OSF/Motif Release 1.2.2. Table B-1 lists these file names. ________________________ Note ________________________ The DECW$XLIBSHR.EXE file is the MIT Release 5 version, not the MIT Release 4 version of Xlib. ______________________________________________________ Table_B-1_Names_of_Shareable_Libraries_Based_on_R5_________ Names_of_Files_Based_on_R4__Names_of_Files_Based_on_R5_____ DECW$DWTLIBSHR.EXE (None) DECW$DWTSHR.EXE (None) DECW$XMULIBSHR.EXE DECW$XMULIBSHRR5.EXE DECW$XTRAPLIBSHR.EXE DECW$XTRAPLIBSHRR5.EXE DECW$XTSHR.EXE______________DECW$XTLIBSHRR5.EXE____________ Release 5 does not provide an equivalent file for DECW$DWTLIBSHR.EXE or DECW$DWTSHR.EXE. Applications that are built for Release 5 cannot link against these files. Shareable libraries that are linked with OSF/Motif Release 1.2.2 have a suffix of "12". They should be linked only with libraries compatible with R5 and OSF/Motif Release 1.2.2. Table B-2 lists these file names. Table B-2 Names of Shareable Libraries Based on OSF/Motif __________Release_1.2.2____________________________________ Names of Files Based on Names of Files Based on Release Release_1.1.3_______________1.2.2__________________________ DDIF$VIEWSHR.EXE DDIF$VIEWSHR12.EXE DECW$BKRSHR.EXE DECW$BKRSHR12.EXE (continued on next page) B-2 OSF/Motif Toolkit Information B.1 OSF/Motif Release 1.2.2 and X11 Release 5 Shareable Libraries Table B-2 (Cont.) Names of Shareable Libraries Based on __________________OSF/Motif_Release_1.2.2__________________ Names of Files Based on Names of Files Based on Release Release_1.1.3_______________1.2.2__________________________ DECW$DXMLIBSHR.EXE DECW$DXMLIBSHR12.EXE DECW$MAILSHR.EXE DECW$MAILSHR12.EXE (None) DECW$MRMLIBSHR12.EXE DECW$PRINTWGTSHR.EXE (None) DECW$TERMINALSHR.EXE DECW$TERMINALSHR12.EXE DECW$XMLIBSHR.EXE DECW$XMLIBSHR12.EXE DGIT$LIBSHR.EXE DGIT$LIBSHR12.EXE IMG$SHRLIB.EXE IMG$SHRLIB12.EXE LWK$DXMSHR.EXE LWK$DXMSHR12.EXE XNL$SHR.EXE_________________XNL$SHR12.EXE__________________ There is no DECW$PRINTWGTSHR12.EXE file; the Print Widget is part of the DECW$DXMLIBSHR12.EXE file. The DECW$MRMLIBSHR12.EXE file is a new image that includes Motif Resource Manager (Mrm) routines that were formerly part of the DECW$XMLIBSHR.EXE file. Any program based on OSF/Motif Release 1.2.2 that calls Mrm routines to access .UID files should link with this library. For example, a typical linker options file for a program based on OSF/Motif Release 1.1.3 might be as follows: SYS$SHARE:DECW$XLIBSHR/SHARE SYS$SHARE:DECW$XTSHR/SHARE SYS$SHARE:DECW$DWTLIBSHR/SHARE SYS$SHARE:DECW$XMLIBSHR/SHARE SYS$SHARE:DECW$DXMLIBSHR/SHARE To link this program with OSF/Motif Release 1.2.2, the linker options file should be changed to: SYS$SHARE:DECW$XLIBSHR/SHARE SYS$SHARE:DECW$XTLIBSHRR5/SHARE SYS$SHARE:DECW$XMLIBSHR12/SHARE SYS$SHARE:DECW$MRMLIBSHR12/SHARE SYS$SHARE:DECW$DXMLIBSHR12/SHARE B-3 OSF/Motif Toolkit Information B.1 OSF/Motif Release 1.2.2 and X11 Release 5 Shareable Libraries These changes eliminate the reference to the XUI Toolkit (DECW$DWTLIBSHR.EXE) and links with the Motif Resource Manager (DECW$MRMLIBSHR12.EXE). B.2 OSF/Motif Release 1.1.3 Programming Support and XUI V1.2-3 Restrictions o Problem: You will encounter problems if you save the previous (Release 1.1.3) programming environment and attempt to run an OSF/Motif Release 1.1.3 (Xlib Release 4) program that is created on a DECwindows Motif Version 1.2 or Version 1.2-3 system by running the executable on a DECwindows Motif Version 1.1 target system. That is, if you build an application on a DECwindows Motif Version 1.2 or Version 1.2-3 for OpenVMS system, the image is linked with Xlib Release 5, by default. If you attempt to run that executable on a system where OSF/Motif Release 1.1.3 is installed, the result is an ident mismatch fatal error. In addition, the OSF/Motif Release 1.1.3 and the Release 1.2.2 files produce different output; they have different structures and are therefore not compatible. Use the appropriate UIL compiler to produce the correct UID file. o Resolution: 1. Rename the DECwindows Motif Version Version 1.1 executable compiler, DECW$UILMOTIF.EXE, to DECW$UILMOTIF113.EXE and keep the file in the SYS$COMMON directory. By doing this, the name of the new Version 1.2-3 compiler, DECW$UILMOTIF.EXE, does not conflict with the previous compiler. 2. Copy the DECW$XLIBSHR.EXE file (Xlib Release 4) to the SYS$COMMON:[SYSEXE.DECW$113] directory. The Xlib Release 5 version of Xlib has the same name; however, a logical name is defined to use the Release 4 version when the programs are linked. The changes in minor ident of DECW$XLIBSHR.EXE between DECwindows Motif Version 1.1 and DECwindows Motif Version 1.2 B-4 OSF/Motif Toolkit Information B.2 OSF/Motif Release 1.1.3 Programming Support and XUI for OpenVMS caused a loss of backward compatibility with DECwindows Motif Version 1.1 systems. B-5 OSF/Motif Toolkit Information B.2 OSF/Motif Release 1.1.3 Programming Support and XUI 3. If you save the previous programming environment during installation, create the following two files and copy them to the SYS$COMMON:[SYSEXE.DECW$113] directory: - DECW$UILCOMPILER113.CLD This file enables UIL/OSF Motif and UIL/XUI to function for either XUI or OSF/Motif Release 1.1.3 if you select DECW$UILMOTIF113.EXE for OSF/Motif Release 1.1.3 or DECW$UILCOMPILER.EXE for XUI. - DECW$DEFINE113_LOGICALS.COM This file points to the saved header files, which in turn point to the Xlib Release 4 version of the DECW$XLIBSHR.EXE file. 4. An application must be run on the same version (or higher) of the operating system as the version where it is linked. For example, an application that is linked on a VMS Version 5.4-3 system must be run on a VMS Version 5.4-3 (or higher) system. DECwindows Motif Version 1.1 applications that are compiled for OpenVMS Version 6.1 systems will run only on OpenVMS Version 6.1 systems and not on systems prior to Version 6.1. V1.2 The X Window and OSF/Motif libraries that are shipped with DECwindows Motif Version 1.2 for OpenVMS software are incompatible with those shipped with previous versions. Run-time compatibility has been preserved, but the programming environment is not compatible. Programming in the XUI or Motif Release 1.1.3 environment that is provided in previous versions of DECwindows Motif is no longer supported in DECwindows Motif Version 1.2 for OpenVMS. However, the installation procedure gives you the option of saving the programming files that already exist on your system. If you choose to save these programming files, they are moved to subdirectories where you can access them for programming. Specifically, the installation creates a subdirectory called [.DECW$113] in each of the directories listed in Table B-3 and moves the previous files into the new subdirectory. B-6 OSF/Motif Toolkit Information B.2 OSF/Motif Release 1.1.3 Programming Support and XUI For more information about saving the programming files, see the DECwindows Motif Version 1.2 for OpenVMS Installation Guide. Table B-3 Directories for Previous XUI or Motif Programming __________Environment______________________________________ Directory_____Contents____New_Location_____________________ DECW$INCLUDE C header SYS$SYSROOT:[DECW$INCLUDE.DECW$113] files SYS$SYSTEM UIL SYS$SYSROOT:[SYSEXE.DECW$113] compiler SYS$LIBRARY Non-C SYS$SYSROOT:[SYSLIB.DECW$113] language ______________bindings_____________________________________ To program with these files, include the new [.DECW$113] subdirectories in the search path for each of the logical names. For example, perform the following: o Change the definition of DECW$INCLUDE as follows: $ SHOW LOGICAL DECW$INCLUDE "DECW$INCLUDE" = "SYS$SYSROOT:[DECW$INCLUDE]" (DECW$LOGICAL_NAMES) = "SYS$SYSROOT:[DECW$INCLUDE.EXTENSIONS]" $ DEFINE/EXECUTIVE/TABLE=DECW$LOGICAL_NAMES DECW$INCLUDE - SYS$SYSROOT:[DECW$INCLUDE.DECW$113], - SYS$SYSROOT:[DECW$INCLUDE], - SYS$SYSROOT:[DECW$INCLUDE.EXTENSIONS] Place the new [.DECW$113] subdirectory first in the search list, since many of the files that have been updated for this release have the same name as the files that were moved to the [.DECW$113] subdirectory. Thus, the files in [.DECW$113] are used for software development. If DECW$INCLUDE is redefined in the SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM command procedure, then modify the previous instructions accordingly. B-7 OSF/Motif Toolkit Information B.2 OSF/Motif Release 1.1.3 Programming Support and XUI To use the UIL compiler for XUI or OSF/Motif Release 1.1.3, perform the following steps: 1. Create a file called SYS$SYSROOT:[SYSEXE.DECW$113]DECW$UILCOMPILER.CLD that contains the following text: define type trace_keywords keyword tokens keyword symbols define type warning_keywords keyword nowarnings keyword noinformationals define type version_keywords keyword V1, syntax=xui_uil keyword V2, syntax=xui_uil, default keyword MOTIF11, syntax=motif_uil define syntax xui_uil image decw$uilcompiler define syntax motif_uil image decw$uilmotif define verb uil image decw$uilcompiler parameter p1, label=source_file, prompt="File", value(required,noconcatenate,type=$infile) qualifier trace, label=trace_qual, value(list,noconcatenate,type=trace_keywords), nonnegatable qualifier warnings, label=warnings_qual, value(list,noconcatenate,type=warning_keywords) qualifier list, label=listing_file, batch, value(type=$outfile) qualifier machine, label=machine_qual, qualifier output, label=resource_file, default, value(type=$outfile) qualifier version, label=version_qual, default, value(type=version_keywords), nonnegatable qualifier XUI, default, nonnegatable, syntax=xui_uil qualifier MOTIF, nonnegatable, syntax=motif_uil qualifier widget_meta_description, label=widget_qual, value(required, noconcatenate, type=$infile) B-8 OSF/Motif Toolkit Information B.2 OSF/Motif Release 1.1.3 Programming Support and XUI disallow XUI and MOTIF 2. Set the DCL command table to use the XUI UIL compiler as follows: $ SET COMMAND SYS$SYSROOT:[SYSEXE.DECW$113]DECW$UILCOMPILER.CLD ________________________ Note ________________________ If you want to revert back to the previous UIL command definition, execute the following command: $ SET COMMAND SYS$LIBRARY:DECW$UILCOMPILER.CLD ______________________________________________________ B.3 DECwindows OSF/Motif Toolkit This section contains information about notes, restrictions, and corrections for the DECwindows OSF/Motif Toolkit. B.3.1 Callable OSF/Motif UIL Compiler (Alpha Only) V1.2-6 The OSF/Motif Release 1.2.2 Toolkit contains a callable User Interface Language (UIL) compiler. You can now link against this image by including the following in your link options: SYS$SHARE:DECW$UILSHR/SHARE For information about the callable interface, see the OSF/Motif Programmer's Guide published by Prentice Hall. B.3.2 Motif Text Widget Translations V1.0 To implement virtual bindings, it is necessary for Compaq to modify the default XmText and XmTextField translation manager syntax. Specifically, the following syntax line is removed: Shift ~Ctrl ~Meta ~Alt osfDelete: cut-clipboard() B-9 OSF/Motif Toolkit Information B.3 DECwindows OSF/Motif Toolkit 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 XmTextField translations in your DECW$XDEFAULTS.DAT file. B.3.3 Upward Compatibility V1.0 The combination of DECW$DWTLIBSHR, DECW$DWTSHR, and DECW$XTSHR shareable images is intended to be binary and upwardly compatible with the previous DECW$DWTLIBSHR shareable image. A possible exception is applications that dynamically activate the image DECW$DWTLIBSHR using LIB$FIND_IMAGE_SYMBOL. The problem with dynamic image activation is that the semantics of the Intrinsics have changed in places between the X Toolkit Intrinsics Release 3 to the MIT X11 Release 4 Intrinsics. A previously linked XUI application calls through entries in the XUI transfer vector that use the X Toolkit Intrinsics Release 3 semantics of the Intrinsics. However, as soon as that application relinks (or dynamically activates DECW$DWTLIBSHR), it uses the MIT X Toolkit Intrinsics Release 4 semantics of the Intrinsics. Applications that dynamically activate DECW$DWTLIBSHR should be changed to link directly against DECW$DWTLIBSHR. DECW$DWTLIBSHR is now a small, thin-layer, shareable image that dynamically activates automatically the majority of the toolkit code only when necessary. There is no reason for applications to continue to dynamically activate DECW$DWTLIBSHR. In addition, Compaq cannot guarantee binary upward compatibility in the future for applications that dynamically activate the toolkit shareable images. DECwindows toolkits (XUI and Motif) are based upon standards that Compaq does not control. When the standards make an incompatible change, Compaq will change the toolkit to follow it. However, the intent is to add code that allows existing executable images to run unchanged. B-10 OSF/Motif Toolkit Information B.3 DECwindows OSF/Motif Toolkit B.3.3.1 Restrictions on Mixing Motif and XUI Widgets V1.0 Mixing Motif and XUI widgets is restricted. The problem results from the fact that both XUI and Motif have their own Vendor Shell widget class. If an application is linked against XUI and not Motif, the XUI Vendor Shell widget class is used in order to maintain compatibility with DECwindows XUI. If an application is linked against Motif, the Motif Vendor Shell widget class is used. Motif widgets require the Motif Vendor Shell; XUI widgets are compatible with the Motif Vendor Shell. The problem occurs when an XUI-only application dynamically activates (using LIB$FIND_IMAGE_SYMBOL) a shareable image that uses Motif. The toolkit makes the decision to use the XUI Vendor Shell when the toolkit is initialized and the Motif widgets in the dynamically activated shareable image do not work. The workaround is to add the application image name to the DECW$USE_XM_VENDOR_SHELL logical name. This logical name contains a comma-separated list of image names for which the toolkit is to use the Motif Vendor Shell. The value of DECW$USE_XM_VENDOR_SHELL logical name defaults to NOTES$MAIN. To add additional image names to this logical name, enter the following: $ DEFINE DECW$USE_XM_VENDOR_SHELL "NOTES$MAIN,- _$ yourimage1,yourimage2,..." Note that DECW$USE_XM_VENDOR_SHELL does not affect applications that use Motif since they are already using the Motif Vendor Shell. B.3.4 Compile-Time Incompatibilities in Motif Header Files V1.2-3 Several macro definitions are removed from the Motif header files in the OSF/Motif programming support. The changes affect the following header files: o DECW$INCLUDE:XMP.H The following definitions are removed: - #define XmLONGBITS sizeof(Cardinal)*8 - #define XmHALFLONGBITS (XmLONGBITS/2) B-11 OSF/Motif Toolkit Information B.3 DECwindows OSF/Motif Toolkit These macros are replaced in the same header file with the following macro: - XmOFFSETBITS Update the code to call the XmOFFSETBITS macro. o DECW$INCLUDE:TEXTP.H The following definitions are removed: - #define MAXINT 2147483647 /* Biggest number that can fit in long */ - #define NODELTA MAXINT The definition of MAXINT is operating-system dependent. Include this definition in applications in one of the following ways: - Include the appropriate system-header file - Define the constant B.4 OSF/Motif Example Programs This section describes example programs from the Open Software Foundation (OSF) that are included in the DECwindows Motif Version 1.2 for OpenVMS software. B.4.1 Cut and Paste Example Program V1.2 This example demonstrates the use of the Motif Clipboard. You can cut and paste application-defined data formats using the XmClipboard API. Run two cut/paste clients and transfer graph values using the pull-down and pop-up menus. B.4.2 DNDDemo Example Program V1.2 This example illustrates a typical use of the drag-and-drop feature. B-12 OSF/Motif Toolkit Information B.4 OSF/Motif Example Programs When the example starts, it does not have any valid drop sites. It starts with different color rectangles that act as drag sources for dragging the colors around. Create the drop sites as follows: o Move the pointer into the drawing area (with white background). o Press MB1 and drag. You see the "rubber-banding" effect. o Release MB1 after dragging a desired distance. A black rectangle appears. You can create as many rectangles as you like. The rectangles inside the drawing area that you created act as valid drop sites for colors. You can test this by initiating the drag from the yellow color rectangle and dragging over to one of the rectangles inside the drawing area and releasing MB2. To initiate a drag, move the pointer over to the drag source, press BTransfer (which is MB2 by default), and start to drag. Notice that the cursor changes to a painter's palette in the same color as the color rectangle from which the drag is initiated. While you are dragging, notice the following: o When dragging over the root window, the drag icon consists of only the painter's palette. o When dragging over parts of the drawing area where there are no rectangles, the drag icon changes to include a "DO NOT ENTER!" sign on top of the painter's palette. o When dragging over any of the rectangles inside the drawing area, the "DO NOT ENTER!" sign is replaced with a painter's brush. To perform a drop, release MB2. If you release MB2 with 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 initiation and disappears. This is an indication that the drop you attempted failed. If you release MB2 with the pointer over any of the rectangles inside the drawing area, the drag icon disappears into the background; this indicates that the drop was a success. The rectangle on which the drop B-13 OSF/Motif Toolkit Information B.4 OSF/Motif Example Programs was attempted, becomes filled in with the color that was dragged. The rectangles inside the drawing area act as drag sources. Initiate the drag with the pointer on any rectangle, and the cursor changes to a rectangle (either of the same size or a smaller size depending on the X cursor size constraints). Drag the rectangle from one place and drop it onto a new place inside the drawing area. The rectangle is physically moved to the new position. If you want to copy the rectangle to a new position, use the appropriate modifier key while dragging, or at the time you attempt the drop (Ctrl is the modifier key for copy in the current implementation). When you drag a rectangle with no modifier key pressed or with the Shift key pressed, the solid rectangle from where the drag was initiated is replaced by a hollow rectangle with dotted-line borders. It continues this way for the duration of the drag or until you press the Ctrl key, which changes the operation to Copy. At that time it regains its original solid form. ________________________ Note ________________________ During dragging you can cancel the drag by pressing the Cancel key (F11). Also, you can press the Help key to get information about whether the drop will succeed and possible drop operations. ______________________________________________________ B.4.3 Dogs Example Program V1.1 This example uses the dog and square widgets. It shows how to incorporate new widgets into the UIL source by using the user-defined function. The dogs example program allows you to change the DogNwagTime and SquareNmakeSquare resources dynamically. If you have a system with sound generation features, you might want to change the bark callback to something other than XBell(). B-14 OSF/Motif Toolkit Information B.4 OSF/Motif Example Programs B.4.3.1 Dog Widget V1.1 The dog widget (DogWidget) demonstrates how to subclassify a primitive widget that remains binary compatible with future versions of Motif. It uses XmResolvePartOffsets() and associated macros and implements all the recommendations in the XmResolvePartOffsets manpage. The dog widget is a subclass of XmPrimitive. It can bark and wag its tail. If you want more advanced tricks, you must subclassify it, or replace up.bm, down.bm, and bark.bm with more advanced bitmaps. The dog widget has the following resources: o DogNwagTime: Time in milliseconds between each wag o DogNbarkTime: Time in milliseconds the bark graphic is displayed o DogNbarkCallback: Callback called by the bark action The dog widget has the following translations: o osfActivate/Return/Space/MB1 = Bark o W/MB2 = Wag tail o S/Shift-MB2 = Stop wagging tail o osfHelp = Help B.4.3.2 Square Widget V1.1 The square widget (SquareWidget) demonstrates how to subclassify a constraint widget that remains 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. B-15 OSF/Motif Toolkit Information B.4 OSF/Motif Example Programs The square widget has the resource SquareNmajorDimension. This resource determines which dimension is used for the new size of the child. Values are SquareWIDTH or SquareHEIGHT. The square widget has the constraint resource SquareNmakeSquare. This resource determines whether the child is forced to be square or set to its preferred shape. B.4.4 Helloint Example Program V1.2 This example is a simple UIL/Xm program with a label and a push button. 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 name LANG or the xnlLanguage resource to set the locale. Set the LOCALSTRINGS suffix and the locale name to one of the following: ___________________________________________________________ Locale______Interface_Type_________________________________ Japan Kanji Hebrew Hebrew French French English_____Standard_English_______________________________ To define the xnlLanguage resource, add the following line to your DECW$XDEFAULTS.DAT file: *xnlLanguage:locale The following fonts are needed for the helloint example program: B-16 OSF/Motif Toolkit Information B.4 OSF/Motif Example Programs ___________________________________________________________ Locale____Font_Name________________________________________ French -adobe-helvetica-medium-r-normal-12-120-75-75-p- 67-iso8859-1 English -adobe-times-medium-r-normal-14-100-100-100-p-74- iso8859-1 Hebrew -Misc-Fixed-Medium-R-Normal-13-120-75-75-C-80- ISO8859-8 Japan -*-JISX0208.1983-1 __________-*-JISX0201.1976-0_______________________________ If you do not have these fonts installed on your system, either change the UIL files to reference other fonts or install the *.DECW$BDF fonts provided in the DECW$EXAMPLES directory. See Managing DECwindows Motif for OpenVMS Systems for instructions on how to install new fonts. B.4.5 Hellomotif Example Program V1.2 This example is a simple UIL/Xm program with a label and a push button. B.4.6 Motifanim Example Program V1.1 The motifanim program demonstrates the following OSF/Motif features: o Declaration of icon/bitmap using UIL for portability across visuals o Exchange of value between UIL and C using Mrm o Use of the Motif form widget o Background procedure running while the client process is waiting for input (Xt intrinsics feature) This example lets you animate a set of pixmaps in an X window. The pixmaps are not fixed by motifanim but are read at startup from existing UID files. B-17 OSF/Motif Toolkit Information B.4 OSF/Motif Example Programs The syntax of all the animation.uid files can add a new set of pixmaps to be animated using motifanim. Some tree examples of animation data files include: dog.uil plane.uil The default animation is dog. To run the example with the other animations, use the following commands: $ SET DEFAULT DECW$EXAMPLES $ motifanim := "$DECW$EXAMPLES:motifanim" $ motifanim -anim plane The files motiflogo.uil, motifanim.uil, and motifanim.c are the core components of the program. B.4.7 Motifgif and Pict Viewing Programs V1.2 The following .gif files are provided: o TOUCAN.GIF, which is a picture of a tropical bird. o CHALLENGER.GIF, which is a picture of the space shuttle Challenger. V1.1 The motifgif and pict programs work together to display a .gif formatted picture. The motifgif program displays a .gif file within Motif constructs. The motifgif program looks for .gif files in the current directory. The motifgif program has three significant components: o motifgif The source and executable code in this directory is a Motif program driving the display of a .gif picture. o pict The program called by motifgif that displays a bitmap of a .gif picture file. This program used to be xgif but has since been converted to Motif. The following problems exist with motifgif: o Resizing a picture does not work. B-18 OSF/Motif Toolkit Information B.4 OSF/Motif Example Programs o The -d option is not used when calling pict, so remote displays must set the DISPLAY environment variable. B.4.8 Motifshell Example Program V1.2 The motifshell program is an example of an environment created using Motif. The purpose of the example is to show how Motif may be used as a standalone environment for dispatching other programs and utilities. The motifshell program is written in C code. There are no UIL references. ________________________ Note ________________________ Displaying a file listing or process status takes some time. These operations are accomplished by spawning a DCL command, capturing the output in a file, and then reading the file. The default font is proportionally spaced. Some listings are more readable if a fixed space font is used, such as Courier. Use the Font option to select a different font. ______________________________________________________ B.4.9 Periodic Example Program V1.2 The periodic example is a demonstration of the displayable widgets in Motif. The program displays Motif widgets in a periodic chart format. B.4.10 Textedit Example Program V1.2 The textedit program is a primitive text editor based on the Motif XmText widget that makes use of its XmNsource resource to allow multiple views of the same underlying text. B-19 OSF/Motif Toolkit Information B.4 OSF/Motif Example Programs Table B-4 describes the View menu options. Table_B-4_View_Menu_Options________________________________ Option_______Description___________________________________ Split Pane Adds a new independently scrollable view of the text. Remove Pane Removes a designated pane. One_Pane_____Removes_all_panes_except_the_designated_pane._ The designated pane is determined in the following way: o If using an explicit focus policy, it is the last view which had focus. o If using a pointer focus policy, it is the last view with which the user interacted. The designated pane is also the one whose clipboard contents are pasted when Paste is selected from the Edit Menu. The textedit sources are separated into independent layers. Textedit contains the source files listed in Table B-5. Table_B-5_Textedit_Source_Files____________________________ File Name_____Description_______________________________________ tfile.c The code to read, write, and remove files. Hides any operating system or filesystem dependencies. app.c Uses tfile.c to provide all the code to manipulate files and their related buffers. This is toolkit- dependent. (continued on next page) B-20 OSF/Motif Toolkit Information B.4 OSF/Motif Example Programs Table_B-5_(Cont.)_Textedit_Source_Files____________________ File Name_____Description_______________________________________ tk.c Isolates dependencies on the Xm Toolkit. The first half of the file provides utility routines and a toolkit-independent (but application-specific) interface that can be used by the toolkit-independent dialog layer of the application. The second half of the file defines all the callback routines. Many of these update state internal to this layer; others perform additional actions. Those actions unambiguously correspond to toolkit-specific action routines defined in the first half of the file. Otherwise, an upcall is made to the toolkit-independent dialog layer to decide what to do. dlg.c Uses tk.c to manage dialog with the user. The code is toolkit-independent. textedit.Initializes the application and instantiates widget hierarchies. The code hides the use of _________UIL_and_Mrm_from_the_rest_of_the_application._____ ________________________ Note ________________________ Moving and removing files is not currently implemented. ______________________________________________________ B.4.10.1 Additional Translations V1.2 Users familiar with emacs may want to add the following translations to their DECW$XDEFAULTS.DAT files: B-21 OSF/Motif Toolkit Information B.4 OSF/Motif Example Programs *XmText.translations: Mod1: scroll-cursor-vertically()\n\ Mod1: scroll-cursor-vertically()\n\ Ctrla: beginning-of-line()\n\ Ctrlb: backward-character()\n\ Ctrld: delete-next-character()\n\ Ctrle: end-of-line()\n\ Ctrlf: forward-character()\n\ Ctrlg: beep()\n\ Ctrlh: delete-previous-character()\n\ Ctrli: cut-primary()\n\ Ctrlj: newline-and-indent()\n\ Ctrlk: set-anchor() end-of-line() key-select() cut-clipboard()\n\ Ctrll: redraw-display()\n\ Ctrlm: newline()\n\ Ctrln: next-line()\n\ Ctrlo: newline-and-backup()\n\ Ctrlp: previous-line()\n\ Ctrlv: next-page()\n\ Ctrlw: cut-clipboard()\n\ Ctrly: paste-clipboard()\n\ Ctrlz: scroll-one-line-up()\n\ Mod1b: backward-word()\n\ Mod1d: delete-next-word()\n\ Mod1f: forward-word()\n\ Mod1h: delete-previous-word()\n\ Mod1i: copy-primary()\n\ Mod1k: delete-to-end-of-line()\n\ Mod1v: previous-page()\n\ Mod1w: copy-clipboard()\n\ Mod1z: scroll-one-line-down()\n\ Mod1 Shiftgreater: end-of-file()\n\ Mod1less: beginning-of-file()\n\ Mod1]: forward-paragraph()\n\ Mod1[: backward-paragraph() B.4.11 View Example Program V1.2 The view program is similar to the DCL command TYPE/PAGE using Motif with internationalization support. It allows you to view files in several languages. B-22 OSF/Motif Toolkit Information B.4 OSF/Motif Example Programs The command file DECW$EXAMPLES:FILEVIEW.COM is provided, which allows you to select a language. Valid languages are French, English, and German. To select a language, perform the following commands: $ SET DEFAULT DECW$USER_DEFAULTS $ @DECW$EXAMPLES:FILEVIEW language This command file copies the .UID and .DAT files to the current directory. It sets the appropriate locale and executes the file viewing example program. When the application is started, a primary top-level shell is created. From the primary top-level shell, you can create secondary shells. Each top-level shell is a parent of a Main Window, the work area of which is a PanedWindow. The menu bar has the following entries: 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 A file selection box is mapped to choose the file. If OpenFile is successful, the current file is closed, all existing panes are destroyed, and the new file is displayed. o Open New Shell Creates a secondary shell similar to the primary shell. Files can be viewed in each shell independently. o Close This entry only exists on the secondary windows. It destroys the top-level shell and closes the file. o Exit This entry only exists on the primary shell; it closes the file and the shell. B-23 OSF/Motif Toolkit Information B.4 OSF/Motif Example Programs View Menu The view menu contains the following options: o New Pane Creates a new pane in the paned window. o Delete Pane Deletes the current pane. o Search Causes a dialog box to pop up for searching text in the file. The OK callback of the dialog box searches the string. If the string is found, it is displayed in the current pane. If the string is not found, then the dialog box pops up. Opening a second file in a window causes the application to end abruptly. The View options do not work correctly. B.4.12 Xmpiano Example Program V1.2 The xmpiano program shows how to write a Motif Interface to Dumb Instruments (MIDI) application. Both a staff, for writing music, and keyboard are provided. At the bottom of the window is a set of notes that may be used on the staff. Selecting one of these note buttons changes the active note accordingly. The selected note is also displayed as the new mouse cursor. Though the note selection is limited, it is possible to play sharps as well as naturals. The program interface has not been written to play flats. The staff automatically resizes larger as notes are added past the right side of the staff. To see these notes, scroll the score window as needed. To use this application, press the right mouse button on a staff that is visible. The following menu items are displayed: B-24 OSF/Motif Toolkit Information B.4 OSF/Motif Example Programs o Add Voice Connects another display to a new staff. After selecting this command, you are prompted for the display to connect. Any music written in the new staff plays to this display. Note that pressing the right mouse button on the new staff shows the name of the display in the menu title. In addition, the menu commands in the menu bar relate to the staff that is being displayed. o Remove Voice Removes the staff as well as the connection to the corresponding display. There is no undo for this command-all music written in this staff is deleted. o Clear Voice Erases all notes on the staff. This does not affect the display connection. o Play Voice Plays the voice of the staff in which the right mouse was pressed. If the voice is the same as the local host, the keys on the keyboard that correspond to the notes appear as though they are being pressed as the notes are played. It is possible to make the keyboard play along with all voices at the same time; however, the code must be compiled with the -DCHORDS option. Note that this can slow down the application significantly on many servers. o Play All Plays all voices at the same time on each of the specified displays. o Save Voice Saves the corresponding voice to a file. A FileSelectionDialog is displayed to prompt for the name of the file in which to save the voice. The display connection information is not saved. o Load Voice Loads (appends) a previously saved voice to the corresponding staff. o Quit Exits the example program. B-25 OSF/Motif Toolkit Information B.4 OSF/Motif Example Programs This version does not allow editing of notes. To edit, clear the staff and start again, or read the data from a saved file. To set the color of the notes, change the foreground color of the application. To do this, use the -fg option on the command line. For example: $ xmpiano :== $DECW$EXAMPLES:xmpiano $ xmpiano -fg blue B-26 OSF/Motif Toolkit Information B.4 OSF/Motif Example Programs B.4.13 Motif Sample Programs V1.2 Table B-6 lists sample programs showing various Motif Toolkit functionality. Table_B-6_Motif_Sample_Programs____________________________ File_Name_____Description__________________________________ xmdialogs.c dialog sampler xmfonts.c font browser xmeditor.c text editor xmlist.c list example xmprotocol.c window manager protocols example xmter.c shape & animation example xmform.c form attachment example xmforc.c form attachment + rowcolumn example xmmap.c drawingarea + scrolledwindow example xmgetres.c resource fetching example xmapdef.c_____app_defined_scrolled_window_example__________ The following notes apply to these sample programs: 1. The xmfonts program defaults to displaying the fonts whose name length are less than 10 characters. On some systems, the font path contains only long XLFD font names. It may be necessary either to set the resource XMFONTS*maxLen to a larger number (80), or to specify a numColumns resource of 1. 2. If you run the program xmter with a window manager other than Motif Window Manager, that window manager has to remove all the window decorations (for example, borders). The program xmter directs Motif Window Manager to remove the window decorations. 3. The xmform program displays a string made of Motif widgets embedded in a Form. Use the following commands: B-27 OSF/Motif Toolkit Information B.4 OSF/Motif Example Programs $ xmform :== $DECW$EXAMPLES:xmform $ xmform string The variable string is optional. If string is supplied, the available letters for string are F,I,M,O,T. The string of letters that you use must be in uppercase and enclosed in quotation marks. If string is omitted, xmform returns "MOTIF". 4. The xmgetres program is an example of how to use XmGetSecondaryResourceData. Use the following commands to invoke xmgetres: $ xmgetres :== $DECW$EXAMPLES:xmgetres $ xmgetres WidgetClass The variable WidgetClass is optional. If WidgetClass is omitted, it defaults to a class named "Widget". You can also use the class "All", which displays the resources for all the Xt and the Motif widgets. See the OSF/Motif Programmer's Reference manual for a list of available widget classes. B.4.14 Xmtravel Example Program V1.2 The xmtravel example is a front end to a travel agent client and flight database. The program is designed to illustrate various user-interface design concepts as well as be compliant with the OSF/Motif Style Guide. The program is just an example, many of the functions are either not implemented or use predefined settings. B.4.15 Resource Files for Example Programs V1.2 Many of the example programs have associated resource files for defining various display attributes. To use these files, either copy them from the directory DECW$EXAMPLES to your DECW$USER_DEFAULTS directory, or add their contents to your DECW$XDEFAULTS.DAT file. B-28 OSF/Motif Toolkit Information B.4 OSF/Motif Example Programs The list of example programs and the resource files associated with them is as follows: ___________________________________________________________ Example_Program_______Resource_File________________________ 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.DAT XMEDITOR.EXE XMDEMOS.DAT XMFONTS.EXE XMDEMOS.DAT XMFORC.EXE XMDEMOS.DAT XMFORM.EXE XMDEMOS.DAT XMGETRES.EXE XMDEMOS.DAT XMLIST.EXE XMDEMOS.DAT XMMAP.EXE XMDEMOS.DAT XMPROTOCOL.EXE XMDEMOS.DAT XMTER.EXE XMDEMOS.DAT XMTRAVEL.EXE__________XMTRAVEL.DAT_________________________ If a resource file is not found, the example programs run, but some of the display attributes may be incorrect. B.4.16 UID Files for Example Programs V1.2 The UID files used by the example programs must be located in either the current directory or your DECW$USER_DEFAULTS directory. If they are not found, the application fails to start. The UID files can be copied from the DECW$EXAMPLES directory. B.5 OSF/Motif List of Known Problems Included in the DECwindows Motif software is an OSF file that contains the OSF/Motif known problems. During the installation this file is copied from the kit to SYS$HELP:DECW$MOTIF_OSF_BUGLIST_V12.TXT. B-29 C _________________________________________________________________ Using the NCSA Mosaic Browser (VMS 5.5-2 Only) Compaq DECwindows Motif for OpenVMS provides the National Center for Supercomputing Applications (NCSA) Mosaic Version 2.4 browser to let you navigate and access information on the Internet. The NCSA Mosaic browser is provided as sample, "as is" software to introduce you to the Internet and help you get started using a World Wide Web viewer. Because the NCSA Mosaic browser that ships with this release is only a sample implementation, we have placed Mosaic with the other sample software in the DECW$UTILS directory. The Mosaic browser enables OpenVMS users to search, retrieve, display, store, and forward data using the Internet. Mosaic functions in conjunction with the World Wide Web environment, which is a collection of information servers. Note that the graphical user interface for Mosaic is not compliant with the Motif style guide; therefore, the Mosaic browser does not look the same as the DECwindows Motif out-of-the-box (OOTB) applications. The following information about Mosaic is included in this appendix: o Section C.1, Starting Mosaic Software o Section C.2, Creating a Home Page o Section C.3, Configuring Mosaic to Process Multimedia Files o Section C.4, Customizing the Mosaic Browser o Section C.5, Restrictions for Using Mosaic from Behind a Firewall C-1 Using the NCSA Mosaic Browser (VMS 5.5-2 Only) C.1 Starting Mosaic Software C.1 Starting Mosaic Software V1.2-3 The Mosaic browser, which is located in the DECW$UTILS directory, is installed as part of the product installation for the Compaq DECwindows Motif for OpenVMS product. To access the verb and start Mosaic, select Menus... from the Options Menu in FileView. Mosaic is listed in the Item Names list. Add the verb Mosaic to a menu, such as the Applications Menu, so that you can invoke Mosaic and display the DECwindows Motif home page. Refer to Using DECwindows Motif for OpenVMS for information about adding verbs to menus. C-2 Using the NCSA Mosaic Browser (VMS 5.5-2 Only) C.1 Starting Mosaic Software ________________________ Note ________________________ You can display the sample DECwindows Motif home page without a TCP/IP connection to the network. However, to access information contained in the topics in the Help menu requires that Compaq TCP/IP Services for OpenVMS be installed. ______________________________________________________ C.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 the Internet. Click on the On HTML... topic in the Help menu for information about using HTML (Hypertext Markup Language) to create a home page. HTML uses markup tags to tell Mosaic how to format text. A Beginner's Guide to HTML is displayed, which provides information about markup tags, examples, formatting, creating links, troubleshooting, and so on. Note that you can access topics in the Help menu only if your system is connected to the TCP/IP network using Compaq TCP/IP Services for OpenVMS. As an example of an HTML source, see the DECwindows Motif sample home page. Click on View Source... from the File menu to see the HTML source. C.3 Configuring Mosaic to Process Multimedia Files V1.2-4 The Mosaic browser that is included with Compaq DECwindows Motif for OpenVMS provides support for recognizing and processing the following types of files: o GIF o Audio o MPEG o MIME C-3 Using the NCSA Mosaic Browser (VMS 5.5-2 Only) C.3 Configuring Mosaic to Process Multimedia Files If Mosaic encounters a hyperlink (or an anchor) to any of these file types, it attempts to start an external program to display the image or to play the sound. If Mosaic cannot locate an appropriate external viewer, it prompts the user to enter a file name where the data file can be stored in case the data is needed outside of Mosaic. To determine what external viewer will display the image or play the sound, Mosaic does the following: 1. Determines the MIME type of the incoming file according to either the file extension or the way the file is specified by the document server. If the file extension is used to determine the external viewer, Mosaic uses either a built-in default list or an extension map file that can be configured by the user. 2. Matches the MIME file type of the incoming file to an external viewer according to either the built-in default list or a setup that is configured by the user and specified in the file DECW$UTILS:XMOSAIC-SETUP.COM. For example, GIF files are mapped to the xv viewer. The xv viewer is shareware software that is not provided with DECwindows Motif. However, the xv viewer is available from the following location as an OpenVMS freeware offering: http://www.openvms.compaq.com/openvms/internetnetworks.html The xv mapping is defined in the file DECW$UTILS:XMOSAIC- SETUP.COM, a self-documented command procedure, as follows: $ XV :== $DECW$EXAMPLES:PICT.EXE The executable PICT.EXE is used to display the GIF file. Note that PICT.EXE cannot be used to display a JPEG file. Other mappings include the following: ___________________________________________________________ Image_Type____________Display/Sound_Logical_Name___________ audio/* - > showaudio image/xwd - > xwud image/x-xwd - > xwud image/x-xwindowdump - > xwud image/*_______________-_>__xv______________________________ C-4 Using the NCSA Mosaic Browser (VMS 5.5-2 Only) C.3 Configuring Mosaic to Process Multimedia Files Mappings in the previous list that are followed by an asterisk (*) are available in some versions of Mosaic (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: $ APLAY :== mcr decsound -volume 70 -speaker -play $ SHOWAUDIO :== mcr decsound -volume 70 -speaker -play $ XWUD :== $decw$utils:xwud.exe C.4 Customizing the Mosaic Browser V1.2-4 You can customize the Mosaic browser by setting any of the NCSA Mosaic X resources in the file DECW$USER_ DEFAULTS:MOSAIC.DAT. The class name for Mosaic for X is Mosaic. The information that follows shows the names and descriptions of the X resources. Note that class and resource names are the same except that the first character in the resource name is capitalized. The following resources are listed: o Functional resources o Visual resources o Font resources o Proxy gateway resources Functional Resources Table C-1 lists the functional resources and descriptions. C-5 Using the NCSA Mosaic Browser (VMS 5.5-2 Only) C.4 Customizing the Mosaic Browser Table_C-1_Functional_Resources_____________________________ Resource______________Description__________________________ annotationsOnTop: Indicates whether inlined document Boolean annotation hyperlinks are prepended to the document (if true) or postpended (if false). (Default is false). autoPlaceWindows: If set to false, the new Document Boolean View windows are not automatically positioned by the program itself; your Window Manager determines the placement. (Default is true.) catchPriorAndNext: Controls whether using the keys Prior Boolean and Next (Page Up and Page Down on most keyboards) are explicitly caught in the Document View window and passed to the vertical scrollbar, or whether the normal Motif scrolled window mechanism is relied upon to automatically take this action. (Default is false.) If the Page Up and Page Down key sequences are not functioning appropriately for your environment, set this resource to true. (Refer to the information about hot keys.) confirmDeleteAnnotatioConfirms deleted annotations through Boolean a confirmation dialog box. (Default is true.) confirmExit: Boolean Determines whether the NCSA Mosaic browser pops up a dialog box to confirm exiting from the program when the Exit Program menu option is selected. (Default is true.) (continued on next page) C-6 Using the NCSA Mosaic Browser (VMS 5.5-2 Only) C.4 Customizing the Mosaic Browser Table_C-1_(Cont.)_Functional_Resources_____________________ Resource______________Description__________________________ defaultAuthorName: Identifies your full name (for string example, John Q. Public). Your full name is normally stored in the system password file, and Mosaic extracts the name from that file if this resource is NULL; otherwise, the value of this resource is used. (Default is NULL.) defaultHeight: Specifies the default height in integer pixels for a Document View window. (Default is 680.) defaultHotlistFile: Specifies a file name to store string the default hotlist (or a list of bookmarks). (Default is ".mosaic- hotlist-default". The value of the environment variable $HOME is prepended to this string.) defaultWidth: Specifies the default width in pixels integer for a Document View window. (Default is 620.) (continued on next page) C-7 Using the NCSA Mosaic Browser (VMS 5.5-2 Only) C.4 Customizing the Mosaic Browser Table_C-1_(Cont.)_Functional_Resources_____________________ Resource______________Description__________________________ delayImageLoads: Selects delayed image loading, Boolean which is for users with slow network connections. If set to true, Mosaic substitutes a small icon for inlined- images and an arrow icon for inlined- images that also act as hyperlinks. Clicking on an icon tells Mosaic to load that inlined-image; clicking on the arrow is equivalent to following the associated hyperlink. Selecting Load Images in Current from the Mosaic Options menu loads and displays all the inlined-images in the current document. Delayed image loading can also be selected with the -dil command-line flag or on a per- window basis from the Options menu in Mosaic. (Default is false.) displayURLsNotTitles: Displays URLs wherever document Boolean titles are usually displayed, if set to true. (Default is false.) DocsDirectory: Overrides the location of the help string documents. (Default is NULL.) documentsMenuSpecfile:Specifies the name of the file string that holds an optional "Documents Menu Specfile" to allow sites to add their own Documents menu to the Mosaic menu bar. For more information, see the documentation about creating a configurable Documents menu. (Default is "/usr/local/lib/mosaic/documents.menu".) (continued on next page) C-8 Using the NCSA Mosaic Browser (VMS 5.5-2 Only) C.4 Customizing the Mosaic Browser Table_C-1_(Cont.)_Functional_Resources_____________________ Resource______________Description__________________________ fancySelections: Cuts and pastes from the Document Boolean View window with fancy selections enabled in the HTML widget, which results in underlined headers, bulleted lists, and so on, if set to true. Uses normal selection behavior if set to false. Note that selections can be for each window at any time. (Default is false.) fullHostname: string Allows explicit setting of the fully qualified host name for systems that fail on a call to gethostbyname(). Use the fullHostname resource only if necessary, in conjunction with gethostbynameIsEvil. gethostbynameIsEvil: Set to true if you are running Boolean your system on a Sun set up so that when the system attempts to find its own full host name through gethostbyname(), the system coredumps. (Default is false.) globalExtensionMap: Set to the location of the system- string wide extension map config file of your choice. (Default is "/usr/local/lib/mosaic/mime.types".) globalHistoryFile: Specifies the name of the file to string store the global history of all documents accessed from session to session. (Default is .mosaic-global- history. The value of the environment variable $HOME will be prepended to this string.) (continued on next page) C-9 Using the NCSA Mosaic Browser (VMS 5.5-2 Only) C.4 Customizing the Mosaic Browser Table_C-1_(Cont.)_Functional_Resources_____________________ Resource______________Description__________________________ globalTypeMap: Specifies the location of the system- string wide mailcap (type map config) file of your choice. (Default is "/usr/local/lib/mosaic/mailcap".) gunzipCommand: Specifies the command to uncompress string gzip files (that is, files with an extension of .z.) You can obtain gunzip from prep.ai.mit.edu in /pub/gnu. (Default is gunzip -n - f, which requires the 1.2.4 version of gzip.) hdfMaxImageDimension: Specifies the maximum height and/or integer width of an HDF inlined image in pixels. (Default is 400.) hdfMaxDisplayedDatasetSpecifies the maximum number of integer displayed data sets while browsing HDF files. If more than the maximum number exist in an HDF file, Mosaic displays the HDF file in "brief mode". (Default is 15.) hdfMaxDisplayedAttribuSpecifies the maximum number of integer displayed attributes while browsing HDF files. If more than the maximum number exist in an HDF file, Mosaic displays the HDF file in "brief mode." (Default is 10.) hdfPowerUser: Set to true if most of the supporting Boolean text in an HDF file will be removed. (Default is false.) homeDocument: string Specifies the document to access at program startup. See the information about on specifying your home document. (Default is http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/ NCSAMosaicHome.html) (continued on next page) C-10 Using the NCSA Mosaic Browser (VMS 5.5-2 Only) C.4 Customizing the Mosaic Browser Table_C-1_(Cont.)_Functional_Resources_____________________ Resource______________Description__________________________ imageCacheSize: Specifies the size of the inlined- integer image cache in kilobytes. The - ics command-line flag can also be used. All the images in a given document are (temporarily) cached while on that page, regardless of the imageCacheSize value. Cache flushes the least recently viewed. (Default is 2048.) initialWindowIconic: Set to true if the first Document Boolean View window opened (when the program starts) will be iconified. (Default is false.) maxWaisResponses: Controls the maximum number of integer matches Mosaic accesses from a WAIS server. (Default is 200.) personalAnnotationDireSpecifies 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 named directory does not exist, it is created. However, intermediate directories, if any are named, are not created. (Default is .mosaic-personal-annotations. The value of the environment variable $HOME will be prepended to this string.) personalExtensionMap: Specifies the location of the string personal extension map configuration file of your choice. The value of the environment variable HOME is prepended. (Default is .mime.types) (continued on next page) C-11 Using the NCSA Mosaic Browser (VMS 5.5-2 Only) C.4 Customizing the Mosaic Browser Table_C-1_(Cont.)_Functional_Resources_____________________ Resource______________Description__________________________ personalTypeMap: Specifies the location of the string personal mailcap file of your choice. The value of the environment variable HOME is prepended. (Default is .mailcap) printCommand: string Specifies the name of the default command for the Print menu option. This command accepts a single argument: the name of the file to print. Note that this location can be changed at any time through the Print option's dialog box. (Default is lpr) recordCommandLocation:Specifies the location (full path string name) of the command used to record audio annotations (on Sun, SGI, and HP platforms). If the named command does not exist when Mosaic is started, audio annotations are disabled (the menu entry becomes insensitive). (Default is "/usr/sbin/recordaiff" on SGI; "/usr/demo/SOUND/record" on Sun; "/usr/audio/bin/srecorder" on HP.) recordCommand: Specifies the command used to record string audio annotations; this is the full command, using the command named in recordCommandLocation as the first word. (Default is "recordaiff -n 1 -s 8 -r 8000" on SGI; "record" on Sun; "srecorder -au" on HP. The named command accepts a single additional argument: the file name of the new audio file. The command also correctly terminates recording when a SIGINT is sent.) (continued on next page) C-12 Using the NCSA Mosaic Browser (VMS 5.5-2 Only) C.4 Customizing the Mosaic Browser Table_C-1_(Cont.)_Functional_Resources_____________________ Resource______________Description__________________________ reloadReloadsImages: Clears out the Reload option cached Boolean image data for the current document before reloading the document if set to true; thus causing the images to also be reloaded. This is useful for HTML authors who are using Mosaic to view their work. (Default is false.) sendmailCommand: Specifies a pointer to the sendmail string binary. It assumes that this program accepts command-line arguments that specify addresses to which messages should be mailed and accepts other headers and message text from stdin. (Default is "/usr/lib/sendmail".) simpleInterface: Allows the Mosaic menu bar and bottom Boolean button configuration to be minimized considerably. (Default is false). tmpDirectory: string Specifies the name of the directory in which to store temporary files generated by Mosaic. This directory should contain at least 10 or 20 megabytes, in case you to pull down a very large data file. Setting this resource is equivalent to using the command-line flag, -tmpdir, or setting the environment variable TMPDIR. trackFullURLs: Enables prototypical smart display Boolean of "where you're going" during mouse tracking, including format definition, if set to false. (Default is true.) (continued on next page) C-13 Using the NCSA Mosaic Browser (VMS 5.5-2 Only) C.4 Customizing the Mosaic Browser Table_C-1_(Cont.)_Functional_Resources_____________________ Resource______________Description__________________________ trackPointerMotion: Sets the mouse pointer so that it Boolean will not be tracked so that URLs are visible on the lower status line, if set to false. (Default is true.) trackVisitedAnchors: Displays visited anchors (that is, Boolean anchors that point to documents that have previously been viewed) with a different style than anchors that are not yet visited, if set to true. (On slow systems, changing this resource to false may substantially improve the performance of Mosaic.) (Default is true.) tweakGopherTypes: Mosaic interprets Gopher documents Boolean strictly by the Gopher typing system, if set to false. When set to true, Mosaic uses its own mechanism to determine the file types of Gopher documents. (Default is true.) twirlIncrement: Indicates the minimum number of bytes integer that are are transferred between updates of the twirling transfer icon for normal (FTP, Gopher, HTTP) transfers. (Default is 4096.) twirlingTransferIcon: Set to false to turn off the twirling Boolean NCSA logo during document transfers. Clicking the icon still interrupts a transfer. (Default is true.) uncompressCommand: Specifies the command to uncompress string compressed files (that is, files with an extension of .Z). (Default is uncompress). (continued on next page) C-14 Using the NCSA Mosaic Browser (VMS 5.5-2 Only) C.4 Customizing the Mosaic Browser Table_C-1_(Cont.)_Functional_Resources_____________________ Resource______________Description__________________________ useDefaultExtensionMapSet to false to keep any default Boolean file-extension-to-MIME-type mappings from Mosaic. Keeping this resource 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-viewer mappings from Mosaic. It is strongly recommended that you leave this resource set to true; override the setting as necessary. (Default is true.) useGlobalHistory: Automatically stores a global history Boolean of everywhere you visit, if set to true. (This history is used to shade anchors in different colors based on whether you visited the corresponding documents, if the resource trackVisitedAnchors is set to true.) (Default is true.) xtermCommand: string Specifies the name of the command used to start a terminal window for a telnet session. (Default is xterm on most platforms; the default is ______________________aixterm_-v_on_IBM_AIX_3.x_systems.)__ Visual Resources Table C-2 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_ DEFAULTS:MOSAIC.DAT in the following format: C-15 Using the NCSA Mosaic Browser (VMS 5.5-2 Only) C.4 Customizing the Mosaic Browser Mosaic*anchorColor: cyan Table_C-2_Visual_Resources_________________________________ Resource______________Description__________________________ anchorColor: color Specifies the color to shade anchors whose corresponding documents have not previously been visited. (Default is blue3.) visitedAnchorColor: Specifies the color to shade anchors color whose corresponding documents have previously been visited. (Default is violetred4.) activeAnchorFG: Specifies the color to shade anchors color that are in the process of being activated. (Default is red.) activeAnchorBG: Specifies the color to shade the color background of the anchors that are in the process of being activated. (Default is grey80, which is the same color as the background in the browser.) anchorUnderlines: Specifies the number of lines to integer draw underneath the unvisited anchors (Valid values: 0, 1, 2, 3) (Default is 1.) visitedAnchorUnderlineSpecifies the number of lines to draw integer underneath the visited anchors. Valid values: 0, 1, 2, 3 (Default is 1.) dashedAnchorUnderlinesSets drawn lines under the unvisited Boolean anchors to dashes, if set to true. (Default is false.) dashedVisitedAnchorUndSetsndrawn lines under unvisited Boolean anchors to dashes, if set to true. (Default is false.) (continued on next page) C-16 Using the NCSA Mosaic Browser (VMS 5.5-2 Only) C.4 Customizing the Mosaic Browser Table_C-2_(Cont.)_Visual_Resources_________________________ Resource______________Description__________________________ colorsPerInlinedImage:Specifies the number of unique colors integer to allocate for each inlined-image. (Note that this setting does not affect the images that are displayed externally to the NCSA Mosaic browser (for example, GIF images passed to an external viewer).) (Default is 50.) percentVerticalSpace: Specifies the height of the vertical integer space between paragraphs, headers and paragraphs, and so on, as expressed as a percentage of the normal line height. (Default is 90.) reverseInlinedBitmapCoSpecifies to reverse foreground and Boolean background colors in inlined XBM bitmaps, if set to true. (Default is false.) verticalScrollOnRight:Specifies that the Document View Boolean window places its scroll bar on the left side, if set to false. (Default ______________________is_true.)____________________________ Font Resources Font resources, which are also associated with the HTML widget, can be changed dynamically from the Options menu. Table C-3 lists the font resource names and descriptions. Table_C-3_Font_Resources___________________________________ Resource_______Description_________________________________ font: font Used in normal formatted text. (Default is "-adobe-times-medium-r-normal-*-17-*-*-*-*-*-iso8859-1".) italicFont: Used in italic formatted text. (Default is font "-adobe-times-medium-i-normal-*-17-*-*-*-*-*-iso8859-1".) (continued on next page) C-17 Using the NCSA Mosaic Browser (VMS 5.5-2 Only) C.4 Customizing the Mosaic Browser Table_C-3_(Cont.)_Font_Resources___________________________ Resource_______Description_________________________________ boldFont: Used in bold formatted text. (Default is font "-adobe-times-bold-r-normal-*-17-*-*-*-*-*-iso8859-1".) fixedFont: Used in fixed (typewriter style) formatted font text. (Default is "-adobe-courier-medium-r-normal-*-17-*-*-*-*-*-iso8859-1".) header1Font: Used in level 1 headers. (Default is font "-adobe-times-bold-r-normal-*-24-*-*-*-*-*-iso8859-1".) header2Font: Used in level 2 headers. (Default is font "-adobe-times-bold-r-normal-*-18-*-*-*-*-*-iso8859-1".) header3Font: Used in level 3 headers. (Default is font "-adobe-times-bold-r-normal-*-17-*-*-*-*-*-iso8859-1".) header4Font: Used in level 4 headers. (Default is font "-adobe-times-bold-r-normal-*-14-*-*-*-*-*-iso8859-1".) header5Font: Used in level 5 headers. (Default is font "-adobe-times-bold-r-normal-*-12-*-*-*-*-*-iso8859-1".) header6Font: Used in level 6 headers. (Default is font "-adobe-times-bold-r-normal-*-10-*-*-*-*-*-iso8859-1".) addressFont: Used in addresses. (Default is "-adobe-times-medium-i-normal-*-17-*-*-*-*-*-iso8859-1".) font plainFont: Used in plaintext regions or preformatted font documents. (Default is "-adobe-courier-medium-r-normal-*-14-*-*-*-*-*-iso8859-1".) listingFont: Used in listing regions. (Default is font "-adobe-courier-medium-r-normal-*-12-*-*-*-*-*-iso8859-1".) fixedboldFont: Used for bold in fixed (typewriter style) font formatted text. fixeditalicFontUsed for italics in fixed (typewriter style) font formatted text. plainboldFont: Used for bold in plaintext regions or font preformatted documents. plainitalicFontUsed for italic in plaintext regions or font___________preformatted_documents._____________________ Proxy Gateway Resources When your proxy gateway has been established by your network or system administrator, you can use its resources. Table C-4 provides additional details about proxy gateway support in the NCSA Mosaic Version 2.4 browser. C-18 Using the NCSA Mosaic Browser (VMS 5.5-2 Only) C.4 Customizing the Mosaic Browser Table_C-4_Proxy_Gateway_Resources__________________________ Resource______________Description__________________________ ftpProxy: String Used for ftp URLs. gopherProxy: String Used for gopher URLs. httpProxy: String Used for http URLs. newsProxy: String Used for news URLs. waisProxy: String Used for wais URLs. ProxyGateway:_String__Used_for_all_access_methods._________ C.5 Restrictions for Using Mosaic from Behind a Firewall V1.2-3 The following sections present information about using the ProxyGateway and NoProxy resources with Mosaic to access information on the Internet when security restrictions (that is, a firewall) exist between internal and external network access at your site. C.5.1 ProxyGateway Resource NCSA Mosaic Version 2.4 provided in Compaq DECwindows Motif for OpenVMS supports the proxy gateway (ProxyGateway) resource. A proxy gateway is a trusted agent that enables Mosaic to access network information that is either within or outside the firewall, but not both. When the Mosaic browser is used from behind a firewall, 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. Note, however, that if the proxy gateway is located outside of your firewall, then information behind the firewall (such as home pages, World Wide Web documents, and Notes files) cannot be accessed by the proxy gateway. C-19 Using the NCSA Mosaic Browser (VMS 5.5-2 Only) C.5 Restrictions for Using Mosaic from Behind a Firewall C.5.2 NoProxy Resource If your site requires the ability to access Internet information both within and outside the firewall, then a version of Mosaic that supports the NoProxy resource is required. This resource allows you to specify a list of domains that should not be consulted by the proxy gateway (that is, access to information in these domains does not go through the proxy gateway). As previously stated, the NoProxy resource restricts access for the proxy gateway to a set of domains that are not consulted by the proxy gateway. You can specify the NoProxy resource, provided that you have NCSA Mosaic Version 2.4a for OpenVMS, in the file DECW$USER_DEFAULTS:MOSAIC.DAT according to the following format: Mosaic*ProxyGateway: http://www-proxy.site.org:8080/ Mosaic*NoProxy: localhost, site.org ___________________________________________________________ Where:________________Description__________________________ www-proxy.site.org Name of the host that runs the proxy server 8080 Port number through which Mosaic communicates to the proxy server through the firewall local host, site.org List of site names, which are separated by commas, excluded from ______________________going_through_the_proxy_server_______ Refer to the following URL for additional information about proxy gateways: http://webservices.web.cern.ch/WebServices/ C-20 _________________________________________________________________ Index A______________________________ C______________________________ Access control, 2-22 Calendar enabling and disabling, 5-8 removing from a subpanel, AccessX support 2-28 keyboard enhancements, 2-18 CDA Animation applications, 3-15 applications, 2-38, 2-40 Answerback message dynamic font support, DECterm, 2-52 2-39 Applications packing, 2-41 compiling Fortran, 4-10 unpacking, 2-42 Auto Repeat setting WRITE$FONT logical name, changing in DECterm, 2-50 2-39 B changes to external reference _______________________________ processing, 4-13 Backdrop converters, 4-32 default, 2-35 converting Asian-language Bindings support text files, 4-32 languages, 4-3 defining logical names, 4-31 Bookreader Display Options..., 2-44 draft-quality printing, 2-37 drag-and-drop restoring last login state, implementing, 4-11 2-37 internationalization support, specifying DECW$BOOKSHELF 4-30 files, 2-38 logical names with convert, using comments in the 4-14 DECW$BOOKSHELF file, 2-38 message, 2-44 using UNIX command line, packing and unpacking error 2-37 messages, 2-43 paper size button, 2-44 programming external referencing, 4-13 Index-1 CDA Compound Document Architecture programming (cont'd) See CDA interface changes, 4-12 Console port logical names with convert selecting, 3-23 , 4-14 Console Window release notes, 4-11 console messages, 3-23 restructuring of shareable controlling the initial images, 4-15 position, 3-24 style guide message, 4-14 defining a global symbol, restructuring of shareable 3-24 images, 4-15 displaying console messages, specifying an options file, 3-23 4-30 DISABLE (default), 3-23, style guide message, 4-14 3-24 C header files, 4-10 ENABLE, 3-24 Clock values, 3-23 using the alarm, 2-45 WINDOW, 3-23 Color Customizer, 2-3 invoking, 3-24 auto shadowing toggle button, selecting the Alternate 2-9 Console port, 3-23 building, 2-4 Copyright notice command summary, 2-6 displaying in a DECterm DECterms unaffected, 2-9 window, 2-48 mapping color resources and color cells, 2-7 D______________________________ modifying DECW$LOGIN.COM, Debugger 2-5 using in DECterm, 3-27 running, 2-5 DEC CDA Base Services, 4-12 supported DECchart application applications, 2-4 invoking from the Session displays, 2-3 Manager, 2-68 using on multiheaded systems, DECsound, 2-45 2-9 DECterm xsetroot_cust demo, 2-10 answerback message, 2-52 Command files automatic window positioning, for checking version, 3-4 3-26 Compatibility batch scrolling, 2-46 shareable images, B-10 changing the Auto Repeat Compiling applications setting, 2-50 See also Applications color selection, 2-50 Fortran, 4-10 DECCRA sequence, 4-18 Compose character, 2-36 DECLFKC sequences, 4-18 device output files, 2-49 diagnostic crash file, 2-55 Index-2 DECterm (cont'd) DECW$INCLUDE:TEXTP.H header diagnostic crash messages, file 2-55 definition changes, B-12 displaying the copyright DECW$INCLUDE:XMP.H header file notice, 2-48 See also Header files escape sequences, 2-47 changes, B-11 finish printing option, 5-2 removed definitions font sizes, 2-46, 2-49 XmHALFLONGBITS, B-11 graphics, 2-54 XmLONGBITS, B-11 hold-screen response time, DECW$LOGIN.DAT 3-27, 5-5 customizing the login screen, local echo, 2-52 3-18 logicals, 3-25 DECW$UTILS page-movement sequences, global symbols, 3-17 4-18 DECwindows positioning, 2-51 delayed startup on Alpha, printing files, 2-49 3-10 /PROCESS problem, 2-56 DECwindows Desktop programming issues, 4-17 release notes for general ReGIS input cursors, 4-17 user, 2-36 ReGIS locator report, 2-57 DECwindows Extensions to Motif reporting window size, 2-48 , 4-20 resizing the terminal, 2-48 DECwindows OSF/Motif Toolkit resource file name, 2-47 See Toolkit resource usage, 2-54 Detached processes, 2-26 screen print services, 2-53 Development support, 4-2 scrolling through the Dialog boxes keyboard, 2-48 changing the position seven-bit printer support, Set Password, 3-19 2-53 Start Session, 3-19 system management, 3-25 Display server terminal emulator, 2-55 shared memory extension, user font selection, 2-51 4-21 using the debugger, 3-27 shared memory pixmaps, 4-27 virtual terminal support, shared memory XImages, 4-23 3-27 supporting AccessX, 2-18 DECTPU Drag-and-drop programming issues, 4-19 using, 2-19, 4-11, 5-3 DECW$CDPLAYER DXmCSText widget required privileges, 2-58 input method support, 4-20 DECW$CONSOLE_GEOMETRY DXmFormSpaceButtonsEqually global symbol, 5-6 routine DECW$CONSOLE_SELECTION sizing and spacing widgets, global symbol, 5-6 4-20 Index-3 DXmLAYOUT_LEFT_DOWN constant Finish printing option DXmNlayoutDirection resource, DECterm, 5-2 5-9 Font limitations, 2-35 DXmLAYOUT_LEFT_UP constant Font resources DXmNlayoutDirection resource, See Mosaic 5-9 Fortran DXmLAYOUT_RIGHT_DOWN constant compiling applications, 4-10 DXmNlayoutDirection resource, Functional resources 5-9 See Mosaic DXmLAYOUT_RIGHT_UP constant DXmNlayoutDirection resource, G 5-9 _______________________________ DXmNlayoutDirection resource GBLPAGES parameter, 3-1 constants, 5-9 GET_CHAR_STRUCT function access, 5-8 E______________________________ Global symbols EFS DECW$CONSOLE_GEOMETRY, 5-6 DECW$CONSOLE_SELECTION, 5-6 See Extended File Graphics card support Specifications Cirrus, 2-29 Escape sequences DECterm, 2-47 H______________________________ Extended File Specifications Header files (EFS) DECW$INCLUDE:TEXTP.H, B-12 File Manager support, 2-62 DECW$INCLUDE:XMP.H, B-11 file selection popup, 2-61 languages, 4-3 FileView support, 2-61 Hold-screen response time programming library support, enhancing, 5-5 2-62 Home page Support overview, 2-61 See also Mosaic translated image support, creating, C-3 2-64 F I______________________________ _______________________________ Icon files File Manager viewing, 2-24 accessing files using ACLs, Input cursors 2-28 cross-hair, 4-17 limitations, 2-33 diamond, 4-17 refreshing views, 3-14 rubber-band line, 4-17 shredding files, 2-24 rubber-band rectangle, 4-17 Files selecting, 4-17 previously optional, 3-2 Installation FileView DMA setting, 3-1 application startup, 3-29 system parameters, 3-1, 3-5 private logos, 2-70 Index-4 Internationalization Mail converting files, 4-32 keyboard actions (cont'd) locale support, 4-37 activating pushbuttons in viewing files, 4-30 dialog boxes, 2-60 Internet highlighting selections, See also Mosaic 2-60 browsing, 2-2, 2-3, C-1 pasting messages, 2-60 sending messages from K______________________________ DECnotes, 2-59 Key bindings, 2-36 Messages Keyboard System Menu Bar: Pseudo Mouse enhancements for disabled not available, 3-28 users, 2-18 MIT X11 scrolling in DECterm, 2-48 Release 3 Intrinsics messages, B-10 L______________________________ Release 4 Intrinsics Language variants messages, B-10 selecting, 2-24 Mosaic Local echo configuring DECterm, 2-52 processing Locale support, 4-36 Audio files, C-3 Logical names GIF files, C-3 defining in the CDA Viewer, MIME files, C-3 4-31 MPEG files, C-3 Login logos multimedia files, C-3 customizing, 3-20, 5-7 creating a home page, C-3 Login screen determining an external changing colors, 3-18 viewer, C-4 customizing, 3-18 external view setup DECW$LOGIN.DAT, 3-18 examples, C-5 entering username and file location, C-2 password, 2-29 firewall, C-19 position, 2-29 font resources, C-17 welcome message, 2-29, 3-13 functional resources, C-5 Logos mappings, C-4 modifying the Compaq logo, NoProxy resource restrictions, C-20 3-18 providing as the Internet browser, C-1 M______________________________ proxy gateway resources, Mail C-18 choosing window colors, 2-59 restrictions, C-19 color customizer, 2-60 setting Mosaic X resources, dragging messages, 2-58 C-5 keyboard actions, 2-60 starting, C-2 Index-5 Mosaic New Desktop (cont'd) starting (cont'd) removing calendar from a an external program, C-4 subpanel, 2-28 supporting the NoProxy saving and restoring resource, C-20 applications, 2-32 supporting the ProxyGateway saving sessions, 2-27 resource, C-19 screen saver support, 2-23 visual resources, C-15 setting default display, Motif and XUI widgets 2-28 mixing, B-11 shredding multilevel Motif Window Manager directories, 2-24 centering lines for multiline ToolTalk support, 2-32 icon titles, 2-73 using ACLs, 2-28 color customizer, 2-71 using screen lock, 2-28 configuration file, 2-72 viewing icon files, 2-24 customizing Node name display colors on multihead disabling, 3-20 systems, 2-73 Notepad moving the icon box off the linking with the Release screen, 2-73 1.1.3 Toolkit, 2-65 restarting, 2-72 running earlier versions of O______________________________ DECwindows, 2-71 Options file supporting customization for specifying, 4-30 monochrome monitors, 2-72 OSF/Motif Toolkit Mozilla, 2-2 examples, B-12 MWM cutpaste, B-12 See Motif Window Manager dnddemo, B-12 Dogs, B-14 N______________________________ widget, B-15 NCSA Enhanced Mosaic, 2-3 helloint, B-16 Netscape Navigator, 2-2 hellomotif, B-17 New Desktop MOTIFANIM, B-17 changing workspaces, 2-29 MOTIFGIF, B-18 detached processes, 2-26 motif samples, B-27 font selection, 2-35 motifshell, B-19 Front Panel, 2-32 periodic, B-19 language variants, 2-24 pict, B-18 logging in, 2-29 PICT, B-18 Login Screen, 2-29 resource files for example overview of, 2-23 programs, B-28 reference pages, 2-26 Square widget, B-15 release notes for general textedit, B-19 user, 2-23 to 2-35 Index-6 OSF/Motif Toolkit Proxy gateway resources examples (cont'd) See Mosaic uid files for example Pushbuttons programs, B-29 DECwindows Mail view, B-22 activating in dialog boxes xmpiano, B-24 , 2-60 xmtravel, B-28 known problems, B-29 R______________________________ Overlay support Rebooting after installation, See also Window Manager 3-7 colormap Reference pages avoiding potential viewing, 2-26 problems, 3-31 ReGIS input cursors modifying applications, 3-31 See also Input cursors sharing overlay colormaps Resources with the Window Manager, See also Mosaic 3-31 font, C-17 P functional, C-5 _______________________________ proxy gateway, C-18 Paint setting in Mosaic, C-5 creating private colormaps, visual, C-15 2-65 Run-time support, 4-2 enhancing performance during basic operations, 2-66 S______________________________ Parameter datasize Save/restore protocol, 2-32 mismatches, 4-41 Security options, 5-6 Pascal programming Session Manager, 2-69 .PEN files, 4-40 Server PEN files tuning, 3-14 using with Pascal programs, Session Manager 4-40 color customizer, 2-70 Printing DECchart application, 2-68 Bookreader, 2-37 DECterm windows, 2-67 Print Screen known problems problems with PostScript private logos, 2-70 output, 2-66 saving sessions, 2-27 Process security options, 2-69 creating with virtual stopping a process, 2-70 terminal support, 3-27 Set Password dialog box Programming environments, 4-2 changing the position, 3-19 Programming support and XUI, Seven-bit printer support B-4 DECterm, 2-53 Index-7 Shareable images Toolkit (cont'd) compatibility, B-10 extensions upward compatibility, B-10 DXmCSText widget, 4-20 Shareable linkages SVN widget, 4-20, 4-21 installing images, 3-3 mixing Motif and XUI Widgets, Shared memory B-11 creating and using XImages, modifying XmText and 4-23 XmTextField translation extension support, 4-21 manager syntax, B-9 pixmaps, 4-27 OSF/Motif Release 1.2.3, 4-1 Spyglass Enhanced Mosaic OSF/Motif Release 1.2.4, 4-1 no longer supported, 2-3 OSF/Motif Release 1.2.5, 4-1 Start Session OSF/Motif Release 1.2.6, 4-1 blue login screen, 3-13 release 1.1.3 applications Start Session dialog box abort, 2-22 changing the position, 3-19 saving programming Structured Visual Navigation environments, B-4 See SVN UIL compiler, B-9 SVN widget Toolkit shareable images DXmSvnDeleteEntries routine, See Shareable images 4-21 Translated image support extended selection, 4-20 Extended File Specifications live horizontal scrolling, (EFS), 2-64 4-21 Translated-image support, 4-6 System running on OpenVMS systems, recommended quotas, 3-14 4-4 tuning non-VGA devices, 3-14 Translations System menu bar unsupported with XmText messages, 3-28 Widget, 2-20 T______________________________ U Tear-off menus _______________________________ using, 5-3 UIL files Terminal compiling, B-9 resizing, 2-48 parsing, 4-9 Toolkit UIL source code compatibility, 4-2 documentation, 5-10 naming in OSF/Motif Release 1.2.2 and X11 V______________________________ R5 Shareable Libraries, Version checking command files B-1 , 3-4 using _Xm routines, 4-9 Virtual terminal support description of Release 1.2.3, creating a process, 3-27 A-1 Index-8 Visual resources Xlib (cont'd) See Mosaic vendor pluggable layer, 4-38 XmNinputMethod resource W______________________________ using the shell to specify Widgets input methods, 4-20 See also Motif and XUI XmText Widget widgets, B-11 unsupported translations, sizing and spacing using 2-20 DXmFormSpaceButtonsEqually XNL library , 4-20 xnl_parsedatetime, 4-34 Window Dump utility xnl_xnl_langinfo, 4-34 dump to print file (xpr), xnl_langinfo 2-10 year 200 issues, 4-34 Window Manager xnl_parsedatetime overlay support, 3-30 year 2000 issues, 4-34 Window size XSelectAsyncEvent routine reporting for DECterm, 2-48 allocating memory, 4-39 Workspaces, 2-35 XSelectAsyncInput routine changing, 2-29 allocating memory, 4-39 XtAppMainLoop routine, 4-36 X______________________________ X Image extension, 4-28 Xlib Compaq international Xlib implementation, 4-39 extensions client side library, 4-29 Internationalization, 4-37 locale, 4-36 macros PAllHints, 4-41 routines files for Pascal programs, 4-40 parameter datasize, 4-41 XSelectAsyncEvent, 4-39 XSelectAsyncInput, 4-39 XtAppMainLoop, 4-36 XtOpenDisplay, 4-41 XtResolvePathname, 4-36 variables DISPLAY, 4-35 RESOURCE_NAME, 4-35 UIDPATH, 4-35 Index-9