____________________________________________________ DECwindows Motif V1.2-3 for OpenVMS Language Variants Release Notes July 1995 This manual describes software problems, corrections, and restrictions, as well as documentation changes that pertain to the DECwindows Motif Worldwide Support V1.2-3 for OpenVMS software and the DECwindows Motif V1.2-3 for OpenVMS Czech, Hungarian, Japanese, Korean, Polish, Russian, Slovak, Thai, Simplified Chinese and Traditional Chinese language variants. Revision/Update Information: This is a new manual. Operating System: OpenVMS Alpha Version 1.5 OpenVMS Version 5.5-2 Software Version: DECwindows Motif Worldwide Support V1.2- 3 for OpenVMS Alpha, DECwindows Motif V1.2-3 for OpenVMS language variants, DECwindows Motif Worldwide Support V1.2- 3 for OpenVMS VAX, and DECwindows Motif V1.2-3 for OpenVMS language variants. Digital Equipment Corporation ________________________________________________________________ June 1995 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. © Digital Equipment Corporation 1995. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: Alpha, Bookreader, CDA, DDIF, DEC, DECfonts, DEClinks, DECnet, DECpresent, DECterm, DECwindows, DECwrite, Digital, DTIF, LinkWorks, LN03, OpenVMS, ReGIS, ULTRIX, VAX, VAX C, VAX DOCUMENT, VAXstation, VMS, VT320, VT330, VT340, XUI, and the DIGITAL logo. The following are third-party trademarks: HP, LaserJet, PaintJet, QuietJet, RuggedWriter, and ThinkJet are registered trademarks of Hewlett-Packard Company. IBM is a registered trademark of International Business Machines Corporation. LaserWriter is a registered trademark of Apple Computer, Inc. Motif, OSF, OSF/1, and OSF/Motif are registered trademarks and Open Software Foundation is a trademark of the Open Software Foundation, Inc. POSIX is a registered trademark of the IEEE. PostScript is a registered trademark of Adobe Systems Incorporated. UNIX is a registered trademark licensed exclusively by X/Open Company Limited. X Window System is a trademark of the Massachusetts Institute of Technology. All other trademarks and registered trademarks are the property of their respective holders. This document was prepared using VAX DOCUMENT, Version 2.2. _________________________________________________________________ Contents Preface................................................... xi 1 DECwindows Motif New Features 1.1 Drag-and-Drop Functionality and Tear-Off Menus......................................... 1-1 1.1.1 Using Drag-and-Drop Functionality......... 1-2 1.1.2 Using Tear-off Menus...................... 1-2 1.2 Customizing the Login Screen.................. 1-3 1.2.1 Customizing the Digital Logo and Login Screen Colors............................. 1-3 1.2.2 Changing Position of the Start Session and Set Password Dialog Boxes................. 1-4 1.2.3 Disabling a Node Name Display in the Start Session Dialog Box........................ 1-5 1.3 Color Customizer Example Program.............. 1-5 1.3.1 Supported Displays........................ 1-5 1.3.2 Supported Applications.................... 1-6 1.3.3 Building the Color Customizer on OpenVMS Systems................................... 1-6 1.3.4 Running the Color Customizer.............. 1-7 1.3.5 Modifying the DECW$LOGIN.COM File......... 1-7 1.3.6 Command Interface Summary ................ 1-8 1.3.7 Changing the Mapping Between Color Resources and Color Cells................. 1-9 1.3.8 DECterm Windows Not Affected.............. 1-11 1.3.9 Changing the Default Value of the Automatic Shadowing Toggle Button......... 1-11 1.3.10 Using the Customizer on Multihead Systems................................... 1-11 1.3.11 Using the XSETROOT_CUST.EXE Demonstration Program................................... 1-12 1.4 Bookreader-New Feature........................ 1-12 iii 1.5 CDA New Applications.......................... 1-12 1.5.1 Pack and Unpack Applications.............. 1-12 1.5.1.1 Pack Application........................ 1-13 1.5.1.2 Unpack Application...................... 1-14 1.5.1.3 Pack and Unpack Error Messages.......... 1-15 1.6 DECterm....................................... 1-16 1.6.1 User Font Selection....................... 1-16 1.6.2 Local Echo................................ 1-17 1.6.3 Answerback Message........................ 1-17 1.6.4 Seven-Bit Printer Support................. 1-18 1.6.5 New Escape Sequences...................... 1-19 1.7 Window Dump to Print File (xpr) Utility....... 1-19 1.8 Keyboard Enhancements for Disabled Users...... 1-27 1.8.1 Sticky Keys............................... 1-27 1.8.2 Mouse Keys................................ 1-27 1.8.3 Toggle Keys............................... 1-28 1.8.4 Repeat Keys............................... 1-28 1.8.5 Slow Keys................................. 1-28 1.8.6 Bounce Keys............................... 1-28 1.8.7 Time Out.................................. 1-28 2 General User Release Notes 2.1 Notes Specific to DECwindows Motif Worldwide Support V1.2-3 for OpenVMS.................... 2-1 2.2 Access Control Not Explicitly Enabled by Default....................................... 2-2 2.3 DECwindows Motif Application Notes............ 2-3 2.3.1 Bookreader................................ 2-3 2.3.2 Calendar.................................. 2-3 2.3.3 Cardfiler................................. 2-4 2.3.4 CDA Run-Time Services..................... 2-4 2.3.4.1 CDA Dynamic Font Support................ 2-5 2.3.4.2 CDA WRITE$FONTS Logical Name............ 2-6 2.3.4.3 CDA Documents........................... 2-6 2.3.4.4 CDA PostScript Documents................ 2-7 2.3.5 CDA-Hints, Restrictions, and Known Problems.................................. 2-7 2.3.5.1 Display PostScript with the CDA Viewer.................................. 2-7 2.3.5.2 New Message for CDA Viewer.............. 2-8 2.3.5.3 CDA Paper Size Button Renamed........... 2-8 2.3.5.4 CDA Watch Progress Restriction.......... 2-8 iv 2.3.5.5 CDA Viewer Supports DECfonts Version 1.2..................................... 2-8 2.3.5.6 CDA Viewer-Viewing PostScript Files with Errors.................................. 2-9 2.3.6 Clock-DECsound Capability................. 2-9 2.3.7 DECsound.................................. 2-9 2.3.7.1 DECsound Prerequisites.................. 2-9 2.3.7.2 DECsound Problems....................... 2-10 2.3.8 DECterm................................... 2-10 2.3.8.1 VT330 and VT340 Terminal Emulation...... 2-10 2.3.8.2 CREATE/TERMINAL/DETACHED/PROCESS........ 2-11 2.3.8.3 Printing to an Attached Printer......... 2-11 2.3.8.4 DECterm Graphics........................ 2-12 2.3.8.5 DECterm Initialization.................. 2-13 2.3.8.6 DECterm Resource Usage.................. 2-14 2.3.8.7 Diagnostic Crash File and Messages-New and Enhanced............................ 2-14 2.3.8.8 Keyboards and Languages................. 2-15 2.3.8.9 Monitor Screen Width Determines Default Font Size............................... 2-15 2.3.8.10 Condensed German Standard Font Not Available............................... 2-16 2.3.8.11 ReGIS Locator Report.................... 2-16 2.3.9 DECW$CDPLAYER............................. 2-16 2.3.10 LinkWorks................................. 2-16 2.3.10.1 LinkWorks Manager Application Renamed to DEClinks................................ 2-16 2.3.10.2 LinkWorks Manager (DEClinks) Application Retired................................. 2-17 2.3.11 DECwindows Mail........................... 2-17 2.3.11.1 Using the Color Customizer with DECwindows Mail......................... 2-17 2.3.11.2 Multiple Tabs in Long Text Lines........ 2-17 2.3.11.3 DECwindows Mail Ends Without Print Queues.................................. 2-18 2.3.11.4 DECwindows Mail Is Linked with the OSF/Motif Release 1.1.3 Toolkit......... 2-18 2.3.11.5 DECwindows Mail-Known Problems.......... 2-18 v 2.3.12 DECwindows Motif Window Manager........... 2-19 2.3.12.1 Using the Color Customizer with DECwindows Motif Window Manager......... 2-19 2.3.12.2 Configuration File...................... 2-19 2.3.12.3 DECwindows XUI Applications............. 2-20 2.3.12.4 Restarting Motif Window Manager......... 2-20 2.3.13 Motif Window Manager-Known Problems....... 2-20 2.3.13.1 Accelerators for Icon in Icon Box....... 2-20 2.3.13.2 Application Started as Icon ............ 2-20 2.3.13.3 Customizing Color-Related Resources for Monochrome Monitors..................... 2-21 2.3.13.4 Customizing Colors on 4-Plane Displays................................ 2-21 2.3.13.5 Customizing Icon Placement in Icon Box..................................... 2-21 2.3.13.6 DECwindows XUI Modal Dialog Boxes....... 2-21 2.3.13.7 Customizing the Icon Box................ 2-22 2.3.13.8 Moving the Icon Box Off Screen.......... 2-22 2.3.13.9 Truncating the Icon Title............... 2-22 2.3.13.10 Invoking Motif Window Manager Help...... 2-22 2.3.13.11 Multihead Systems-Customizing Colors.... 2-22 2.3.13.12 Multiline Icon Title Not Centered ...... 2-22 2.3.13.13 Restored Window Icons Not Displayed..... 2-22 2.3.13.14 Truncated Icon Title in Vertical Icon Box..................................... 2-23 2.3.13.15 Window Menu on Icon-Displaying with Keyboard................................ 2-23 2.3.14 Notepad................................... 2-23 2.3.14.1 Notepad Is Linked with the OSF/Motif Release 1.1.3 Toolkit................... 2-23 2.3.14.2 Options/Split View...................... 2-23 2.3.15 Paint..................................... 2-23 2.3.15.1 Private Colormaps....................... 2-24 2.3.15.2 Enhancing the Performance of Some Paint Operations.............................. 2-24 2.3.15.3 Editing Color Images.................... 2-24 2.3.15.4 Saving a Paint File..................... 2-24 2.3.16 Print Screen.............................. 2-25 2.3.16.1 Print Screen Modifications.............. 2-25 2.3.16.2 Large Default Icon...................... 2-25 2.3.16.3 Queue Options Dialog Box................ 2-25 2.3.16.4 Changed Resource Values................. 2-25 vi 2.3.17 Session Manager and FileView ............. 2-26 2.3.17.1 Security Options........................ 2-26 2.3.17.2 Using the Color Customizer with Session Manager................................. 2-26 2.3.17.3 FileView DELETE Functionality-Changed ........................................ 2-27 2.3.17.4 FileView Icons.......................... 2-27 2.3.17.5 Input Focus Change When Starting Private Logo.................................... 2-27 2.3.17.6 Session Manager Process-Stopping........ 2-27 2.4 Public Profiles for Layered Products.......... 2-28 2.5 Toolkit Notes................................. 2-28 3 System Manager Release Notes 3.1 DECwindows Motif Login Screen-Known Color Problem....................................... 3-1 3.2 Define DECW$UTILS Global Symbol When Moving DECW$EXAMPLES Global Symbol................... 3-1 3.3 FileView Creates Detached Processes by Default....................................... 3-2 3.4 Logical Names................................. 3-3 3.5 Customized Login Logos........................ 3-4 3.6 Version Checking Command Files................ 3-5 3.7 Layered Product Fonts......................... 3-6 3.8 DECterm System Management Issues.............. 3-7 3.8.1 DECterm Logical Names..................... 3-7 3.8.2 Automatic Window Positioning.............. 3-8 3.8.3 Hold Screen Response Time................. 3-8 3.8.4 Nohangup and Virtual Terminal Support..... 3-8 4 Programmer Release Notes 4.1 Programming Release Notes Specific to DECwindows Motif Worldwide Support V1.2-3 for OpenVMS ...................................... 4-1 4.2 DECwindows Motif Worldwide Support V1.2-3 for OpenVMS Toolkit Versions...................... 4-2 4.3 Run-Time and Programming Environment.......... 4-3 4.4 OSF/Motif Toolkit Compatibility............... 4-4 4.4.1 _Xm Routines.............................. 4-4 4.4.2 OSF/Motif Release 1.2.3 and X11 R5 Shareable Libraries....................... 4-5 vii 4.4.3 OSF/Motif Release 1.1.3 Ada Bindings...... 4-8 4.5 OSF/Motif Release 1.1.3 Programming Support and XUI....................................... 4-8 4.6 Adding POSIX for OpenVMS Support to DECwindows Transports.................................... 4-11 4.6.1 POSIX fork() Routine ..................... 4-11 4.6.2 SYS$POSIX_FORK_CONTROL System Service..... 4-12 4.7 Translated Image Support...................... 4-13 4.8 Cross-Development Tools....................... 4-14 4.9 Compiling Applications Written in C........... 4-15 4.9.1 C Header Files............................ 4-16 4.10 Compiling Applications Written in Fortran..... 4-16 4.11 CDA Application............................... 4-17 4.11.1 CDA-Implementing Drag-and-Drop Functionality............................. 4-17 4.11.2 CDA Run-Time Services New Features........ 4-18 4.11.2.1 Version Number.......................... 4-18 4.11.2.2 Changes to the Programming Interface for CDA..................................... 4-18 4.11.2.3 Changes to External Reference Processing.............................. 4-19 4.11.2.4 New Message for Style Guide Fallback.... 4-20 4.11.2.5 Using Logical Names with CONVERT Commands................................ 4-20 4.11.2.6 Restructuring Shareable Images.......... 4-21 4.12 DECterm Programming........................... 4-22 4.12.1 Page Movement Escape Sequences............ 4-22 4.12.2 DECCRA Sequence........................... 4-23 4.12.3 DECLFKC Sequence.......................... 4-23 4.12.4 ReGiS Input Cursors....................... 4-23 4.13 DECwindows OSF/Motif Toolkit.................. 4-23 4.13.1 Compilation Error When Including Both CURSES.H and XMP.H Files.................. 4-24 4.13.2 Motif Text Widget Translations............ 4-24 4.13.3 Traversing a Motif Menu Bar with Keys..... 4-24 4.13.4 Upward Compatibility...................... 4-25 4.13.4.1 Restrictions on Mixing Motif and XUI Widgets................................. 4-25 4.13.5 DECwindows Motif Toolkit Functionality.... 4-26 4.14 OSF/Motif Example Programs.................... 4-26 4.14.1 Cutpaste Example Program.................. 4-26 4.14.2 DNDDemo Example Program................... 4-27 viii 4.14.3 Dogs Example Program...................... 4-28 4.14.3.1 Dog Widget.............................. 4-29 4.14.3.2 Square Widget........................... 4-29 4.14.4 Helloint Example Program.................. 4-30 4.14.5 Hellomotif Example Program................ 4-31 4.14.6 Motifanim Example Program................. 4-32 4.14.7 Motifgif and Pict Viewing Programs........ 4-32 4.14.8 Motifshell Example Program................ 4-33 4.14.9 Periodic Example Program.................. 4-33 4.14.10 Textedit Example Program.................. 4-34 4.14.10.1 Additional Translations................. 4-35 4.14.11 View Example Program...................... 4-37 4.14.12 Xmpiano Example Program................... 4-38 4.14.13 Motif Sample Programs..................... 4-40 4.14.14 Xmtravel Example Program.................. 4-41 4.14.15 Resource Files for Example Programs....... 4-41 4.14.16 UID Files for Example Programs............ 4-42 4.15 DECwindows Extensions to Motif................ 4-42 4.15.1 DXmCSText Input Method Support............ 4-43 4.15.2 Help Callback Routines.................... 4-43 4.15.3 SVN-Horizontal Live Scrolling Not Supported................................. 4-43 4.15.4 SVN Horizontal Separator Line............. 4-43 4.15.5 DXmFormSpaceButtonsEqually Restriction.... 4-43 4.16 Display Server Extensions..................... 4-43 4.16.1 Display PostScript (DPS) Server Extension-Color Cells..................... 4-44 4.16.2 X Image Extension......................... 4-44 4.16.3 Client Side Extension Library............. 4-45 4.16.4 Shared Memory Extension Support........... 4-45 4.16.4.1 How to Use Shared Memory Extension...... 4-46 4.16.4.2 Using Shared Memory XImages............. 4-47 4.16.4.3 Using Shared Memory Pixmaps............. 4-51 4.16.5 Using Extension Include Files............. 4-52 4.17 Xlib Issues................................... 4-52 4.17.1 DECW$XLIBSHR Problem with AST Handling.... 4-53 4.17.2 xlibint.h Is Now a Public Header File..... 4-53 4.17.3 Command Procedure Builds .PEN Files....... 4-53 4.17.4 Parameter/Protocol Datasize Mismatches.... 4-53 4.17.5 XSelectAsyncEvent and XSelectAsyncInput Routines ................................. 4-54 ix 4.17.6 Xlib Internationalization................. 4-55 4.17.6.1 Vendor Pluggable Layer.................. 4-55 4.17.6.2 Digital Internationalization Xlib Implementation.......................... 4-56 4.17.6.3 Locale in OpenVMS Systems............... 4-57 5 Documentation Release Notes 5.1 DEC CDA Base Services Documentation........... 5-1 5.2 DECwindows Motif Worldwide Support V1.2-3 for OpenVMS Documentation......................... 5-2 5.3 DECwindows Motif Documentation Corrections.... 5-4 5.3.1 Using DECwindows Motif for OpenVMS........ 5-4 5.3.1.1 Adding Target Screen Options to Application Menu Items ................. 5-4 5.3.1.2 Changing the Startup Environment........ 5-4 5.3.2 VMS DECwindows Guide to Xlib (Release 4) Programming: VAX Binding.................. 5-4 5.3.3 DECwindows Extensions to Motif............ 5-5 5.3.4 Overview of DECwindows Motif for OpenVMS Documentation............................. 5-5 5.4 OSF/Motif List of Known Problems.............. 5-5 6 Internationalization (I18N) Release Notes 6.1 New I18N Features............................. 6-1 6.1.1 X Window System Release 5................. 6-1 6.1.2 OSF/Motif Release 1.2.3 Toolkit........... 6-2 6.1.3 UIL Compiler Internationalization Features.................................. 6-2 6.1.3.1 How To Specify String Constants In UIL..................................... 6-2 6.1.3.2 Exceptions In String Constants.......... 6-3 6.1.4 Multiple codesets support for some language.................................. 6-3 6.1.5 Input Server Service Layer (IMSSL)........ 6-3 6.1.6 Selecting Input Style and Input Server.... 6-4 6.1.7 Supporting Input Styles................... 6-4 6.1.8 Simplified/Traditional Chinese Conversion................................ 6-4 6.1.9 New Features in DECterm................... 6-5 6.2 General Release Notes......................... 6-5 6.2.1 Locale.................................... 6-5 x 6.2.2 Examples.................................. 6-7 6.3 Known Problems and Restrictions............... 6-7 6.3.1 Menu Bar.................................. 6-7 6.3.2 Multiple Language Resource Files.......... 6-8 6.3.3 Input Server.............................. 6-8 6.3.4 User Defined Characters (UDC)............. 6-8 6.3.5 DECterm................................... 6-8 6.3.5.1 Downline Loadable Characters............ 6-8 6.3.5.2 DRCS Not Fully Supported................ 6-8 6.3.5.3 Two-byte Characters at the Last Column Ignored................................. 6-8 6.3.5.4 Calculation of Rows and Columns......... 6-9 6.3.5.5 Defining DECterm Title in Command Line.................................... 6-9 6.3.6 Cardfiler Quick Copy Problem.............. 6-9 6.3.7 Codeset Conversion Support in Cut-and-Paste............................. 6-9 6.3.8 CDA Viewer................................ 6-9 6.3.9 Bookreader................................ 6-9 6.3.9.1 Printing Restrictions................... 6-9 6.3.9.2 Copyright Statements in Printed Material................................ 6-10 6.3.9.3 Problems with Keyboard Equivalents...... 6-10 6.3.9.4 Font Size of Bookreader................. 6-11 6.3.10 Pre-Edit and Status Area Not Redrawn...... 6-11 6.3.11 Off-the-spot Needs Manual Resizing........ 6-11 6.3.12 Limitations when Running in Standard (English) OpenVMS......................... 6-11 6.4 Notes for Japanese and Asian Language Variants...................................... 6-12 6.4.1 Notes for Japanese Support................ 6-12 6.4.1.1 Supported Locale........................ 6-12 6.4.1.2 Input Server............................ 6-12 6.4.1.3 Ximp Support............................ 6-12 6.4.1.4 Japanese Keyboards...................... 6-13 6.4.1.5 Kana Input.............................. 6-13 6.4.1.6 Keyboard Indicator...................... 6-13 6.4.1.7 Conversion Candidate.................... 6-13 6.4.1.8 Known Problems.......................... 6-14 6.4.1.8.1 Toolkit................................ 6-14 6.4.1.8.2 Applications........................... 6-14 xi 6.4.2 Notes for Korean Support.................. 6-14 6.4.2.1 Supported Locale........................ 6-14 6.4.2.2 Input Server............................ 6-15 6.4.2.3 Known Problems.......................... 6-15 6.4.2.3.1 Applications........................... 6-15 6.4.2.3.2 Toolkit................................ 6-15 6.4.2.3.3 Bookreader............................. 6-15 6.4.3 Notes for Thai Support.................... 6-15 6.4.3.1 Supported Locales....................... 6-15 6.4.3.2 Thai Keyboards.......................... 6-16 6.4.3.3 Input Method............................ 6-16 6.4.3.4 Known Problems.......................... 6-16 6.4.3.4.1 Toolkit................................ 6-16 6.4.3.4.2 Applications........................... 6-16 6.4.4 Notes for Simplified Chinese Support...... 6-16 6.4.4.1 Supported Locale........................ 6-16 6.4.4.2 Input Server............................ 6-17 6.4.4.3 Font Alias for UDC...................... 6-17 6.4.4.4 Motif Window Manager.................... 6-17 6.4.4.5 Known Problems.......................... 6-17 6.4.4.5.1 Applications........................... 6-18 6.4.4.5.2 Toolkit................................ 6-18 6.4.5 Notes for Traditional Chinese Support..... 6-19 6.4.5.1 Supported Locales....................... 6-19 6.4.5.2 Input Server............................ 6-19 6.4.5.3 Font Alias for UDC...................... 6-19 6.4.5.4 Motif Window Manager.................... 6-19 6.4.5.5 UDC Font Converter...................... 6-20 6.4.5.6 Known Problems.......................... 6-20 6.4.5.6.1 Applications........................... 6-20 6.4.5.6.2 Toolkit................................ 6-21 6.5 Notes for European Language Variants.......... 6-21 6.5.1 Multiple Language Variant Installations... 6-21 6.5.2 Invoking and Running DECwindows Motif V1.2-3 for OpenVMS Language Variants...... 6-22 6.5.3 Software Release Notes.................... 6-23 6.5.3.1 General Software Release Notes.......... 6-23 6.5.3.1.1 Mnemonics.............................. 6-23 6.5.3.1.2 File Selection Dialog Boxes............ 6-23 6.5.3.1.3 Sorting 8-Bit Characters............... 6-23 6.5.3.1.4 Operating System Error Messages........ 6-23 6.5.3.1.5 Saveset Names.......................... 6-24 6.5.3.1.6 Language Variant Interdependencies..... 6-24 xii 6.5.3.1.7 Motif Default Language................. 6-24 6.5.3.1.8 Motif Window Manager Default Language............................... 6-25 6.5.3.1.9 Private Resource Files................. 6-25 6.5.3.2 Session Manager......................... 6-25 6.5.3.2.1 Session Manager Language............... 6-26 6.5.3.2.2 Session Manager Customization.......... 6-26 6.5.3.2.3 FileView/Session Manager............... 6-26 6.5.3.2.4 Void Applications Menu................. 6-27 6.5.3.3 Bookreader.............................. 6-27 6.5.3.3.1 Bookreader Default Bookshelf........... 6-28 6.5.3.3.2 Navigation Window View Menu............ 6-28 6.5.3.3.3 Printing Restrictions.................. 6-28 6.5.3.4 Color Widget............................ 6-28 6.5.3.5 DECwindows Mail......................... 6-29 6.5.3.5.1 Pick-Month-Day-Year.................... 6-29 6.5.3.5.2 Mail Default Folder and Drawer......... 6-29 6.5.3.6 Clock................................... 6-29 6.5.3.7 DECterm................................. 6-29 6.5.3.7.1 Private Resource File in Multiple Language Systems....................... 6-29 6.5.3.7.2 Downline Loadable Characters........... 6-30 6.5.3.7.3 DECterm Print Default.................. 6-30 6.5.3.8 Window Manager and Control/Compose Sequence (Russian LV only).............. 6-30 6.5.3.9 Icon Box................................ 6-30 6.5.3.10 Notepad................................. 6-31 6.5.3.10.1 Obsolete Private Resource File......... 6-31 6.5.3.11 Paint................................... 6-32 6.5.3.11.1 Cannot open a new file................. 6-32 6.5.3.12 Terminal Display Density................ 6-32 6.5.3.13 ISO Latin Characters.................... 6-33 6.5.3.14 Using [GROUP SHIFT] on Latin2 Specific LK-401 Keyboards........................ 6-33 6.5.3.15 Drag & Drop Restriction................. 6-35 6.5.4 Documentation Release Notes............... 6-35 6.5.4.1 Getting Started with DECwindows Motif OpenVMS User Interface V1.2-3........... 6-35 6.5.4.1.1 Tutorial............................... 6-35 6.5.4.1.2 Sizing Windows......................... 6-35 6.5.4.1.3 Selecting and Moving Text.............. 6-35 xiii 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 ANSI C Compliance......................... A-3 A.3.3 Display and Screen Specific Data.......... A-3 A.3.4 Drag and Drop............................. A-4 A.3.5 Tear-Off Menus............................ A-4 A.3.6 Insensitive Visuals....................... A-5 A.3.7 Other Visual Changes...................... A-5 A.3.8 Titles for Frames......................... A-6 A.3.9 Audible Warning........................... A-6 A.3.10 Color Enhancements........................ A-6 A.3.11 Baseline Alignment........................ A-6 A.3.12 Expanded Traversal Set.................... A-6 A.3.13 Two-Dimensional Menu Traversal............ A-7 A.3.14 Input Focus............................... A-7 A.3.15 Traversal Access Functions................ A-7 A.3.16 Virtual Keys.............................. A-7 A.3.17 Resource Management....................... A-9 A.3.18 Changes for CUA and Windows Compliance.... A-9 A.4 Changes and Enhancements to Specific Widgets....................................... A-9 A.4.1 XmClipboard............................... A-9 A.4.2 XmCommand................................. A-10 A.4.3 XmList.................................... A-10 A.4.4 XmMessageBox.............................. A-11 A.4.5 XmRowColumn and Menus..................... A-11 A.4.6 XmScrollBar............................... A-12 A.4.7 XmScrolledWindow.......................... A-12 A.4.8 XmSelectionBox, XmFileSelectionBox........ A-12 A.4.9 XmText.................................... A-12 A.4.10 XmTextField............................... A-13 A.4.11 XmToggleButton, XmToggleButtonGadget...... A-14 A.5 Motif Window Manager Enhancements............. A-14 A.5.1 Changes to MWM............................ A-14 A.5.2 New and Enhanced MWM Resources............ A-15 A.5.3 New and Enhanced MWM Functions............ A-15 A.5.4 New MWM Action............................ A-16 xiv A.6 Changes to the User Interface Language........ A-17 Index Tables 1-1 Moving the Digital Logo and Changing Login Screen Colors ............................ 1-3 1-2 Changing Position of the Start Session and Set Password Dialog Boxes................. 1-4 1-3 Window Dump to Print File Options......... 1-21 3-1 SYS$MANAGER Global Symbols................ 3-4 3-2 Logical Names Supported by DECterm........ 3-7 4-1 Names of Shareable Libraries Based on R5........................................ 4-6 4-2 Names of Shareable Libraries Based on OSF/Motif Release 1.2.3................... 4-7 4-3 Directories for Previous XUI or Motif Programming Environment................... 4-9 4-4 Drag-and-Drop Widgets..................... 4-17 4-5 New Header File Names..................... 4-19 4-6 Names of Shareable Images................. 4-21 4-7 View Menu Options......................... 4-34 4-8 Textedit Source Files..................... 4-34 4-9 Motif Sample Programs..................... 4-40 4-10 Routine Names and Arguments Sent as 16-Bit Values.................................... 4-53 5-1 DECwindows Motif Worldwide Support 1.2-3 for OpenVMS Documentation................. 5-2 6-1 Language Variant Dependency............... 6-22 6-2 Installation names........................ 6-24 6-3 Parameter Values.......................... 6-25 6-4 LNE1 keyboards............................ 6-33 6-5 Using [GROUP SHIFT]....................... 6-34 xv _________________________________________________________________ Preface DECwindows Motif Worldwide Support V1.2-3 for OpenVMS is the software required to install the DECwindows Motif V1.2- 3 for OpenVMS Czech, Hungarian, Japanese, Korean, Polish, Russian, Slovak, Thai, Simplified Chinese and Traditional Chinese language variants. It incorporates OSF/Motif Version 1.2.3 and is based on Release 5 of the X Window System Intrinsics. As with DECwindows Motif Version 1.2, this product continues to support the XUI user interface and toolkit (run-time support only). In this manual, DECwindows XUI (X User Interface) refers to the DECwindows product prior to DECwindows Motif Version 1.0. These release notes describe software problems, corrections, and restrictions as well as documentation changes that pertain specifically to the DECwindows Motif Worldwide Support V1.2-3 for OpenVMS software and the DECwindows Motif V1.2-3 for OpenVMS language variants. They also describe software problems, corrections, restrictions, and documentation changes from DECwindows Motif Version 1.1 and 1.0 that have not been updated in the existing documentation for those products. Margin notes indicate the DECwindows Motif versions that apply to each release note. Intended Audience This manual contains the following information: o Chapter 1 describes the new features introduced with DECwindows Motif Worldwide Support V1.2-3 for OpenVMS. o Chapter 2 contains general user release notes for all users. xi 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 the contents of the documentation set that can be used with the DECwindows Motif Worldwide Support V1.2-3 for OpenVMS software. Additions and corrections to the documentation set are included in this chapter. o Chapter 6 describes the internationalization support provided by this kit. The internationalized features are based on the OSF/Motif Release 1.2.3 toolkit and X Window System Release 5. They enable software developers to develop internationalized software on the OpenVMS platform. o Appendix A contains the release notes for OSF/Motif Release 1.2. Conventions In this manual, every use of OpenVMS Alpha means the OpenVMS Alpha operating system, every use of OpenVMS VAX means the OpenVMS VAX operating system, and every use of OpenVMS means both the OpenVMS Alpha operating system and the OpenVMS VAX operating system. In this manual, every use of OpenVMS Alpha means the OpenVMS Alpha operating system. In this manual, every use of DECwindows and DECwindows Motif refers to DECwindows Motif for OpenVMS software. The following conventions are used to identify information specific to OpenVMS Alpha or to OpenVMS VAX: 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. xii PF1 x A sequence such as PF1 x indicates that you must first press and release the key labeled PF1 and then press and release another key or a pointing device button. GOLD x A sequence such as GOLD x indicates that you must first press and release the key defined as GOLD and then press and release another key. GOLD key sequences can also have a slash (/), dash (-), or underscore (_) as a delimiter in EVE commands. The GOLD key definition is often mapped to the PF1 key on the keypad. 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.) . . . 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, if you choose more than one option, you must enclose the choices in parentheses. xiii [ ] 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, braces surround a required choice of options; you must choose one of the options listed. boldface text Boldface text represents the introduction of a new term or the name of an argument, an attribute, or a reason (user action that triggers a callback). Boldface text is also used to show user input in Bookreader versions of the manual. 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 device- name contains up to five alphanumeric characters). UPPERCASE TEXT Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege. struct Monospace type in text identifies the following C programming language elements: keywords, the names of independently compiled external functions and files, syntax summaries, and references to variables or identifiers introduced in an example. xiv - A hyphen in code examples indicates that additional arguments to the request are provided on the line that follows. numbers All numbers in text are assumed to be decimal unless otherwise noted. Nondecimal radixes-binary, octal, or hexadecimal-are explicitly indicated. mouse The term mouse refers to any pointing device, such as a mouse, a puck, or a stylus. MB1, MB2, MB3 MB1 indicates the left mouse button, MB2 indicates the middle mouse button, and MB3 indicates the right mouse button. (The user can redefine the buttons.) PB1, PB2, PB3, PB1, PB2, PB3, and PB4 indicate buttons on PB4 the puck. SB1, SB2, SB3 SB1, SB2, and SB3 indicate buttons on the stylus. xv 1 _________________________________________________________________ DECwindows Motif New Features This chapter describes the following new features introduced with DECwindows Motif Worldwide Support V1.2-3 for OpenVMS: o Drag-and-drop functionality o Tear-off menus o Customizing the LOGIN screen o Support for additional European languages o Color customizer example program o Bookreader-new feature o CDA-new pack and unpack applications o DECterm-new features o Window Dump to Print File Utility o Keyboard Enhancements for Disabled Users 1.1 Drag-and-Drop Functionality and Tear-Off Menus V1.2- The following user features are available in DECwindows 3 Motif Worldwide Support V1.2-3 for OpenVMS applications: o Drag-and-drop functionality All of the DECwindows Motif Worldwide Support V1.2-3 for OpenVMS applications support the drag-and-drop feature, except DECwindows Mail and Notepad. o Tear-off menus The following applications do not support tear-off menus: - CDA Viewer 1-1 DECwindows Motif New Features 1.1 Drag-and-Drop Functionality and Tear-Off Menus - LinkWorks Manager - DECwindows Mail - Notepad - Print Screen 1.1.1 Using Drag-and-Drop Functionality V1.2- The drag-and-drop feature lets you move or copy screen 3 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. 1.1.2 Using Tear-off Menus V1.2- The DECwindows Motif applications allow you to tear off 3 pull-down and pop-up menus. Tear-off menus let you keep frequently used menus displayed without repeatedly pulling them down or popping them up. To tear off a menu: 1. Display a pull-down or pop-up menu. If the menu is a tear-off menu, a dotted line appears at the top of the menu. 2. Click on the dotted line with MB1. The menu remains active until you close it 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. 1-2 DECwindows Motif New Features 1.2 Customizing the Login Screen 1.2 Customizing the Login Screen V1.2- Several new resources have been created for the 3 purpose of customizing the login screen. To customize the login screen, create in SYS$MANAGER a file named DECW$LOGIN.DAT that contains your resource definitions. The custom resource definitions from SYS$MANAGER:DECW$LOGIN.DAT are merged together with the resource definitions supplied by Digital (in the file SYS$COMMON:[DECW$DEFAULTS.SYSTEM]DECW$LOGIN.DAT) to form the new login screen. Custom versions of the DECW$LOGIN.DAT resource file should reside in SYS$MANAGER and NOT in DECW$SYSTEM_DEFAULTS. This prevents your custom file from being overwritten when upgraded to a newer version of DECwindows Motif. It also prevents the custom file from superseding the file supplied by Digital. 1.2.1 Customizing the Digital Logo and Login Screen Colors V1.2- You can define the resources in Table 1-1 to control the 3 position and colors of the Digital logo and the color of the screen background in the Start Session screen. Table 1-1 Moving the Digital Logo and Changing Login Screen __________Colors___________________________________________ Resource__________Description______________________________ rootColor Color of the screen background. logoColor Color of the Digital logo (default is burgundy). logoX x position of the Digital logo (default is 0). logoY y position of the Digital logo (default is 75). (continued on next page) 1-3 DECwindows Motif New Features 1.2 Customizing the Login Screen Table 1-1 (Cont.) Moving the Digital Logo and Changing __________________Login_Screen_Colors______________________ Resource__________Description______________________________ centerLogoX Boolean; if true (default), the Digital logo is centered horizontally on the __________________screen.__________________________________ For example, to position the Digital logo at x=100, y=600, add the following resource definitions to the SYS$MANAGER:DECW$LOGIN.DAT file: decw$login.logoX: 100 decw$login.logoY: 600 decw$login.centerLogoX: false 1.2.2 Changing Position of the Start Session and Set Password Dialog Boxes V1.2- You can define the resources in Table 1-2 to control the 3 position of the Start Session and Set Password dialog boxes. Table 1-2 Changing Position of the Start Session and Set __________Password_Dialog_Boxes____________________________ Resource______________Description__________________________ centerStartSessionX Boolean; if true (default), the Start Session dialog box is centered horizontally. centerStartSessionY Boolean; if true (default), the Start Session dialog box is centered vertically. centerSetPasswordX Boolean; if true (default), the Set Password dialog box for expired passwords is centered horizontally. centerSetPasswordY Boolean; if true (default), the Set Password dialog box is centered ______________________vertically.__________________________ 1-4 DECwindows Motif New Features 1.2 Customizing the Login Screen For example, to position the Start Session dialog box at x=100, y=600, add the following resource definitions to the SYS$MANAGER:DECW$LOGIN.DAT file: decw$login.centerStartSessionX: false decw$login.centerStartSessionY: false decw$login.HiddenShell.x: 100 decw$login.HiddenShell.y: 600 To position the Set Password dialog box at x=30, y=100, add the following resource definitions to the SYS$MANAGER:DECW$LOGIN.DAT file: decw$login.centerSetPasswordX: false decw$login.centerSetPasswordY: false decw$login.SetPasswordShell.x: 30 decw$login.SetPasswordShell.y: 100 1.2.3 Disabling a Node Name Display in the Start Session Dialog Box V1.2- To prevent a node name from being displayed in the Start 3 Session dialog box, add the following resource definition to the SYS$MANAGER:DECW$LOGIN.DAT file: decw$login.displayNodeName: false 1.3 Color Customizer Example Program V1.2- The color customizer example program allows you to 3 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. 1.3.1 Supported Displays V1.2- The color customizer supports any display using pseudocolor 3 or grayscale visuals. This includes most 4- and 8-plane workstation displays. 1-5 DECwindows Motif New Features 1.3 Color Customizer Example Program 1.3.2 Supported Applications V1.2- The color customizer can affect the colors of any 3 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. ______________________________________________________ 1.3.3 Building the Color Customizer on OpenVMS Systems V1.2- To build the color customizer on OpenVMS systems, perform 3 the following steps: 1. Copy the files to a private directory. For example: $ SET DEFAULT SYS$LOGIN $ CREATE/DIRECTORY [.CUSTOMIZER] $ SET DEFAULT [.CUSTOMIZER] $ 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 1-6 DECwindows Motif New Features 1.3 Color Customizer Example Program 1.3.4 Running the Color Customizer V1.2- To run the color customizer, perform the following steps: 3 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. ______________________________________________________ 1.3.5 Modifying the DECW$LOGIN.COM File V1.2- As noted in Section 1.3.4, the color customizer should be 3 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. 1-7 DECwindows Motif New Features 1.3 Color Customizer Example Program 1.3.6 Command Interface Summary V1.2- A box containing a list of available palettes is in the 3 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. 1-8 DECwindows Motif New Features 1.3 Color Customizer Example Program 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. 1.3.7 Changing the Mapping Between Color Resources and Color Cells V1.2- The file DXMDEFAULTS.DAT allows you to control how many 3 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 1-9 DECwindows Motif New Features 1.3 Color Customizer Example Program purposes of automatic shadowing. If a color value named "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. ______________________________________________________ 1-10 DECwindows Motif New Features 1.3 Color Customizer Example Program 1.3.8 DECterm Windows Not Affected V1.2- The color customizer does not affect the colors of 3 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. 1.3.9 Changing the Default Value of the Automatic Shadowing Toggle Button V1.2- The default value of the automatic shadowing toggle 3 button is set using the Custom.autoShadow resource in the CUSTOM.DAT file as follows: Custom.autoShadowing: False The default value is True. 1.3.10 Using the Customizer on Multihead Systems V1.2- The color customizer affects only applications started on 3 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. 1-11 DECwindows Motif New Features 1.3 Color Customizer Example Program 1.3.11 Using the XSETROOT_CUST.EXE Demonstration Program V1.2- The XSETROOT_CUST.EXE demonstration program, created during 3 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 1.4 Bookreader-New Feature V1.2- The Bookreader application allows draft-quality printing of 3 books or topics. To print a book, perform the following steps: 1. Select a book from the Bookreader:Library window. 2. Click on the Print Book... option from the File menu in the Bookreader:Library window. 3. Use the Print dialog box to specify print format options and the name of the printer. 1.5 CDA New Applications This section contains new CDA applications introduced with the DECwindows Motif Worldwide Support V1.2-3 for OpenVMS software. 1.5.1 Pack and Unpack Applications V1.2- CDA Run-Time Services includes two standalone applications 3 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 was packaged by the CDA Pack application and creates a copy of the original document file and all its externally referenced files. 1-12 DECwindows Motif New Features 1.5 CDA New Applications 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. 1.5.1.1 Pack Application V1.2- The CDA Pack application creates a single output file that 3 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 finishes. If you specify /NOSKIP_MISSING, the 1-13 DECwindows Motif New Features 1.5 CDA New Applications 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. /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 could be 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 1.5.1.2 Unpack Application V1.2- The CDA Unpack application unpacks an input file created 3 by the Pack application. The output files are the .DDIF or .DTIF file that was 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 all the files created 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 was created by the Pack application. Qualifier: 1-14 DECwindows Motif New Features 1.5 CDA New Applications /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. 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. 1.5.1.3 Pack and Unpack Error Messages V1.2- This section describes new messages associated with the CDA 3 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. 1-15 DECwindows Motif New Features 1.5 CDA New Applications NOOUTFIL, No output file was created. Severity: Warning Explanation: The Pack application could not find any external references in the .DDIF or .DTIF document to be packed, and you did not specify the /ALWAYS_ENCODE qualifier. OUTFILE, Output file created: file-name Severity: Warning Source: CDA_UNPACK Explanation: The Unpack application created the specified file while unpacking a file created by the Pack application. 1.6 DECterm V1.2- This section describes the new DECterm features that are 3 introduced with DECwindows Motif Worldwide Support V1.2-3 for OpenVMS. 1.6.1 User Font Selection V1.2- DECterm now allows available fonts to be selected from the 3 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. 1-16 DECwindows Motif New Features 1.6 DECterm 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 DEC 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, may not result in an optimal display or otherwise perform as expected. ______________________________________________________ On OpenVMS VAX and OpenVMS Alpha systems, Version 6.1 or higher, two additional fonts are available: the VT330 font and the VT font. The VT330 font is based on the 10x20 font used in the VT330 and VT340 terminals. The VT font is a new 9x18 font derived from the VT330 font. Use these fonts on a system where they are available by entering the following font name strings in the font name text field: -DEC-VT330-*-*-*--20-*-*-*-c-*-*-* -DEC-VT-*-*-*--18-*-*-*-c-*-*-* 1.6.2 Local Echo V1.2- DECterm now supports a local echo mode. In the 3 Options/General dialog box, select Local Echo. This 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. 1.6.3 Answerback Message V1.2- A user interface is now available to enter answerback 3 messages. This answerback message field is for compatibility with Digital terminals. 1-17 DECwindows Motif New Features 1.6 DECterm The answerback field is a buffer that contains up to thirty characters. The answerback field in earlier Digital 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 #0D is entered in the answerback field, DECterm responds with a carriage return. If two consecutive number sign characters are entered (##), a single number sign is transmitted. 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. 1.6.4 Seven-Bit Printer Support V1.2- When the 7-Bit Printer button is selected in the 3 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. 1-18 DECwindows Motif New Features 1.6 DECterm 1.6.5 New Escape Sequences V1.2- The following escape sequences are now supported by 3 DECterm: o All page movement sequences (NP, PP, PPA, PPB, and PPR). o One rectangular area operation sequence (DECCRA). o The DECLFKC sequence. o The ReGIS command S(C(In)) now supports the rubber-band rectangle cursor and the diamond cursor. See Chapter 4 for details and restrictions on the use of these sequences. 1.7 Window Dump to Print File (xpr) Utility V1.2- The Window Dump to Print File utility prints an X Window 3 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 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. Use the following command format: $ xpr input_file [options...] 1-19 DECwindows Motif New Features 1.7 Window Dump to Print File (xpr) Utility 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 1-3 defines the available options. 1-20 DECwindows Motif New Features 1.7 Window Dump to Print File (xpr) Utility Table_1-3_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) 1-21 DECwindows Motif New Features 1.7 Window Dump to Print File (xpr) Utility Table_1-3_(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) 1-22 DECwindows Motif New Features 1.7 Window Dump to Print File (xpr) Utility Table_1-3_(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 tobe 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) 1-23 DECwindows Motif New Features 1.7 Window Dump to Print File (xpr) Utility Table_1-3_(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" 1-24 DECwindows Motif New Features 1.7 Window Dump to Print File (xpr) Utility 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: 1-25 DECwindows Motif New Features 1.7 Window Dump to Print File (xpr) Utility 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. 1-26 DECwindows Motif New Features 1.8 Keyboard Enhancements for Disabled Users 1.8 Keyboard Enhancements for Disabled Users The AccessX extension provides features to help disabled users interact with workstations running DECwindows Motif V1.2-3 for OpenVMS Alpha. V1.2- These features make it easier to use the keyboard and 3 mouse. You can interact with workstations by entering commands and manipulating menus and dialog boxes. However, with AccessX features, performing these input operations is 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. 1.8.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. 1.8.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. 1-27 DECwindows Motif New Features 1.8 Keyboard Enhancements for Disabled Users 1.8.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. 1.8.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. 1.8.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. 1.8.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. 1.8.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.<> 1-28 2 _________________________________________________________________ General User Release Notes This chapter contains information about DECwindows Motif for general users. 2.1 Notes Specific to DECwindows Motif Worldwide Support V1.2-3 for OpenVMS The release notes in this chapter are cumulative from VMS DECwindows Motif Version 1.0 and still apply to Worldwide Support 1.2-3. The following sections contain general user release notes that pertain specifically to DECwindows Motif Worldwide Support V1.2-3 for OpenVMS: o Section 2.3.1, Bookreader o Section 2.3.2, Calendar o Section 2.3.4.1, CDA Dynamic Font Support o Section 2.3.4.2, CDA WRITE$FONTS Logical Name o Section 2.3.4.3, CDA Documents o Section 2.3.4.4, CDA PostScript Documents o Section 2.3.5.1, Display PostScript with the CDA Viewer o Section 2.3.5.2, New Message for CDA Viewer o Section 2.3.5.3, CDA Paper Size Button Renamed o Section 2.3.5.4, CDA Watch Progress Restriction o Section 2.3.6, Clock-DECsound Capability o Section 2.3.10.1, LinkWorks Manager Application Renamed to DEClinks o Section 2.3.10.2, LinkWorks Manager (DEClinks) Application Retired o Section 2.3.11.1, Using the Color Customizer with DECwindows Mail 2-1 General User Release Notes 2.1 Notes Specific to DECwindows Motif Worldwide Support V1.2-3 for OpenVMS o Section 2.3.11.2, Multiple Tabs in Long Text Lines o Section 2.3.11.3, DECwindows Mail Ends Without Print Queues o Section 2.3.11.4, DECwindows Mail Is Linked with the OSF/Motif Release 1.1.3 Toolkit o Section 2.3.12.1, Using the Color Customizer with DECwindows Motif Window Manager o Section 2.3.13.10, Invoking Motif Window Manager Help o Section 2.3.14.1, Notepad Is Linked with the OSF/Motif Release 1.1.3 Toolkit o Section 2.3.14.2, Options/Split View o Section 2.3.16.1, Print Screen Modifications o Section 2.3.17.1, Security Options o Section 2.3.17.2, Using the Color Customizer with Session Manager o Section 2.5, Toolkit Notes 2.2 Access Control Not Explicitly Enabled by Default 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. 2-2 General User Release Notes 2.3 DECwindows Motif Application Notes 2.3 DECwindows Motif Application Notes This section contains information about DECwindows Motif applications. 2.3.1 Bookreader V1.2- The following problem exists with the Bookreader 3 application: when tearing off a pop-up menu from the Bookreader library window, Bookreader ends abruptly due to an access violation. The pop-up menu (selected by using MB3) works if the user does not attempt to tear it off. 2.3.2 Calendar V1.2- The following are known problems with the Calendar 3 application: o When initially running the Calendar application after installing DECwindows Motif Worldwide Support V1.2-3 for OpenVMS, Calendar displays a message dialog box stating that the Calendar database file needs to be upgraded to the new format. If the Motif Window Manager is listed before Calendar in the Session Manager Automatic Startup list, then the message dialog box will be small and unreadable. As a possible solution, move Calendar before the Motif Window Manager in the Automatic Startup list. o Calendar incorrectly issues an error message when LinkWorks Services (DEClinks) are turned off. (See Section 2.3.10 for more information about DEClinks.) o Calendar does not remove Link highlighting when Links are made inactive. o If the Window Manager buttons are customized so that an action is taken when the pointer is in the window and you press MB1, double clicking on the Month display is disabled. 2-3 General User Release Notes 2.3 DECwindows Motif Application Notes 2.3.3 Cardfiler V1.0 You cannot modify or save DECwindows Motif card files from a DECwindows X User Interface (XUI) version of the Cardfiler. The card file format of the Cardfiler contains additional information used for creating hyperinformation (LinkWorks) connections. This information is lost if a DECwindows Motif version of the card file is read and saved using the XUI version of Cardfiler. All LinkWorks connections that are made to that card file might be lost or unpredictable. However, the DECwindows XUI version of Cardfiler can be used to read DECwindows Motif card files. Information in the old card file format is compatible with the DECwindows Motif Version 1.0 Cardfiler. DECwindows XUI card files are changed to Motif format when they are read in and saved using the DECwindows Motif Cardfiler. 2.3.4 CDA Run-Time Services V1.2- This section describes new features contained in the CDA 3 Run-time Services component: o New Pack and Unpack applications are provided. See Section 1.5 for a full description. o Performance enhancements have been made in viewing CDA and PostScript documents. o Dynamic font support is implemented. Future upgrades to installed fonts are usable by the CDA Viewer and the PostScript back end. o The DECwindows CDA Viewer now supports DECfonts Version 1.2. o CDA support has been improved for documents created by DECwrite that contain links to other documents. You can find additional information about CDA in the following manuals: o Digital CDA Base Services Reference Manual Provides reference material for using the CDA data structures and access routines to create compound document applications, converters, and viewers. o Technical Overview of the Digital CDA Base Services 2-4 General User Release Notes 2.3 DECwindows Motif Application Notes Provides an introduction to CDA, compound document processing concepts, and using the DEC CDA Base Services. 2.3.4.1 CDA Dynamic Font Support V1.2- As well as supporting a static-table for the fonts 3 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 and the PostScript back-end converter 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 or the PostScript back-end converter 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. For further information on the Font utility, see the following documents: 2-5 General User Release Notes 2.3 DECwindows Motif Application Notes o DECwrite Installation Guide for VMS Systems o DECpresent Installation Guide for VMS Systems o DECfonts Typeface Collection and User's Guide for OpenVMS 2.3.4.2 CDA WRITE$FONTS Logical Name V1.2- The default location for the WRITE$FONTS.INI file is 3 SYS$LIBRARY, but, if the logical name WRITE$FONTS is defined, the CDA Viewer or the PostScript back end 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.3.4.3 CDA Documents V1.2- The current version of CDA Run-Time Services includes 3 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. If the problem persists, please submit a Software Performance Report along with a copy of the document (and any associated documents). The new CDA Pack application 2-6 General User Release Notes 2.3 DECwindows Motif Application Notes (see Section 1.5.1) allows you to create a single file that includes a .DDIF or .DTIF document and its associated files. 2.3.4.4 CDA PostScript Documents V1.2- The PostScript viewing feature of the CDA Viewer no longer 3 reads the entire PostScript document before displaying the first page. Instead, it processes one page at a time. In the case of large documents, this significantly reduces the time needed to display the first page. Note that since the PostScript file is no longer read in all at once, the total number of pages in the PostScript document is not known until the last page is read. Therefore, the current page indicator does not show the number of pages in the document until the entire PostScript document has been read by the CDA Viewer. 2.3.5 CDA-Hints, Restrictions, and Known Problems This section contains helpful hints, known restrictions, and known problems with the CDA Viewer. 2.3.5.1 Display PostScript with the CDA Viewer V1.2- The previous version of the CDA Viewer had a compatibility 3 problem with the previous version of the DECwindows Display PostScript extensions. This problem sometimes caused parts of the data displayed on a page to be rotated, shifted, or incorrectly scaled- sometimes to an extent that the data was no longer visible on the screen. The first page of some documents appeared blank but became visible after displaying the second page. The problem is fixed in the latest version of the CDA Viewer; however, if a previous version of the CDA Viewer is run on one system (the client) with display set to another system (the server), and the server has the new Display PostScript engine, then the problem still exists. The solution is to upgrade the version of CDA on the client system. 2-7 General User Release Notes 2.3 DECwindows Motif Application Notes 2.3.5.2 New Message for CDA Viewer V1.2- The CDA Viewer issues the following new message if it is 3 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. User Action: This error is usually caused by insufficient memory. Reduce the system load and start the application again. 2.3.5.3 CDA Paper Size Button Renamed V1.2- In the CDA Viewer, the name of the Paper Size button in 3 the Open dialog box has been changed to Display Options. However, the function invoked by the button has not changed. 2.3.5.4 CDA Watch Progress Restriction V1.2- If you are using the CDA Viewer to view a PostScript 3 document, and you have the Watch Progress feature enabled, manipulating CDA Viewer buttons (other than the Cancel button) or scroll bars while the wait cursor is active can cause corruption of the display. 2.3.5.5 CDA Viewer Supports DECfonts Version 1.2 V1.1 For DECwindows Motif Version 1.1, the CDA Viewer supports DECfonts Version 1.2. The Linotext fonts were renamed following DECfonts Version 1.1 and before Version 1.2. If a .DDIF file contains DECfonts Version 1.1 Linotext text, the CDA Viewer does not find it and defaults to Courier 12 point for this text. To correct this problem, modify the font using DECwrite or DECpresent in conjunction with DECfonts Version 1.2. 2-8 General User Release Notes 2.3 DECwindows Motif Application Notes 2.3.5.6 CDA Viewer-Viewing PostScript Files with Errors V1.0 If you use the CDA Viewer to view a PostScript file that contains syntax errors, the CDA Viewer can stop processing without displaying an error message until you click on the Cancel button. This problem also occurs if you specify a .PS formatted file other than PostScript to the viewer. This problem can occur in the CDA Viewer application or in any application that uses the callable CDA Viewer interface in DDIF$VIEWSHR. Specify only valid PostScript files to the CDA Viewer when specifying the .PS format. 2.3.6 Clock-DECsound Capability V1.2- The Clock application includes an alarm feature that 3 can be used if your system has sound capabilities. 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.3.7 DECsound This section contains information about DECsound. 2.3.7.1 DECsound Prerequisites V1.1 The prerequisites for using DECsound with the DECwindows Motif product are as follows: o DEC 3000 Alpha Model 400 computer with either a phone handset or phone headset. o DEC 3000 Alpha Model 500 computer with either a phone handset or phone headset as audio devices. This computer also has a separate microphone and speaker connection. o VAXstation 4000 Model VLC computer with either a phone handset or phone headset. o VAXstation 4000 Model 60 computer with either a phone handset or phone headset. 2-9 General User Release Notes 2.3 DECwindows Motif Application Notes o VAXstation 4000 Model 90 computer with either a phone handset or phone headset. 2.3.7.2 DECsound Problems V1.1 The following are known problems with DECsound: o Links to audio files created using DECwrite Version 2.0 and DECpresent Version 1.0 cannot be played back using the CDA Viewer because these applications currently store links to audio files as private data that cannot be accessed by other CDA applications. To correct this problem, use DECwrite or DECpresent to view documents with links to audio recordings. o The Record operation does not work when you select part of the waveform. To correct this problem, do not select any part of the waveform before you click on the Record button. 2.3.8 DECterm This section contains information about known restrictions and problems with the DECterm application. 2.3.8.1 VT330 and VT340 Terminal Emulation V1.0 As described in the DECwindows Motif Software Product Description (SPD), 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. o The checkerboard character (character 97 in the DEC 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 8 planes or less. On servers with more than 8 planes, DECterm uses overlay mode, because replace mode does not work on those servers. 2-10 General User Release Notes 2.3 DECwindows Motif Application Notes 2.3.8.2 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, creation of the DECterm succeeds, but creation of the process inside the DECterm fails. In this case, the DCL command CREATE/TERMINAL command returns the following error message: Duplicate process name 2.3.8.3 Printing to an Attached Printer V1.1 To print to a port device, you need 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, the following command must be entered from a privileged account or included in the system startup file: $ SET PROTECTION=WORLD:RW TTA3:/DEVICE 2-11 General User Release Notes 2.3 DECwindows Motif Application Notes 2.3.8.4 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 4 colors on a 4-plane or monochrome system and 16 colors on color systems with more than 4 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 Any dialog boxes created while DECterm is using a private colormap appear black. To prevent this problem, create the dialog boxes (that is, invoke them for the first time) when DECterm is using the default colormap. 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-12 General User Release Notes 2.3 DECwindows Motif Application Notes 2.3.8.5 DECterm Initialization V1.1 To ensure that your DECterm windows do not shrink unexpectedly to the default size of 80 characters by 24 lines, systemwide and user login command procedures (SYLOGIN.COM and LOGIN.COM) should not execute the SET TERMINAL/INQUIRE command procedure on DECterm windows. Executing the SET TERMINAL/INQUIRE command on mailbox devices that are created from the Session Manager also prevents the Session Manager from starting applications such as DECterm. You do not have to use the SET TERMINAL/INQUIRE command because the DECterm controller provides OpenVMS systems with the proper characteristics and size of DECterm windows. To make login procedures work correctly on DECterm windows and in other environments such as on terminals, use the following commands in a systemwide or user login command procedure: $ ! $ ! SYS$MANAGER:SYLOGIN.COM and users' LOGIN.COM might contain the $ ! following command line: $ ! $ IF (F$MODE() .EQS. "INTERACTIVE") THEN SET TERMINAL/INQUIRE $ ! To avoid resizing of a terminal window on a workstation, you $ ! can substitute the following command sequence: $ ! $ IF f$getdvi( "sys$output:", "trm" ) $ THEN $ devnam = f$getdvi( "sys$output:", "devnam" ) - "_" - "_" $ devnam = f$extract(0, 2, devnam) $ if devnam .eqs. "WT" then goto skip_inquire $ if devnam .eqs. "TW" then goto skip_inquire $ if devnam .eqs. "FT" then goto skip_inquire $ if devnam .eqs. "RT" then goto skip_inquire $ set terminal sys$output:/inquire $ skip_inquire: $ ENDIF This routine bypasses the SET TERMINAL/INQUIRE command on DECterm, SET HOST, and VWS, and also on nonterminal devices such as the mailboxes created by the Session Manager. 2-13 General User Release Notes 2.3 DECwindows Motif Application Notes 2.3.8.6 DECterm Resource Usage V1.1 You cannot create more terminal windows than your system resources and quotas allow. In the previous version of DECterm, the DECterm controller process would end abruptly and all DECterm windows would disappear when quotas were exceeded. If you have insufficient resources, a dialog box now appears with a message indicating that no additional DECterm windows can be created. 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, you must log out of all DECterm windows that are running on the host system before you increase the number of terminal windows. 2.3.8.7 Diagnostic Crash File and Messages-New and Enhanced V1.1 DECterm now produces a diagnostic file when a status code of level Fatal is returned. The file DECTERM_ERROR.LOG is produced in the login directory when DECterm exits abnormally. If you have a problem with DECterm and submit a Software Performance Report (SPR), include a copy of the log file. Under certain circumstances, a log file can be generated even when no problem has been 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. This mode should be used only for diagnosing problems because it causes generation of Session Manager message windows 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-14 General User Release Notes 2.3 DECwindows Motif Application Notes 2.3.8.8 Keyboards and Languages V1.1 The following information is specific to DECterm keyboards and languages: o As with any LK201 keyboard, to start a compose sequence, press the Compose key and space bar at the same time. The Compose key is a modifier, used like a Shift key. o Change the Keyclick Volume, Auto Repeat, Keyboard Type (national keyboards), Keyboard Usage mode (data processing and typewriter mode), and Caps Lock/Shift Lock by selecting Keyboard... from the Options menu in the Session Manager on a workstationwide basis, instead of through DECterm. o National Replacement Character Sets (NRCS) are selected from 7-Bit NRCS Selection... on the Options menu in DECterm. This selection is independent of both the keyboard dialect and the keyboard usage mode. For example, you must change both the Session Manager and the DECterm options to use the French NRCS with the French keyboard. o When the keyboard becomes locked (for example, when the input silo is full), the bell rings in DECterm for each character that is entered until the lock condition is cleared. 2.3.8.9 Monitor Screen Width Determines Default Font Size V1.0 Three font sets are available for 100 dots-per-inch monitors: 100, 140, and 180 decipoint fonts. When a 100- dpi monitor with a physical screen width of less than 325 millimeters is used (approximate screen width of a 15-inch monitor), the 140 and 100 decipoint fonts are selected, respectively, for the Big and Little font sets. If the physical screen width is larger than 325 millimeters, then the 180 and 140 decipoint fonts are used. To use the smaller font sets on a large 100-dpi monitor, place the following lines in the DECW$TERMINAL_DEFAULTS.DAT file: DECW$TERMINAL.main.terminal.littleFontSetName: -*-terminal-*-*-*--*-100-*-*-*-*-*-* DECW$TERMINAL.main.terminal.bigFontSetName: -*-terminal-*-*-*--*-140-*-*-*-*-*-* 2-15 General User Release Notes 2.3 DECwindows Motif Application Notes Alternatively, you can enter these font strings in the text fields for the "Other" fonts in the Options/Window dialog box. 2.3.8.10 Condensed German Standard Font Not Available V1.0 Condensed versions of the German Standard (GS) font do not exist. If Condensed is selected while the German Standard font is selected, the GS font remains selected. There is no visible change in the font or any other indication that Condensed has been selected. However, if you subsequently select Large or Small font, the condensed version of the Large or Small font is selected. 2.3.8.11 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.3.9 DECW$CDPLAYER 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.3.10 LinkWorks This section contains information about LinkWorks (DEClinks). 2.3.10.1 LinkWorks Manager Application Renamed to DEClinks V1.2- Note that the LinkWorks Run-Time Library bundled with 3 DECwindows Motif for OpenVMS is not the same product as the LinkWorks Version 2.1 Client/Server Groupware application. Refer to SPDs 48.55.xx, 48.56.xx, 48.57.xx, 48.58.xx, 48.59.xx, 48.60.xx, 48.61.xx, and 48.62.xx, for more information on LinkWorks Version 2.1. 2-16 General User Release Notes 2.3 DECwindows Motif Application Notes LinkWorks that is included in the LinkWorks Developer's Toolkit Version 1.0 and LinkWorks Run-Time Library is renamed to DEClinks to avoid confusion between the two products. Although LinkWorks continues to appear on the Session Manager applications menu and in documentation, the application that ships with DECwindows Motif is the DEClinks run-time application. 2.3.10.2 LinkWorks Manager (DEClinks) Application Retired V1.2- The DECwindows Motif Worldwide Support 1.2-3 for OpenVMS 3 release contains the final release of the LinkWorks (DEClinks) application. Future versions of DECwindows Motif will contain neither the LinkWorks run-time libraries nor the LinkWorks Manager executable images. 2.3.11 DECwindows Mail This section contains information about the DECwindows Mail application. 2.3.11.1 Using the Color Customizer with DECwindows Mail V1.2- If you are using the color customizer sample program 3 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 the color customizer and restart DECwindows Mail. See Section 1.3 for more information about the color customizer. 2.3.11.2 Multiple Tabs in Long Text Lines V1.2- The DECwindows Mail application contains a problem when 3 reading tabs within text areas that contain many lines. For example, the DECwindows Mail application ends when trying to read mail messages that have multiline "To", "From", "CC", or "Subject" strings with embedded tabs. As a possible solution, if you receive a mail message that you cannot read, forward, or reply to, then use the character-cell OpenVMS Mail application to process the message. You can still use DECwindows Mail to move the mail message to another folder. 2-17 General User Release Notes 2.3 DECwindows Motif Application Notes 2.3.11.3 DECwindows Mail Ends Without Print Queues V1.2- If you attempt to print a file or alter print settings on a 3 system with no printer queues using DECwindows Mail, then DECwindows Mail stops processing. 2.3.11.4 DECwindows Mail Is Linked with the OSF/Motif Release 1.1.3 Toolkit V1.2- The DECwindows Mail application is linked with the 3 OSF/Motif Release 1.1.3 Toolkit and has not been modified to link with the OSF/Motif Release 1.2.3 Toolkit, which is shipped with the DECwindows Motif Worldwide Support V1.2-3 for OpenVMS software. The following restrictions apply: o DECwindows Motif Worldwide Support V1.2-3 for OpenVMS drag-and-drop functionality is not supported. As a possible solution, use the standard clipboard (Cut, Copy, and Paste) operations to transfer text into DECwindows Mail. o DECwindows Motif Worldwide Support V1.2-3 for OpenVMS tear-off menus are not supported. 2.3.11.5 DECwindows Mail-Known Problems V1.0 The following problems exist with the DECwindows Mail application: o The XUI Window Manager does not automatically set input focus to windows when they are mapped. You must click on each window to get input focus. o The next and previous arrow buttons in the Read window do not dim at the end or beginning of the folder, respectively. They are ineffective if selected. o Use of the Message button in the Read window to scroll through a large message can be very slow. o Folders and Drawers with links are not highlighted in the paned interface. LinkWorks operations, however, can still be performed on these items. o Performance of the text widget in the Create-Send window can be degraded if the word wrap option is turned on. To enhance performance, turn off the word wrap option. 2-18 General User Release Notes 2.3 DECwindows Motif Application Notes 2.3.12 DECwindows Motif Window Manager This section contains information about the DECwindows Motif Window Manager. 2.3.12.1 Using the Color Customizer with DECwindows Motif Window Manager V1.2- If you are using the color customizer provided in the 3 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 1.3 for more information about the color customizer. 2.3.12.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-19 General User Release Notes 2.3 DECwindows Motif Application Notes 2.3.12.3 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.3.12.4 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.3.13 Motif Window Manager-Known Problems This section contains information about known problems with the Motif Window Manager. 2.3.13.1 Accelerators for Icon in Icon Box V1.0 When using an icon box, the accelerators on an icon's Window menu do not work unless you display that menu. Instead, accelerators always apply to the icon box. 2.3.13.2 Application Started as Icon V1.0 If an application is started as an icon before the Window Manager is started, the application's Main window is not minimized when the Window Manager is started. This can occur when you change X properties relating to icons before the Window Manager is started or when the Window Manager is starting. It can also occur if you start an application as an icon when the Window Manager is restarted after it has been previously started and is inactive. 2-20 General User Release Notes 2.3 DECwindows Motif Application Notes 2.3.13.3 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 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.3.13.4 Customizing Colors on 4-Plane Displays V1.1 A 4-plane display has a limited number of colors. You might not be able to modify colors with the color mix widget if the system usurps the color entries. To correct this problem, distribute as many of the colors as possible between the screen, window, border, icons, and pointer. 2.3.13.5 Customizing Icon Placement in Icon Box V1.0 If you customize the icon placement of applications by specifying iconX and iconY resources in the application's resource file, the placement is ignored if you are using an icon box. 2.3.13.6 DECwindows XUI Modal Dialog Boxes V1.0 Two problems exist with DECwindows XUI modal dialog boxes. If an application displays a dialog box before the main window is visible, the modal dialog box might be hidden behind the main window. It then appears that the application is hung. In this case, you must terminate the application. If you dismiss a modal dialog box, the focus might not automatically revert to its parent. 2-21 General User Release Notes 2.3 DECwindows Motif Application Notes 2.3.13.7 Customizing the Icon Box V1.0 To customize the position and size of an icon box, move and resize the icon box and then select Apply Current Settings from the Workspace Options menu. 2.3.13.8 Moving the Icon Box Off Screen V1.0 If you move the icon box to the edge of the screen and then resize it using the keyboard, you can move it 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.3.13.9 Truncating the Icon Title V1.0 The text for inactive icons is truncated to the size of the icons. Currently, there are two methods to view the complete text for an icon. You can make the icon active or you can customize your icons by choosing the Icon Options menu item and changing the width of the icons. 2.3.13.10 Invoking Motif Window Manager Help V1.2- Invoking Motif Window Manager Help through the workspace 3 Help menu causes the Motif Window Manager to stop. 2.3.13.11 Multihead Systems-Customizing Colors 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.3.13.12 Multiline Icon Title Not Centered V1.0 The Window Manager does not center all the lines of a multiline icon title. 2.3.13.13 Restored Window Icons Not Displayed V1.0 If you are not storing icons in an icon box, the icons for the restored windows are not displayed on the screen. 2-22 General User Release Notes 2.3 DECwindows Motif Application Notes 2.3.13.14 Truncated Icon Title in Vertical Icon Box V1.0 If the icon box is displayed vertically with only one column, then when an icon is selected, the active icon label is truncated on the right side. 2.3.13.15 Window Menu on Icon-Displaying with Keyboard V1.0 If you bring up the Window menu on an icon by highlighting the icon and pressing F4, the Window menu is not posted and might not work properly. 2.3.14 Notepad This section contains information about the Notepad application. 2.3.14.1 Notepad Is Linked with the OSF/Motif Release 1.1.3 Toolkit V1.2- The Notepad application is linked with the OSF/Motif 3 Release 1.1.3 Toolkit and has not been modified to link with the OSF/Motif Release 1.2.3 Toolkit, which is shipped with the DECwindows Motif Worldwide Support V1.2-3 for OpenVMS software. The following restrictions apply: o DECwindows Motif Worldwide Support V1.2-3 for OpenVMS drag-and-drop functionality is not supported. As a possible solution, use the standard clipboard (Cut, Copy, and Paste) operations to transfer text into Notepad. o DECwindows Motif Worldwide Support V1.2-3 for OpenVMS tear-off menus are not supported. 2.3.14.2 Options/Split View V1.2- When using the Options/Split View, the lower view window 3 appears to be empty. To correct this problem, resize the Notepad window by any amount and the lower view window displays properly. 2.3.15 Paint This section contains information about the Paint application. 2-23 General User Release Notes 2.3 DECwindows Motif Application Notes 2.3.15.1 Private Colormaps V1.1 If your workstation does not have sufficient colormap entries to view or edit a color image, Paint creates a private colormap. When this happens, the Paint image retains its colors, but the colors on the rest of the workstation are modified. To restore the colors to their original values, give another window input focus by clicking on it. 2.3.15.2 Enhancing the 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.3.15.3 Editing Color Images V1.0 When you edit color images, all drawing operations occur in the current drawing color. You can determine the current color only if the Palette dialog box is visible. The current drawing color is highlighted in the Palette dialog box. In addition to selecting a different color from the Palette dialog box, you can use the dropper tool to pick up a color from the canvas. The change in the current drawing color is reflected in the Palette dialog box. 2.3.15.4 Saving a Paint File V1.0 Saving a Paint file creates an empty file along with the saved picture file. The latest version of the output file is the saved picture. The previous version is the empty file. This empty file can be deleted. 2-24 General User Release Notes 2.3 DECwindows Motif Application Notes 2.3.16 Print Screen This section contains information about the Print Screen application. 2.3.16.1 Print Screen Modifications V1.2- The Print Screen application is modified for the DECwindows 3 Motif Worldwide Support V1.2-3 for OpenVMS release. The Print Screen user interface is redesigned so that it is easier to determine which options are selected. Once you select options, choose either Print or Print... from the File menu to start the screen capture operation. 2.3.16.2 Large Default Icon V1.0 The Print Screen application does not have its own distinctive icon and does not support icon sizes other than large. As a result, the icon is the default Motif icon of four squares. If you attempt to customize the icon size, only a portion of this icon is viewable. 2.3.16.3 Queue Options Dialog Box V1.0 The Queue Options dialog box has the following limitation: regardless of language implementation, the title of the print widget always appears in the English language as Queue Options and is not translated into the local language. 2.3.16.4 Changed Resource Values V1.0 The resource values in the file DECW$PRINTSCREEN.DAT are identical to the labels on the associated buttons. This permits the file to be read and edited by users in any locale. The resulting incompatibity makes existing saved values in the file DECW$PRINTSCREEN.DAT unusable to Print Screen. To use these saved values, print out the previous file for reference and then select and save the desired options using the Print Screen user interface. 2-25 General User Release Notes 2.3 DECwindows Motif Application Notes 2.3.17 Session Manager and FileView This section contains information about the Session Manager and FileView applications. 2.3.17.1 Security Options V1.2- In the Session Manager Security Options dialog box, place 3 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.3.17.2 Using the Color Customizer with Session Manager V1.2- If you are using the color customizer example program 3 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 1.3 for more information about the color customizer. 2-26 General User Release Notes 2.3 DECwindows Motif Application Notes 2.3.17.3 FileView DELETE Functionality-Changed V1.0 With DECwindows XUI, when you deleted a file using FileView and you specified the file with a semicolon at the end (such as SAMPLE.DAT;), FileView deleted all versions of the file. This function was different from the DCL command DELETE, which deletes only the latest version of a file whose name ends with a semicolon. In DECwindows Motif, if you use the FileView DELETE command and you specify a file with a semicolon at the end, FileView deletes only the latest version of the file. 2.3.17.4 FileView Icons Some dialog boxes include " FileView" in the title bar and use FileView icons, even though they are invoked from the Session Manager. 2.3.17.5 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.3.17.6 Session Manager Process-Stopping 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-27 General User Release Notes 2.3 DECwindows Motif Application Notes If you stop the Session Manager process, be sure to restart DECwindows (if you have system manager privileges) with the following command: $ @SYS$MANAGER:DECW$STARTUP RESTART 2.4 Public Profiles for Layered Products V1.0 Layered products that provide a DECwindows interface can use the Create Public Profile File command to create a profile file that ships with the layered product and is installed when the system manager installs the layered product. The file can be placed in the SYS$COMMON:[VUE$LIBRARY.USER] directory. Product-specific profile files should be named by appending the product prefix to the name PROFILE.VUE$DAT. For example, the file CMS$PROFILE.VUE$DAT names a profile containing CMS definitions. Any command files or other related files can also be placed in SYS$COMMON:[VUE$LIBRARY.USER] and should be referenced as VUE$LIBRARY in the profile. For more information on using the Create Public Profile File command, refer to Using DECwindows Motif for OpenVMS. 2.5 Toolkit Notes V1.2- Applications that are linked against OSF/Motif Release 3 1.1.3 may end abruptly when attempting to print on systems which do not have any print queues. This affects DECwindows Mail, which links against the OSF/Motif Release 1.1.3 libraries and is shipped as part of the DECwindows Motif V1.2-3 for OpenVMS software. Layered products which link 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 in order to accept print jobs. Give the print queue a name that indicates the print queue is not connected to a printer, for example, NULL_PRINTER. 2-28 3 _________________________________________________________________ System Manager Release Notes 3.1 DECwindows Motif Login Screen-Known Color Problem V1.2- A problem may occur on systems that have a customized 3 DECW$LOGIN.DAT file. The Start Session dialog box is the color blue instead of tan. If this condition exists, look for a customized DECW$LOGIN.DAT file in the directory SYS$COMMON:[DECW$DEFAULTS.USER] and move it to SYS$MANAGER. A DECW$LOGIN.DAT file in SYS$COMMON:[DECW$DEFAULTS.USER] prevents the "*background:" resource from being defined; thus, it will default to the color blue. Digital provides a copy of the DECW$LOGIN.DAT file in the SYS$COMMON:[DECW$DEFAULTS.SYSTEM] directory. Any customized versions of this file should reside only in SYS$MANAGER. 3.2 Define DECW$UTILS Global Symbol When Moving DECW$EXAMPLES Global Symbol V1.2- By default, DECW$UTILS points to a subdirectory of 3 DECW$EXAMPLES. If you define a DECW$EXAMPLES global symbol in the DECW$PRIVATE_APPS_SETUP.COM command procedure to change the directory for DECwindows example programs, you must also define DECW$UTILS to change the directory for utilities. For example, to redefine both DECW$EXAMPLES and DECW$UTILS, add the following lines to the SYS$MANAGER:DECW$PRIVATE_ APPS_SETUP.COM procedure: $ DECW$EXAMPLES == "SYS$SYSROOT:[DECWEXAMPLES] $ DECW$UTILS == "SYS$SYSROOT:[DECWEXAMPLES.UTILS] 3-1 System Manager Release Notes 3.2 Define DECW$UTILS Global Symbol When Moving DECW$EXAMPLES Global Symbol ________________________ Note ________________________ If the SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM file does not exist, create it from the SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.TEMPLATE file. ______________________________________________________ Then, restart DECwindows Motif with the following command: $@SYS$MANAGER:DECW$STARTUP RESTART The DECW$UTILS global symbol is new in DECwindows Motif Worldwide Support 1.2-3 for OpenVMS. 3.3 FileView Creates Detached Processes by Default V1.1 Starting with DECwindows Motif Version 1.1, applications created by FileView and Session Manager are detached processes. The implication of this change 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: 3-2 System Manager Release Notes 3.3 FileView Creates Detached Processes by Default $ 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.4 Logical Names V1.2- The following startup changes are made in DECwindows Motif 3 Worldwide Support 1.2-3 for OpenVMS: o If the corresponding global symbols are not defined, then the logical names in Table 3-1 are deassigned during execution of the file SYS$MANAGER:DECW$STARTAPPS.COM: 3-3 System Manager Release Notes 3.4 Logical Names Table_3-1_SYS$MANAGER_Global_Symbols_______________________ Logical_Name_______________Global_Symbol___________________ DECW$LOGIN_LOG DECW$LOGINLOG DECW$LOGIN_BACKGROUND DECW$LOGINLOGO DECW$LOGIN_LOGO_SUB DECW$LOGINLOGOSUB DECW$LOGIN_MULTIPLE DECW$LOGINMANY DECW$SESSION_LOG DECW$SESSIONLOG DECW$SYLOGIN_______________DECW$SYLOGINCOM_________________ In previous versions of DECwindows Motif, DECW$STARTAPPS.COM defined the logical names if the global symbols were defined, but it did not deassign the logical names if the global symbols were not defined. Therefore, to remove a customization and return to the default setting, you edited the file SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM and deassigned the logical names. o The DECwindows login log file, set by defining the global symbol DECW$LOGINLOG, now has a default value of SYS$MANAGER:DECW$LOGIN.LOG. In previous versions of DECwindows Motif, the global symbol was null by default, so the log file was not created. o SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.TEMPLATE has been reformatted and updated to reflect additional global symbols that can be customized. 3.5 Customized Login Logos 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. 3-4 System Manager Release Notes 3.5 Customized Login Logos 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 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. 3.6 Version Checking Command Files V1.0 The VMS DECwindows Motif Version 1.0 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 VMS DECwindows Motif Version 1.0: 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. 3-5 System Manager Release Notes 3.6 Version Checking Command Files o DECW$VERSIONS.COM A command procedure that assigns symbols for the version of DECwindows (from Xlib), the version of the transport (from transport_common), the version of the server (from the dix shareable), the version of Xlib, the version of the toolkit (from DECW$XMLIBSHR.EXE), the version of the applications (from VUE$MASTERSHR.EXE), and the version of the programming support (from DECW$UILMOTIF.EXE). 3.7 Layered Product Fonts V1.0 Fonts supplied by the DECwindows kit come with prebuilt font directory files. However, layered products do not supply font directory files with their fonts. If you want to use any layered products that supply their own X fonts, you must invoke the DECW$MKFONTDIR command file for the X server to be able to access the layered products fonts. You need to invoke this command file only for layered products installed after DECwindows because the DECwindows installation automatically invokes DECW$MKFONTDIR. You should enter the following command: $ @SYS$UPDATE:DECW$MKFONTDIR You must then end the current session and start a new session before the server can access the fonts. 3-6 System Manager Release Notes 3.8 DECterm System Management Issues 3.8 DECterm System Management Issues This section contains information about DECterm system management issues. 3.8.1 DECterm Logical Names V1.1 Table 3-2 describes the logical names that are supported by DECterm starting with VMS DECwindows Motif Version 1.1. These logical names must be defined in your LOGIN.COM file so that the controller sees them. Table_3-2_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. 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. (continued on next page) 3-7 System Manager Release Notes 3.8 DECterm System Management Issues Table_3-2_(Cont.)_Logical_Names_Supported_by_DECterm_____________ Logical_Name______________________Description____________________ DECW$DECTERM_DISABLE_QUOTA_ Turns off quota checking. CHECKING DECW$DECTERM_MEM_DIAG Shows controller quota __________________________________calculations.__________________ 3.8.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.8.3 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.8.4 Nohangup and Virtual Terminal Support V1.0 The /NOHANGUP qualifier is no longer supported in DECterm. The pseudoterminal driver used by DECterm for terminal creation does not inhibit asynchronous system trap (AST) notification when you enter the SET TERMINAL/NOHANGUP command. In previous releases, this feature of the driver was often used for directing debugger output to a separate window. 3-8 System Manager Release Notes 3.8 DECterm System Management Issues The driver no longer supports the TT2$M_DISCONNECT bit used to cause a created process to establish a virtual terminal on creation. Therefore, DECterm does not inherently offer virtual terminal support. However, you can simulate /NOHANGUP and virtual terminal support by entering the following command: $ CREATE/TERMINAL/NOPROCESS [/DEFINE=xxx] This command creates a DECterm with no associated process but with a logical name of "xxx" that points to the terminal. This technique permits output to be directed to a separate DECterm other than to the one in which the application is running. To redirect output, enter the following commands: $ DEFINE /USER DBG$INPUT xxx: $ DEFINE /USER DBG$OUTPUT xxx: $ RUN /DEBUG application.exe To create a session that uses a virtual terminal, enter the following command (note that the /DEFINE qualifier is not required): $ CREATE/TERMINAL/NOPROCESS Then establish focus to the newly created DECterm, press Return and log in. 3-9 4 _________________________________________________________________ Programmer Release Notes 4.1 Programming Release Notes Specific to DECwindows Motif Worldwide Support V1.2-3 for OpenVMS The release notes in this chapter are cumulative from DECwindows Motif Version 1.0 and still apply to Worldwide Support 1.2-3. The following sections contain programmer release notes that pertain specifically to DECwindows Motif Worldwide Support V1.2-3 for OpenVMS: o Section 4.2, DECwindows Motif Worldwide Support V1.2-3 for OpenVMS Toolkit Versions o Section 4.3, Run-Time and Programming Environment o Section 4.4, OSF/Motif Toolkit Compatibility o Section 4.4.1, _Xm Routines o Section 4.4.2, OSF/Motif Release 1.2.3 and X11 R5 Shareable Libraries o Section 4.4.3, OSF/Motif Release 1.1.3 Ada Bindings o Section 4.5, OSF/Motif Release 1.1.3 Programming Support and XUI o Section 4.7, Translated Image Support o Section 4.8, Cross-Development Tools o Section 4.11.1, CDA-Implementing Drag-and-Drop Functionality o Section 4.11.2, CDA Run-Time Services New Features o Section 4.12, DECterm Programming o Section 4.13.1, Compilation Error When Including Both CURSES.H and XMP.H Files 4-1 Programmer Release Notes 4.1 Programming Release Notes Specific to DECwindows Motif Worldwide Support V1.2-3 for OpenVMS o Section 4.14, OSF/Motif Example Programs o Section 4.14.1, Cutpaste Example Program o Section 4.14.2, DNDDemo Example Program o Section 4.14.4, Helloint Example Program o Section 4.14.5, Hellomotif Example Program o Section 4.14.8, Motifshell Example Program o Section 4.14.10, Textedit Example Program o Section 4.14.10.1, Additional Translations o Section 4.14.11, View Example Program o Section 4.14.12, Xmpiano Example Program o Section 4.14.13, Motif Sample Programs o Section 4.14.14, Xmtravel Example Program o Section 4.14.15, Resource Files for Example Programs o Section 4.14.16, UID Files for Example Programs o Section 4.15.1, DXmCSText Input Method Support o Section 4.16.4, Shared Memory Extension Support o Section 4.16.5, Using Extension Include Files o Section 4.17.1, DECW$XLIBSHR Problem with AST Handling o Section 4.17.2, xlibint.h Is Now a Public Header File o Section 4.17.6, Xlib Internationalization 4.2 DECwindows Motif Worldwide Support V1.2-3 for OpenVMS Toolkit Versions V1.2- The DECwindows Motif Worldwide Support 1.2-3 for OpenVMS 3 release is based on the OSF/Motif Release 1.2.3 Toolkit and MIT X11 Release 5 (R5). V1.1 The VMS DECwindows Motif Version 1.1 release was based on the OSF/Motif Release 1.1.3 Toolkit and MIT X11 Release 4 (R4). V1.0 The VMS DECwindows Motif Version 1.0 release was based on the OSF/Motif Release 1.1.1 Toolkit and MIT X11 Release 4 (R4). 4-2 Programmer Release Notes 4.3 Run-Time and Programming Environment 4.3 Run-Time and Programming Environment V1.2- The following run-time and programming environment are 3 provided with the DECwindows Motif Worldwide Support V1.2-3 for OpenVMS software: o Run-time support is provided for the OSF/Motif Release 1.2.3, OSF/Motif Release 1.1.3, and X User Interface (XUI) toolkits. o Development support is provided for the OSF/Motif Release 1.2.3 Toolkit only. You can, however, choose during installation to save the programming files that exist on your system before DECwindows Motif Worldwide Support 1.2-3 for OpenVMS is actually installed. If you choose to save these programming files, they are moved to subdirectories and can be accessed for programming. See the DECwindows Motif V1.2-3 for OpenVMS Language Variants Installation Guide for a more detailed explanation of saving the Release 1.1.3 programming environment. o Application development with DECwindows Motif Worldwide Support 1.2-3 for OpenVMS is supported for the C, DEC C++, Fortran, and Pascal programming languages only. o In order for a program to execute on a DECwindows Motif Version 1.1 system, it must be linked on DECwindows Motif Version 1.1 or a previous version. If a program is linked on DECwindows Motif Worldwide Support 1.2-3 and executed on DECwindows Motif Version 1.1, it fails and displays the following error message: %SYSTEM-F-IDMISMATCH, ident mismatch with global section or shareable image A program that uses the new features of the OSF/Motif Release 1.2.3 Toolkit must be linked on a DECwindows Motif Worldwide Support 1.2-3 system and can only be executed on DECwindows Motif Worldwide Support 1.2-3 software or higher. 4-3 Programmer Release Notes 4.4 OSF/Motif Toolkit Compatibility 4.4 OSF/Motif Toolkit Compatibility V1.2- The OSF/Motif Release 1.2.3 Toolkit is not binary 3 compatible with the OSF/Motif Release 1.1.3 Toolkit, which was provided with the DECwindows Motif Version 1.1 for OpenVMS product. To use the OSF/Motif Release 1.2.3 Toolkit with existing applications, modify your build procedures (as shown in Section 4.4.2), recompile, and relink your applications with the OSF/Motif Release 1.2.3 Toolkit. You may need to modify the source files. If the code generates errors because of references to display structure fields, define the constant XLIB_ILLEGAL_ACCESS for X11 R4 compatible structure access. For example: $ CC/DEFINE=XLIB_ILLEGAL_ACCESS DECBURGER.C 4.4.1 _Xm Routines V1.2- The OSF/Motif Toolkit is implemented with many internal- 3 only routines, which are prefixed with _Xm. These routines are intended to be used only by the standard Motif widgets. The application programming interface (API) is not documented, and OSF does not support these routines. OSF reserves the right to change the API, add new _Xm routines, delete existing _Xm routines, and change the functionality of any _Xm routines without warning or notice. _______________________ Warning _______________________ Digital supplies access to the _Xm routines by copying them into the shareable image transfer vector for the OSF/Motif Release 1.2.3 Toolkit. Digital does not guarantee the use of these routines and Digital does not document or support these routines. Users who call these functions do so at their own risk. ______________________________________________________ 4-4 Programmer Release Notes 4.4 OSF/Motif Toolkit Compatibility 4.4.2 OSF/Motif Release 1.2.3 and X11 R5 Shareable Libraries V1.2- Because the OSF/Motif Release 1.2.3 Toolkit and the 3 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.3 can only link against OSF/Motif 1.2.3-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.3-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.3-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.3 Toolkit do not have a suffix. These libraries are as follows: 4-5 Programmer Release Notes 4.4 OSF/Motif Toolkit Compatibility o CDA$ACCESS.EXE o DECW$D2DXLIBSHR.EXE o DECW$XEXTLIBSHR.EXE o DECW$XLIBSHR.EXE o XDPS$DPSBINDINGSSSHR.EXE o XDPS$DPSCLIENTSHR.EXE o XDPS$DPSLIBSHR.EXE o XIE$SHRLIB.EXE 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.3. Table 4-1 lists these file names. Table_4-1_Names_of_Shareable_Libraries_Based_on_R5_________ Names_of_Files_Based_on_R4__Names_of_Files_Based_on_R5_____ DECW$AILSHR.EXE DECW$AILSHRR5.EXE 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.3 have a suffix of "12". They should be linked only with libraries compatible with R5 and OSF/Motif Release 1.2.3. Table 4-2 lists these file names. 4-6 Programmer Release Notes 4.4 OSF/Motif Toolkit Compatibility Table 4-2 Names of Shareable Libraries Based on OSF/Motif __________Release_1.2.3____________________________________ Names of Files Based on Names of Files Based on Release Release_1.1.3_______________1.2.3__________________________ DDIF$VIEWSHR.EXE DDIF$VIEWSHR12.EXE DECW$BKRSHR.EXE DECW$BKRSHR12.EXE DECW$DXMLIBSHR.EXE DECW$DXMLIBSHR12.EXE DECW$MAILSHR.EXE (none) (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__________________ Note that there is no DECW$MAILSHR12.EXE file because DECwindows Mail links against the OSF/Motif Release 1.1.3 Toolkit, and there is no DECW$PRINTWGTSHR12.EXE file because the Print Widget is now 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.3 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 4-7 Programmer Release Notes 4.4 OSF/Motif Toolkit Compatibility To link this program with OSF/Motif Release 1.2.3, 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 These changes eliminate the reference to the XUI Toolkit (DECW$DWTLIBSHR.EXE) and links with the Motif Resource Manager (DECW$MRMLIBSHR12.EXE). 4.4.3 OSF/Motif Release 1.1.3 Ada Bindings V1.2- This release of DECwindows Motif Worldwide Support V1.2-3 3 for OpenVMS does not include Ada bindings for either the OSF/Motif Release 1.1.3 Toolkit or the OSF/Motif Release 1.2.3 Toolkit. Strongly typed bindings for both toolkits ship as part of the next release of the Ada language product. If the DECwindows Motif Worldwide Support V1.2-3 for OpenVMS software is installed on OpenVMS DECwindows Motif Version 1.1, then the existing OSF/Motif Release 1.1.3 Ada bindings, located in the DECW$INCLUDE directory, are not deleted or moved. 4.5 OSF/Motif Release 1.1.3 Programming Support and XUI V1.2- The X Window and OSF/Motif libraries that are shipped 3 with DECwindows Motif Worldwide Support V1.2-3 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 Worldwide Support V1.2-3 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 4-8 Programmer Release Notes 4.5 OSF/Motif Release 1.1.3 Programming Support and XUI in Table 4-3 and moves the previous files into the new subdirectory. For more information about saving the programming files, see the DECwindows Motif V1.2-3 for OpenVMS Language Variants Installation Guide. Table 4-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. 4-9 Programmer Release Notes 4.5 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) 4-10 Programmer Release Notes 4.5 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 ______________________________________________________ 4.6 Adding POSIX for OpenVMS Support to DECwindows Transports V1.1 Transports specific to DECwindows require code modifications to support POSIX for OpenVMS fork() requirements. If you have written a specific transport and also plan to implement POSIX for OpenVMS support, you must make changes to your transport source code. This note describes the required changes. 4.6.1 POSIX fork() Routine V1.1 The POSIX fork() routine creates a copy of the currently executing process, completely cloning P1 and P0 space. Both the original process (the parent) and the new process (the child) proceed on identical paths from that point. When using the POSIX fork() routine, data is not duplicated because: o Files that are not opened through the POSIX for OpenVMS file system are not known to the child. o Channels that are not shareable or opened through POSIX for OpenVMS are not known to the child. o The AST queue of the parent is not copied to the child. Because of these limitations, the POSIX for OpenVMS implementation has placed certain demands on protected shareable images, including transports specific to DECwindows: 4-11 Programmer Release Notes 4.6 Adding POSIX for OpenVMS Support to DECwindows Transports o It is the responsibility of each protected shareable image to acknowledge that it can be forked. o Based on how the child process should function, each protected shareable image must handle any cleanup or duplication of its own data in a routine called a fork callback. Specific transports must acknowledge (on the client side) that they can be forked. The SYS$POSIX_FORK_CONTROL system service, described in Section 4.6.2, is provided for this purpose. Specific transports need not perform any cleanup work. 4.6.2 SYS$POSIX_FORK_CONTROL System Service V1.1 A new SYS$POSIX_FORK_CONTROL system service was added in VMS Version 5.5 that registers that a protected shareable image can be forked. It also registers the address and parameter to a fork callback. The execution of the POSIX fork() routine fails if the application has been linked with, or has activated, a protected shareable image that has not called SYS$POSIX_ FORK_CONTROL. Therefore, in your specific transport's open routine, add a call to the SYS$POSIX_FORK_CONTROL system service similar to the following: $ POSIX_FORK_CONTROL(CNTRL = POSIX$C_SETUP_CALLBACK, WHEN = POSIX$M_CALL_IN_CHILD,HANDLER = posix_fork_cb); In this example, the CNTRL parameter indicates that the image is setting up a callback so that it can be forked, the WHEN parameter tells when to call the fork callback, and the HANDLER parameter gives the address of the fork callback. Other parameters that are not used in this example allow for a parameter to be passed to the callback routine and to specify the access mode (maximized to that of the caller). 4-12 Programmer Release Notes 4.7 Translated Image Support 4.7 Translated Image Support DECwindows Motif Worldwide Support 1.2-3 for OpenVMS Alpha includes support for DECwindows Motif Version 1.1 for OpenVMS VAX images on an OpenVMS Alpha V1.2- system. 3 The DECwindows Motif Worldwide Support 1.2-3 for OpenVMS Alpha release does not include support for running translated DECwindows Motif Worldwide Support 1.2-3 for OpenVMS VAX images on OpenVMS Alpha systems. If you want to run an application against DECwindows Motif Worldwide Support 1.2-3 shareable images on an OpenVMS Alpha system, build it (compile and link) on an OpenVMS Alpha system. You cannot obtain a Worldwide Support 1.2- 3 translated image by building your application against the DECwindows Motif Worldwide Support 1.2-3 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 Worldwide Support 1.2-3 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 V1.2-3 for OpenVMS Language Variants Installation Guide for instructions. The DECwindows Motif Release 1.1.3 and Release 1.2.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: 4-13 Programmer Release Notes 4.7 Translated Image Support 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. For more information on translated image support, see the DECmigrate for OpenVMS AXP Systems Translating Images guide.<> 4.8 Cross-Development Tools V1.2- The OpenVMS Alpha Migration Toolkit runs on the OpenVMS VAX 3 operating system and supports development for OpenVMS Alpha operating systems. To develop DECwindows Motif applications in a multiplatform environment, you need the OpenVMS Alpha Migration Toolkit and the DECwindows Motif Worldwide Support 1.2-3 for OpenVMS Alpha software. DECwindows Motif is not part of the OpenVMS Alpha Migration Toolkit. The following steps explain how to extract DECwindows Motif files from the save sets on the DECwindows Motif Worldwide Support V1.2-3 for OpenVMS Alpha kit for use in a multitools environment. ________________________ Note ________________________ Because of OSF requirements, you must purchase a DECwindows Motif Worldwide Support V1.2-3 for OpenVMS license to unpack the DECwindows Motif save sets for multiplatform development. ______________________________________________________ During installation of the OpenVMS Alpha Migration Toolkit, the logical name ALPHA$LIBRARY is created. This logical name is used as the destination of the files in the OpenVMS BACKUP commands that follow. 4-14 Programmer Release Notes 4.8 Cross-Development Tools Unpack the DECwindows Motif Worldwide Support V1.2-3 for OpenVMS Alpha save sets for multiplatform development into the ALPHA$LIBRARY directory using the BACKUP command. o Use the following commands to unpack the B and C save sets, which contain all bindings: $ BACKUP DWMOTIF_AXPW1123.B/SAVE/SELECT=[SYSLIB]*.* ALPHA$LIBRARY: $ BACKUP DWMOTIF_AXPW1123.C/SAVE/SELECT=[SYSLIB]*.* ALPHA$LIBRARY: o Use the BACKUP command to unpack the language bindings from the following save sets: - E (MIT C bindings) - J (Fortran bindings) - L (Pascal bindings) For example: $ BACKUP DWMOTIF_AXPW1123.E/SAVE ALPHA$LIBRARY: $ BACKUP DWMOTIF_AXPW1123.J/SAVE ALPHA$LIBRARY: $ BACKUPDWMOTIF_AXPW1123.L/SAVE ALPHA$LIBRARY: o Use the BACKUP command to unpack the files from the following save set: - Q (Translated image support) For example: $ BACKUP DWMOTIF_AXPW1123.Q/SAVE/SELECT=[SYSLIB]*.IIF ALPHA$LIBRARY: Note that you only need the .IIF files from the Q save set. The OpenVMS Alpha Migration Toolkit Reference Manual provides programmer's reference information on the tools included in the OpenVMS Alpha Migration Toolkit. 4.9 Compiling Applications Written in C Use the /STANDARD=VAXC compiler switch when you compile DECwindows Motif programs written in C. Using this switch ensures that compile errors do V1.1 not occur while using DECwindows Motif header files.<> 4-15 Programmer Release Notes 4.9 Compiling Applications Written in C 4.9.1 C Header Files V1.0 During the VAX C installation procedure, you have the option to extract the VAX C definition files (.h files) or leave the .h files in the text library. If you extract the definition files, you are able to use #include control lines of the following form: #include 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.10 Compiling Applications Written in Fortran Some of the include files used for writing DECwindows Motif applications in Fortran, such as the DECW$MOTIF.FOR file, contain structure V1.1 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 4-16 Programmer Release Notes 4.10 Compiling Applications Written in Fortran - 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.11 CDA Application This section contains programming information about the CDA application. 4.11.1 CDA-Implementing Drag-and-Drop Functionality V1.2- Drag-and-drop functionality, which lets you move or copy 3 information between widgets, is implemented in the widgets listed in Table 4-4. Table_4-4_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 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-17 Programmer Release Notes 4.11 CDA Application 4.11.2 CDA Run-Time Services New Features V1.2- This section describes new programming features in this 3 version of the CDA Run-Time Services. See Chapter 2 for new user features. 4.11.2.1 Version Number V1.2- CDA Version 1.6 was part of DECwindows Motif Version 1.1; 3 CDA Version 1.7 was released after DECwindows Motif Version 1.1. The current version of DECwindows Motif provides the CDA Run-Time Services component of CDA Version 1.8. This section identifies differences between CDA Version 1.6 and CDA Version 1.8 of the CDA Run-Time Services component. 4.11.2.2 Changes to the Programming Interface for CDA V1.2- This section describes the changes to the programming 3 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-18 Programmer Release Notes 4.11 CDA Application 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-5 for a list of new header file names. Table_4-5_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.11.2.3 Changes to External Reference Processing V1.2- CDA Run-Time Services now supports relative file 3 specifications for external references. In the previous version, external reference file specifications had to be either absolute file name or simple references (where the file was expected to be found in the same directory as the parent document). In this version, relative references are also supported. A relative reference is one in which the directory path is not fully specified but is relative to the directory path of the parent document. 4-19 Programmer Release Notes 4.11 CDA Application 4.11.2.4 New Message for Style Guide Fallback V1.2- A new message is issued when a local style guide cannot be 3 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.11.2.5 Using Logical Names with CONVERT Commands V1.2- There is a restriction when using logical names with 3 document conversion operations. 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 containing relative file specifications cause the conversion to fail. This occurs because the converter processing options are examined by the back-end converter 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 find the actual file specification so that the directory can be parsed and extended with a relative specification. The conversion only fails when the external reference has 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-20 Programmer Release Notes 4.11 CDA Application 4.11.2.6 Restructuring Shareable Images V1.2- The CDA Viewer was restructured in CDA Version 1.7, and two 3 new shareable images were introduced to allow installation on systems that did not have DECwindows installed. In DECwindows Motif Worldwide Support V1.2-3 for OpenVMS, shareable images that use the X services are renamed. The shareable images in the various versions of CDA are listed in Table 4-6. Table_4-6_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.8 shareable image. 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 determine whether it can execute in a given environment. The DDIF$VIEW.EXE application now replaces this routine. 4-21 Programmer Release Notes 4.11 CDA Application 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.12 DECterm Programming V1.2- This section contains information about DECterm 3 programming. 4.12.1 Page Movement Escape Sequences V1.2- The following page movement escape sequences are 3 implemented in DECterm: NP Next Page PP Previous Page PPA Page Position Absolute PPB Page Position Backward PPR Page Position Relative 4-22 Programmer Release Notes 4.12 DECterm Programming ________________________ Note ________________________ DECterm does not support cursor coupling; the cursor is always bound to the current (displayed) page. ______________________________________________________ 4.12.2 DECCRA Sequence V1.2- DECterm supports the DECCRA (Copy Rectangular Area) 3 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.12.3 DECLFKC Sequence V1.2- Since DECterm does not have a user interface to redefine 3 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.12.4 ReGiS Input Cursors V1.2- DECterm supports two kinds of input cursors: the diamond 3 cursor and the rubber-band rectangle cursor. To select these cursors, use the S(C(In)) command. If "n" is equal to 4, then the rubber-band rectangle is used; otherwise the diamond cursor is used. ________________________ Note ________________________ If a shape other than the diamond cursor is desired, define the logical name DECW$DECTERM_ REGIS_CURSOR to be one of the numbers defined in the SYS$LIBRARY:DECW$CURSOR.H file. ______________________________________________________ 4.13 DECwindows OSF/Motif Toolkit This section contains information about notes, restrictions, and corrections for the DECwindows OSF/Motif Toolkit. 4-23 Programmer Release Notes 4.13 DECwindows OSF/Motif Toolkit 4.13.1 Compilation Error When Including Both CURSES.H and XMP.H Files V1.2- When compiling a C program that includes the files curses.h 3 and XmP.h, or any Motif header file which causes XmP.h to be included, such as LabelP.h, a compilation error similar to the following may be generated: Boolean move; %CC-E-MACREQARGS, Macro reference requires an argument list; "move" not substituted. At line number 407 in SYS$COMMON:[DECW$INCLUDE]XMP.H;1. This error occurs as a result of the file curses.h defining a macro named "move", which conflicts with a member field in an OSF/Motif Release 1.2.3 structure for drag-and-drop support. This error can be prevented by placing the include statement for the file curses.h after the include statements for any DECwindows Motif header files. 4.13.2 Motif Text Widget Translations V1.0 To implement Digital virtual bindings, it is necessary for Digital to modify the default XmText and XmTextField translation manager syntax. Specifically, the following syntax line is removed: Shift ~Ctrl ~Meta ~Alt osfDelete: cut-clipboard() 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. 4.13.3 Traversing a Motif Menu Bar with Keys V1.0 A problem exists with using the keyboard to traverse a Motif menu bar with servers based upon MIT X11 R3 or previous versions. Keyboard traversal only works if the mouse pointer is positioned within the currently pulled- down menu. 4-24 Programmer Release Notes 4.13 DECwindows OSF/Motif Toolkit 4.13.4 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, Digital 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 Digital does not control. When the standards make an incompatible change, Digital will change the toolkit to follow it. However, the intent is to add code that allows existing executable images to run unchanged. 4.13.4.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 4-25 Programmer Release Notes 4.13 DECwindows OSF/Motif Toolkit 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. 4.13.5 DECwindows Motif Toolkit Functionality DECwindows Motif Toolkit functionality is available with the following restriction: for the DECwindows Motif product, C modules are compiled V1.1 using the default MEMBER_ALIGNMENT switch in the C compiler. If you intend to port a toolkit application that is written in C, see the VAX C Run-Time Library release notes in the OpenVMS Alpha AXP Version 1.0 Release Notes.<> 4.14 OSF/Motif Example Programs This section describes example programs from the Open Softare Foundation (OSF) that are included in the DECwindows Motif Worldwide Support V1.2-3 for OpenVMS kit. 4.14.1 Cutpaste Example Program V1.2- This example demonstrates the use of the Motif Clipboard. 3 You can cut and paste application-defined data formats using the XmClipboard API. Run two cutpaste clients and transfer graph values using the pull-down and pop-up menus. 4-26 Programmer Release Notes 4.14 OSF/Motif Example Programs 4.14.2 DNDDemo Example Program V1.2- This example illustrates a typical use of the drag-and-drop 3 feature. 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 4-27 Programmer Release Notes 4.14 OSF/Motif Example Programs 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 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. ______________________________________________________ 4.14.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(). 4-28 Programmer Release Notes 4.14 OSF/Motif Example Programs 4.14.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 4.14.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. 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. 4-29 Programmer Release Notes 4.14 OSF/Motif Example Programs 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. 4.14.4 Helloint Example Program V1.2- This example is a simple UIL/Xm program with a label and a 3 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: 4-30 Programmer Release Notes 4.14 OSF/Motif Example Programs ___________________________________________________________ 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: ___________________________________________________________ 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. 4.14.5 Hellomotif Example Program V1.2- This example is a simple UIL/Xm program with a label and a 3 push button. 4-31 Programmer Release Notes 4.14 OSF/Motif Example Programs 4.14.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. 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. 4.14.7 Motifgif and Pict Viewing Programs 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. 4-32 Programmer Release Notes 4.14 OSF/Motif Example Programs 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. o .gif files The files that contain the bitmapped displays. The following problems exist with motifgif: o Resizing a picture does not work. o The -d option is not used when calling pict, so remote displays must set the DISPLAY environment variable. No .gif files are supplied with VMS DECwindows Motif Version 1.1. 4.14.8 Motifshell Example Program V1.2- The motifshell program is an example of an environment 3 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. ______________________________________________________ 4.14.9 Periodic Example Program V1.2- The periodic example is a demonstration of the displayable 3 widgets in Motif. The program displays Motif widgets in a periodic chart format. 4-33 Programmer Release Notes 4.14 OSF/Motif Example Programs 4.14.10 Textedit Example Program V1.2- The textedit program is a primitive text editor based on 3 the Motif XmText widget that makes use of its XmNsource resource to allow multiple views of the same underlying text. Table 4-7 describes the View menu options. Table_4-7_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 4-8. Table_4-8_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) 4-34 Programmer Release Notes 4.14 OSF/Motif Example Programs Table_4-8_(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. ______________________________________________________ 4.14.10.1 Additional Translations V1.2- Users familiar with emacs may want to add the following 3 translations to their DECW$XDEFAULTS.DAT files: 4-35 Programmer Release Notes 4.14 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() 4-36 Programmer Release Notes 4.14 OSF/Motif Example Programs 4.14.11 View Example Program V1.2- The view program is similar to the DCL command TYPE/PAGE 3 using Motif with internationalization support. It allows you to view files in several languages. 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 4-37 Programmer Release Notes 4.14 OSF/Motif Example Programs This entry only exists on the primary shell; it closes the file and the shell. 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. 4.14.12 Xmpiano Example Program V1.2- The xmpiano program shows how to write a Motif Interface 3 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: o Add Voice 4-38 Programmer Release Notes 4.14 OSF/Motif Example Programs 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. 4-39 Programmer Release Notes 4.14 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 4.14.13 Motif Sample Programs V1.2- Table 4-9 lists sample programs showing various Motif 3 Toolkit functionality. Table_4-9_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. 4-40 Programmer Release Notes 4.14 OSF/Motif Example Programs 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: $ 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 MOTIF PROGRAMMING manual for a list of available widget classes. 4.14.14 Xmtravel Example Program V1.2- The xmtravel example is a front end to a travel agent 3 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. 4.14.15 Resource Files for Example Programs V1.2- Many of the example programs have associated resource files 3 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. 4-41 Programmer Release Notes 4.14 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. 4.14.16 UID Files for Example Programs V1.2- The UID files used by the example programs must be located 3 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. 4.15 DECwindows Extensions to Motif This section contains information about the Digital extensions to the Motif Toolkit. 4-42 Programmer Release Notes 4.15 DECwindows Extensions to Motif 4.15.1 DXmCSText Input Method Support V1.2- X11 R5 input method support is added to the DXmCSText 3 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.15.2 Help Callback Routines V1.0 Help callback routines invoked through DXmHelpOnContext should be prepared to accept a NULL callback structure parameter. DXmHelpOnContext cannot obtain sufficient information to construct a valid callback structure and so passes a NULL. 4.15.3 SVN-Horizontal Live Scrolling Not Supported V1.0 Horizontal live scrolling is not yet supported in the Structured Visual Navigation (SVN) widget. 4.15.4 SVN Horizontal Separator Line V1.1 When displaying an application that uses the SVN widget on a Sun system running OpenWindows Version 2, the horizontal separator line of the SVN widget is not always displayed due to a problem with the OpenWindows server. The problem does not exist with OpenWindows Version 3. 4.15.5 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.16 Display Server Extensions This section contains information about the display server extensions. 4-43 Programmer Release Notes 4.16 Display Server Extensions 4.16.1 Display PostScript (DPS) Server Extension-Color Cells V1.0 You can associate a colormap with a DPS context using the DPSCreateContext routine or the setXgcdrawablecolor operator. You can also specify that DPS allocate its own colors from the specified colormap using the actual parameter to DPSCreateContext or the setXgcdrawablecolor operator. If you have created the colormap using the AllocAll flag, you must not also specify a nonzero value for the actual parameter. DPS always allocates colors as shareable and AllocAll forces all possible colormap entries to be allocated as nonshareable. 4.16.2 X Image Extension V1.1 The X Image Extension (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. VMS DECwindows Motif Version 1.1 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_ 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. 4-44 Programmer Release Notes 4.16 Display Server Extensions 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. XIE is documented in the DECimage Application Services for VMS X Image Extension Programmer's Reference Manual. 4.16.3 Client Side Extension Library V1.1 Starting with Version 1.1, Xlib added a client side library that allows VMS 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.16.4 Shared Memory Extension Support Shared memory extension support provides the capability to share memory XImages. This is a version of the XImage interface where the actual image 4-45 Programmer Release Notes 4.16 Display Server Extensions V1.2- data is stored in a shared-memory segment. Consequently, 3 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. These routines are included in the client side extension library. See Section 4.16.3 for details on linking this library. 4.16.4.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. 4-46 Programmer Release Notes 4.16 Display Server Extensions ___________________________________________________________ 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.16.4.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 4-47 Programmer Release Notes 4.16 Display Server Extensions 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. 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; 4-48 Programmer Release Notes 4.16 Display Server Extensions 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 Worldwide Support 1.2-3 for OpenVMS Alpha. Using global sections, these routines emulate the shared memory routines on UNIX systems. ______________________________________________________ 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. 4-49 Programmer Release Notes 4.16 Display Server Extensions 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; 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. 4-50 Programmer Release Notes 4.16 Display Server Extensions ___________________________________________________________ Argument____Description____________________________________ 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.16.4.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.16.4.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. 4-51 Programmer Release Notes 4.16 Display Server Extensions 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. 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.16.4.2).<> 4.16.5 Using Extension Include Files V1.2- To ensure that programs that contain extension include 3 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.17 Xlib Issues This section contains information about Xlib. 4-52 Programmer Release Notes 4.17 Xlib Issues 4.17.1 DECW$XLIBSHR Problem with AST Handling The DECW$XLIBSHR shareable image contains an AST handling problem. Many Xlib routines reenable ASTs upon returning, even if the calling V1.2- application disabled ASTs prior to calling the Xlib 3 routine. If your application expects ASTs to remain disabled after calling Xlib routines, you have to explicitly disable ASTs after the Xlib call.<> 4.17.2 xlibint.h Is Now a Public Header File V1.2- To write application interfaces for your server extensions, 3 DECwindows Motif for OpenVMS provides the OpenVMS header file called xlibint.h in the DECW$INCLUDE directory. 4.17.3 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.17.4 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-10 lists routine names and the longword arguments that are sent only as 16-bit values. Table 4-10 Routine Names and Arguments Sent as 16-Bit ___________Values__________________________________________ Routine_Name_______________________Routine_Arguments_______ XAllocColorCells/ALLOC_COLOR_ nplanes,npixels CELLS (continued on next page) 4-53 Programmer Release Notes 4.17 Xlib Issues Table 4-10 (Cont.) Routine Names and Arguments Sent as ___________________16-Bit_Values___________________________ Routine_Name_______________________Routine_Arguments_______ XDrawArc/DRAW_ARC x,y,width,height, angle1,angle2 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.17.5 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-54 Programmer Release Notes 4.17 Xlib Issues 4.17.6 Xlib Internationalization V1.2- The X Window System Version 11, Release 5 (X11 R5) defines 3 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, Digital 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.17.6.1 Vendor Pluggable Layer V1.2- Digital provides a general mechanism called the vendor 3 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. 4-55 Programmer Release Notes 4.17 Xlib Issues 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. Digital 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.17.6.2 Digital Internationalization Xlib Implementation V1.2- The Digital implementation (Xi18n) provides enhanced 3 support and a stable internationalization environment. The Digital 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 Worldwide Support 1.2-3 for OpenVMS 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. 4-56 Programmer Release Notes 4.17 Xlib Issues 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. o The XIM protocol (protocol between Xlib and input method server) has been proposed to the X Consortium for inclusion in the X11 R6 standard. 4.17.6.3 Locale in OpenVMS Systems V1.2- DECwindows Motif Worldwide Support 1.2-3 for OpenVMS 3 software is dependent on a locale environment that conforms to the ANSI C library. In the DEC C environment, the set of supporting locales does not fully utilize the internationalized Xlib. Therefore, Xlib provides a minimal locale support environment that allows DECwindows Motif Worldwide Support 1.2-3 to run on a host environment without locale support. The locale support environment can use the locale environment provided by DECC$SHR if it is available; otherwise, Xlib uses its internal locale environment. Locales can be set by using the setlocale() function if the locale is supported by Xlib. The following functions and macros are provided in the OpenVMS locale environment: setlocale mblen mbtowc mbstowcs wctomb wcstombs MB_LEN_MAX If you write internationalized applications using these functions in the locale environment, do the following: o For Xlib applications, include . If you include , you must do so before . o For Motif applications, is automatically included. 4-57 Programmer Release Notes 4.17 Xlib Issues o Turn on the following compilation flags: /define=(X_LOCALE,X_WCHAR,_WCHAR_T_,XLIB_XPG4_FUNCS) 4-58 5 _________________________________________________________________ Documentation Release Notes This chapter describes the following information: o Section 5.1, DEC CDA Base Services Documentation o Section 5.2, DECwindows Motif documentation that can be used with DECwindows Motif Worldwide Support V1.2-3 for OpenVMS. o Section 5.3, DECwindows Motif Documentation Corrections o Section 5.4, OSF/Motif List of Known Problems 5.1 DEC CDA Base Services Documentation V1.0 The DEC CDA Base Services programming documentation set describes how software developers can write CDA supported applications and converters. You can order the complete documentation set, or you can order the following individual books: o The Technical Overview of the DEC CDA Base Services (AA- PHJYA-TE) provides an overview of compound document processing terminology and the various components of the CDA architecture, which include the DDIF and DTIF interchange formats, the CDA data structures and access routines, the converter architecture, and the CDA Viewer. o Creating Compound Documents Using the DEC CDA Base Services (AA-PHK2A-TE) provides a tutorial that describes how to use the CDA access routines to create CDA conforming compound document applications. o Writing Converters Using the DEC CDA Base Services (AA- PHK1A-TE) provides a tutorial that describes how to use the CDA access routines to write CDA conforming front end and back end converters. 5-1 Documentation Release Notes 5.1 DEC CDA Base Services Documentation o Reference Manual (Volume 1) (AA-PHJZA-TE) and Reference Manual (Volume 2) (AA-PHKOA-TE) provide reference material that supplements the two CDA user guides. These two manuals describe the DDIF and DTIF aggregates and syntax diagrams, the CDA access routines and user- defined routines, converter routines, callable window and character-cell CDA Viewer routines, and converter widget routines. 5.2 DECwindows Motif Worldwide Support V1.2-3 for OpenVMS Documentation V1.2- Table 5-1 lists the documents that can be used with the 3 DECwindows Motif Worldwide Support V1.2-3 for OpenVMS software. Many documents have been updated for this release; updated information for other books is included only in these release notes. Table 5-1 DECwindows Motif Worldwide Support 1.2-3 for __________OpenVMS_Documentation____________________________ Title___________________________________Software_Version___ DECwindows Motif V1.2-3 for OpenVMS Version 1.2-3 Language Variants Release Notes DECwindows Motif V1.2-3 for OpenVMS Version 1.2-3 Language Variants Installation Guide DECwindows Motif Guide for Worldwide Version 1.2 Support DECwindows Motif for OpenVMS Version 1.2 Applications Guide DECwindows Motif for OpenVMS Guide to Version 1.2 Non-C Bindings Using DECwindows Motif for OpenVMS Version 1.1[1] (Digital Press) DECwindows Motif for OpenVMS Quick Version 1.2 Reference Card [1]Updates_to_these_documents,_if_any,_are_noted_in_this___ release notes chapter. (continued on next page) 5-2 Documentation Release Notes 5.2 DECwindows Motif Worldwide Support V1.2-3 for OpenVMS Documentation Table 5-1 (Cont.) DECwindows Motif Worldwide Support 1.2-3 __________________for_OpenVMS_Documentation________________ Title___________________________________Software_Version___ Managing DECwindows Motif for OpenVMS Version 1.2 Systems Overview of DECwindows Motif for Version 1.2 OpenVMS Documentation DECwindows Extensions to Motif Version 1.2 DECwindows Companion to the OSF/Motif Version 1.2 Style Guide DECwindows Motif Guide to Application Version 1.2 Programming VMS DECwindows Device Driver Manual Version 1.0[1] VMS DECwindows Transport Manual Version 1.0[1] Porting XUI Applications to Motif Version 1.0[1] VMS DECwindows Guide to Xlib (Release Version 1.0[1] 4) Programming: MIT C Binding VMS DECwindows Guide to Xlib (Release Version 1.0[1] 4) Programming: VAX Binding VMS DECwindows Display PostScript Version 1.0[1] System Programming Supplement X Window System (Digital Press) Release 5 Third Edition X Window System Toolkit (Digital Release 4 Press) X and Motif Quick Reference Guide Release 5 (Digital Press) OSF/Motif Style Guide (Prentice-Hall) Version 1.2 OSF/Motif Programmer's Guide Version 1.2 (Prentice-Hall) OSF/Motif Programmer's Reference Version 1.2 (Prentice-Hall) [1]Updates_to_these_documents,_if_any,_are_noted_in_this___ release notes chapter. ___________________________________________________________ 5-3 Documentation Release Notes 5.3 DECwindows Motif Documentation Corrections 5.3 DECwindows Motif Documentation Corrections This section contains corrections to existing DECwindows Motif documentation. 5.3.1 Using DECwindows Motif for OpenVMS V1.2- This section contains documentation corrections to the 3 Using DECwindows Motif for OpenVMS manual. 5.3.1.1 Adding Target Screen Options to Application Menu Items V1.2- The example "Adding Target Screen Options to Application 3 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.1.2 Changing the Startup Environment V1.2- The example "Changing Your Logo" is incorrect. To correct 3 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.3.2 VMS DECwindows Guide to Xlib (Release 4) Programming: VAX Binding V1.2- Example 1-1 in the VMS DECwindows Guide to Xlib (Release 3 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 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 5-4 Documentation Release Notes 5.3 DECwindows Motif Documentation Corrections 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.3.3 DECwindows Extensions to Motif V1.2- In Section 2.2 of the DECwindows Extensions to Motif 3 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". The arguments listed for the DXmCreate Cursor routine in Section 2.2 are for OSF/1. The values in the Argument and Description sections are listed as follows: decw$c_wait_cursor decw$c_questionmark_cursor decw$c_inactive_cursor The correct arguments for DECwindows Motif are as follows: DXm_WAIT_CURSOR DXm_HELP_CURSOR DXm_INACTIVE_CURSOR 5.3.4 Overview of DECwindows Motif for OpenVMS Documentation 5.4 OSF/Motif List of Known Problems Included in the DECwindows Motif Worldwide Support V1.2-3 for OpenVMS kit 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. 5-5 6 _________________________________________________________________ Internationalization (I18N) Release Notes This chapter describes the new internationalization features incorporated in DECwindows Motif Worldwide Support V1.2-3 for OpenVMS as well as the known software problems, corrections, and restrictions. 6.1 New I18N Features This section describes the new features introduced with DECwindows Motif Worldwide Support V1.2-3 for OpenVMS. Some highlights of the internationalized features are: o X Window System Release 5 o OSF/Motif Release 1.2.3 (with Internationalized XmText and XmTextField widget classes) o New UIL compiler enhancements o Multiple codesets support o Input Server Service Layer (application programming interfaces for writing input servers) o Selecting input server and input style in Session Manager o Multiple input styles support for input method o Traditional/Simplified Chinese Conversion o New DECterm features 6.1.1 X Window System Release 5 This release incorporates X Window System Release 5, which contains internationalization programming supports such as X Input Method (XIM), internationalized text drawing and inter-client communication. 6-1 Internationalization (I18N) Release Notes 6.1 New I18N Features 6.1.2 OSF/Motif Release 1.2.3 Toolkit In this release, the OSF/Motif Release 1.2.3 toolkit is provided to facilitate the tasks of programmers intending to develop software for worldwide support. In addition to the DXmCSText widget class, the XmText and XmTextField widget classes are also internationalized to support local language text input and display. 6.1.3 UIL Compiler Internationalization Features An additional option /LOCALE is provided to direct the UIL compiler to set the locale before compiling any files. The locale is set according to the LANG logical. If this option is not specified, the compiler does not set the locale. You are strongly recommended to use the /LOCALE option to compile your UIL file. 6.1.3.1 How To Specify String Constants In UIL There are many ways to specify string constants in UIL: 1. Locale-encoded string constants with the /LOCALE option When the /LOCALE option is specified and the UIL file does not contain a "character_set=" statement in the module block, double-quoted strings will be stored as simple multibyte strings and encoded in filecode. 2. 'strings' Single-quoted strings will be stored as simple multibyte strings. The quoted data will not be converted and the data is assumed to be encoded in ISO Latin-1. 3. compound_string ('string') or compound_string ("string") Strings will be converted to and stored as compound strings (XmString). 4. "strings" Usually, double-quoted strings will be stored as simple multibyte strings. 6-2 Internationalization (I18N) Release Notes 6.1 New I18N Features 6.1.3.2 Exceptions In String Constants In the following cases, double-quoted strings are stored as compound strings: 1. Strings contain data of more than one character sets, e.g. mixed ASCII and DEC Korean characters, mixed half- form Katakana and Kanji characters, and mixed CNS 11643 and DTSCS characters in DEC Hanyu. 2. Special characters When characters from the following character sets exist in the string: BIG-5, CNS plane 3 or plane 4. Note that, in these cases, even if the whole string contains only BIG-5, CNS plane 3 or plane 4 characters, it is still stored as a compound string. 6.1.4 Multiple codesets support for some language In some language variants, multiple codesets are supported. For details, please see Appendix A - E. 6.1.5 Input Server Service Layer (IMSSL) With the introduction of X Input Method in X Window System Release 5, a common set of programming interfaces is provided so that programmers can develop software with worldwide language supports. In some countries, such as China, Japan, and Korea, the input methods are so complex that usually they are implemented as separate processes, called input servers. An input server can serve many client processes on the same computer network. This input method model is called the client-server model and requires a communication protocol to be established between the X Input Method library (client) and the input server. Digital has implemented an XIM protocol layer based on the inter-client communication mechanism of X Window Window. The protocol is named as the DECXim protocol. To simplify the task of developing input servers, a set of comprehensive programming interfaces is provided in the Input Server Services Layer (IMSSL). An program example, IMS_EXAMPLE.C, can be found under DECW$EXAMPLES. This example illustrates how to write an input server. 6-3 Internationalization (I18N) Release Notes 6.1 New I18N Features 6.1.6 Selecting Input Style and Input Server You can select your preferred input style and input server through Input Method... under the Session Manager's Options menu. Before you start your applications, you need to determine which input server and which input style you want to use. Most applications cannot switch them after they are invoked and running. One of the exceptions is DECterm. It supports run-time switching of input style and input server when it is running in the following languages: o Traditional Chinese o Simplified Chinese o Korean 6.1.7 Supporting Input Styles Four input styles are supported: o Over the Spot o Off the Spot o Root Window o On the Spot An input server does not need to support all the input styles. If it does not support any of these input styles, the Pre-edit None style will be used. _________________________________________________________________ Over The On The ______________Spot__________Off_The_Spot__Root_Window___Spot_____ decw$jim Y N Y Y decw$hanyuim N Y Y N decw$hanziim N Y Y N decw$hangulim_Y_____________Y_____________Y_____________Y________ 6.1.8 Simplified/Traditional Chinese Conversion Traditional Chinese applications can connect to both Traditional Chinese and Simplified Chinese input servers. Similarly, Simplified Chinese applications can also connect to both Traditional Chinese and Simplified Chinese input servers. 6-4 Internationalization (I18N) Release Notes 6.1 New I18N Features The quick copy and cut-and-paste operations between sSimplified Chinese and Traditional Chinese applications will automatically perform conversion. 6.1.9 New Features in DECterm 1. If DECterm is running in Simplified Chinese, Traditional Chinese or Korean, the Keyboard Options dialog box provides menu items to choose "two-byte delete" and "two-byte cursor movement". When you choose "two-byte delete" and "two-byte cursor movement", pressing the Delete key will send two Delete key sequences to the host, and pressing the Left or Right cursor key will send two Left or Right cursor key sequences. 2. DECterm provides a Input Method Options dialog box when it is running in Simplified Chinese, Traditional Chinese or Korean. This dialog box allows you to select the input server (e.g. switching between the Simplified Chinese and Traditional Chinese input servers) and the input style during run-time. 3. DECterm, when running in Thai, supports space compensation characters specified in ASCII or character format. 6.2 General Release Notes This section contains information about the DECwindows Motif Worldwide Support V1.2-3 for OpenVMS features that are of interest to general users, system managers and programmers. 6.2.1 Locale DECwindows Motif Worldwide Support V1.2-3 for OpenVMS is based on a locale environment that conforms to the ANSI C library. In the DEC C environment on OpenVMS, the set of supporting locales does not cover all language variants supported by DECwindows Motif. Therefore, the X Library provides a built-in locale support so that DECwindows Motif can be running on an environment without the support of the required locales. 6-5 Internationalization (I18N) Release Notes 6.2 General Release Notes The X Library can support the locale environment provided by DECC$SHR (i.e. the XPG4 support) when it is available. Otherwise, the X Library will fallback to use its built-in locale environment. The locale of an application can be selected using the setlocale() function if it is supported by the X Library. The following functions and macros are provided in the DECwindows Motif built-in locale environment: o setlocale o mblen o mbtowc o mbstowcs o wctomb o wcstombs o MB_LEN_MAX If you develop internationalization applications using these functions, do the following: o For applications based on the X Library, include the header file . If your program also includes , include this header before . o For applications based on the DECwindows Motif libraries, the header will be included automatically. o Compile your program with the following compilation flags: /define=(X_LOCALE,X_WCHAR,_WCHAR_T_,XLIB_XPG4_FUNCS) 6-6 Internationalization (I18N) Release Notes 6.2 General Release Notes 6.2.2 Examples 1. XIMDemo This example demonstrates how to write internationalized programs based on the X Library. 2. Periodic This example demonstrates how to write internationalized programs based on the OSF/Motif Release 1.2.3 toolkit. Note: To run periodic, make sure the files PERIODIC.DAT and PERIODIC.UID can be accessed through the DECW$SYSTEM_DEFAULTS logical. 3. IMS_Example This example demonstrates how to write an input server for DECwindows Motif. 4. hellomotif and decburger These two examples illustrate how to provide local language user-interface using the DECwindows Motif toolkit. 6.3 Known Problems and Restrictions This section presents the known problems and restrictions of the DECwindows Motif Worldwide Support V1.2-3 for OpenVMS support. 6.3.1 Menu Bar The menu bars of some applications may not be long enough to hold all menu items on one single line. If this is the case, menu items may be displayed on two separate lines. To display all menu items on one single line, you can resize the application's window so that there is sufficient space to accommodate all menu items. Mnemonics must be present in the menu name and uniquely identified in the menu bar. Otherwise, it may cause unexpected behavior. 6-7 Internationalization (I18N) Release Notes 6.3 Known Problems and Restrictions 6.3.2 Multiple Language Resource Files If you install more than one language variant on your system, make sure you are using the right resource file for the language you have selected. Some applications may save their settings in your home directory. If you save the resources in one locale and use them in another locale, the result may be unpredictable. For example, if you save the modified DECterm resources in the English locale (stored in DECW$TERMINAL.DAT in your home directory) and then use them in the Chinese locale, you may get the wrong fonts displayed on the DECterm window. 6.3.3 Input Server An input server is provided for a local language. You must start the required input server before you invoke an application in that language. For details, please see Appendix Appendix A. 6.3.4 User Defined Characters (UDC) Among all the input methods provided, you must enter user- defined characters through internal codes only. 6.3.5 DECterm 6.3.5.1 Downline Loadable Characters Downline loadable characters (pre-loading and on-demand- loading) are not supported in DECterm. The escape sequence will simply be ignored. 6.3.5.2 DRCS Not Fully Supported In DECterm, only the Standard Character Set (SCS) is supported and the DECDLD control string is ignored. When DECterm receives the SCS of DRCS, it searches the X window server for the fonts with XLFD named as "-*-dec-drcs" and treats it as a soft characters set. 6.3.5.3 Two-byte Characters at the Last Column Ignored Any character which occupies two columns will be ignored by DECterm when displayed in the last column of a line. 6-8 Internationalization (I18N) Release Notes 6.3 Known Problems and Restrictions 6.3.5.4 Calculation of Rows and Columns The calculation of rows and columns in DECterm may not work correctly when the interactive style is Off-the- spot. In this case, setting the rows and columns in the Display Options dialog box may not give the correct sizing of DECterm. You need resize DECterm through mouse actions. 6.3.5.5 Defining DECterm Title in Command Line You cannot define the DECterm title in local language using the DCL command line. For example, you cannot use the following command to define a Chinese DECterm title: $ CREATE/TERM/WINDOW=(TITLE=xx) 6.3.6 Cardfiler Quick Copy Problem In Cardfiler, the following dialog boxes do not support quick copy in local language: name card, rename card and search dialog. 6.3.7 Codeset Conversion Support in Cut-and-Paste Mail and Notepad do not support codeset conversion in clipboard operations, such as cut-and-paste. In turn, Simplified Chinese/Traditional Chinese conversion is not supported, either, in Mail and Notepad. 6.3.8 CDA Viewer CDA Viewer does not support PostScript files which contain multi-byte characters. 6.3.9 Bookreader 6.3.9.1 Printing Restrictions o Printing in landscape mode is not supported. o It may not be possible to print a very large book if the size of the book exceeds the print spooler limits. 6-9 Internationalization (I18N) Release Notes 6.3 Known Problems and Restrictions o Lines in tables may not align properly. o Topic windows that contain multi-column text may not be printed correctly. 6.3.9.2 Copyright Statements in Printed Material Bookreader places a copyright statement at the beginning of anything that is printed. This copyright statement comes from a field in the book file. If the field is empty, a Digital copyright statement is automatically placed at the start of the printed material. If you are producing your own books, be sure to place the correct copyright statement in the book file to avoid having Digital's copyright statement appear in your books. 6.3.9.3 Problems with Keyboard Equivalents Bookreader uses the keyboard accelerators supported in the Motif interface. The following problems exist: o Pressing [F11] to cancel the Print dialog box or Search Results dialog box does not work. o Pressing [F4] to display a pop-up menu does not work. o When using the Screen forward button in the Topic window, when you reach the last screen in the book, the forward arrow is disabled. The focus then cycles around to the Close button. It should cycle to the Screen backward button. o When using the Topic forward button in the Topic window, when you reach the last screen in the book, the forward button is disabled. The focus cycles to the Screen backward button. It should cycle to the Topic backward button. o If any of the topic or screen buttons are selected, pressing Return or Enter moves forward by screen regardless of which button is selected. Pressing the space bar does the right thing. 6-10 Internationalization (I18N) Release Notes 6.3 Known Problems and Restrictions 6.3.9.4 Font Size of Bookreader Font size of the bookreader format documents generated by DECwrite should not be smaller than the available font size in the server. Otherwise, the text will overlap when viewed by the Bookreader. 6.3.10 Pre-Edit and Status Area Not Redrawn When you choose to use the off-the-spot or over-the-spot interactive style, the pre-edit and status areas will not redraw if these areas are occluded by other windows. You have to focus on the input window to redraw the pre-edit and status areas. 6.3.11 Off-the-spot Needs Manual Resizing If you choose to use the off-the-spot input style, the pre-edit and status areas are located at the bottom of an application. The status mode is displayed when you focus on the application's window. In some cases, especially if the application does not support auto-resizing, the pre-edit and status areas may not be seen at the bottom. In this case, you will need to resize the application window to accomodate the pre-edit and status areas. 6.3.12 Limitations when Running in Standard (English) OpenVMS In this version, some of the language variants can be installed and run on standard (English) OpenVMS with some limitations: 1. For Simplified Chinese, Traditional Chinese and Korean, cursor movement and multi-byte character deletion are not supported by the terminal drivers. You have to press the Delete key twice to delete a Chinese or Korean character and press the cursor key twice to traverse a Chinese or Korean character. A workaround to this problem is to enable the "two char delete" and "two char cursor movement" functions in DECterm. 2. The Phrase input method of the Traditional Chinese input server is not supported. 3. Since CMGR does not exist, user-defined characters cannot be defined and displayed on DECwindows screen. 6-11 Internationalization (I18N) Release Notes 6.3 Known Problems and Restrictions 4. Editors, such as EDT and TPU, do not support local language processing. 5. You cannot define local language personal names in DECwindows Mail. 6.4 Notes for Japanese and Asian Language Variants These Notes apply to the Japanese, Korean, Thai, Simplified and Traditional Chinese language variants. 6.4.1 Notes for Japanese Support 6.4.1.1 Supported Locale The following Japanese locales are supported: o ja_JP.deckanji-DEC Kanji o ja_JP.sdeckanji-Super DEC Kanji o ja_JP.eucJP-Japanese EUC o ja_JP (same as ja_JP.sdeckanji) 6.4.1.2 Input Server The input server is located in SYS$SYSTEM:DECW$JIM.EXE. 6.4.1.3 Ximp Support If you want an application to make use of the XIMP implementation, you should define the logical DECW$XVENDORLAYER as SYS$LIBRARY:DECW$XIMPLIBSHR.EXE before you start the application. 6-12 Internationalization (I18N) Release Notes 6.4 Notes for Japanese and Asian Language Variants 6.4.1.4 Japanese Keyboards The following Japanese keyboards are supported: o LK201-AJ o LK401-AJ o LK401-BJ o LK401-JJ o LK421-AJ o LK421-JJ o PCXAJ-AA_LK (for Alpha only) o PCXAJ-AA_PC (for Alpha only) 6.4.1.5 Kana Input Users can enter kana characters directly when the default keymap is set and the current keymap is one of the Japanese keymaps. To enter kana mode, please hit on LK201-AJ, or on other Japanese keyboards, except PCXAJ-AA_LK and PCXAJ-AA_PC which use right- (or right- if keymaps from OpenVMS/Japanese V1.5-1H1 kit are used). Please hit the same key again to go back to ASCII mode. 6.4.1.6 Keyboard Indicator Keyboard indicator (sys$system:decw$kb_indicator) is automatically activated and controls the kana lamp of the Japanese keyboards (except for LK401-AJ, LK421-AJ, PCXAJ-AA_LK and PCXAJ-AA_PC which do not have the kana lamp). 6.4.1.7 Conversion Candidate During kana-kanji conversion, users can get a list of conversion candidates by typing or by . Please select the desired string in the list by a mouse. Arrow keys, , and