____________________________________________________
VMS DECwindows Version 1.1 Release Notes
June 1992
This document describes software problems,
corrections, and restrictions, as well
as documentation changes that pertain to
Version 1.1 of VMS DECwindows Motif.
Revision/Update Information: This manual supersedes
the VMS DECwindows
Motif Version 1.0
Release Notes.
Operating System: VMS Version 5.4-3
Software Version: VMS DECwindows Motif
Version 1.1
Digital Equipment Corporation
Maynard, Massachusetts
________________________________________________________________
June 1992
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.
No responsibility is assumed for the use or reliability
of software on equipment that is not supplied by Digital
Equipment Corporation or its affiliated companies.
© Digital Equipment Corporation 1992.
All Rights Reserved.
The postpaid Reader's Comments forms at the end of this
document request your critical evaluation to assist in
preparing future documentation.
The following are trademarks of Digital Equipment
Corporation: Bookreader, CDA, DEC, DECnet, DECpresent,
DECwindows, DECwrite, Digital, LinkWorks, LiveLink, LN03,
MicroVAX, PrintServer, ReGIS, ULTRIX, VAX, VAXcluster,
VAXserver, VAXstation, VMS, VT330, VT340, XUI, and the
DIGITAL logo.
The following are third-party trademarks:
Motif is a trademark of the Open Software Foundation, Inc.
Adobe is a registered trademark of Adobe Systems
Incorporated.
Display PostScript and PostScript are registered trademarks
of Adobe Systems Incorporated.
Open Software Foundation, OSF, OSF/Motif, and Motif are
trademarks of the Open Software Foundation, Inc.
UNIX is a registered trademark of UNIX System Laboratories,
Inc.
X Window System, Version 11 and its derivations (X, X11,
X Version 11, X Window System) are trademarks of the
Massachusetts Institute of Technology.
ZK5955
This document was prepared using VAX DOCUMENT, Version 2.1.
_________________________________________________________________
Contents
Preface................................................... xi
1 General User Release Notes
1.1 Version 1.1 Specific Release Notes............... 1-1
1.2 Access Control-Not Explicitly Enabled by
Default.......................................... 1-2
1.3 Monitor Screen Width Customized Login Logos...... 1-3
1.4 VMS DECwindows Motif Application Notes........... 1-3
1.4.1 Bookreader .................................... 1-3
1.4.1.1 DECW$BOOKSHELF Logical Name Cannot Reference
Search List................................. 1-4
1.4.1.2 Formal Examples, Figures, and Tables........ 1-4
1.4.1.3 Incorrect Text in Message................... 1-4
1.4.2 Calendar ...................................... 1-4
1.4.3 Cardfiler ..................................... 1-5
1.4.4 CDA Viewer/CDA PostScript Converter ........... 1-5
1.4.4.1 CDA Viewer-Viewing PostScript Files with
Errors...................................... 1-5
1.4.4.2 CDA Viewer/CDA PostScript Converter-Graphics
Objects..................................... 1-6
1.4.4.3 CDA Viewer/CDA PostScript Converter-Page
Problem..................................... 1-6
1.4.4.4 CDA Viewer Supports DECfonts Version 1.2.... 1-6
1.4.4.5 Paper Size... Button Renamed................ 1-6
1.4.4.6 Watch Progress Can Cause CDA Viewer to Lose
Expose Events............................... 1-7
iii
1.4.5 DECterm ....................................... 1-7
1.4.5.1 Condensed German Standard Font Not
Available................................... 1-7
1.4.5.2 Cursor Blink Not Disabled in DECterm
Widget...................................... 1-7
1.4.5.3 DECterm Controller and LOGINOUT............. 1-7
1.4.5.4 DECterm Graphics............................ 1-8
1.4.5.5 DECterm Initialization...................... 1-9
1.4.5.6 DECterm Not a Complete VT330/VT340 Terminal
Emulator.................................... 1-10
1.4.5.7 DECterm Resource Usage...................... 1-10
1.4.5.8 DECterm Text................................ 1-10
1.4.5.9 Diagnostic Crash File and Messages-New and
Enhanced.................................... 1-10
1.4.5.10 Displaying Version Information About
DECterm..................................... 1-11
1.4.5.11 Keyboards and Languages..................... 1-11
1.4.5.12 Monitor Screen Width Determines Default Font
Size........................................ 1-12
1.4.5.13 Nohangup and Virtual Terminal Support....... 1-12
1.4.5.14 DECterm PC Interoperability Restrictions.... 1-13
1.4.5.15 ReGIS and SIXEL............................. 1-14
1.4.5.16 ReGIS Locator Report........................ 1-15
1.4.5.17 /PROCESS=procnam Fails if No Process With
Default Name................................ 1-15
1.4.5.18 Queued Printing Requires Name in File
Field....................................... 1-15
1.4.5.19 Screen Print Services....................... 1-15
1.4.5.20 Simultaneous Multiple Language
Performance-Resource Demanding.............. 1-16
1.4.6 LinkWorks .................................... 1-16
1.4.6.1 Application Identifier Name................. 1-16
1.4.6.2 Application Startup Error................... 1-16
1.4.6.3 Work-In-Progress Box........................ 1-16
1.4.7 Mail Restrictions and Problems ................ 1-17
1.4.8 Paint ......................................... 1-17
1.4.8.1 Enhancing the Performance of Some Paint
Operations.................................. 1-17
1.4.8.2 Editing Color Images........................ 1-18
1.4.8.3 Private Colormaps........................... 1-18
1.4.8.4 Saving a Paint File......................... 1-18
iv
1.4.9 Print Screen ................................. 1-18
1.4.9.1 Keyboard Mnemonics Not Implemented.......... 1-18
1.4.9.2 Options Menu................................ 1-19
1.4.9.3 Print Orientation Option-Not Functional..... 1-19
1.4.9.4 Print Screen Default Icon-Large............. 1-19
1.4.9.5 Queue Options Dialog Box.................... 1-19
1.4.9.6 Reduce Only Setting-Not Functional.......... 1-20
1.4.9.7 Resource Values-Changed..................... 1-20
1.5 DECW$CDPLAYER Enhanced........................... 1-20
1.6 Motif Window Manager (Mwm) Notes................. 1-20
1.6.1 Configuration File ............................ 1-20
1.6.2 DECwindows XUI Applications ................... 1-21
1.6.3 Icons ......................................... 1-21
1.6.4 International Keyboard Performance
Improvement.................................... 1-21
1.6.5 Known Problems with Motif Window Manager ...... 1-22
1.6.5.1 Accelerators for Icon in Icon Box........... 1-22
1.6.5.2 Application Started As Icon ................ 1-22
1.6.5.3 Color-Related Resources for Monochrome
Monitors-Customizing........................ 1-22
1.6.5.4 Customizing Colors on 4-Plane Displays...... 1-22
1.6.5.5 Customized Icon Placement in Icon Box....... 1-23
1.6.5.6 DECwindows XUI Modal Dialog Boxes........... 1-23
1.6.5.7 Icon Box-Customizing........................ 1-23
1.6.5.8 Icon Box Colors on Monocrome and Gray-Scale
Systems..................................... 1-23
1.6.5.9 Icon Box Moved Off Screen................... 1-23
1.6.5.10 Icon Title Truncated........................ 1-23
1.6.5.11 Invoking Help for Mwm ...................... 1-24
1.6.5.12 Multihead Systems-Customizing Colors........ 1-24
1.6.5.13 Multiline Icon Text Not Centered ........... 1-24
1.6.5.14 Multiscreen Systems With Mixed Monitors .... 1-24
1.6.5.15 Next Window on Multihead System............. 1-24
1.6.5.16 Restored Window Icons Not Displayed......... 1-25
1.6.5.17 Truncated Icon Title in Vertical Icon Box... 1-25
1.6.5.18 Window Menu on Icon-Displaying with
Keyboard.................................... 1-25
1.6.6 Motif Window Manager-Restarting ............... 1-25
1.6.7 New Mwm Default Font .......................... 1-25
1.7 Public Profiles for Layered Products............. 1-25
1.8 Session Manager and FileView .................... 1-26
1.8.1 Change in Bindings for Lists in FileView and
Session Manager................................ 1-26
v
1.8.2 EWS Users Must Upgrade to EWS Version 1.0A .... 1-26
1.8.3 FileView DELETE Functionality-Changed ........ 1-26
1.8.4 FileView Starts Detached Processes by
Default........................................ 1-27
1.8.5 User Default Resource File .................... 1-27
1.8.6 Session Manager and FileView-Problems ......... 1-28
1.8.6.1 Input Focus Change When Starting Private
Logo........................................ 1-28
1.8.7 Session Manager Process-Stopping .............. 1-28
1.9 Troubleshooting Information...................... 1-29
1.10 Version Checking Command Files................... 1-29
2 Programmer Release Notes
2.1 Version 1.1 Specific Release Notes............... 2-1
2.2 Adding POSIX Support to DECwindows Transports.... 2-2
2.2.1 The POSIX fork() Routine ...................... 2-2
2.2.2 SYS$POSIX_FORK_CONTROL System Service ......... 2-3
2.3 DEC CDA Base Services ........................... 2-3
2.3.1 DDIF$VIEWSHR Interaction Problems with XUI
Applications................................... 2-4
2.3.2 Function Prototypes and Data Type
Definitions.................................... 2-4
2.3.3 New Item Change Lists for Aggregates .......... 2-5
2.3.4 User Get or Put Routine Parameter ............. 2-5
2.4 DECterm.......................................... 2-6
2.4.1 Controller Communication and Startup .......... 2-6
2.4.2 DECterm Controller MUTEX Hang Bug ............. 2-6
2.4.3 DECterm Logical Names ......................... 2-7
2.4.3.1 DECterm Window Positioning.................. 2-7
2.5 VMS DECwindows Motif Version 1.1 Based on
OSF/Motif Release 1.1.3.......................... 2-8
2.6 DECwindows Toolkit............................... 2-8
2.6.1 Additional Non-C Language Binding Support for
Motif.......................................... 2-8
2.6.2 Intrinsics Changes from the Digital Version of
MIT X11 Release 3 to MIT X11 Release 4......... 2-8
2.6.2.1 Changes in Routine Interfaces............... 2-9
2.6.2.2 Changes in Widget Semantics:................ 2-9
2.6.2.3 Other Changes............................... 2-10
vi
2.6.3 Miscellaneous Toolkit Notes, Corrections, and
Restrictions .................................. 2-11
2.6.3.1 Context-Sensitive Help...................... 2-11
2.6.3.2 Debugging Toolkit Applications-SET
BREAK/EXCEPTION Command .................... 2-11
2.6.3.3 Help Callback Routines...................... 2-11
2.6.3.4 Insensitivity Problem....................... 2-11
2.6.3.5 Intrinsics Key Translator................... 2-12
2.6.3.6 Motif Text Widget Translations.............. 2-13
2.6.3.7 Projected Change for XmText Class Widget.... 2-13
2.6.3.8 Shift Lock.................................. 2-13
2.6.3.9 Traversing a Motif Menu Bar with Keys....... 2-13
2.6.3.10 VAX Format Toolkit Bindings................. 2-14
2.6.3.11 XmText Widget Interactive Performance....... 2-14
2.6.3.12 XUI Application Linking Procedures.......... 2-14
2.6.4 New DECwindows Motif Toolkit Shareable
Images......................................... 2-15
2.6.4.1 Code Shareable Images....................... 2-15
2.6.4.2 Thin-Layer Shareable Image.................. 2-16
2.6.5 Upward Compatibility .......................... 2-16
2.6.5.1 Restrictions on Mixing Motif and XUI
Widgets..................................... 2-17
2.7 Display PostScript (DPS) Server Extension-Color
Cells............................................ 2-17
2.8 Layered Products Fonts........................... 2-18
2.8.1 Accessing Layered Products Fonts .............. 2-18
2.8.2 DECpresent Bullet Fonts Available ............. 2-18
2.9 New OSF/Motif Examples........................... 2-19
2.9.1 MOTIFANIM ..................................... 2-19
2.9.2 MRE ........................................... 2-20
2.9.2.1 The Basics of MRE........................... 2-20
2.9.2.2 Editing Colors With MRE..................... 2-21
2.9.2.3 Editing Fonts With MRE...................... 2-21
2.9.2.4 Locating File Names With MRE................ 2-22
2.9.2.5 Editing Boolean (TRUE/FALSE) Resources With
MRE......................................... 2-22
2.9.2.6 Editing Translation Tables With MRE ........ 2-22
2.9.2.7 The MRE Options Menu........................ 2-22
2.9.2.8 MRE Command Entry........................... 2-23
2.9.2.9 Help on MRE................................. 2-24
2.9.2.10 The MRE Edit Menu........................... 2-24
2.9.2.11 Adding Custom Types; Associating Resources
with Types.................................. 2-24
vii
2.9.2.12 Resources That Modify MRE Behavior.......... 2-25
2.9.2.13 Known Problems With MRE..................... 2-27
2.9.2.14 MOTIFGIF and PICT Viewing Programs.......... 2-27
2.9.2.15 Dog Widget.................................. 2-28
2.10 Toolkit Extensions............................... 2-29
2.10.1 DXmCSText Resources to Specify Input Method ... 2-29
2.10.1.1 DXmNinputMethodType......................... 2-30
2.10.1.2 DXmNinputMethod............................. 2-30
2.10.2 DXmCSText With the XmNblinkRate Resource ...... 2-31
2.10.3 DXmCSTextSetSelection Format Change ........... 2-31
2.10.4 DXmHelpSystem Routine Status Value Changes .... 2-32
2.10.5 DXmNlayoutDirection ........................... 2-33
2.10.5.1 DXmNlayoutDirection in DECwindows Extensions
to Motif.................................... 2-33
2.10.5.2 DXmNlayoutDirection in DECwindows Motif..... 2-35
2.10.6 SVN and Compound String Text Widget
Translations................................... 2-40
2.10.7 SVN-Horizontal Live Scrolling Not Supported ... 2-67
2.10.8 SVN Horizontal Separator Line ................. 2-67
2.11 UIL Extensions................................... 2-67
2.11.1 DXmFormSpaceButtonsEqually Restriction ........ 2-67
2.11.2 UIL Compiler .................................. 2-67
2.12 VAX C Sample Programs............................ 2-67
2.13 VAXstations 3520 and 3540-Problem Running DTM ... 2-68
2.14 X11 Display Server............................... 2-68
2.14.1 100 DPI Fonts Not Available on 75 DPI
Monitors....................................... 2-68
2.14.2 Backingstore Disable-New Feature .............. 2-69
2.14.3 Color Name File-Updated ....................... 2-69
2.14.4 Compatibility Option in Server ................ 2-70
2.14.5 Default Character Processing Correction ....... 2-71
2.14.6 Font Names Now Returned in Lowercase .......... 2-71
2.14.7 Known Problems with the X11 Display Server .... 2-71
2.14.8 Server Infinite Loop Correction .............. 2-71
2.15 X Image Extension (XIE).......................... 2-72
2.16 Xlib Extensions.................................. 2-72
2.16.1 Xlib Client Side Library ...................... 2-73
2.16.2 Xlib Routines ................................. 2-73
2.16.2.1 Ada Bindings File Incomplete................ 2-73
2.16.2.2 Command Procedure Builds .PEN Files......... 2-74
2.16.2.3 Parameter/Protocol Datasize Mismatches...... 2-74
2.16.3 XSelectAsyncEvent and XSelectAsyncInput
Routines ...................................... 2-75
viii
3 Documentation Release Notes
3.1 CDA Documentation................................ 3-1
3.2 VMS DECwindows Motif Documentation............... 3-2
3.3 Corrections to Existing Documentation............ 3-3
3.3.1 DECwindows Companion to the OSF/Motif Style
Guide.......................................... 3-4
3.3.2 DECwindows Extensions To Motif ................ 3-4
3.3.2.1 DXmCSTextReplace Format..................... 3-4
3.3.2.2 XmNmodifyVerifyCallback Resource Callback
Structure................................... 3-4
3.3.3 VMS DECwindows Motif User's Guide ............. 3-5
3.3.4 OSF/Motif Programmer's Reference .............. 3-5
3.3.4.1 Core Reference Page......................... 3-5
3.3.4.2 mwm Reference Page.......................... 3-6
3.3.4.3 RectObj Reference Page...................... 3-6
3.3.4.4 VendorShell Reference Page.................. 3-7
3.3.4.5 VirtualBindings Reference Page.............. 3-7
3.3.4.6 WMShell Reference Page...................... 3-7
3.3.4.7 XmArrowButton Reference Page................ 3-8
3.3.4.8 XmArrowButtonGadget Reference Page.......... 3-8
3.3.4.9 XmBulletinBoard Reference Page.............. 3-8
3.3.4.10 XmCascadeButton Reference Page............. 3-9
3.3.4.11 XmCascadeButtonGadget Reference Page....... 3-9
3.3.4.12 XmCommand Reference Page.................... 3-9
3.3.4.13 XmCreateOptionMenu Reference Page.......... 3-10
3.3.4.14 XmCreatePromptDialog Reference Page........ 3-10
3.3.4.15 XmCreateScrolledText Reference Page........ 3-10
3.3.4.16 XmCreateSelectionDialog Reference Page..... 3-10
3.3.4.17 XmDialogShell Reference Page............... 3-10
3.3.4.18 XmDrawingArea Reference Page............... 3-11
3.3.4.19 XmDrawnButton Reference Page............... 3-11
3.3.4.20 XmFileSelectionBox Reference Page.......... 3-11
3.3.4.21 XmForm Reference Page...................... 3-12
3.3.4.22 XmFrame Reference Page..................... 3-12
3.3.4.23 XmGadget Reference Page.................... 3-12
3.3.4.24 XmGetPixmap Reference Page................. 3-12
3.3.4.25 XmLabel Reference Page..................... 3-13
3.3.4.26 XmLabelGadget Reference Page............... 3-13
3.3.4.27 XmList Reference Page...................... 3-13
3.3.4.28 XmMainWindow Reference Page................ 3-13
3.3.4.29 XmMenuShell Reference Page................. 3-14
3.3.4.30 XmMessageBox Reference Page................ 3-14
3.3.4.31 XmProcessTraversal Reference Page.......... 3-14
ix
3.3.4.32 XmPushButton Reference Page................ 3-14
3.3.4.33 XmPushButtonGadget Reference Page.......... 3-15
3.3.4.34 XmRowColumn Reference Page................. 3-15
3.3.4.35 XmScale Reference Page..................... 3-16
3.3.4.36 XmScrollBar Reference Page................. 3-16
3.3.4.37 XmScrolledWindow Reference Page............ 3-17
3.3.4.38 XmSelectionBox Reference Page.............. 3-17
3.3.4.39 XmSeparator Reference Page................. 3-17
3.3.4.40 XmSeparatorGadget Reference Page........... 3-17
3.3.4.41 XmString Reference Page.................... 3-18
3.3.4.42 XmText Reference Page...................... 3-18
3.3.4.43 XmTextField Reference Page................. 3-18
3.3.4.44 XmTextSetTopCharacter Reference Page....... 3-18
3.3.4.45 XmToggleButton Reference Page.............. 3-19
3.3.4.46 XmToggleButtonGadget Reference Page........ 3-19
3.3.4.47 XmVaCreateSimpleOptionMenu Reference Page.. 3-20
4 Version 1.1 New Features
4.1 DECsound ........................................ 4-1
4.1.1 Prerequisites ................................. 4-1
4.1.2 Starting DECsound ............................. 4-2
4.1.2.1 Session Manager............................. 4-2
4.1.2.2 Enhanced CDA Viewer......................... 4-3
4.1.2.3 Integration With Mail ...................... 4-3
4.1.2.4 DCL Command Line............................ 4-4
4.1.3 Using LiveLink Connections .................... 4-8
4.1.3.1 LiveLink Connections from DECwrite.......... 4-8
4.1.3.2 LiveLink Connections from DECpresent........ 4-10
4.1.4 Online Help for DECsound ...................... 4-11
4.1.5 Problems and Restrictions ..................... 4-11
4.2 VMS DECwindows Motif Help System................. 4-12
4.3 New MIT Utilities................................ 4-13
Index
x
Tables
2-1 DECterm Supported Logical Names ............... 2-7
2-2 Virtual Keysyms for VMS Servers ............... 2-12
2-3 DXmNinputMethodType Values .................... 2-30
2-4 DXmHelpSystem Routine Status Values ........... 2-32
2-5 DXmNlayoutDirection Values .................... 2-34
2-6 DXmNlayoutDirection Values for the
DXmCreateScrolledCSText and DXmCreateCSText
Functions...................................... 2-35
2-7 DXmNlayoutDirection Effect on Widget
Components..................................... 2-36
2-8 DXmSvn Widget Button Syntax Translations ...... 2-40
2-9 DXmSvn Widget Keyboard Syntax Translations .... 2-41
2-10 Action Routines for DXmSvn Widget ............ 2-43
2-11 DXmCSText Widget Button Syntax Translations ... 2-47
2-12 DXmCSText Widget Action Routines ............. 2-50
2-13 Additional DXmCSText Behavior ................. 2-66
2-14 Routine Arguments ............................. 2-74
4-1 Electrical Specifications ..................... 4-2
4-2 Audio Editor Options .......................... 4-5
4-3 Qualifiers to Control DECsound Sessions ....... 4-6
4-4 Bitmap Options ................................ 4-14
4-5 atobm Options ................................. 4-15
4-6 bmtoa Option .................................. 4-16
4-7 xev Options ................................... 4-17
4-8 xlsatoms Options .............................. 4-18
4-9 xlsfonts Options .............................. 4-18
4-10 xlswins Options ............................... 4-20
4-11 xmag Options .................................. 4-21
4-12 xmodmap Options ............................... 4-23
4-13 xprop Options ................................. 4-24
4-14 xrdb Options .................................. 4-29
4-15 xrefresh Options .............................. 4-32
4-16 xset Options .................................. 4-33
4-17 xsetroot Options .............................. 4-38
4-18 xwd Options ................................... 4-40
4-19 xwininfo Options .............................. 4-41
xi
4-20 xwud Options .................................. 4-43
xii
_________________________________________________________________
Preface
This document describes software problems, corrections, and
restrictions, as well as documentation changes that pertain
to VMS DECwindows Motif Version 1.1. It also describes
software problems, corrections, and restrictions, as
well as documentation changes from VMS DECwindows Motif
Version 1.0 that have not been updated in the existing
documentation. A margin note is used to specify which
version applies to each release note.
With VMS DECwindows Motif Version 1.1, extensive changes
to the code paths have been made to help developers more
easily translate this product into multiple languages.
In this manual, DECwindows XUI refers to the VMS DECwindows
product prior to VMS DECwindows Motif Version 1.0.
DECwindows Motif refers to the existing VMS DECwindows
Motif product.
Intended Audience
This document is intended for all users of VMS DECwindows
Motif.
Document Structure
This manual contains the following:
o Chapter 1 contains release notes intended for general
users of VMS DECwindows Motif Version 1.1.
o Chapter 2 contains release notes intended for
application and system programmers.
xi
o Chapter 3 describes the contents of the VMS DECwindows
Motif documentation set. Additions and corrections to
the VMS DECwindows Motif documentation set are included
in this chapter.
Version 1.1.1 corrections to Version 1.1 of the
OSF/Motif Programmer's Reference are also documented.
o Chapter 4 describes new features for VMS DECwindows
Motif Version 1.1, including the new VMS DECwindows
Motif Help, the ability to use DECsound, and the new MIT
utilities.
Associated Documents
See Chapter 3 for a description of all VMS DECwindows Motif
Version 1.1 documentation.
Conventions
The following conventions are used in this manual:
mouse The term mouse is used to refer to
any pointing device, such as a mouse,
a puck, or a stylus.
MB1 (Select) MB1 indicates the left mouse button,
MB2 (Drag) MB2 indicates the middle mouse
MB3 (Menu) button, and MB3 indicates the right
mouse button. (The buttons can be
redefined by the user.)
Ctrl+X A sequence such as Ctrl+X (or Ctrl/X)
indicates that you must hold down
the key labeled Ctrl while you press
another key or a pointing device
button.
PF1 X A sequence such as PF1 X indicates
that you must first press and release
the key labeled PF1, then press and
release another key or a pointing
device button.
<Return> In examples, a key name is shown
enclosed in a box to indicate that
you press a key on the keyboard.
xii
boldface text Boldface text represents the
introduction of an argument or a
new term.
Boldface text is also used to show
user input in online versions of the
book.
xiii
1
_________________________________________________________________
General User Release Notes
This chapter contains information about VMS DECwindows
Motif Version 1.1 that is of interest to general users.
1.1 Version 1.1 Specific Release Notes
The release notes in this manual are cumulative from VMS
DECwindows Motif Version 1.0 and still apply to Version
1.1. The following sections contain general user release
notes that pertain specifically to VMS DECwindows Motif
Version 1.1:
o Section 1.3, Monitor Screen Width Customized Login Logos
o Section 1.4.4.4, CDA Viewer Supports DECfonts Version
1.2
o Section 1.4.4.5, Paper Size... Button Renamed
o Section 1.4.5.3, DECterm Controller and LOGINOUT
o Section 1.4.5.4, DECterm Graphics
o Section 1.4.5.5, DECterm Initialization
o Section 1.4.5.7, DECterm Resource Usage
o Section 1.4.5.8, DECterm Text
o Section 1.4.5.9, Diagnostic Crash File and Messages-New
and Enhanced
o Section 1.4.5.10, Displaying Version Information About
DECterm
o Section 1.4.5.11, Keyboards and Languages
o Section 1.6.5.11, Invoking Help for Mwm
o Section 1.6.5.14, Multiscreen Systems With Mixed
Monitors
General User Release Notes 1-1
General User Release Notes
1.1 Version 1.1 Specific Release Notes
o Section 1.4.5.14, DECterm PC Interoperability
Restrictions
o Section 1.4.5.15, ReGIS and SIXEL
o Section 1.4.5.16, ReGIS Locator Report
o Section 1.4.5.19, Screen Print Services
o Section 1.4.6.1, Application Identifier Name
o Section 1.4.6.2, Application Startup Error
o Section 1.4.6.3, Work-In-Progress Box
o Section 1.4.8.3, Private Colormaps
o Section 1.5, DECW$CDPLAYER Enhanced
o Section 1.6.4, International Keyboard Performance
Improvement
o Section 1.6.7, New Mwm Default Font
o Section 1.8.1, Change in Bindings for Lists in FileView
and Session Manager
o Section 1.8.4, FileView Starts Detached Processes by
Default
o Section 1.9, Troubleshooting Information
1.2 Access Control-Not Explicitly Enabled by Default
V1.0 DECwindows Motif does not enable access control by default
but rather uses whatever access control is set by the
server. The VMS server enables access control at startup
time.
To force the DECwindows Session Manager to explicitly
enable or disable access control 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 will
neither enable nor disable access control.
1-2 General User Release Notes
General User Release Notes
1.2 Access Control-Not Explicitly Enabled by Default
In most cases it should not be necessary to define the
logical name.
1.3 Monitor Screen Width Customized Login Logos
V1.1 By default, if there is no DECwindows Motif license for
the SYSTEM account DECwindows does not display customized
login logos. This is a problem on systems with personal use
DECwindows Motif licenses that do not include SYSTEM on the
list of authorized Motif users.
To display a customized logo without a DECwindows Motif
license for SYSTEM, add the following definition to the
SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM file.
$ DECW$LOGINLOGOSUB == "TRUE"
________________________ Note ________________________
If the file does not exist, copy it from
SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.TEMPLATE.
______________________________________________________
After editing the setup file, restart VMS DECwindows Motif
using the following command:
$ @SYS$MANAGER:DECW$STARTUP RESTART
VMS 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 the X connection is opened.
1.4 VMS DECwindows Motif Application Notes
This section provides information about VMS DECwindows
Motif applications.
1.4.1 Bookreader
This section contains information about the VMS DECwindows
Bookreader.
General User Release Notes 1-3
General User Release Notes
1.4 VMS DECwindows Motif Application Notes
1.4.1.1 DECW$BOOKSHELF Logical Name Cannot Reference Search List
V1.0 If your definition of DECW$BOOKSHELF references a search
list logical name, the contents of your library might be
displayed twice:
$ DEFINE DECW$BOOK MYDISK1:[DECW$BOOK], MYDISK2:[DECW$BOOK]
$ DEFINE DECW$BOOKSHELF DECW$BOOK:-
_$ MY_SHELF_LIBRARY.DECW$BOOKSHELF
To correct this problem, terminate the DECW$BOOKSHELF
logical name with a semicolon (;) as follows:
$ DEFINE DECW$BOOKSHELF DECW$BOOK:-
_$ MY_SHELF_LIBRARY.DECW$BOOKSHELF;
1.4.1.2 Formal Examples, Figures, and Tables
V1.0 The following problems exist with formal tables, figures,
and examples (called formal topics) in Bookreader.
o An excessive amount of white space is allocated at the
bottom of formal topics.
o Occasionally, after you resize some formal topics,
Bookreader creates a scroll bar when none is needed.
Resize the figure again to correct the problem.
1.4.1.3 Incorrect Text in Message
V1.0 In the Topic window, Bookreader displays incorrect text
that directs you to click on a hotspot to display a figure,
table, or example. With DECwindows Motif, you must double
click on a hotspot.
For example, the text for a figure should read FIGURE:
DOUBLE CLICK TO DISPLAY FIGURE.
This problem will be corrected in a future version of VMS
DECwindows Motif.
1.4.2 Calendar
V1.0 The following problems exist with Calendar:
o Calendar incorrectly issues an error message when
LinkWorks Services are turned off.
o Calendar does not remove Link highlighting when Links
are made inactive.
1-4 General User Release Notes
General User Release Notes
1.4 VMS DECwindows Motif Application Notes
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 in the Month display
becomes disabled.
1.4.3 Cardfiler
V1.0 You cannot modify or save DECwindows Motif card files with
a DECwindows XUI version of the Cardfiler.
The card file format of the DECwindows Motif 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. Hence,
all LinkWorks connections that are made to that card file
might be lost or become 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 totally 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.
1.4.4 CDA Viewer/CDA PostScript Converter
This section contains information about the CDA Viewer and
the CDA PostScript Converter.
1.4.4.1 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 hang without
displaying an error message until you click on the Cancel
button. This problem will also occur if you accidentally
specify a non-PostScript file with the format .PS 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.
Be careful to specify only valid PostScript files to the
CDA Viewer when specifying the .PS format.
General User Release Notes 1-5
General User Release Notes
1.4 VMS DECwindows Motif Application Notes
1.4.4.2 CDA Viewer/CDA PostScript Converter-Graphics Objects
V1.0 If the CDA Viewer or the CDA PostScript Converter
encounters a document that contains a graphics object with
a very large number of points, it might generate a limit
check error from either X or the PostScript Printer.
If this error occurs, you should modify your DDIF document
so that the graphic object has fewer points.
This problem will be corrected in a future version of the
CDA Viewer and CDA PostScript Converter.
1.4.4.3 CDA Viewer/CDA PostScript Converter-Page Problem
V1.0 If the CDA Viewer or the CDA PostScript Converter is used
to either view or convert a DECpresent Version 1.0 file to
PostScript, some of the pages might appear blank or solid
black.
This is a problem with the DECpresent Version 1.0 style
files and will be corrected in a future version of
DECpresent. To work around this problem, view or convert
the document to PostScript using the DECpresent File menu.
1.4.4.4 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 12pt for this text.
To correct this problem, use DECwrite or DECpresent in
conjunction with DECfonts Version 1.2 to modify the font.
1.4.4.5 Paper Size... Button Renamed
V1.1 The Paper Size... button in the Open File Selection box has
been renamed to Display Options... with DECwindows Motif
Version 1.1.
The functions invoked by that button are the same.
1-6 General User Release Notes
General User Release Notes
1.4 VMS DECwindows Motif Application Notes
1.4.4.6 Watch Progress Can Cause CDA Viewer to Lose Expose Events
V1.0 If you use the CDA Viewer to view PostScript documents and
have selected the Watch Progress option, the CDA Viewer can
miss expose events for the window.
This problem occurs more often on high performance
workstations such as the VAXstation 3500 series and
VAXstation 3100 Model 76 series workstations. If this
problem does occur, turn off the Watch Progress option
in the Paper Size dialog box to correct the problem.
1.4.5 DECterm
This section contains information about DECterm.
1.4.5.1 Condensed German Standard Font Not Available
V1.0 There is no condensed version of the German Standard (GS)
font. 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.
1.4.5.2 Cursor Blink Not Disabled in DECterm Widget
V1.0 DECterm widgets do not properly receive focus notification
events.
Applications that use the DECterm widget cannot determine
when cursor blink should be enabled and disabled. Cursor
blink might be enabled continuously for these windows, even
when minimized to an icon.
1.4.5.3 DECterm Controller and LOGINOUT
V1.1 The DECterm controller is now initialized by running
LOGINOUT before the controller starts. This change has
the following impact:
o The controller runs the LOGIN files. All logical names
defined in a LOGIN file, including DECW$USER_DEFAULTS,
are used by the controller.
o The process quotas for the controller are set by the
values in SYSUAF instead of SYSGEN. This affects the
total number of DECterm windows that you can create.
General User Release Notes 1-7
General User Release Notes
1.4 VMS DECwindows Motif Application Notes
If the system default quotas are lower than your user
quotas, you can now create more DECterm windows.
1.4.5.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 system 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, bring them up 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
window might not look the same when it is redrawn as
it did when the picture was first drawn.
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.
o The following ReGIS features are not implemented:
- Command Display mode
- Scrolling
- Output cursors
The mouse is used as the input cursor, but the shape
cannot be changed with the S(C(I)) command.
1-8 General User Release Notes
General User Release Notes
1.4 VMS DECwindows Motif Application Notes
1.4.5.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 VMS 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 system-wide 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.
If you attempt to resize a DECterm window before you see a
prompt in the window, the window might disappear.
General User Release Notes 1-9
General User Release Notes
1.4 VMS DECwindows Motif Application Notes
1.4.5.6 DECterm Not a Complete VT330/VT340 Terminal Emulator
V1.0 As described in the Software Product Description (SPD),
DECterm incorporates some of the features of the VT330
and VT340 series video terminals, such as ReGIS and SIXEL
graphics. It does not provide complete VT330 and VT340
terminal emulation.
1.4.5.7 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 crash 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.
1.4.5.8 DECterm Text
V1.1 The following information is specific to DECterm text:
o User-loadable characters (DRCS), local mode, and control
representation mode 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.
1.4.5.9 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.
1-10 General User Release Notes
General User Release Notes
1.4 VMS DECwindows Motif Application Notes
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.
Normal DECterm diagnostics are still enabled by defining a
logical name DECW$TERMINAL_OUTPUT to point to a file.
1.4.5.10 Displaying Version Information About DECterm
<MARGIN_NOT>(V1.1)
For VMS DECwindows Motif Version 1.1, when you select On
Version from the Help menu, a window displays the following
information instead of the current version and copyright
information:
" 1 About DECterm
1.2.4 On Version
To display copyright and version information about DECterm,
choose On Version from the Help menu.
Additional topics :
. Overview of DECterm
"
To display the current version and copyright information,
select About DECterm under the Topic window.
This problem will be corrected in a future version of VMS
DECwindows Motif.
1.4.5.11 Keyboards and Languages
V1.1 The following information is specific to DECterm keyboards
and languages:
o To start a compose sequence on an LK201 keyboard, you
must press Compose+space bar. The Compose key is a
modifier and is used like a Shift key.
o Keyclick Volume, Auto Repeat, Keyboard Type (national
keyboards), Keyboard Usage mode (data processing
/typewriter mode), and Caps Lock/Shift Lock should be
changed by selecting Keyboard... from the Options menu
General User Release Notes 1-11
General User Release Notes
1.4 VMS DECwindows Motif Application Notes
in the Session Manager on a workstation-wide 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
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. On VT320, VT330, and VT340 terminals, the
Keyclick Volume option is disabled.
1.4.5.12 Monitor Screen Width Determines Default Font Size
V1.0 There are three font sets available for 100 dpi 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 set on a small monitor, place the
following commands in the DECW$TERMINAL_DEFAULTS.DAT file:
DECW$TERMINAL.main.terminal.littleFontSetName:
-DEC-terminal-*-r-*--*-100-100-100-c-*-*-*
DECW$TERMINAL.main.terminal.bigFontSetName:
-bitstream-terminal-*-r-*--*-140-100-100-c-*-*-*
1.4.5.13 Nohangup and Virtual Terminal Support
V1.0 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; therefore, the /NOHANGUP qualifier is no longer
supported in DECterm. In previous releases, this feature of
the driver was often used for directing debugger output to
a separate window.
1-12 General User Release Notes
General User Release Notes
1.4 VMS DECwindows Motif Application Notes
The driver also no longer supports the TT2$M_DISCONNECT
bit that is 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 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 establish a session that uses a virtual terminal, enter
the following command (note that the /DEFINE qualifier
is not required), establish focus to the newly created
DECterm, press Return and log in:
$ CREATE/TERMINAL/NOPROCESS
1.4.5.14 DECterm PC Interoperability Restrictions
V1.1 The following interoperability restrictions apply when
using DECterm on a PC system:
o The DECterm window is not sized properly on the PC
screen. Initially, the DECterm window is located
partially off the screen and is larger than the PC
screen. You must manually center and resize the window.
To make the window fit on the screen, choose Window...
from the Options menu. Select Condensed Font (132
columns) and click on the OK button. To save the change,
select Save Options from the Options menu.
o When the Backspace toggle button is enabled, pressing
the backspace key produces no response on the PC system.
To prevent this problem, select the Delete setting for
this toggle button.
General User Release Notes 1-13
General User Release Notes
1.4 VMS DECwindows Motif Application Notes
o The Comma Key Sends (,<) option does not work on the PC.
Pressing the Comma key produces a comma, but pressing
Shift/, produces the number 9.
To prevent this problem, select the Comma Key Sends (,,)
option of this toggle button.
o The Tilde Key Sends ESC option does not work on the PC.
When this option is enabled, pressing the Tilde (~) key
does not operate as an escape key.
To prevent this problem, select the Tilde Key Sends (`~)
option of this toggle button.
o DECterm does not support function, editing, and keypad
keys on non-LK201 keyboards. This is a problem for PC-
based and MAC-based X servers. These servers do not
generate all the KEYSYM functions the LK201 supports and
not all DECterm functions are accessible. For example,
you cannot run EDT in screen mode from DECterm if you
are not using an LK201 keyboard.
You might not be able to run programs that depend on
those keys if your keyboard does not include certain
LK201 keys. There are, however, some functional
equivalents for these keys. For example, EDT has a
line editing mode in which commands can be entered in
alphanumeric form rather than with function keys.
If a program requires function keys, you can manually
enter the escape sequences for the keys. For example,
press <ESC>Ow for the KP7 key and press Ctrl+3 or Ctrl+[
for the escape function. The escape sequences for each
key are listed in the DECterm Text Programming Manual.
1.4.5.15 ReGIS and SIXEL
V1.1 Inadequate initialization and memory leaks have been
corrected for DECterm graphics. DECterm should not
fail when displaying ReGIS and SIXEL images. Displaying
these images, or entering VTX, should not terminate the
controller.
1-14 General User Release Notes
General User Release Notes
1.4 VMS DECwindows Motif Application Notes
1.4.5.16 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[]<CR>, where <CR> is a carriage return (ASCII code 13).
1.4.5.17 /PROCESS=procnam Fails if No Process With Default Name
V1.0 When a new process is created, it is assigned a default
name that is the same as the user name. If there is no
process with the default name and a DECterm is created with
the /PROCESS=procnam switch, the new process will have the
default process name rather than the specified one. If the
/PROCESS=procnam qualifier specifies a process name that is
already in use, creation of the DECterm will succeed, but
creation of the process will fail.
The DCL command CREATE/TERMINAL returns the error message:
Duplicate process name
1.4.5.18 Queued Printing Requires Name in File Field
V1.0 The Queued Printer feature in the Printer Options dialogue
box queues files to print only if you enter a file name in
the file name entry box. A file with the name specified in
the file field is generated in SYS$LOGIN whenever printing
is selected with the Queued Printing option enabled.
1.4.5.19 Screen Print Services
V1.1 To use screen print services to a port device, you must
have read and write privileges. You cannot use screen
print by allocating the device, since the controller task
requires access to the device. Set the device to WORLD:RW.
To use the printer port on a VAX 3100, the following
command must be entered from a privileged account or
included in the system startup file:
$ SET PROTECTION=WO:RW TTA3:/DEVICE
General User Release Notes 1-15
General User Release Notes
1.4 VMS DECwindows Motif Application Notes
1.4.5.20 Simultaneous Multiple Language Performance-Resource
Demanding
V1.0 DECterm is a multithreaded application that permits
creating multiple DECterms from a single client task called
a controller. The controller is started automatically when
the first DECterm is requested. A controller supports only
one language at a time. For simultaneous multiple language
support, an additional controller must be started for each
language (and one for each display, if the target device is
multihead). Controllers are resource demanding, and optimum
performance in a multiple-language environment requires
additional resources.
1.4.6 LinkWorks
This section contains information about LinkWorks Services.
1.4.6.1 Application Identifier Name
V1.1 In the previous release of LinkWorks, the application
identifier name was omitted from the Source and Target
portions of the Complete Link... dialog box. The
application identifier name is supplied for VMS DECwindows
Motif Version 1.1.
1.4.6.2 Application Startup Error
V1.1 In the previous release of LinkWorks, the following
message was displayed when a LinkWorks path was followed
by selecting Step Forward from the Link menu:
Application startup error
With VMS DECwindows Motif Version 1.1, the message is no
longer displayed when following a LinkWorks path.
1.4.6.3 Work-In-Progress Box
V1.1 When you select the Go To or Visit operations from the
Link menu, an application is invoked to display and edit
the destination of the link. If the application is already
running, the destination object appears immediately. If the
application has to be started, display of the destination
object might be delayed because of the need to start the
application. This delay might be up to a minute or more
depending on the application, the system resources, and the
system activity.
1-16 General User Release Notes
General User Release Notes
1.4 VMS DECwindows Motif Application Notes
With VMS DECwindows Motif Version 1.1, a Work-In-Progress
box appears for a lengthy response to a LinkWorks
navigation request. This box contains an OK button, which
you can press to dismiss the box. If you do not dismiss
the box, it automatically disappears when the navigation
request is completed.
1.4.7 Mail Restrictions and Problems
V1.0 The following problems exist in Mail:
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.
1.4.8 Paint
This section contains information about the Paint
application.
1.4.8.1 Enhancing the Performance of Some Paint Operations
V1.0 On GPX systems, Paint might appear slow even with basic
operations such as drawing a brush stroke. The reason is
that 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. Resizing to the least possible image area
significantly reduces the amount of pixmap memory required.
General User Release Notes 1-17
General User Release Notes
1.4 VMS DECwindows Motif Application Notes
1.4.8.2 Editing Color Images
V1.0 When editing 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.
1.4.8.3 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 using the default window manager focus
policy.
For more information about changing focus and colormaps
with the Window Manager, see the VMS DECwindows Motif
User's Guide or the OSF/Motif Programmer's Guide.
1.4.8.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.
1.4.9 Print Screen
This section contains information about the Print Screen
application.
1.4.9.1 Keyboard Mnemonics Not Implemented
V1.0 Keyboard mnemonics have not been implemented in this
version of Print Screen.
Operation of Print Screen is possible through keyboard-
traversal key sequences and by using the mouse.
1-18 General User Release Notes
General User Release Notes
1.4 VMS DECwindows Motif Application Notes
1.4.9.2 Options Menu
V1.0 The Options menu item has the following limitations:
o The PostScript page size options are not functional in
this release.
o The OK, Cancel, and Help buttons on the PostScript
options and SIXEL Options dialog boxes might appear
off center.
1.4.9.3 Print Orientation Option-Not Functional
V1.0 The Print Orientation (with Portrait and Landscape
settings) option has been added to Print Screen, however,
it is not yet functional.
1.4.9.4 Print Screen Default Icon-Large
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 icon size, only a
portion of this icon is viewable.
1.4.9.5 Queue Options Dialog Box
V1.0 The Queue Options dialog box has the following limitations.
o The settings for the options listed in the Queue Options
dialog box do not operate correctly. You should not
change the settings since most of them do not work. In
previous versions of DECwindows, the Options... button
was disabled because of this problem.
The only supported options are to select a queue and
then to select the OK or Cancel buttons.
o 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.
General User Release Notes 1-19
General User Release Notes
1.4 VMS DECwindows Motif Application Notes
1.4.9.6 Reduce Only Setting-Not Functional
V1.0 The Reduce Only radio button in the Fit-To-Paper option is
not yet functional.
1.4.9.7 Resource Values-Changed
V1.0 The resource values in the file DECW$PRINTSCREEN.DAT now
are identical to the labels on the associated buttons.
This permits the file to be read and edited by users in any
locale.
This resulting incompatibity makes existing saved values in
DECW$PRINTSCREEN.DAT unusable to Print Screen. To use these
saved values, print out the old file for reference and then
select and save the desired options using the Print Screen
user interface.
1.5 DECW$CDPLAYER Enhanced
V1.1 With DECwindows Motif Version 1.1, the DECW$CDPLAYER
application has been enhanced to improve the user interface
due to the Motif widgets and UIL.
To use the new version, you must copy DECW$CDPLAYER.UID
and DECW$CDPLAYER.DAT to either DECW$USER_DEFAULTS or
DECW$SYSTEM_DEFAULTS.
The DECW$CDPLAYER application requires PHY_IO and
DIAGNOSE privileges to operate the compact disk player
hardware. Either your process or the image must have these
privileges.
1.6 Motif Window Manager (Mwm) Notes
This section contains information about the VMS DECwindows
Motif Window Manager.
1.6.1 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.
1-20 General User Release Notes
General User Release Notes
1.6 Motif Window Manager (Mwm) Notes
With the Motif binding, you can nolonger 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 re-enable 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.
1.6.2 DECwindows XUI Applications
V1.0 The resource Mwm*useDECMode allows earlier 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).
1.6.3 Icons
V1.0 Icons with bitmaps of depth greater than 1 are no longer
supported. The Window Manager reports a warning only if
the Mwm*ICCCMCompliant resource is set to TRUE and it then
attempts to display the icon. This resource is turned off
by default.
1.6.4 International Keyboard Performance Improvement
V1.1 With VMS DECwindows Motif Version 1.1, performance is
improved for international keyboards when you customize
Mwm. Select the For International Keyboards option, or the
Ignore The Mod Keys option from Workspace Options, or set
the resource Mwm*ignoreModKeys to TRUE. Mwm only ignores
the Mod keys that are used by the current keyboard. Mwm
also automatically updates all the window bindings if the
you change the keyboard using the Keyboard Options from the
Session Manager window.
In Version 1.0, if the Mwm*ignoreModKeys resource was
set, Mwm would ignore all the Mod keys, regardless of
the current keyboard. This degradedthe response to the
keyboard and mouse. For backward compatibility, you can
still achieve this by setting the Mwm*ignoreAllModKeys
resource to TRUE.
General User Release Notes 1-21
General User Release Notes
1.6 Motif Window Manager (Mwm) Notes
1.6.5 Known Problems with Motif Window Manager
This section contains information about known problems with
the Motif Window Manager.
1.6.5.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.
1.6.5.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.
1.6.5.3 Color-Related Resources for Monochrome
Monitors-Customizing
V1.0 Mwm 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.
1.6.5.4 Customizing Colors on 4-Plane Displays
V1.1 There are a limited number of colors on a 4-plane display.
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.
1-22 General User Release Notes
General User Release Notes
1.6 Motif Window Manager (Mwm) Notes
1.6.5.5 Customized 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.
1.6.5.6 DECwindows XUI Modal Dialog Boxes
V1.0 There are several problems 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, then the focus might not
automatically revert to its parent.
1.6.5.7 Icon Box-Customizing
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.
1.6.5.8 Icon Box Colors on Monocrome and Gray-Scale Systems
V1.0 Customizing the icon box background color for monochrome
and gray-scale monitors does not work properly unless you
have a multihead system with different monitor types. You
cannot change the default icon box background color for
monochrome and gray-scale systems.
1.6.5.9 Icon Box Moved 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. Then you can move
the window back onto the screen.
1.6.5.10 Icon Title Truncated
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. First, you can make the icon
active. Second, you can customize your icons using the Icon
Options menu item and change the width of the icons.
General User Release Notes 1-23
General User Release Notes
1.6 Motif Window Manager (Mwm) Notes
1.6.5.11 Invoking Help for Mwm
V1.1 If you invoke Help for Mwm on screen 1 of a multiscreen
system, Help fails and generates an error.
To correct this problem, invoke Help for Mwm on screen 0
only. This problem will be addressed in a future update.
1.6.5.12 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 into
another system with that monitor type or directly edit the
resource files.
1.6.5.13 Multiline Icon Text Not Centered
V1.0 The Window Manager does not center all the lines of a
multiline icon title.
1.6.5.14 Multiscreen Systems With Mixed Monitors
V1.1 If you have a multiscreen system with mixed monitor types,
such as one color and one monochrome monitor, the Window
Manager dialog boxes might not appear with the correct
colors on the second screen. For example, if screen one is
a monochrome monitor, the text might not be readable.
To correct this problem, you should modify the colors for
screen 0 to create enough contrast between the foreground
and background colors so that they can be interpreted
as black-on-white or white-on-black for the monochrome
monitor.
This will be fixed in a future release in conjunction with
the R5 intrinsics.
1.6.5.15 Next Window on Multihead System
V1.0 On a multihead system, if you continuously cycle the
windows using Ctrl+MB1 or by selecting Next Window,
eventually the cycling does not work properly.
1-24 General User Release Notes
General User Release Notes
1.6 Motif Window Manager (Mwm) Notes
1.6.5.16 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.
1.6.5.17 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.
1.6.5.18 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.
1.6.6 Motif Window Manager-Restarting
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 how the window is restarted
for your system.
In the future, the restart method might change to
dynamically check which parameters were passed to the
Window Manager when it was initially started.
1.6.7 New Mwm Default Font
V1.1 The default font for Mwm is now the same as the default
font for the DECwindows toolkit. This font is not as
condensed and is more readable. You can change back to the
Version 1.0 font by modifying DECW$MWM.DAT and replacing
Menu-Medium with Helvetica-Bold.
1.7 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
SYS$COMMON:[VUE$LIBRARY.USER] directory. Product-specific
profile files should be named by appending the product
General User Release Notes 1-25
General User Release Notes
1.7 Public Profiles for Layered Products
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 the VMS DECwindows Motif User's
Guide.
1.8 Session Manager and FileView
This section contains information about the Session Manager
and FileView.
1.8.1 Change in Bindings for Lists in FileView and Session
Manager
V1.1 With VMS DECwindows Motif Version 1.1, the list windows in
FileView and the Session Manager are more consistent with
the default Motif toolkit for keyboard and mouse actions.
The file lists are located in the main FileView window
and the Work in Progress box. Actions that have changed
include:
o Selecting multiple discontiguous files
o Using Ctrl+MB1 instead of Shift+MB1
1.8.2 EWS Users Must Upgrade to EWS Version 1.0A
V1.0 VAXELN Window Server (EWS) users must upgrade to EWS
Version 1.0A to use DECwindows Motif Version 1.0. If you
end a session while using EWS Version 1.0, the server
crashes. The login box does not appear unless the server
is explicitly restarted.
1.8.3 FileView DELETE Functionality-Changed
V1.0 Previously 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 only deletes the latest version of a file that ends
with a semicolon.
1-26 General User Release Notes
General User Release Notes
1.8 Session Manager and FileView
In DECwindows Motif, if you use FileView's DELETE command
and you specify a file with a semicolon at the end,
FileView now deletes only the latest version of the file.
1.8.4 FileView Starts Detached Processes by Default
V1.1 With VMS DECwindows Motif Version 1.0, users often exceeded
their process quota because the default was SUBPROCESS.
With VMS DECwindows Motif Version 1.1, the default process
type for many applications started by FileView and the
Session Manager is DETACHED. The implication of this change
is that the SYS$MANAGER:SYLOGIN.COM and SYS$LOGIN:LOGIN.COM
command procedures are executed during application startup.
Extensive login command procedures degrade application
startup.
To enhance application startup, you can conditionalize the
SYLOGIN.COM and LOGIN.COM command procedures to execute
only the commands required for application startup.
Commands that should be executed include the redefinition
of DECW$USER_DEFAULTS, if present, and other logical name
definitions referenced in a DECwindows application. You can
add the following lines to the SYLOGIN.COM and LOGIN.COM
files after those application startup commands.
$ 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.
1.8.5 User Default Resource File
V1.0 During Session Manager startup, the user default resource
file DECW$XDEFAULTS.DAT and all session resource files
are now read from the DECW$USER_DEFAULTS: directory. This
is a change from previous versions when the resource file
was read from the SYS$LOGIN: directory. By default, the
DECW$USER_DEFAULTS: directory points to the SYS$LOGIN:
directory, but you can change this by defining the logical
General User Release Notes 1-27
General User Release Notes
1.8 Session Manager and FileView
name DECW$USER_DEFAULTS in your LOGIN.COM or DECW$LOGIN.COM
file.
1.8.6 Session Manager and FileView-Problems
V1.0 The following are known limitations for Session Manager and
FileView:
o You must reselect Autostart selections after upgrading
to DECwindows Motif Version 1.0. Previous Autostart
customization is not used in this version of DECwindows
Motif.
o Some dialog boxes include FileView in the title bar and
use FileView icons, even though they are invoked from
the Session Manager.
o The function of creating a new view by pressing the
shift key while clicking MB1 on a directory is not
implemented in this version. Use the New View... menu
item to create a new view.
1.8.6.1 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.
1.8.7 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).
1-28 General User Release Notes
General User Release Notes
1.8 Session Manager and FileView
One workaround for the problem is to restart DECwindows
on each workstation in a batch job that runs during
off-hours.
If you stop the Session Manager process be sure and restart
(if you have system manager privileges) DECwindows with the
following command:
$@SYS$MANAGER:DECW$STARTUP RESTART
1.9 Troubleshooting Information
V1.1 The VMS DECwindows Motif Version 1.1 kit contains a file
that explains some of the common problems that you might
encounter while using VMS DECwindows and provides general
troubleshooting techniques. The name of this file is
TROUBLESHOOTING_GUIDE.TXT and it can be found in SYS$HELP.
1.10 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 the possible results:
- Facility codes do not match.
- Identifiers are the same.
- Second identifier is older than the first.
- Second identifier is newer then the first.
o DECW$VERSIONS.COM
General User Release Notes 1-29
General User Release Notes
1.10 Version Checking Command Files
A convenient 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).
1-30 General User Release Notes
2
_________________________________________________________________
Programmer Release Notes
This chapter contains information about VMS DECwindows
Motif Version 1.1 that is of interest to programmers.
2.1 Version 1.1 Specific Release Notes
The release notes in this manual are cumulative from VMS
DECwindows Motif Version 1.0 and still apply to Version
1.1. The following sections contain programmer release
notes that pertain specifically to VMS DECwindows Motif
Version 1.1:
o Section 2.2, Adding POSIX Support to DECwindows
Transports
o Section 2.4.1, Controller Communication and Startup
o Section 2.4.2, DECterm Controller MUTEX Hang Bug
o Section 2.4.3, DECterm Logical Names
o Section 2.4.3.1, DECterm Window Positioning
o Section 2.6.3.10, VAX Format Toolkit Bindings
o Section 2.9, New OSF/Motif Examples
o Section 2.10.1, DXmCSText Resources to Specify Input
Method
o Section 2.10.2, DXmCSText With the XmNblinkRate Resource
o Section 2.10.3, DXmCSTextSetSelection Format Change
o Section 2.10.4, DXmHelpSystem Routine Status Value
Changes
o Section 2.10.5, DXmNlayoutDirection
o Section 2.10.6, SVN and Compound String Text Widget
Translations
o Section 2.10.8, SVN Horizontal Separator Line
Programmer Release Notes 2-1
Programmer Release Notes
2.1 Version 1.1 Specific Release Notes
o Section 2.11.1, DXmFormSpaceButtonsEqually Restriction
o Section 2.11.2, UIL Compiler
o Section 2.15, X Image Extension (XIE)
o Section 2.16.1, Xlib Client Side Library
o Section 2.16.3, XSelectAsyncEvent and XSelectAsyncInput
Routines
2.2 Adding POSIX Support to DECwindows Transports
V1.1 DECwindows-specific transports require code modifications
to support POSIX fork() requirements. If you have written
a specific transport and also plan to implement POSIX
support, you must make the required changes to your
transport source code. This note describes the required
changes.
2.2.1 The 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 file system
are not known to the child.
o Channels that are not shareable or opened through POSIX
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 implementation
has placed certain demands on protected shareable images,
including DECwindows specific 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.
2-2 Programmer Release Notes
Programmer Release Notes
2.2 Adding POSIX Support to DECwindows Transports
Specific transports must acknowledge (on the client side)
that they can be forked. The SYS$POSIX_FORK_CONTROL system
service, described in Section 2.2.2, is provided for this
purpose.
Specific transports do not need to perform any cleanup
work.
2.2.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).
2.3 DEC CDA Base Services
This section contains information about the CDA Toolkit.
Programmer Release Notes 2-3
Programmer Release Notes
2.3 DEC CDA Base Services
2.3.1 DDIF$VIEWSHR Interaction Problems with XUI Applications
V1.0 If you have an existing, working DECwindows XUI application
that is linked directly against DDIF$VIEWSHR and you are
creating CDA Viewer widgets by fetching them as user-
defined widgets from a DRM hierarchy, the fetch fails after
you install DECwindows Motif.
The problem occurs only if your application satisfies all
of the conditions stated previously. The problem does not
occur if you use C calls to create CDA Viewer widgets; the
problem also does not occur if you are not linked directly
to DDIF$VIEWSHR (for example, if you use LIB$FIND_IMAGE_
SYMBOL to load DDIF$VIEWSHR).
If possible, you should upgrade your application to use the
Motif DDIF$VIEWSHR to avoid this problem.
2.3.2 Function Prototypes and Data Type Definitions
V1.0 New function prototypes and data type definitions are now
available when using DEC CDA Base Services.
C include files, which define generic, platform-independent
data types and prototypes, are now available for use when
you are referencing CDA access, user-defined, converter,
or Viewer routines. Use of these files is optional but
strongly recommended to reduce the possibility of argument
or data type mismatches that can result from programming
errors and to improve the portability of CDA applications
among platforms.
The new C include files are listed as follows:
cda$typ.h Defines new, generic data types
cda$ptp.h Prototype definitions for CDA access
routines
dvr$decw_ptp.h Prototype definitions for DECwindows CDA
Viewer routines
dvr$cc_ptp.h Prototype definitions for character cell
CDA Viewer routines
For more information, refer to the Reference Manual in the
DEC CDA Base Services documentation set.
2-4 Programmer Release Notes
Programmer Release Notes
2.3 DEC CDA Base Services
2.3.3 New Item Change Lists for Aggregates
V1.0 DEC CDA Base Services has added new item-change lists for
DDIF$_LW1, DDIF$_LL1, and DDIF$_GLA aggregates.
When reading documents with the CDA access routines
and with the DDIF$_INHERIT_ATTRIBUTES processing option
turned on, applications can now distinguish between items
explicitly present and those present by inheritance in the
DDIF$_LL1, DDIF$_LW1, and DDIF$_GLA aggregates.
To permit programmers to do this, the DEC CDA Base Services
has added aggregate items DDIF$_LW1_ITEM_CHANGE_LIST,
DDIF$_LL1_ITEM_CHANGE_LIST, and DDIF$_GLA_ITEM_CHANGE_
LIST to aggregates DDIF$_LW1, DDIF$_LL1, and DDIF$_GLA
respectively. The item change lists specified by these
items will enumerate the items that were explicitly
specified in the particular aggregate.
2.3.4 User Get or Put Routine Parameter
V1.0 The user get or put routine parameter is no longer
referenced by DDIF Front and Back Ends.
Applications that call CONVERT can provide their own user
get or put routines to perform stream I/O. Applications
provide their own get or put routines by using the item-
list items CDA$_INPUT_PROCEDURE or CDA$_OUTPUT_PROCEDURE.
They can also specify an associated parameter value (via
item-list items CDA$_INPUT_PROCEDURE_PARM and CDA$_OUTPUT_
PROCEDURE_PARM) to be passed to the get or put routine.
Using the DEC CDA Base Services shipped with VMS Version
5.4, applications that converted to or from DDIF or DTIF
format and that provided user get or put routines were
required to pass the actual value of the parameter in the
item list.
In VMS DECwindows Motif Version 1.0, applications must
instead encode the associated parameter item as the
address of a longword containing the value that is
actually to be passed to the get or put routine. In other
words, applications must provide an additional level of
indirection, since the DDIF Front and Back Ends will
dereference the item-list item before calling the user
get or put routine.
Programmer Release Notes 2-5
Programmer Release Notes
2.3 DEC CDA Base Services
To be consistent with this approach, user-written
Converter Front and Back Ends that support stream I/O
should dereference the parameter item before passing it
to the input or output routine. (Stream I/O support is
provided via the items CDA$_INPUT_PROCEDURE and CDA_$INPUT_
PROCEDURE_PARM or CDA$_OUTPUT_PROCEDURE and CDA$_OUTPUT_
PROCEDURE_PARM as passed to the Converter entry points
domain$READ_format and domain$WRITE_format)
Applications that call the CDA Viewer routine DvrViewerFile
also require similar recoding if they provide callback
routine and parameter arguments to DvrViewerFile.
2.4 DECterm
This section contains information about DECterm programming
issues.
2.4.1 Controller Communication and Startup
V1.1 With VMS DECwindows Motif Version 1.1, the mailbox name for
task-to-task communication is stored by using a root window
property instead of a logical name. No more DECW$TERMINAL_
MAILBOX_* system logical names are created. Also, the
DECterm controller is no longer installed with privileges.
2.4.2 DECterm Controller MUTEX Hang Bug
V1.1 If your terminal windows are hung when you run DECterm
and the DECterm controller is in a MUTEX state, define the
following logical name to stop resource wait from occurring
when the controller is initialized:
$ DECW$DECTERM_CTRL_SSRWAIT = 1
You should only define this logical name when the DECterm
controller is hung in a MUTEX state. Other use of this
logical name can have a negative impact on other parts of
the toolkit.
2-6 Programmer Release Notes
Programmer Release Notes
2.4 DECterm
2.4.3 DECterm Logical Names
V1.1 Table 2-1 describes the logical names that are supported by
DECterm for VMS DECwindows Motif Version 1.1.
Table_2-1_DECterm_Supported_Logical_Names__________________
Logical_Name__________Description__________________________
DECW$DECTERM_CTRL_ Required for controller startup.
OPTIONS
DECW$DECTERM_CTRL_ Defines WSEXTENT quota for
WSEXTENT controller.
DECW$DECTERM_CTRL_ Defines WSQUOTA quota for controller.
WSQUOTA
DECW$DECTERM_CTRL_ Defines PSWAPM quota for controller.
PSWAPM
DECW$DECTERM_CTRL_ Sets SSRWAIT flag for controller.
SSRWAIT
DECW$DECTERM_ Quota values are not checked before a
DISABLE_QUOTA_ terminal is created when this is set
CHECKING to 1.
DECW$DECTERM_MEM_ Monitors memory usage in the
DIAG controller.
Used for diagnostics.
DECW$DECTERM_OUTPUT Defines output for DECterm
controller.
______________________Used_for_diagnostics.________________
2.4.3.1 DECterm 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 made
bigger by using the 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 not to move
the DECterm, add the following line to your DECW$TERMINAL_
DEFAULT.DAT file:
DECW$TERMINAL.main.terminal.autoAdjustPosition: off
Programmer Release Notes 2-7
Programmer Release Notes
2.4 DECterm
Another resource is available if the hold screen key is too
slow. Add the following lines to your 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.
2.5 VMS DECwindows Motif Version 1.1 Based on OSF/Motif Release
1.1.3
V1.0 VMS DECwindows Motif Version 1.0 release was based on the
OSF/Motif Release 1.1.1.
V1.1 VMS DECwindows Motif Version 1.1 release is based on the
OSF/Motif Release 1.1.3.
2.6 DECwindows Toolkit
This section contains information about the DECwindows
Toolkit.
2.6.1 Additional Non-C Language Binding Support for Motif
V1.0 Additional language binding support for Motif is supplied
for three languages: Ada, FORTRAN, and Pascal. The files
are in SYS$LIBRARY and are named DECW$MOTIF.ADA for Ada,
DECW$MOTIF.FOR for FORTRAN, and DECW$MOTIF.PAS for Pascal.
2.6.2 Intrinsics Changes from the Digital Version of MIT X11
Release 3 to MIT X11 Release 4
V1.0 This section describes changes in the Intrinsics from
the Digital version of the MIT X11 Release 3 Intrinsics
(Digital Release 3) to the MIT X11 Release 4 Intrinsics
(MIT X11 Release 4).
2-8 Programmer Release Notes
Programmer Release Notes
2.6 DECwindows Toolkit
2.6.2.1 Changes in Routine Interfaces
V1.0 The following changes occur in routine interfaces:
o The names parameter in XtNameToWidget routine differs
in where to begin matching the widget name in the widget
hierarchy. Digital Release 3 expects the first name
in the qualified name to be the "root" widget. MIT X11
Release 4 expects the first name in the qualified name
to be a child of the root widget.
o Digital Release 3 gets the application shell name from
XtInitialize names parameter; MIT X11 Release 4 does
not (it uses NULL). You will need to break XtInitialize
up into its component parts in order to name the shell
widget.
o Digital Release 3 Intrinsics accept a NULL application
context in XtDisplayInitialize and uses the default
application context; MIT X11 Release 4 does not.
o The XtCancelSelectionCallbackProc parameter has been
deleted from calls to XtGetSelectionValueIncremental
and XtGetSelectionValuesIncremental in MIT X11 Release
4. Applications are expected to recognize a canceled
selection by the fact that the XtSelectionCallbackProc
is called with a type of XT_CONVERT_FAIL.
However, the parameters of the VAX format Intrinsics
routines XT$GET_SELECTION_VALUE_INCR and XT$GET_
SELECTION_VALUES_INCR have not changed. The
XtCancelSelectionCallbackProc parameter is ignored.
2.6.2.2 Changes in Widget Semantics:
V1.0 This section describes changes in widget semantics.
________________________ Note ________________________
Widgets created with XUI low- and high-level routines
will retain the Digital Release 3 behavior even after
the application is relinked.
______________________________________________________
The changes in widget semantics are as follows:
o Parameters to incremental selection callbacks use
a changed passing mechanism. Specifically, in
XtConvertSelectionIncrProc, XtSelectionDoneIncrProc, and
Programmer Release Notes 2-9
Programmer Release Notes
2.6 DECwindows Toolkit
XtCancelConvertSelectionProc, MIT X11 Release 4 passes
the receiver-id argument by reference; Digital Release
3 passes it by value. In XtConvertSelectionIncrProc,
MIT X11 Release 4 passes the max_length argument by
reference; Digital Release 3 passes it by value.
o MIT X11 Release 4 passes additional parameters to event
handlers, widget instance initialization procedures, and
widget set_values procedures. These parameters can be
safely ignored and Digital Release 3 behavior will be
retained. See the specifications for the MIT X11 Release
4 Intrinsics for more information.
o MIT X11 Release 4 requires the setting of a flag in a
class extension record in order to allow gadget children
for a widget class. See the specifications for the MIT
X11 Release 4 Intrinsics for more information.
o MIT X11 Release 4 handles XtSetValues of callbacks
correctly, but Digital Release 3 widget code might
contain a workaround that does not work with the fixed
Intrinsics. If the widget set_values routine compares
the old and new values of a callback field and attempts
to replace the callbacks, you should remove that code.
The Intrinsics now include this function.
o MIT X11 Release 4 does not invoke accelerator actions on
insensitive widgets; Digital Release 3 does.
2.6.2.3 Other Changes
V1.0 This section describes other changes that affect upward
compatibility.
o The information in four Digital Release 3 public .h
files (Convert.h, Translate.h, Selection.h, Event.h)
is now included in the Intrinsic.h file. The files are
retained for upward compatibility. If your application
includes these files, you should replace them with the
Intrinsic.h file instead.
o Four Digital Release 3 public .h files (CompObj.h,
CompObjP.h, WindowObj.h, WindowObjP.h) do not exist
in MIT X11 Release 4. The files are retained for upward
compatibility. For the sake of portability, you should
not use them.
2-10 Programmer Release Notes
Programmer Release Notes
2.6 DECwindows Toolkit
o Additional instance fields have been added to the end
of WMShell and VendorShell instance parts in MIT X11
Release 4. This will affect an application that accesses
fields within shell instance records without using the
DwtResolvePartOffsets method to do so.
2.6.3 Miscellaneous Toolkit Notes, Corrections, and Restrictions
This section contains information about notes,
restrictions, and corrections for the Toolkit.
2.6.3.1 Context-Sensitive Help
V1.0 Context-sensitive help mode can be terminated only by
clicking MB1. There is no keyboard equivalent.
2.6.3.2 Debugging Toolkit Applications-SET BREAK/EXCEPTION
Command
V1.0 If you enter the debugger command SET BREAK/EXCEPTION when
debugging a toolkit application, your application might
stop when the toolkit attempts to activate the shareable
image DECW$DXM_I18NLIB.EXE or DECW$DXM_I18NIOSHR.EXE, which
might not be on your system.
If your application stops, enter the debugger command GO
to continue execution. This is an expected event and the
toolkit has an exception handler in place to handle it.
2.6.3.3 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.
2.6.3.4 Insensitivity Problem
V1.0 The following widgets (and gadgets) do not display dimmed
(greyed) when they are set insensitive:
o XmArrowButton
o XmScrollBar
o XmScale
o XmText
o DXmCSText
Programmer Release Notes 2-11
Programmer Release Notes
2.6 DECwindows Toolkit
2.6.3.5 Intrinsics Key Translator
V1.0 Motif defines an Intrinsics key translator that in turn
translates certain keycodes into Virtual keysyms. See
the entry in the OSF/Motif Programmer's Reference on
VirtualBindings for information on Virtual keysyms.
The set of Virtual keysyms for Digital VMS servers is
listed in Table 2-2.
Table_2-2_Virtual_Keysyms_for_VMS_Servers__________________
OSF_Keysyms___________Digital_VMS_Keysyms__________________
osfCancel: <Key>F11
osfLeft: <Key>Left
osfUp: <Key>Up
osfRight: <Key>Right
osfDown: <Key>Down
osfEndLine: Alt<Key>Right
osfBeginLine: Alt<Key>Left
osfPageUp: <Key>Prior
osfPageDown: <Key>Next
osfBackSpace: <Key>Delete
osfDelete: Shift<Key>Delete
osfUndo: Alt<Key>Delete
osfCopy: Shift<Key>DRemove
osfCut: <Key>DRemove
osfPaste: <Key>Insert
osfAddMode: Shift<Key>F8
osfHelp: <Key>Help
osfMenu: <Key>F4
osfmenu bar: <Key>F10
osfSelect: <Key>Select
osfActivate:__________<Key>KP_Enter________________________
2-12 Programmer Release Notes
Programmer Release Notes
2.6 DECwindows Toolkit
2.6.3.6 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 <Key>osfDelete: cut-clipboard()
If you use virtual bindings where the osfCut virtual keysym
is not bound, you will not have any key sequence bound to
the cut-clipboard action by default. To work around this,
you can override the XmText and XmTextField translations in
your DECW$XDEFAULTS.DAT file.
2.6.3.7 Projected Change for XmText Class Widget
V1.0 OSF/Motif Release 1.1 uses XmText class widgets when it
automatically creates text widgets in composite widgets
such as the XmFileSelectionBox widget.
A future release of OSF/Motif could change to create
XmTextField class widgets instead. If your application
manipulates the text widgets of such composite widgets, be
careful to use only routines that work with both XmText
class and XmTextField class widgets. Otherwise, your
application might not work in the future.
2.6.3.8 Shift Lock
V1.0 OSF/Motif Release 1.1 currently treats the Shift Lock key
combination as a modifier. Mnemonics, accelerators, and
certain keys in keyboard traversal do not operate if the
Shift Lock is on.
2.6.3.9 Traversing a Motif Menu Bar with Keys
V1.0 There is a problem with using the keyboard to traverse a
Motif menu bar with servers based upon the Digital Release
3 or earlier. The problem is that keyboard traversal
only works if the mouse pointer is positioned within the
currently pulled down menu.
Programmer Release Notes 2-13
Programmer Release Notes
2.6 DECwindows Toolkit
2.6.3.10 VAX Format Toolkit Bindings
V1.1 The argument passing mechanism for some arguments to
XT$APP_MAIN_LOOP and XT$CREATE_APPLICATION_SHELL is
inconsistent, but exist for backwards compatibility. This
only affects the VAX format functions. If the C functions
XtAppMainLoop and XtCreateApplicationShell are used, the
arguments should be passed as follows:
o XT$APP_MAIN_LOOP-The application_context parameter
should be passed by value instead of by reference
o XT$CREATE_APPLICATION_SHELL-The argcount parameter
should be passed by value instead of by reference
2.6.3.11 XmText Widget Interactive Performance
V1.0 The performance of the XmText widget on large text buffers
degrades significantly when the value of XmNwordWrap is
set to On. Consider setting the value of XmNwordWrap to Off
or making it user selectable if XmText widget interactive
performance is a problem in your application.
2.6.3.12 XUI Application Linking Procedures
V1.0 You might need to modify XUI application-linking procedures
to specifically include SYS$SHARE:DECW$XLIBSHR.EXE, which
is the Xlib shareable image. The DECW$DWTLIBSHR.EXE
shareable image previously linked against the Xlib
shareable image, but it no longer does. If your linking
procedure includes one of the following lines, you will
need to add another line to the procedure:
SYS$SHARE:DECW$DWTLIBSHR/SHARE
SYS$LIBRARY:DECW$DWTLIBSHR/SHARE
The line that you need to add, if it is not already in your
linking procedure, is as follows:
SYS$SHARE:DECW$XLIBSHR/SHARE
2-14 Programmer Release Notes
Programmer Release Notes
2.6 DECwindows Toolkit
2.6.4 New DECwindows Motif Toolkit Shareable Images
V1.0 For VMS DECwindows Motif Version 1.0, the architecture of
the DECwindows Toolkit shareable images is new. There are
three reasons for this change in architecture:
o To add support for OSF/Motif.
o To allow the possibility of mixing XUI and Motif widgets
in the same application (NOTE: A restriction on mixing
XUI and Motif widgets is described in the following
sections).
o To provide binary upward compatibility from the Digital
version of the MIT X11 Release 3 Intrinsics to the
standard MIT X11 Release 4 Intrinsics and to allow
Digital to supply better binary upward compatibility
support in the future.
There are now two classes of DECwindows toolkit shareable
images:
o Code shareable images that contain the toolkit functions
o Thin-layer shareable images against which an application
links
There are five shareable images used to support XUI and
Motif.
2.6.4.1 Code Shareable Images
V1.0 The toolkit code resides in four other shareable images:
o DECW$XMLIBSHR
o DECW$DXMLIBSHR
o DECW$DWTSHR
o DECW$XTSHR
Use the DECW$XMLIBSHR shareable image for applications that
use XM (standard OSF/Motif routines).
Use the DECW$DXMLIBSHR shareable image for applications
that use DXM (the Digital extension to Motif).
DECW$DWTSHR and DECW$XTSHR shareable images are activated
by DECW$DWTLIBSHR as needed.
Programmer Release Notes 2-15
Programmer Release Notes
2.6 DECwindows Toolkit
2.6.4.2 Thin-Layer Shareable Image
V1.0 The DECW$DWTLIBSHR shareable image has been changed into a
thin-layer shareable image.
Continue to use DECW$DWTLIBSHR with applications that use
only XUI or Intrinsics, or both.
DECW$DWTLIBSHR contains only the "public" symbols that the
application links against (for example, the transfer vector
and global data) and the code that dynamically activates
the code shareable images. It does not contain the toolkit
code.
2.6.5 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 from the Digital version of the MIT X11
Release 3 Intrinsics (Digital 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 Digital Release 3 semantics of the Intrinsics. However,
as soon as that application relinks (or dynamically
activates DECW$DWTLIBSHR), it uses the MIT X11 Release
4 semantics of the Intrinsics (see Section 2.6.2 for
details).
Applications that dynamically activate DECW$DWTLIBSHR
should be changed to link directly against DECW$DWTLIBSHR.
DECW$DWTLIBSHR is now a thin-layer, shareable image that
is small and that dynamically activates automatically the
majority of the toolkit code only when necessary. So 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
2-16 Programmer Release Notes
Programmer Release Notes
2.6 DECwindows Toolkit
toolkit to follow it. However, the intent is to add code
that allows existing executable images to run unchanged (as
has been done with this release).
2.6.5.1 Restrictions on Mixing Motif and XUI Widgets
V1.0 There is a restriction on mixing Motif and XUI widgets.
The problem results from the fact that both XUI and Motif
have their own Vendor Shell widget class. If an application
is linked against XUI and not Motif, the XUI Vendor Shell
widget class is used in order to maintain compatibility
with DECwindows XUI. If an application is linked against
Motif, the Motif Vendor Shell widget class is used. Motif
widgets require the Motif Vendor Shell; XUI widgets are
compatible with the Motif Vendor Shell. The problem occurs
when an XUI-only application dynamically activates (using
LIB$FIND_IMAGE_SYMBOL) a shareable image that uses Motif.
The Toolkit makes the decision to use the XUI Vendor Shell
when the Toolkit is initialized and the Motif widgets in
the dynamically activated shareable image do not work.
The workaround is to add the application image name to
the DECW$USE_XM_VENDOR_SHELL logical name. This logical
name contains a comma-separated list of image names for
which the Toolkit is to use the Motif Vendor Shell. The
value of DECW$USE_XM_VENDOR_SHELL logical name defaults to
NOTES$MAIN. To add additional image names to this logical
name, enter the following:
$ DEFINE DECW$USE_XM_VENDOR_SHELL "NOTES$MAIN,-
_$ yourimage1,yourimage2,..."
Note that DECW$USE_XM_VENDOR_SHELL does not affect
applications that use Motif since they are already using
the Motif Vendor Shell.
2.7 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 allocates its
own colors from the specified colormap using the actual
parameter to DPSCreateContext or the setXgcdrawablecolor
operator.
Programmer Release Notes 2-17
Programmer Release Notes
2.7 Display PostScript (DPS) Server Extension-Color Cells
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.
2.8 Layered Products Fonts
This section contains information about layered product
fonts.
2.8.1 Accessing Layered Products Fonts
V1.0 If you want to use any layered products that supply
their own X fonts, your system manager must invoke the
DECW$MKFONTDIR command file in order for the X server
to be able to access the layered products' fonts. The
system manager will need to invoke this command file
only for layered products installed after DECwindows
because DECwindows installation automatically invokes
DECW$MKFONTDIR.
The system manager should enter the following command:
$ @SYS$UPDATE:DECW$MKFONTDIR
After the system manager enters this command, you must
end the current session and start a new session before the
server can access the fonts.
The reason is that the DECwindows X Server now supports
font directory files for faster startup. Fonts supplied by
the DECwindows kit come with prebuilt font directory files.
However, layered products do not supply font directory
files with their fonts.
This restriction will be lifted in the future as layered
products are modified to invoke the DECW$MKFONTDIR command
file in their kit installation procedures.
2.8.2 DECpresent Bullet Fonts Available
V1.0 The VMS DECwindows Motif Version 1.0 software kit provides
nine 75 dpi and nine 100 dpi bullet fonts. These fonts are
for the sole use of DECpresent. In addition, the kit also
provides a font metrics file PRESENT_BULLETS.AFM and a
corresponding PostScript file PRESENT_BULLETS.PS.
2-18 Programmer Release Notes
Programmer Release Notes
2.9 New OSF/Motif Examples
2.9 New OSF/Motif Examples
Some new examples from OSF have been added to the
DECwindows Motif Kit.
2.9.1 MOTIFANIM
V1.1 This 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 inputs (Xt intrinsics feature)
Motifanim 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 easily add
a new set of pixmaps to be animated using motifanim. Some
tree examples of animation data files include:
o dog.uil
o plane.uil
o superman.uil (superman<N>.xbm are referenced in
superman.uil)
The default animation is dog. To run the demo with the
other animations, use the commands:
$set default decw$examples
$motifanim := "$decw$examples:motifanim"
$motifanim -anim plane
$motifanim -anim superman
The files motiflogo.uil, motifanim.uil, and motifanim.c are
the core components of the program.
Programmer Release Notes 2-19
Programmer Release Notes
2.9 New OSF/Motif Examples
2.9.2 MRE
V1.1 MRE gives you a convenient way to view and edit your
resource files. The internal rules of MRE, which can be
extended by a user-supplied file, allow it to determine
whether resources are colors, fonts, files, or other
types. Based on the type of a resource, MRE provides the
appropriate editing mechanism:
o Colorbars for colors
o Font selection window for fonts
o File selection window for files
o Simple text window for others
2.9.2.1 The Basics of MRE
V1.1 Use one of the following commands to run MRE:
$ set default decw$examples
$ run mre
or
$ set default decw$examples
$ mre := "$decw$examples:mre"
$ mre <filename>
If you invoke MRE without command line arguments, it
searches for the file named .Xdefaults in your home
directory. If you specify a file on the command line, MRE
uses that file instead.
MRE loads the resource file that you specify (or
.Xdefaults) and presents all resource lines in a listbox.
Using options from the view menu, you can sort the listbox
based on:
resource -- sm*file*sensitive: on
^^^^^^^^^
specification -- sm*file*sensitive: on
^^^^^^^^^^^^^^^^^
value -- sm*file*sensitive: on
^^
2-20 Programmer Release Notes
Programmer Release Notes
2.9 New OSF/Motif Examples
You can toggle the display of various resource categories
using the toggle buttons in the lower half of the view
menu. You can also use the Short Cut pixmap buttons to
the left of the list to quickly restrict display to only
colors, only fonts, or only Booleans (TRUE/FALSE).
You can select a particular resource to edit by double-
clicking on the resource in the list or by selecting the
Edit button under the list. In the case of font or color
resources, an appropriate editing window opens. For Boolean
resources, the value flips to its opposite. For other types
of resources, this version of MRE provides a text window.
To clone a resource, edit the text in the selection window
beneath the listbox and click on the Add button. To delete
a resource, select it and click on the Delete button.
2.9.2.2 Editing Colors With MRE
V1.1 If you have a color system, MRE lets you edit colors usingI scale widgets and a list of named colors. Selecting a namedCH color from the list sets the scale values properly for the= named color and updates the color in the patch.l G The Set Root Window Background button sets the backgroundsF of your display, if you select a named color. You cannotA use it to set a hex value string as the background.s E Clicking on MB3 in the color patch window allows you toiB take the current background color of that window andB assign it to the window's foreground, topShadow, andG bottomShadow. You can use this to view color combinations C while maintaining Motif's three-dimensional illusion.i & 2.9.2.3 Editing Fonts With MRE E V1.1 The font edit window lets you locate fonts matching theeE criteria that you set. You can specify a font name maskeG by editing the contents of the Current Selection CriteriaUD window or by using the banks of the radio-style toggleC buttons. The toggle buttons generate usable font namehE masks only if your system has fonts that conform to the G comparatively new X Logical Font Description Conventions.h I Programmer Release Notes 2-21r
d Programmer Release Notes" 2.9 New OSF/Motif Examples D Once you establish search criteria, click on Filter toH Criteria and the listbox beneath the button is filled withD matching fonts. (Depending on your configuration, this$ might take some time.) C Selecting Display All Matches presents an area of the H window for each matching font. You can type into the panesI to see how particular character combinations are handled by I each font. Select any of the displayed fonts by clicking on H the Select button that appears to the left of its name. ToH make the selection, click on OK in the main font selection window.l F Selecting a single font, either from the listbox or fromH a pane, displays a window that contains just that font. To9 dismiss the window, click on the OK button.a G The toggle button banks can be changed by editing the UILt specs. , 2.9.2.4 Locating File Names With MRE C V1.1 MRE uses Motif's File Selection dialog box to let you F locate files used as resources. This dialog box does not< indicate that you are about to save your file. ? 2.9.2.5 Editing Boolean (TRUE/FALSE) Resources With MREo C V1.1 Selecting the Edit button when the currently selected E resource is a Boolean type causes the value to flip. NooD window is opened. Selecting Edit again flips the valueF back. In this version, the pairs true/false, yes/no, and2 on/off are recognized and supported. 3 2.9.2.6 Editing Translation Tables With MREc I V1.1 This version of MRE provides no special support for editing ! translation tables.y $ 2.9.2.7 The MRE Options Menu G V1.1 You can use MRE as a front end to xrdb. Using the options F menu, you can merge or load either the current selectionG or the current listbox contents into the RESOURCE_MANAGERmF property of your server. The current listbox contents isD not the entire loaded database. It is the set of items< currently eligible for display in the listbox. % 2-22 Programmer Release Notesm
g s I Programmer Release Notes I 2.9 New OSF/Motif Examples D Dump Database to SYS$OUTPUT is only used for debuggingI MRE. It puts the line information structures for MRE on thet screen.n F The Show Widget Hierarchy and Values option is primarilyE for debugging, but it can be used to study the behaviordG of individual MRE widgets. Selecting this option displaysoF a bulletin board that contains a button for each fetchedG widget and gadget making up MRE. The buttons are indenteddE to indicate parent-child relationships. Clicking on anyiD button displays the complete set of resource names andE values for the widget whose name appears on the button.nG Above the resource names and values there is an OK buttonlB and two text fields. Clicking on the OK button callsF XtSetValues with the string in the first text field usedD as the resource name and the string in the second textE field treated as an integer value. For example, you canoC resize a widget by clicking on OK when the first texteD field contains Width and the second contains 1000. MREE does not screen your calls for you. Setting values on a F destroy callback causes problems. To eliminate access toG this option, comment it out of mre_menu.uil and recompilesG mre_menu.uid. No recompilation of C files is necessary to ) disable this or any option. E The Command Entry toggles a command entry window on andg off. ! 2.9.2.8 MRE Command Entry H V1.1 Selecting the Command Entry toggle button from the OptionsF menu adds a command entry window to the MRE main window.2 Valid commands for this version are: 9 o SORT (by) [RESource|SPECification|VALue] ) ([Ascending|Descending])t o HELP (subject) & o SAVE ((as)(filename)) o EXITm F ________________________ Note ________________________ C Lower case indicates optional characters in a word,nE parentheses surround optional words in a command, anda I Programmer Release Notes 2-23
Programmer Release Notes" 2.9 New OSF/Motif Examples * brackets surround choices. F ______________________________________________________ 2.9.2.9 Help on MREp H V1.1 This version has no help text. Clicking on the Help buttonC displays empty help windows. When you request help onmC version, help displays an information dialog box thatpG contains version information for MRE, the server, and thee font path. " 2.9.2.10 The MRE Edit Menu @ V1.1 The Cut, Copy, and Paste functions are provided toB demonstrate how to interact with the Motif clipboardG functions. They are of no use in MRE and are duplications F of the functions available when using the Add and DeleteI buttons from the main window. For example, material that iseH cut or copied to the clipboard is held as a regular string= and can be pasted into a text editor, xmeditor.r F 2.9.2.11 Adding Custom Types; Associating Resources with Types A V1.1 The file mre_types, or any file with specificationsoE provided in the resource mreTypeFile, is read by MRE at G startup. Entries in this file can indicate how MRE should G treat various resource names, and can define new resource F categories. To associate a resource with a type, add the* following line to mre_types: ( TYPE regular_expression G TYPE is from MISC COLOR FONT Boolean FILE TRANSLATION andiF
regular_expression is a regular expression. For example: COLOR sheen$ D This example indicates that any resource specificationD whose left-hand side ends in "sheen" should be assumedG to be a color specification. One such resource definition ' might be mre*sheen: blue. H You can also define enumerated and range types to MRE. ForF example, the following lines cause MRE to treat resourceB specifications ending in "mousename" as having three; potential values: mickey, mighty, and minnie.u 3 DEFINE TRIPLET mickey;mighty;minnie " TRIPLET mousename$ % 2-24 Programmer Release Notese
e s I Programmer Release NoteseI 2.9 New OSF/Motif ExamplesF F If you select this resource, MRE builds a radio box withI the appropriate toggle buttons to simplify your choice. YoufG are also provided with a text field, if you want to enteru' an exception to the rule.i F To define a range, use digits and a hyphen. For example: & DEFINE BORDERSIZE 0-10' BORDERSIZE borderWidth$e I This causes MRE to edit borderWidth resources by presentingy a scale widget.d C The more type definitions you provide, the longer MREeI takes to start up. Therefore, a good strategy is to provideeG multiple mreTypeFile files for different applications and D use aliases to run MRE for different applications. For example: D alias mre.emacs "mre -xrm mreTypeFile:mre_emacstypes" 3 2.9.2.12 Resources That Modify MRE Behavior A V1.1 MRE behavior, like those of all Motif programs, can.D be modified by setting various resources. This section6 describes MRE resources that can be set. 0 mergeOnSave: on|off [default: off] D If on, MRE calls xrdb -merge when information is beingH saved to file. Xrdb stores resources in a property in yourF server. If this RESOURCE_MANAGER property exists on yourI server, applications use the resource information from this I property in place of that in $HOME/.Xdefaults. Thus, if you G have a RESOURCE_MANAGER property set but don't merge your H updated .Xdefaults into it, you might not see your updates0 reflected in application behavior. 6 fontText: [default: "This is a sample."] G When editing a font resource, MRE can be asked to display G all fonts matching certain criteria. This resource is the H text that is presented in each font. The text is presentedG in editable text widgets, so it can also be modified wheni displayed. I Programmer Release Notes 2-25a
- l Programmer Release Notes" 2.9 New OSF/Motif Examples 3 printHierarchy: on|off [default: off]t D If on, dump the widget hierarchy to standard output onF startup. This information can be used by the terminally-H customizing to play with the resource values of individualH widgets. The widget hierarchy can also be printed from the option menu. : rgbTextFile: [default: /usr/lib/X11/rgb.txt] G Specifies the file whose contents are placed in the coloriH edit window's named colors listbox. It is recommended that) you use the default values.o 4 internalPixmaps: on|off [default: off] G Specifies whether MRE should substitute hard-coded bitmapbD data from its C source files for the pixmaps otherwiseH loaded from uid files. This resource should not be needed. / mreTypeFile: [default: mre_types]t D Specifies the file that MRE searches for resource typeG rules. In this version, each line in this file must be of the form:e & TYPE regular_expression or8 DEFINE TYPENAME choice1;choice2;...choicen or0 DEFINE TYPENAME lowvalue-highvalue G TYPE is from MISC COLOR FONT Boolean FILE TRANSLATION and I regular_expression is a regular expression. Choose TYPENAME E for a custom type. Choice 1...choice n are enumerations F of that type. Lowvalue and highvalue are decimal integer# strings. For example:c COLOR sheen$ H This indicates that any resource specification whose left-E hand side ends in "sheen" is a color specification. Onew@ such resource definition might be mre*sheen: blue. F The following example shows that resource specificationsH with the ending "mousename" should be edited by presenting> the choices mickey, mighty, and minnie. ResourceE specifications ending with borderWidth should be edited = by presenting a scale ranging from zero to ten.R % 2-26 Programmer Release Notesn
I Programmer Release Notes I 2.9 New OSF/Motif Examplesr 1 DEFINE TRIPLET mickey;mighty;minnie $ DEFINE BORDERSIZE 0-10 TRIPLET mousename$% BORDERSIZE borderWidth$l G MRE has internal rules and can operate without this file. ( fontList: [default: fixed] I MRE uses Motif resolution independence feature. For windows G to be sized appropriately for a given font, both the fontUB and fontList resources must be set to the same font. ( 2.9.2.13 Known Problems With MRE 4 V1.1 The following problems exist with MRE: D o The MRE main selection box does not handle vertical' resizes intelligently. B o Both Font and FontList resources must specify theC same font for MRE windows to be presented at sizes / appropriate to any given font.e E o In those windows using Xm100TH_FONT_UNITS resolutioniC independence mode, scroll bar sliders might not beo visible. E o The File Selection dialog boxes used in editing file H resources do not properly display the existing filenameC specified for the resource. Clicking on OK without H selecting a filename sets the resource to an incomplete specification.r C o Keyboard traversal is not complete in all windows.. G o This VMS DECwindows Motif version does not incorporaten xrdb. 3 2.9.2.14 MOTIFGIF and PICT Viewing Programs0 F V1.1 Motifgif and pict are two programs that work together toH display a .gif formatted picture. Motifgif displays a .gifI file within motif constructs. Motifgif looks for .gif filess' in the current directory.a A There are three significant components to motifgif:p @ o motifgif-The source and executable code in thisF directory that is a motif program driving the display# of a .gif picture. I Programmer Release Notes 2-27
d t Programmer Release Notes" 2.9 New OSF/Motif Examples D o pict-The program called by motifgif that displays aG bitmap of a .gif picture file. This program used to be 6 xgif but has been con
rted to motif. @ o .gif files-The files that contain the bitmapped displays. 9 The following problems exist with motifgif: 2 o Resizing a picture does not work. C o -d option is not used when calling pict, so remotelD displays must set the DISPLAY environment variable. G No .gif files are supplied with this VMS DECwindows Motife EFT version. 2.9.2.15 Dog Widget_ H V1.1 This section contains information about sources of the Dog; widget, the Square widget, and the Dogs demo. Dog Widget H The Dog widget demonstrates how to subclassify a primitiveH widget that remains binary compatible with future versionsE of Motif. It uses XmResolvePartOffsets() and associatedeB macros and implements all the recommendations in the+ XmResolvePartOffsets manpage. F The Dog widget is a subclass of XmPrimitive. It can barkH and wag its tail. If you want more exotic tricks, you mustI subclassify it, or replace up.bm, down.bm, and bark.bm withd$ more advanced bitmaps. 9 The Dog widget has the following resources:a B o DogNwagTime-Time in milliseconds between each wag F o DogNbarkTime-Time in milliseconds the bark graphic is displayed D o DogNbarkCallback-Callback called by the bark action < The Dog widget has the following translations: 4 o osfActivate/Return/Space/MB1 = Bark ! o W/MB2 = Wag tailn 0 o S/Shift-MB2 = Stop wagging tail o osfHelp = Helpi % 2-28 Programmer Release Notesn
i t I Programmer Release Notes I 2.9 New OSF/Motif Examplesx Square Widget ? The Square widget demonstrates how to subclassifye5 a constraint widget that remains binary ? compatible with future versions of Motif. It uses = XmResolveAllPartOffsets() and associated macrosn; and implements all the recommendations in the . XmResolveAllPartOffsets manpage. A The Square Widget is a subclass of XmBulletinBoard.tD It forces its children to be square using a constraint resource. 1 The Square widget has one resource: I o SquareNmajorDimension-Determines which dimension is used I for the new size of the child. Values are SquareWIDTH or SquareHEIGHT. < The Square widget has one constraint resource: I o SquareNmakeSquare-Determines whether the child is forcedc< to be square or set to its preferred shape. Dogs Demos ? The Dogs demo uses the Dog and Square widgets. IthH illustrates how to incorporate new widgets into UIL source1 by using the user-defined function. @ The Dogs demo allows you to dynamically change the: DogNwagTime and SquareNmakeSquare resources. G If you have a machine with sound generation features, you G might want to change the bark callback to something othert than XBell(). 2.10 Toolkit Extensionsd I This section contains information about toolkit extensions.e : 2.10.1 DXmCSText Resources to Specify Input Method F V1.1 Two resources have been added to the DXmCSText widget to< allow applications to specify an input method: $ o DXmNinputMethodType o DXmNinputMethod I Programmer Release Notes 2-29v
o r Programmer Release Notes 2.10 Toolkit Extensions G The toolkit does not supply an input method. ApplicationsoI or local engineering groups must provide an input method iff@ the default toolkit input behavior is not desired. F ________________________ Note ________________________ @ These resources do not apply to ISO8859 locales. F ______________________________________________________ $ 2.10.1.1 DXmNinputMethodType I DXmNinputMethodType specifies the type of input method used H by DXmCSText. The values for Table 2-3 describe the values for this resource. I Table_2-3_DXmNinputMethodType_Values_______________________e I Value___________________________Description________________e I DXmIM_DEFAULT_TYPE The default input method ofsI the current locale is used.i F DXmIM_NONE_TYPE No input method is used;G the default toolkit inputRD behavior is preserved. H DXmIM_STRING_TYPE The input method specifiedI ________________________________in_DXmNinputMethod_is_used.a E The correct way to toggle between two input methods, orrI between an input method and the usual input behavior of theaA toolkit, is to set the DXminputMethodType resource. > The default is DXmIM_STRING_TYPE. Access is CSG. 2.10.1.2 DXmNinputMethod D DXmNinputMethod specifies the name of the input methodE to be used by DXmCSText. This resource is valid only if D DXmNinputMethodType is DXmIM_STRING_TYPE. If the namedD input method does not exist on the system, the default5 toolkit input behavior is used instead.i B In previous releases, this resource was undocumentedE but available with a slightly different definition. For G backwards compatibility, it is possible to toggle between C input methods by using two toolkit-named input method % 2-30 Programmer Release Notesu
_ r I Programmer Release NotesnI 2.10 Toolkit Extensions G names, IM_DEFAULT and IM_NONE. These strings are reserved H by the DXm toolkit and should not be used by applications. @ Setting DXminputMethod to IM_DEFAULT is equivalentB to setting DXminputMethodType to DXmIM_DEFAULT_TYPE.H Setting DXminputMethod to IM_NONE is equivalent to setting4 DXminputMethodType to DXmIM_NONE_TYPE. C The preferred way of changing input methods is to seteH DXminputMethodType. Applications that change input methodsD by setting the DXminputMethod resource gain processingG speed and regain memory by setting the DXminputMethodTypeb resource instead.h 0 Access for DXmNinputMethod is CSG. 7 2.10.2 DXmCSText With the XmNblinkRate Resourcee @ V1.1 If an application uses a DXmCSText widget with theG XmNblinkRate resource set to 0, the cursor does not blink or display. G To correct this problem, set the blink rate to a non-zero F value. A value of 1 displays the cursor but causes it to# blink at a slow rate.R 2 2.10.3 DXmCSTextSetSelection Format Change 8 V1.1 With VMS DECwindows Motif Version 1.1, theE DXmCSTextSetSelection routine has the following format:i C void DXmCSTextSetSelection(widget, first, last, time)d- Widget widget; , DXmCSTextPosition first;+ DXmCSTextPosition last;m+ Time time;. C This change does not cause any problems with previoustE applications that declared the first and last argumentsl( for DXmCSTextSetSelection. I Programmer Release Notes 2-31
Programmer Release Notes 2.10 Toolkit Extensions 9 2.10.4 DXmHelpSystem Routine Status Value Changesi F V1.1 With VMS DECwindows Motif Version 1.1, the status valuesE that Bookreader passes to the error processing routines @ have changed. These changes apply to the followingH routines, which are described in the DECwindows Extensions to Motif Manual: # o DXmHelpSystemClose % o DXmHelpSystemDisplaye " o DXmHelpSystemOpen 8 Table 2-4 describes the new status values. I Table_2-4_DXmHelpSystem_Routine_Status_Values______________o I ValueBookreader_Status__Description________________________. - 0 Bkr_Success Success E 1 Bkr_Busy Bookreader is currently engaged C in an operation. Under normal H operation, this occurs only duringD a Bookreader invocation when aC person tries to invoke help ahI second time. The recommended actionmC is to do nothing. Eventually, H Bookreader comes up and subsequentF calls are handled appropriately. E 2 Bkr_Send_Event_ The help routines cannot send afG Failure client message to Bookreader. TheoG recommended action is to call the H DXmHelpSystemOpen routine again to? start another Bookreader.t D 3 Bkr_Startup_ Bookreader cannot be run. ThisE Failure means that Bookreader cannot be D started by LIB$SPAWN. PossibleG causes are the SYS$SYSTEM logicaleG name has been redefined, there is1F a hardware error, or the process> quota has been exceeded. I (continued on next page)i % 2-32 Programmer Release Notes
a I Programmer Release NotesPI 2.10 Toolkit Extensionse I Table_2-4_(Cont.)_DXmHelpSystem_Routine_Status_Values______ I ValueBookreader_Status__Description________________________n I 4 Bkr_Create_ A client context cannot be created.aF Client_Failure This error can only occur duringB a call to DXmHelpSystemOpen.F The recommended action is to tryC calling the DXmHelpSystemOpene4 routine again. D 5 Bkr_Invalid_ Something other than a "topic"B Object or "dir" was passed into theF DXmHelpSystemDisplay routine for? the object type argument. C 6 Bkr_Get_Data_ Bookreader could not retrievenH Failure information from the help_context.F The recommended action is to try@ calling the routine again. E 7 Bkr_Bad_Filename No filename was passed into the I ________________________DXmHelpSystemOpen_routine._________e " 2.10.5 DXmNlayoutDirection F V1.1 The DXmNlayoutDirection resource is used by applicationsE that require interpretation of direction, widget layoutaF direction, and widget traversal direction. This resourceF allows the application to be configured for environmentsE that expect direction from either left-to-right or fromd right-to-left. F 2.10.5.1 DXmNlayoutDirection in DECwindows Extensions to Motif F V1.1 The behavior of this resource depends on the function orI widget that you use. Check the sections that follow for theoH specific function or widget. All the functions and widgetsH described in this section are documented in VMS DECwindowsI Extensions to Motif. The DXmNlayoutDirection description ist) an addition to that manual. E DXmNlayoutDirection performs as a read/write value that G holds the layout direction of the widget components, suchoI as labels, popups, pushbuttons, and scroll bars in relationS8 to each other for the following functions: ( o DXmCreateColorMixDialog I Programmer Release Notes 2-33
h X Programmer Release Notes 2.10 Toolkit Extensionsn o DXmCreateCSText $ o DXmCreateHelpDialog % o DXmCreatePrintDialog ( o DXmCreateScrolledCSText o DXmCreateSvn E Table 2-5 describes the effect this resource has on theiE DXmLAYOUT_LEFT_DOWN and DXmLAYOUT_RIGHT_DOWN values for these functions. I Table_2-5_DXmNlayoutDirection_Values_______________________ I DXmLAYOUT_LEFT_DOWN________DXmLAYOUT_RIGHT_DOWN____________n G The direction of the The direction of the layout istI layout is right to left left to right and top to bottom.i and top to bottom H The default is DXmLAYOUT_RIGHT_I ___________________________DOWN,_or_3._Access_is_CSG._______ E DXmNlayoutDirection performs as a read/write value thatiD holds the layout direction of the vertical scroll barsE in relation to the text for the DXmCreateScrolledCSTexteH function. In addition, this resource controls the resizing- direction for the widget width._ F ________________________ Note ________________________ F The legal values for DXmNlayoutDirection, if specified( in a resource file, are: ? o left_down-layout is left to right and top to bottom. @ o right_down-layout is right to left and top to bottom. F ______________________________________________________ F Table 2-6 describes the effect that this resource has onI the DXmLAYOUT_LEFT_DOWN and DXmLAYOUT_RIGHT_DOWN values ford this function. % 2-34 Programmer Release Notes
h , I Programmer Release Notes I 2.10 Toolkit Extensions : Table 2-6 DXmNlayoutDirection Values for theC DXmCreateScrolledCSText and DXmCreateCSTexteI __________Functions________________________________________ I DXmLAYOUT_LEFT_DOWN________DXmLAYOUT_RIGHT_DOWN_____________ > The default value for The default value forD XmNscrollLeftSide is XmNscrollLeftSide is FALSE.C TRUE. If XmNresizeWidth If XmNresizeWidth is TRUE,oE is TRUE, the left edge of the right edge of the widgeti1 the widget resizes. resizes. H The default is DXmLAYOUT_RIGHT_I ___________________________DOWN,_or_3._Access_is_CSG.______ 8 2.10.5.2 DXmNlayoutDirection in DECwindows Motif 5 V1.1 The following OSF/Motif widgets support " DXmNlayoutDirection: B o XmLabelGadget class and XmLabelGadget subclasses: ) - XmCascadeButtonGadgeta & - XmPushButtonGadget ( - XmToggleButtonGadget ( o XmPrimitive subclasses: - XmLabelD - XmList - Xmscroll bar # - XmCascadeButtoni - XmPushButton " - XmToggleButton & o XmManager subclasses: " - XmSelectionBox - XmForm - XmMessageBox - XmCommand & - XmFileSelectionBox I Programmer Release Notes 2-35
c s Programmer Release Notes 2.10 Toolkit Extensionsk I Table 2-7 describes the effect that the DXmNlayoutDirectiont7 resource has on these widgets components.s I Table_2-7_DXmNlayoutDirection_Effect_on_Widget_Components__i WidgetI Component___DXmLAYOUT_LEFT_DOWN___DXmLAYOUT_RIGHT_DOWN_____ G CascadeButtoCascade graphic Cascade graphic appearsmG / Gadget appears on left-hand on right-hand side, andiI side, and the menu the menu is brought up onlG is brought up on the the right. XmALIGNMENT_ D left. XmALIGNMENT_ BEGINNING aligns theG BEGINNING aligns the left edges of lines andnF right edges of lines XmALIGNMENT_END alignsI and XmALIGNMENT_ the right edges of lines.c- END aligns the leftt) edges of lines.. G Command Prompt string is Prompt string is placedNI placed on right-hand on left-hand side, with ao? side, with a default default of ">". ! of "<".h I FileSelectioButtons are laid out Buttons are laid out fromrI from right to left, left to right, labels are H labels are aligned aligned to the left-handE to the right-hand side, scroll bars are E side, scroll bars aligned to the right-iF are aligned to the hand side, and text isF left-hand side, and displayed from left to6 text is displayed right.- from right to left._ I (continued on next page) % 2-36 Programmer Release Notes
I Programmer Release Notes I 2.10 Toolkit Extensions D Table 2-7 (Cont.) DXmNlayoutDirection Effect on WidgetI __________________Components_______________________________ WidgetI Component___DXmLAYOUT_LEFT_DOWN___DXmLAYOUT_RIGHT_DOWN_____ B Form The word "near" The word "near" is? means right when defined to mean D referenced in the left when referenced@ OSF/Motif Reference in the OSF/MotifH Manual for the Reference Manual for theE XmNrubberPositioning, XmNrubberPositioning, B XmNleftAttachment, XmNleftAttachment,> XmNleftOffset, XmNleftOffset,D XmNleftPosition, XmNleftPosition, andH and XmNleftWidget XmNleftWidget resources.A resources. The word "far" is ? The word "far" defined to mean E is defined to right when referenced @ mean left when in the OSF/MotifD referenced in the Reference Manual forG OSF/Motif Reference the XmNrightAttachment,2? Manual for the XmNrightOffset, E XmNrightAttachment, XmNrightPosition, and I XmNrightOffset, XmNrightWidget resources.a+ XmNrightPosition,V, and XmNrightWidget$ resources. E Label / XmALIGNMENT_ XmALIGNMENT_BEGINNINGeH Gadget BEGINNING aligns the aligns the left edges ofI right edges of lines lines and XmALIGNMENT_END.I and XmALIGNMENT_ aligns the right edges of 6 END aligns the left lines.) edges of lines. I Message Buttons are laid out Buttons are laid out from H Box from right to left, left to right, pixmap isG pixmap is placed at placed at the left-handi5 the right-hand side. side.t I (continued on next page)t I Programmer Release Notes 2-37t
. Programmer Release Notes 2.10 Toolkit Extensions D Table 2-7 (Cont.) DXmNlayoutDirection Effect on WidgetI __________________Components_______________________________ WidgetI Component___DXmLAYOUT_LEFT_DOWN___DXmLAYOUT_RIGHT_DOWN_____ G Option Label is aligned Label is aligned on the E Menu on the right side left side and the bar D and bar graphic graphic is placed onF is placed on left the right side. If theH side. If the pull- pull-down menu cannot beG down menu cannot placed over the button,wH be placed over the the menu is displayed to? button, the menu the right side.e- is displayed to the $ left side. I PanedWindow The sash is placed The sash is placed on thet; on the left side. right side.D G Popup Menu The hot spot is The hot spot is locatedlI located at the upper at the upper left corner. ' right corner.n E Pull-Down If pulled down from If pulled down from atH Menu a menu bar or a menu bar or a horizontalF horizontal menu, menu, the left edge ofI the right edge pull-down menu is alignedXI of pull-down menu with the left edge of its F is aligned with parent cascade button.+ the right edge of , its parent cascade! button. B Pushbutton The accelerator The accelerator isF /Gadget is displayed on displayed on the rightB the left side. side. XmALIGNMENT_D XmALIGNMENT_ BEGINNING aligns theF BEGINNING aligns the left edge of lines andF right edge of lines XmALIGNMENT_END alignsH and XmALIGNMENT_END the right edge of lines.. aligns the left edge# of lines.U I (continued on next page)_ % 2-38 Programmer Release Noteso
e r I Programmer Release NoteseI 2.10 Toolkit ExtensionsS D Table 2-7 (Cont.) DXmNlayoutDirection Effect on WidgetI __________________Components_______________________________ WidgetI Component___DXmLAYOUT_LEFT_DOWN___DXmLAYOUT_RIGHT_DOWN_____r E RowColumn Children are laid Children are laid outrC out from right to from left to right, E left, including including cascades in ; cascades in a menu a menu bar. bar. I Scale The text string The text string is placedeG is placed on the on the left side of theXH right side. If scale. If XmNorientationA
XmNorientation is is XmVERTICAL and I XmVERTICAL, and XmNshowValue is TRUE, the I XmNshowValue is value is displayed on the H TRUE, the value right side of the scale.D is displayed on If XmNorientation isI the left side XmHORIZONTAL, the defaultWI of the scale. If XmNprocessingDirection isu? XmNorientation XmMAX_ON_RIGHT. * is XmHORIZONTAL,% the defaultm0 XmNprocessingDirection+ is XmMAX_ON_LEFT. D scroll bar If XmNorientation If XmNorientation isI is XmHORIZONTAL, XmHORIZONTAL, the default_I the default XmNprocessingDirection isD? XmNprocessingDirectionXmMAX_ON_RIGHT.w+ is XmMAX_ON_LEFT. E ScrolledWindThe default The default XmNscrollaI XmNscroll barPlacement is XmBOTTOM_ 6 barPlacement is RIGHT.( XmBOTTOM_LEFT. I (continued on next page)i I Programmer Release Notes 2-39
Programmer Release Notes 2.10 Toolkit Extensions D Table 2-7 (Cont.) DXmNlayoutDirection Effect on WidgetI __________________Components_______________________________ WidgetI Component___DXmLAYOUT_LEFT_DOWN___DXmLAYOUT_RIGHT_DOWN_____ H SelectionBoxThe buttons are laid The buttons are laid outG out from right to from left to right, andcI left, and labels are labels are aligned on theo: aligned on the right left side. side.C B ToggleButtonThe accelerator is The accelerator isF / Gadget displayed on the displayed on the rightB left side of the side of the label,F label, and the and the toggle graphicE toggle graphic is placed on the left B is placed on the side of the label.E right side of the XmALIGNMENT_BEGINNING H label. XmALIGNMENT_ aligns the left edges ofG BEGINNING aligns lines, and XmALIGNMENT_ D the right edges END aligns the right? of lines, and edges of lines. ) XmALIGNMENT_END ) aligns the leftpI ____________edges_of_lines.________________________________w ? 2.10.6 SVN and Compound String Text Widget Translations" F V1.1 This section contains Structured Visual Navigation (SVN)E and Compound String Text Widget translation information ? that is not currently available in the DECwindows ) Extensions to Motif Manual.t I Table_2-8_DXmSvn_Widget_Button_Syntax_Translations_________r I Event_________________Action_Routine_______________________i 4 BSelectPress: svn_button1_down 2 BSelectRelease: svn_button1_up 6 BSelectDrag: svn_button1_motion I (continued on next page)t % 2-40 Programmer Release Notes
I Programmer Release NotessI 2.10 Toolkit Extensionso I Table_2-8_(Cont.)_DXmSvn_Widget_Button_Syntax_Translations_T I Event_________________Action_Routine_______________________f 9 BExtendPress: svn_shiftbutton1_down_ 2 BExtendRelease: svn_button1_up 6 BExtendDrag: svn_button1_motion 8 BTogglePress: svn_ctrlbutton1_down 2 BToggleRelease: svn_button1_up 6 BToggleDrag: svn_button1_motion 4 BDragPress: svn_button2_down 2 BDragRelease: svn_button2_up 6 BDragDrag: svn_button2_motion E BDragToggle: (MB2-ctrl-click) svn_button2_downm D BDrag: (MB2-Alt-click) svn_button2_down 4 BMenu: svn_button3_down 0 BFocusIn: svn_focus_in 1 BFocusOut: svn_focus_out I BHelp:________________svnhelp______________________________ D Table 2-9 describes the keyboard syntax for the DXmSvn widget." I Table_2-9_DXmSvn_Widget_Keyboard_Syntax_Translations_______h I Event_________________Action_Routine_______________________F / KMenu: svn_f4_menu 2 KDown: svn_arrow_down 0 KUp: svn_arrow_up 1 KPageDown: svn_page_downs / KPageUp: svn_page_up 5 KEndData: svn_scroll_to_topg 8 KBeginData: svn_scroll_to_bottom 1 KExtendUp: svn_extend_up I (continued on next page)a I Programmer Release Notes 2-41
I Programmer Release Notes 2.10 Toolkit Extensionsh = Table 2-9 (Cont.) DXmSvn Widget Keyboard Syntax I __________________Translations_____________________________ I Event_________________Action_Routine_______________________ 3 KExtendDown: svn_extend_downn 5 MShiftKPageUp: svn_extend_pageupt 7 MShiftKPageDown: svn_extend_pagedown 5 MShiftKBeginData: svn_extend_to_top 8 MShiftKEndData: svn_extend_to_bottom 2 KLeft: svn_arrow_left 3 KRight: svn_arrow_right 6 KBeginLine: svn_scroll_to_left 7 KEndLine: svn_scroll_to_right 1 KPageLeft: svn_page_leftt 2 KPageUp: svn_page_right 6 KActivate: svn_activate_entry 6 MCtrlKActivate: svn_activate_entry 6 KSpace: svn_activate_entry 6 MCtrlKSpace: svn_activate_entry 6 KSelect: svn_activate_entry + KHelp: svnhelp 2 KSelectAll: svn_select_all 4 KDeSelectAll: svn_deselect_all 3 KNextColumn: svn_next_column 3 KPrevColumn: svn_prev_columnc ; MShiftKTab: LclTraversePrevTabGroupt ; KTab: LclTraverseNextTabGroupn ; MCtrlKTab: LclTraversePrevTabGroupd . KCancel: svn_cancel 2 KNextPara: svn_next_level I KPrevPara:____________svn_prev_level_______________________ F Table 2-10 further describes the action routines for the DXmSvn widget. % 2-42 Programmer Release Notesu
r f I Programmer Release Notes I 2.10 Toolkit Extensionse I Table_2-10_Action_Routines_for_DXmSvn_Widget_______________l I Action_Routine
______Description__________________________ I svn_button1_down Selects and moves the location cursor G to the current entry. Deselects all 2 other entries. B svn_button1_up Completes selection started byB the button1 press. Reports theC DXmSvnNentrySelectedCallback tosA the application if specified.hB If this BtnUp was a completionC of a double MB1 click, then theEH DXmSvnNselectAndConfirmCallback willE be reported to the application if . specified. H svn_button1_motion Extends selection to include entriesG that are passed over with the mousexD motion. If the Ctrl modifier wasF pressed with this MB1 motion, thenD all entries passed over with theF mouse selection state are toggled. D svn_shiftbutton1_ Extends selection to include allE down entries between the last selected_G entry and this current entry. MovesrG the location cursor to this currentm* entry. F svn_ctrlbutton1_down Toggles the selection state of theH current entry and moves the location9 cursor to this entry. F svn_button2_down Initiates a drag operation. If MB2C is pressed on a selected entry, E all selected entries are dragged.nE If MB2 is pressed on a unselected I entry, only that entry is dragged. If H application dragging is set, via theF DXmSvnSetApplDragging routine, theH DXmSvnNdraggingCallback is reported,1 if specified. I (continued on next page) I Programmer Release Notes 2-43R
N , Programmer Release Notes 2.10 Toolkit Extensionso I Table_2-10_(Cont.)_Action_Routines_for_DXmSvn_Widget_______ I Action_Routine________Description__________________________ A svn_button2_up Completes the drag operation. @ The DXmSvnNselectionsDragged? callback is reported to the @ application if specified and@ the entries are selected. IfD application dragging is set, viaF the DXmSvnSetApplDragging routine,E the DXmSvnNdraggingEndCallback isnF reported, if specified. If the MB2G click is made without mouse motion,eD the DXmSvnNentryTransferCallbackF is reported to the application, if. specified. I svn_button2_motion A ghost object is created and followsL> the mouse with MB2 motion. H svn_button3_down Reports DXmSvnNpopupMenu callback toI the application if specified for thiss* entry. G svn_focus_in Sets focus to the SVN widget. Moves D location cursor to last selected5 entry in display. F svn_focus_out Removes focus from the SVN widget.E Also removes location cursor fromh8 last selected entry. = svnhelp Reports the help callbacke> DXmSvnNhelpCallback to the> application, if specified. H svn_f4_menu Reports the DXmNpopupMenuCallback toH the application if specified for theC entry with the location cursor. I svn_arrow_down Selects and moves the location cursorNE to the next entry in the display,_B scrolling the display down, if. necessary. I (continued on next page)V % 2-44 Programmer Release Notest
d I Programmer Release NotesCI 2.10 Toolkit Extensions_ I Table_2-10_(Cont.)_Action_Routines_for_DXmSvn_Widget________ I Action_Routine________Description__________________________P B svn_arrow_up Selects and moves the locationG cursor to the previous entry in the I display, scrolling the display up, ift. necessary. C svn_page_down Scrolls the display to the nexteH screen of entries. Selects and movesD the location cursor to the entryI located at the same relative positioni7 on the next screen. G svn_page_up Scrolls the display to the previousuH screen of entries. Selects and movesD the location cursor to the entryI located at the same relative position ; on the previous screen._ D svn_scroll_to_top Scrolls to the last entry in theF SVN display. Selects and moves theB location cursor to that entry. E svn_scroll_to_bottom Scrolls to the first entry in the F SVN display. Selects and moves theB location cursor to that entry. B svn_extend_up Adds the previous entry to theI extended selection. Selects and moves G the location cursor to the previouseD entry, scrolling the display, if. necessary. G svn_extend_down Adds the next entry to the extended D selection. Selects and moves theG location cursor to that next entry, H scrolling the display, if necessary. H svn_extend_pageup Extends the selection to include allI entries in the next screen. Moves the H location cursor to the entry locatedH at the same relative position on the0 next screen. I (continued on next page)e I Programmer Release Notes 2-45_
_ _ Programmer Release Notes 2.10 Toolkit Extensions_ I Table_2-10_(Cont.)_Action_Routines_for_DXmSvn_Widget_______ I Action_Routine________Description__________________________w H svn_extend_pagedown Extends the selection to include allI entries in the previous screen. Moves D the location cursor to the entryI located at the same relative positionv; on the previous screen.c H svn_extend_to_top Extends selection from the currentlyI selected entry to the top entry known H to SVN. Moves the location cursor to3 that top entry.v H svn_extend_to_bottom Extends selection from the currentlyF selected entry to the bottom entryD known to SVN. Moves the location@ cursor to that bottom entry. H svn_arrow_left Scrolls the display one character to- the left. H svn_arrow_right Scrolls the display one character to. the right. F svn_scroll_to_left Scrolls to the extreme left of the, display. G svn_scroll_to_right Scrolls to the extreme right of the_, display. H svn_page_left Scrolls the display horizontally one= screen width to the left.s H svn_page_right Scrolls the display horizontally one> screen width to the right. D svn_activate_entry Selects and confirms the currentH entry. Equivalent to double clicking( MB1. E svn_select_all Selects all entries known to SVN.n G svn_deselect_all Deselects all entries known to SVN.t H svn_next_column Selects the next column component to. the right. I (continued on next page) % 2-46 Programmer Release Notest
e t I Programmer Release NoteshI 2.10 Toolkit Extensions I Table_2-10_(Cont.)_Action_Routines_for_DXmSvn_Widget_______ I Action_Routine________Description__________________________ I svn_prev_column Selects the previous column component 0 to the left. E LclTraversePrevTabGrouMoves the location cursor (focus) H to the next Tab group. In SVN, thereI are primary and secondary window that G are both scrollable and in separate H TAB groups. This function allows theI focus to move to other window in SVN.e D LclTraverseNextTabGrouMoves the location cursor to theE previous Tab group. In SVN, there I are primary and secondary window thataG are both scrollable and in separate H TAB groups. This function allows theI focus to move to other window in SVN. E svn_cancel Cancels any dragging operation or C extended selection in progress. D Moves the location cursor to theH previous entry that it was on before> the operation was started. D svn_next_level Scrolls to the entry at the next? level in the SVN hierarchy.a H svn_prev_level Scrolls to the entry at the previousI ______________________level_in_the_SVN_hierarchy.__________ I Table 2-11 describes the button syntax translations for the DXmCSText widget.e I Table_2-11_DXmCSText_Widget_Button_Syntax_Translations_____l I Event_________________Action_Routine_______________________0 0 BSelect Press: grab-focus() 3 BSelect Motion: extend-adjust() 0 BSelect Release: extend-end() 2 BExtend Press: extend-start() I (continued on next page)X I Programmer Release Notes 2-47t
t h Programmer Release Notes 2.10 Toolkit Extensions ? Table 2-11 (Cont.) DXmCSText Widget Button Syntax I ___________________Translations____________________________ I Event_________________Action_Routine_______________________ 3 BExtend Motion: extend-adjust() 0 BExtend Release: extend-end() 6 BToggle Press: move-destination() 5 BDrag Press: secondary-start() 6 BDrag Motion: secondary-adjust() - BDrag Release: copy-to()i 5 MCtrl BDrag Press: secondary-start() 6 MCtrl BDrag Motion: secondary-adjust() - MCtrl BDrag Release: copy-to() 5 MAlt BDrag Press: secondary-start()n 6 MAlt BDrag Motion: secondary-adjust() - MAlt BDrag Release: move-to()e 0 KUp: process-up() 6 MShift KUp: process-shift-up() 8 MCtrl KUp: backward-paragraph() > MShift MCtrl KUp: backward-paragraph(extend) 2 KDown: process-down() 8 MShift KDown: process-shift-down() 7 MCtrl KDown: forward-paragraph() = MShift MCtrl KDown: forward-paragraph(extend) 4 KLeft: left-character() 4 MShift KLeft: key-select(left) / MCtrl KLeft: left-word()c 5 MShift MCtrl KLeft: left-word(extend) 5 KRight: right-character() 5 MShift KRight: key-select(right) 0 MCtrl KRight: right-word() 6 MShift MCtrl KRight: right-word(extend) I (continued on next page)e % 2-48 Programmer Release Notes
I Programmer Release Notes I 2.10 Toolkit Extensions ? Table 2-11 (Cont.) DXmCSText Widget Button Syntax I ___________________Translations____________________________C I Event_________________Action_Routine_______________________ 3 KPageUp: previous-page()r 9 MShift KPageUp: previous-page(extend)_ / KPageDown: next-page() 5 MShift KPageDown: next-page(extend) > MCtrl KPageUp: page-horizontal-backward() = MCtrl KPageDown: page-horizontal-forward()e 7 MAlt KLeft: left-side-of-line()s = MShift Malt KLeft: left-side-of-line(extend)o 8 MAlt KRight: right-side-of-line() > MShift MAlt KRight: right-side-of-line(extend) : MCtrl MAlt KLeft: extreme-left-of-file() @ MShift MCtrl MAlt extreme-left-of-file(extend) KLeft: ; MCtrl MAlt KRight: extreme-right-of-file()i A MShift MCtrl MAlt extreme-right-of-file(extexd) KRight:v 4 Malt <Key>F17: toggle-text-path > <Key>F17: toggle-editing-path-move() < MShift <Key>F17: toggle-editing-path-stay 1 KTab: process-tab()t 4 KNextField: next-tab-group() 4 KPrevField: prev-tab-group() 4 KEnter: process-return() . KActivate: activate() ; KDelete: delete-next-character() ? KBackSpace: delete-previous-character() 5 KAddMode: toggle-add-mode() 1 KSpace: self-insert()o 0 KSelect: set-anchor() I (continued on next page)n I Programmer Release Notes 2-49g
e s Programmer Release Notes 2.10 Toolkit Extensions ? Table 2-11 (Cont.) DXmCSText Widget Button Syntax I ___________________Translations____________________________ I Event_________________Action_Routine_______________________ 0 KExtend: key-select() 4 MAny KCancel: process-cancel() 5 KClear: clear-selection() 0 KSelectAll: select-all() 2 KDeselectAll: deselect-all() 3 KCut: cut-clipboard() 4 KCopy: copy-clipboard() 5 KPaste: paste-clipboard() 1 KPrimaryCut: cut-primary() 2 KPrimaryCopy: copy-primary() 2 KPrimaryPaste: copy-primary() 3 KQuickCut: quick-cut-set() 4 KQuickCopy: quick-copy-set() 4 KQuickPaste: quick-copy-set() 5 KQuickExtend: do-quick-action()g * KHelp: Help() I KAny:_________________self-insert()________________________ F Table 2-12 further describes the action routines for the DXmCSText widget.a I Table_2-12_DXmCSText_Widget_Action_Routines________________e I Action_Routine________Description__________________________r ; activate(): Calls the callbacks fore8 XmNactivateCallback. B backward- Moves the insertion cursor one: character(): character to the left. I (continued on next page) % 2-50 Programmer Release Notes
I Programmer Release Notes I 2.10 Toolkit Extensions I Table_2-12_(Cont.)_DXmCSText_Widget_Action_Routines________ I Action_Routine________Description__________________________r G backward- If XmNeditMode is XmMULTI_LINE_EDITvE paragraph(extend): and this action is called with no H argument, moves the insertion cursorH to the first nonwhitespace characterF following the first previous blankB line or beginning of the text. I If the insertion cursor is already ateG the beginning of a paragraph, moves I the insertion cursor to the beginning > of the previous paragraph. C If XmNeditMode is XmMULTI_LINE_ G EDIT and this action is called withlF extend, moves the insertion cursorE as in the case of no argument and : extends the selection. D backward- If this action is called with noH word(extend): argument, moves the insertion cursorH to the first nonwhitespace characterH after the first whitespace characterG to the left or the beginning of the_D line. If the insertion cursor isG already at the beginning of a word, E moves the insertion cursor to the C beginning of the previous word.n D If called with extend, moves theI insertion cursor as in the case of nooG argument and extends the selection.r @ beep(): Causes the terminal to beep. D beginning-of- If this action is called with noH file(extend): argument, moves the insertion cursorA to the beginning of the text. D If called with extend, moves theI insertion cursor as in the case of no G argument and extends the selection. I (continued on next page) I Programmer Release Notes 2-51
x d Programmer Release Notes 2.10 Toolkit Extensions I Table_2-12_(Cont.)_DXmCSText_Widget_Action_Routines________ I Action_Routine________Description__________________________e D beginning-of- If this action is called with noH line(extend): argument, moves the insertion cursorA to the beginning of the line.o D If called with extend, moves theI insertion cursor as in the case of no G argument and extends the selection.m C clear-selection(): Clears the current selection by_D replacing each character, exceptG <Return>, with a <space> character. G copy-clipboard(): Copies the current selection to the . clipboard. G copy-primary(): Copies the primary selection to theX5 insertion cursor.m D copy-to(): If a secondary selection exists,I copies the secondary selection to theS5 insertion cursor._ E If no secondary selection exists,_G copies the primary selection to then5 pointer location.n E cut-clipboard(): Cuts the current selection to thed. clipboard. E cut-primary(): Cuts the primary selection to thed5 insertion cursor.i G delete-next- If XmNpendingDelete is TRUE and the C character(): cursor is inside the selection, A deletes the entire selection;rD
otherwise, deletes the character@ following the insert cursor. I (continued on next page)c % 2-52 Programmer Release Notes
I Programmer Release NoteseI 2.10 Toolkit Extensions I Table_2-12_(Cont.)_DXmCSText_Widget_Action_Routines________ I Action_Routine________Description__________________________r G delete-next-word(): If XmNpendingDelete is TRUE and the C cursor is inside the selection,rA deletes the entire selection; E otherwise, deletes the characterscE following the insertion cursor to F the next space, tab or end of line. character. G delete-previous- If XmNpendingDelete is TRUE and the8C character(): cursor is inside the selection, A deletes the entire selection; D otherwise, deletes the characterE of text immediately preceding the_5 insertion cursor._ G delete-previous- If XmNpendingDelete is TRUE and the_C word(): cursor is inside the selection, A deletes the entire selection; E otherwise, deletes the characters I preceding the insertion cursor to theaH next space, tab or beginning of line. character. B delete-selection(): Deletes the current selection. H delete-to-end-of- Deletes the characters following theG line(): insertion cursor to the next end of 3 line character. D delete-to-start-of- Deletes the characters precedingH line(): the insertion cursor to the previous@ beginning of line character. D deselect-all(): Deselects the current selection. @ do-quick-action(): Marks the end of a secondaryH selection. Performs the quick actionF initiated by the quick-copy-set or9 quick-cut-set action. I (continued on next page) I Programmer Release Notes 2-53
D Programmer Release Notes 2.10 Toolkit Extensions I Table_2-12_(Cont.)_DXmCSText_Widget_Action_Routines________o I Action_Routine________Description__________________________ D end-of-file(extend): If this action is called with noH argument, moves the insertion cursor; to the end of the text.s D If called with extend, moves theI insertion cursor as in the case of no G argument and extends the selection. D end-of-line(extend): If this action is called with noH argument, moves the insertion cursor; to the end of the line.r D If called with extend, moves theI insertion cursor as in the case of no G argument and extends the selection. C extend-adjust(): Selects text from the anchor toaF the pointer position and deselectsG text outside that range. Moving theiF pointer over several lines selectsF text from the anchor to the end ofH each line the pointer moves over andE up to the pointer position on the 1 current line._ E extend-end(): Moves the insertion cursor to theh< position of the pointer. I extend-start(): Adjusts the anchor using the balance-_F beam method. Selects text from theF anchor to the pointer position andF deselects text outside that range. D extreme-left-of- If this action is called with noF file(extend): argument and the current text pathI is left to right, moves the insertion0H cursor to the beginning of the text. F If called with no argument and theG current text path is right to left,2I moves the insertion cursor to the endR0 of the text. I (continued on next page)v % 2-54 Programmer Release Notes
s t I Programmer Release NotesnI 2.10 Toolkit Extensionsa I Table_2-12_(Cont.)_DXmCSText_Widget_Action_Routines________b I Action_Routine________Description__________________________ D If called with extend, moves theI insertion cursor as in the case of no G argument and extends the selection. F The text path can be initially setF using the DXmNtextPath resource orI interactively (see toggle-text-path). D extreme-right-of- If this action is called with noF file(extend): argument and the current text pathI is left to right, moves the insertion B cursor to the end of the text. F If called with no argument and theG current text path is right to left, E moves the insertion cursor to the : beginning of the text. D If called with extend, moves theI insertion cursor as in the case of no G argument and extends the selection. F The text path can be set initiallyF using the DXmNtextPath resource orI interactively (see toggle-text-path). B forward- Moves the insertion cursor one; character(): character to the right. H forward- If XmNeditMode is XmMULTI_LINE_EDIT,E paragraph(extend): and this action is called with no H argument, moves the insertion cursorI the the first nonwhitespace character I following the next blank line. If the F insertion cursor is already at theG beginning of a paragraph, moves the H insertion cursor to the beginning of7
the next paragraph.k I (continued on next page)R I Programmer Release Notes 2-55_
_ _ Programmer Release Notes 2.10 Toolkit Extensionsw I Table_2-12_(Cont.)_DXmCSText_Widget_Action_Routines________r I Action_Routine________Description__________________________ C If XmNeditMode is XmMULTI_LINE_ G EDIT and this action is called with F extend, moves the insertion cursorE as in the case of no argument and : extends the selection. D forward- If this action is called with noH word(extend): argument, moves the insertion cursorE to the first whitespace character E or end of line following the next C nonwhitespace character. If the(F insertion cursor is already at theF end of a word, moves the insertionG cursor to the end of the next word. D If called with extend, moves theI insertion cursor as in the case of nooG argument and extends the selection.s H grab-focus(): This key binding performs the actionG in the XmNselectArray, depending on H the number of multiple mouse clicks.H The default selection array orderingF is one click to move the insertionG cursor to the pointer position, two I clicks to select a word, three clickslF to select a line of text, and four> clicks to select all text. ; Help(): Calls the callbacks for D XmNhelpCallback if any exist. IfH there are no help callbacks for thisF widget, this action calls the helpF callbacks for the nearest ancestor2 that has them. C insert- If XmNpendingDelete is TRUE andiG string(string): the cursor is inside the selection, I deletes the entire selection. Inserts E "string" at the insertion cursor. I (continued on next page) % 2-56 Programmer Release Notes
I Programmer Release NotesrI 2.10 Toolkit Extensions I Table_2-12_(Cont.)_DXmCSText_Widget_Action_Routines________ I Action_Routine________Description__________________________ A key- If called with an argument oftG select(direction): "right", moves the insertion cursorsB one character to the right andD extends the selection. If calledI with an argument of "left", moves thecI insertion cursor one character to thesF left and extends the selection. IfH called with no argument, extends the. selection. G kill-next- If XmNpendingDelete is TRUE and theoC character(): cursor is inside the selection, A deletes the entire selection. B Otherwise, kills the characterF following the insertion cursor andC stores the character in the cut.+ buffer.e G kill-next-word(): If XmNpendingDelete is TRUE and the C cursor is inside the selection,rA deletes the entire selection.eC Otherwise, kills the characters-E following the insertion cursor tooF the next space, tab or end of lineH character, and stores the characters6 in the cut buffer. G kill-previous- If XmNpendingDelete is TRUE and the C character(): cursor is inside the selection, A deletes the entire selection. B Otherwise, kills the characterE of text immediately preceding the C insertion cursor and stores the @ character in the cut buffer. I (continued on next page) I Programmer Release Notes 2-57
Programmer Release Notes 2.10 Toolkit Extensions I Table_2-12_(Cont.)_DXmCSText_Widget_Action_Routines________ I Action_Routine________Description__________________________o G kill-previous- If XmNpendingDelete is TRUE and thetC word(): cursor is inside the selection,eA deletes the entire selection. C Otherwise, kills the characters E preceding the insertion cursor to D the next space, tab or beginningE of line character, and stores the A characters in the cut buffer. I kill-selection(): Kills the currently selected text and F stores the text in the cut buffer. F kill-to-end-of- Kills the characters following theD line(): insertion cursor to the next endD of line character and stores theA characters in the cut buffer. B kill-to-start-of- Kills the characters precedingD line(): the insertion cursor to the nextC beginning of line character anduD stores the characters in the cut+ buffer. B left-character(): Moves the insertion cursor one: character to the left. D left-side-of- If this action is called with noF line(extend): argument and the current text pathI is left to right, moves the insertion H cursor to the beginning of the line. F If called with no argument and theG current text path is right to left, I moves the insertion cursor to the endl0 of the line. D If called with extend, moves theI insertion cursor as in the case of nomG argument and extends the selection.c I (
ntinued on next page)c % 2-58 Programmer Release Notes
I Programmer Release NotesNI 2.10 Toolkit Extensionse I Table_2-12_(Cont.)_DXmCSText_Widget_Action_Routines________a I Action_Routine________Description__________________________x F The text path can be set initiallyF using the DXmNtextPath resource orI interactively (see toggle-text-path).t D left-word(extend): If this action is called with noA argument and the current textrD path is left to right, moves theA insertion cursor to the firsttE nonwhitespace character after the E first whitespace character to thelF left or the beginning of the line.F If the insertion cursor is alreadyI at the beginning of a word, moves theeH insertion cursor to the beginning of6 the previous word. D If this action is called with noI argument and the current text path islF right to left, moves the insertionB cursor to the first whitespaceF character or end of line followingE the next nonwhitespace character.oF If the insertion cursor is alreadyC at the end of a word, moves theeF insertion cursor to the end of the. next word. D If called with extend, moves theI insertion cursor as in the case of no G argument and extends the selection. F The text path can be set initiallyF using the DXmNtextPath resource orI interactively (see toggle-text-path). E move-destination(): Moves the insertion cursor to the I pointer position without changing any G existing selection. If no selection F exists, also moves the destinationC cursor to the pointer position.e I (continued on next page) I Programmer Release Notes 2-59
r Programmer Release Notes 2.10 Toolkit Extensionsw I Table_2-12_(Cont.)_DXmCSText_Widget_Action_Routines________s I Action_Routine________Description__________________________s D move-to(): If a secondary selection exists,G cuts the secondary selection to thetE insertion cursor. If no secondary F selection exists, cuts the primaryF selection to the pointer location. C new-line(): If XmNpendingDelete is TRUE andNG the cursor is inside the selection,rI deletes the entire selection. Inserts F a newline at the insertion cursor. G newline-and- If XmNpendingDelete is TRUE and the C backup(): cursor is inside the selection, A deletes the entire selection.oE Inserts a newline and repositionslF the insertion cursor to the end of@ the line before the newline. C newline-and- If XmNpendingDelete is TRUE andhG indent(): the cursor is inside the selection,aI deletes the entire selection. Inserts F a newline and then the same numberF of whitespace characters as at theC beginning of the previous line. E next-line(): Moves the insertion cursor to thet. next line. E next-page(extend): If this action is called with now H argument, moves the insertion cursor5 forward one page. D If called with extend, moves theI insertion cursor as in the case of noDG argument and extends the selection._ D next-tab-group(): Traverses to the next tab group. G page-horizontal- If the current text path is left to:E backward(): right, scrolls the viewing window : left one path of text. I (continued on next page) % 2-60 Programmer Release Notesh
I Programmer Release Notes I 2.10 Toolkit Extensions I Table_2-12_(Cont.)_DXmCSText_Widget_Action_Routines________ I Action_Routine________Description__________________________n E If the current text path is rightnG to left, scrolls the viewing windowi; right one path of text., F The text path can be set initiallyF using the DXmNtextPath resource orI interactively (see toggle-text-path). G page-horizontal- If the current text path is left to E forward(): right, scrolls the viewing window ; right one path of text. H If the current text path is right toI left, scrolls the viewing window left 5 one path of text. F The text path can be set initiallyF using the DXmNtextPath resource orI interactively (see toggle-text-path).r G page-left(): Scrolls the viewing window left one 1 page of text. H page-right(): Scrolls the viewing window right one1 page of text.h H paste-clipboard(): Pastes the contents of the clipboard@ before the insertion cursor. H prev-tab-group(): Traverses to the previous tab group. E previous-line(): Moves the insertion cursor to theN2 previous line. D previous- If this action is called with noH page(extend): argument, moves the insertion cursor2 back one page. D If called with extend, moves theI insertion cursor as in the case of no G argument and extends the selection. I (continued on next page) I Programmer Release Notes 2-61
Programmer Release Notes 2.10 Toolkit Extensions I Table_2-12_(Cont.)_DXmCSText_Widget_Action_Routines________r I Action_Routine________Description__________________________u G process-cancel(): Cancels the current extend-adjust()tG or secondary-adjust() operation andhH leaves the selection state as it was9 before the operation.l H process-down(): If XmNeditMode is XmSINGLE_LINE_EDITD and XmNnavigationType is XmNONE,E traverses to the widget below the A current one in the tab group.f H If XmNeditMode is XmMULTI_LINE_EDIT,G moves the insertion cursor down one ) line.o F process-home(): Moves the insertion cursor the the: beginning of the line. D process-return(): If XmNeditMode is XmSINGLE_LINE_A EDIT, calls the callbacks foroG XmNactivateCallback. If XmNeditModeiC is XmMULTI_LINE_EDIT, inserts ai, newline. H process-shift- If XmNeditMode is XmMULTI_LINE_EDIT,G down(): moves the insertion cursor down one ) line. H process-shift-up(): If XmNeditMode is XmMULTI_LINE_EDIT,E moves the insertion cursor up one ) line.e I process-tab(): If XmNeditMode is XmSINGLE_LINE_EDIT,nG traverses to the next tab group. If E XmNeditMode is XmMULTI_LINE_EDIT, 2 inserts a tab. H process-up(): If XmNeditMode is XmSINGLE_LINE_EDITD and XmNnavigationType is XmNONE,E traverses to the widget above the = current one in tab group. I (continued on next page) % 2-62 Programmer Release Notest
I Programmer Release Notes I 2.10 Toolkit Extensions I Table_2-12_(Cont.)_DXmCSText_Widget_Action_Routines________ I Action_Routine________Description__________________________e H If XmNeditMode is XmMULTI_LINE_EDIT,E moves the insertion cursor up one ) line. F quick-copy-set(): Marks the beginning of a secondaryD selection for use in quick copy. F quick-cut-set(): Marks the beginning of a secondaryC selection for use in quick cut. D redraw-display(): Redraws the contents of the text, windows. B right-character(): Moves the insertion cursor one; character to the right.t D right-side-of- If this action is called with noF line(extend): argument and the current text pathI is left to right, moves the insertionaB cursor to the end of the line. F If called with no argument and theG current text path is right to left, E moves the insertion cursor to the : beginning of the line. D If called with extend, moves theI insertion cursor as in the case of no G argument and extends the selection. F The text path can be set initiallyF using the DXmNtextPath resource orI interactively (see toggle-text-path). I (continued on next page) I Programmer Release Notes 2-63
Programmer Release Notes 2.10 Toolkit Extensions I Table_2-12_(Cont.)_DXmCSText_Widget_Action_Routines________ I Action_Routine________Description__________________________a D right-word(extend): If this action is called with noI argument and the current text path isRF left to right, moves the insertionB cursor to the first whitespaceF character or end of line followingE the next nonwhitespace character. F If the insertion cursor is alreadyC at the end of a word, moves the F insertion cursor to the end of the. next word. D If this action is called with noA argument and the current texttD path is right to left, moves theA insertion cursor to the firstuE nonwhitespace character after theeE first whitespace character to the F left or the beginning of the line.F If the insertion cursor is alreadyI at the beginning of a word, moves thelH insertion cursor to the beginning of6 the previous word. D If called with extend, moves theI insertion cursor as in the case of nofG argument and extends the selection.i F The text path can be set initiallyF using the DXmNtextPath resource orI interactively (see toggle-text-path).o H scroll-one-line- Scrolls the text area down one line. down(): F scroll-one-line- Scrolls the text area up one line. up():m F secondary-adjust(): Extends the secondary selection to9 the pointer position.d I secondary-notify(): Copies the secondary selection to thet7 destination cursor. I (continued on next page)h % 2-64 Programmer Release Notes
I Programmer Release Notes I 2.10 Toolkit Extensionse I Table_2-12_(Cont.)_DXmCSText_Widget_Action_Routines________e I Action_Routine________Description__________________________E F secondary-start(): Marks the beginning of a secondary. selection. H select-adjust(): Extends the selection. The amount ofG text selected depends on the number H of mouse clicks, as specified by the? XmNselectionArray resource. 4 select-all(): Select all text. H select-end(): Extends the selection. The amount ofG text selected depends on the number H of mouse clicks, as specified by the? XmNselectionArray resource. @ select-start(): Marks the beginning of a new5 selection region.h C self-insert(): If XmNpendingDelete is TRUE anddG the cursor is inside the selection, I deletes the entire selection. Inserts I the character associated with the key D pressed at the insertion cursor. H set-anchor(): Resets the anchor point for extendedI selections. Resets the destination of @ secondary selection actions. = set-insertion- Sets the insertion point. point(): H set-selection- Sets the text source and location of2 hint(): the selection. B toggle-add-mode(): Toggles the state of Add Mode. G toggle-editing-path- Toggles the editing path direction.o move(): I If the direction is toggled for righteI to left editing, the insertion cursor B stays at the current position. I (continued on next page)o I Programmer Release Notes 2-65a
e n Programmer Release Notes 2.10 Toolkit Extensionso I Table_2-12_(Cont.)_DXmCSText_Widget_Action_Routines________r I Action_Routine________Description__________________________ H If the direction is toggled for leftC to right editing, the insertioneF cursor will move to the right mostE position of the previous right to . left text. G toggle-editing-path- Toggles the editing path direction. E stay(): The insertion cursor stays at ther5 current position.T C toggle-text-path(): Toggles the text path direction E of the entire text. Inverses each C segment's direction, creating a F mirror image of the original text. H traverse-home(): Traverses to the first widget in the. tab group. G traverse-next(): Traverses to the next widget in the . tab group. G traverse-prev(): Traverses to the previous widget in_2 the tab group. D unkill(): Restores last killed text to theI ______________________position_of_the_insertion_cursor.____T H Table 2-13 describes additional behavior for the DXmCSText widget.f I Table_2-13_Additional_DXmCSText_Behavior___________________ I ______________________Description__________________________ I <FocusIn>: Draws the insertion cursor and starts 8 blinking the cursor. I <FocusOut>:___________Stops_blinking_the_cursor.___________- % 2-66 Programmer Release Notes_
T I Programmer Release Notes I 2.10 Toolkit Extensions : 2.10.7 SVN-Horizontal Live Scrolling Not Supported A V1.0 The following problem exists with customized (live) I scrolling in the (Structured Visual Navigation) SVN widget. G Horizontal live scrolling is not yet supported by the SVN widget.t , 2.10.8 SVN Horizontal Separator Line E V1.1 When displaying an application that uses the SVN widgetsD on a Sun system running OpenWindows V2, the horizontalG separator line of the SVN widget is not always displayed. G This is due to a problem with the OpenWindows server. TheS9 problem does not exist with OpenWindows V3.n 2.11 UIL Extensions_ B The following section provides information about UIL extensions., 5 2.11.1 DXmFormSpaceButtonsEqually Restriction G V1.1 The convenience routine, DXmFormSpaceButtonsEqually sizes D and spaces all widgets or gadgets equally if they haveE a subclass of XmLabel or XmLabelGadget. The results are B undefined if a widget or gadget is not a subclass of' XmLabel or XmLabelGadget. 2.11.2 UIL Compiler G V1.1 Certain arithmetic operations in the UIL compiler and WML I compilation process have been corrected. You must recompilehG any WMD files that were generated with a previous versiontG of VMS DECwindows Motif. If you do not recompile, you getdH an XtMalloc error when you use the WIDGET_META_DESCRIPTION! qualifier with UIL. " 2.12 VAX C Sample Programs C V1.0 During the VAX C installation procedure, you have thelF option to extract the VAX C definition files (.h files),G or leave the .h files in the text library. If you extract H the definition files, you are able to use #include control* lines of the following form: # #include <filename.h> I Programmer Release Notes 2-67
Programmer Release Notes" 2.12 VAX C Sample Programs G All DECwindows sample C programs assume that the .h files C were extracted; the samples contain #include <module_ E name.h> notation for the included files. The DECwindows C programming documentation also makes this assumption. G VAX C should be installed using the option to extract the library modules. I If you have already installed VAX C and you did not extractsI the .h files, the DECwindows sample C programs do not work.mI To correct this problem, reinstall VAX C and extract the .h_ files. : 2.13 VAXstations 3520 and 3540-Problem Running DTM B V1.0 The XTrap server extension does not work properly onG VAXstations 3520 and 3540. Since the Digital Test ManagereD (DTM) uses the XTrap extension, running DTM causes theH DECwindows server to enter a compute-bound state. The only; recovery method is to reboot the workstation. 2.14 X11 Display Serverr E This section contains information about the X11 Displayy Server. = 2.14.1 100 DPI Fonts Not Available on 75 DPI Monitors E V1.0 Applications displaying on DECwindows workstations with C 75 dpi monitors cannot access 100 dpi fonts. However,tC applications displaying to 100 dpi monitors can stilluF access 75 dpi fonts, but you should program applicationsF to use only the 100 dpi fonts when displaying to 100 dpi monitors. ? Access to 75 dpi fonts when displaying to 100 dpi G monitors is provided for compatibility with older Digital G applications that use only 75 dpi font names. Support for G using 75 dpi fonts on 100 dpi monitors will be phased out " in a future release. B To use applications that use only 100 dpi font namesF with 75 dpi monitors, enter the following command from a! privileged account: > $ SET FILE SYS$COMMON:[SYSFONT.DECW.100DPI]*.* -= _$ /ENTER=SYS$COMMON:[SYSFONT.DECW.USER_COMMON]n % 2-68 Programmer Release Notesr
e a I Programmer Release NotesaI 2.14 X11 Display Servera I You must end the current session and start a new session toe5 make the fonts available to the server.l / 2.14.2 Backingstore Disable-New Feature) E V1.0 Backingstore support can now be disabled in the server.n? To disable backingstore, define the global symbolxF DECW$SERVER_DISABLE_BACKING_STORE to be TRUE in the fileC SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM as follows:e 9 $ DECW$SERVER_DISABLE_BACKING_STORE=="TRUE" & 2.14.3 Color Name File-Updated G V1.0 The file DECW$RGB.COM now contains all of the color names4G and values that were distributed with MIT X Window System F Version 11 Release 4 (MIT X11 Release 4). The colors areG listed in DECW$RGB.COM in alphabetical order so that they-I can be easily compared with the table of common color namesnA published in the X and Motif Quick Reference Guide. B Following the list of MIT X11 Release 4 common colorF names in the file DECW$RGB.COM is a list of a set of theH Digital specific color names and their values. These namesG include DECWBlue and a set of color names for the default ' DECwindows system colors.e E The color value for DECWBlue has been changed to better F reflect the Digital corporate standard for Digital Blue. I The following color names are the default DECwindows system colors:e " o Screen background ! o Border topshadowk " o Border background $ o Border bottomshadow ! o Window topshadowa " o Window background $ o Window bottomshadow H These color names are also specified without spaces in theF names (for example, ScreenBackground), as are all of the3 MIT X11 Release 4 common color names. I Programmer Release Notes 2-69h
h c Programmer Release Notes 2.14 X11 Display Server H Following the Digital specific color names in DECW$RGB.COMB are four additional color names and values that wereE included in previous releases of the DECwindows systemsoD but that are not part of the MIT X11 Release 4 colors. These colors are: $ o Medium forest green " o MediumForestGreen ! o Medium goldenrod o MediumGoldenrod - 2.14.4 Compatibility Option in Serverd H V1.0 There were some inconsistencies between pre-X11 R4 serversD and the X11 protocol that allowed undefined bits to beE set in some X requests. By strictly enforcing this part B of the protocol, however, some applications that setG undefined bits no longer worked. To remedy the situation, D there i
new server option that relaxes the protocolG enforcement for the event masks passed to the following X I library calls: XChangeWindowAttributes (when specifying the I CWDontPropagate value mask), XGrabPointer, and XGrabButton. H In VMS DECwindows Motif Version 1.0, the default value forF this option is On; however, this will likely change in aI future release of DECwindows Motif. To disable this option, G define the global symbol DECW$SERVER_BUG_COMPATIBILITY as I FALSE in the file SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM as follows:t 6 $ DECW$SERVER_BUG_COMPATIBILTIY=="FALSE" A It is suggested that you disable this option unlesstC you find that you have an application that needs this D compatibility to run. If you do, Digital suggests thatH you either recode the application, removing undefined bitsH from these event masks, or contact your software supplier. % 2-70 Programmer Release Notesr
a o I Programmer Release NotestI 2.14 X11 Display Server 6 2.14.5 Default Character Processing Correction ? V1.0 If an attempt was made to display an undefined or D nonexistent character in a font and that character wasF between the minimum and maximum columns of the font, theH server displayed nothing instead of displaying the defaultE character specified for the font. This problem has beend corrected. 3 2.14.6 Font Names Now Returned in Lowercase A V1.0 In order to strictly conform to the X protocol, the F DECwindows X server has been modified to return all fontG names in lowercase. This modification does not affect thesG majority of applications, as font name matching is always * done without regard to case. 9 2.14.7 Known Problems with the X11 Display Servers G V1.0 The following problems occur with the X11 Display Server:o G o Backingstore is not supported for the VAXstations 3520.H and 3540. If a client requests Backingstore, the serverE does not provide it and continues to generate Exposez events. E o On a GPX system, if you run a new server with an old B graphics device driver, the cursor colors are notI updated. To update the cursor colors, you have to reboot ; your system to load the new device driver.e . 2.14.8 Server Infinite Loop Correction A V1.0 If a client application quickly opened and closed atE connection to the server (for example, in order to test H for the existence of a server), the server would sometimesD go into an infinite loop and not process requests fromF other clients. The screen would appear to freeze and theI only workaround was to restart the server. This problem has1 been corrected.o I Programmer Release Notes 2-71
t Programmer Release Notes$ 2.15 X Image Extension (XIE) $ 2.15 X Image Extension (XIE) I V1.1 The X Image Extension (XIE) allows image display processing D to be done using resources on the server side of the XH client-server model. XIE eliminates the need to repeatedlyH transmit image data from the client to the server and alsoH allows data to be transmitted in compressed form, reducing the network load. F VMS DECwindows Motif Version 1.1 includes the XIE clientC side sharable library (XIE$SHRLIB.EXE) and C language H header files. These allow applications to communicate with= any X11 server that supports the XIE extension.l A An XIE program uses a structure called the XIEImage B to describe image data on the client side. This is aH general mechanism that describes data that the destinationC server is incapable of processing. You should consult E the documentation for the server system for informationaD on what data types and sizes are supported. Unless theB documentation specifies different limits, the serverD is capable of processing unsigned byte (UdpK_DTypeBU),G unaligned bit field (UdpK_DTypeVU), and aligned bit fieldrD (UdpK_DTypeV) data, with a maximum depth of 8 bits perH pixel per component. The XIE client library supports theseH data types, as well as unsigned word (UdpK_DTypeWU), and a= depth of up to 16 bits per pixel per component.s B The XIE protocol and programming interface are beingE standardized within the X Consortium, and programs that D use XIE will probably have to be modified. You can useD the Image Display Services (IDS) component of DECimageC Application Services for VMS as an alternative to the F XIE library interface. IDS provides a higher level modelD of image display and automatically uses XIE when it is( available and appropriate. H XIE is documented in the DECimage Application Services forB VMS X Image Extension Programmer's Reference Manual. 2.16 Xlib Extensions F This section contains information about Xlib extensions. % 2-72 Programmer Release Notes
5 i I Programmer Release NoteslI 2.16 Xlib Extensionst ' 2.16.1 Xlib Client Side Library C V1.1 For Version 1.1, Xlib has added a client side library A that allows VMS clients to issue Shape, XInput, andgD Multibuffer extension requests to servers that provideF these features (for example, the VAX VMS server does notG support the Shape extension). The name of this library isw" DECW$XEXTLIBSHR.EXE. A You must modify the linking file options for client C applications that issue Shape, XInput, or MultibufferlI extension requests to link to the Xlib extensions shareable I image in SYS$LIBRARY:DECW$XEXTLIBSHR.EXE. Add the following$/ line to your linker options file:8 0 SYS$LIBRARY:DECW$XEXTLIBSHR/SHARE D For more information on Shape, XInput, and MultibufferC extensions, see the following text files in SYS$HELP: o SHAPE.TXT o XINPUT.TXTa o MULTIBUFFER.TXT 2.16.2 Xlib Routines D This section contains information about Xlib routines. - 2.16.2.1 Ada Bindings File Incomplete H V1.0 VMS DECwindows Motif Version 1.0 does not include completeH Xlib programming support for the Ada programming language.G Routines added to Xlib for this release are not available F in the Ada bindings. The routines are listed as follows: ? ALLOC_CLASS_HINT LIST_PIXMAP_FORMATS A ALLOC_ICON_SIZE RECONFIGURE_WM_WINDOWd ? ALLOC_NAMED_COLOR RM_DESTROY_DATABASEa C ALLOC_SIZE_HINTS SCREEN_NUMBER_OF_SCREENR = ALLOC_STANDARD_COLORMAP SET_RGB_COLORMAPSe = FREE_STRING_LIST SET_TEXT_PROPERTY A GET_COMMAND SET_WM_CLIENT_MACHINE C GET_GC_VALUES SET_WM_COLORMAP_WINDOWSa I Programmer Release Notes 2-73
c c Programmer Release Notes 2.16 Xlib Extensions 8 GET_RGB_COLORMAPS SET_WM_HINTS < GET_TEXT_PROPERTY SET_WM_ICON_NAME 7 GET_WM_CLIENT_MACHINE SET_WM_NAMEh ? GET_WM_COLORMAP_WINDOWS SET_WM_NORMAL_HINTS = GET_WM_HINTS SET_WM_PROPERTIES < GET_WM_ICON_NAME SET_WM_PROTOCOLS = GET_WM_NAME SET_WM_SIZE_HINTS H GET_WM_NORMAL_HINTS STRING_LIST_TO_TEXT_PROPERTY H GET_WM_PROTOCOLS TEXT_PROPERTY_TO_STRING_LIST ; ICONIFY_WINDOW WITHDRAW_WINDOWt 7 LIST_DEPTHS WM_GEOMETRYk 4 2.16.2.2 Command Procedure Builds .PEN Files E V1.0 To allow Pascal programs to "inherit" environment filesrG for Xlib and Motif, the system manager should execute thetD command procedure SYS$LIBRARY:DECW$PEN_BUILD.COM. ThisB command procedure generates the DECW$XLIBDEF.PEN andF DECW$MOTIF.PEN files. The .PEN files compile into Pascal; programs faster than the provided .PAS files.u 7 2.16.2.3 Parameter/Protocol Datasize Mismatches G V1.0 Several Xlib routines accept longword parameters that are I not sent in their entirety in the X Protocol message to the G server. In each case, the Xlib routine sends out only theeI least significant 16 bits of the parameter value. This is aeI constraint of the field size within the X Protocol message. G Table 2-14 lists routine names and the longword arguments 2 that are sent only as 16-bit values. I Table_2-14_Routine_Arguments_______________________________a I Routine_Name_________________________Arguments_____________ B XAllocColorCells/ALLOC_COLOR_CELLS nplanes,npixels D XDrawArc/DRAW_ARC x,y,width,height,@ angle1,angle2 > XDrawLine/DRAW_LINE x1,x2,x3,x4 I (continued on next page)l % 2-74 Programmer Release Notese
l e I Programmer Release NotesyI 2.16 Xlib Extensions$ I Table_2-14_(Cont.)_Routine_Arguments_______________________ I Routine_Name_________________________Arguments_____________ 6 XDrawPoint/DRAW_POINT x,y C XDrawRectangle/DRAW_RECTANGLE x,y,width,heightb 6 XDrawString/DRAW_STRING x,y 6 XDrawString16/DRAW_STRING16 x,y 6 XDrawText/DRAW_TEXT x,y 6 XDrawText16/DRAW_TEXT16 x,y = XFillArc/FILL_ARC x,y,width, G height,angle1,angle2 I XFillRectangle/FILL_RECTANGLE________x,y,width,height______P ? 2.16.3 XSelectAsyncEvent and XSelectAsyncInput Routinesp > V1.1 The XSelectAsyncEvent and XSelectAsyncEventInputF routines allocate memory for the storage of AST delivery@ information. This memory is freed in several ways: D o If you close a display (XCloseDisplay), all the ASTI delivery information associated with all windows on that6" display is freed. B o If you destroy a window (XDestroyWindow), the AST? delivery information for that window is freed. I The AST delivery information for subwindows is not freed by XDestroyWindow. D If you want to turn off AST notification for all event? types within a given window and also free the ASTDC delivery information, the client application can call G XSelectAsyncEvent or XSelectAsyncInput passing the event_rF mask argument equal to minus one (all bits set), and the1 ast_routine argument equal to zero. I Programmer Release Notes 2-75
I 3eI _________________________________________________________________r I Documentation Release Notesv ? This chapter describes the following information: 4 o DEC CDA Base Services documentation 3 o VMS DECwindows Motif documentationm ? o VMS DECwindows Motif documentation corrections) 3.1 CDA Documentation A V1.0 The DEC CDA Base Services programming documentation A set describes how software developers can write CDA F supported applications and converters. You can order theH complete documentation set, or you can order the following individual books:e I o The Technical Overview of the DEC CDA Base Services (AA-ID PHJYA-TE) provides an overview of compound documentB processing terminology and the various componentsD of the CDA architecture, which include the DDIF andF DTIF interchange formats, the CDA data structures andI access routines, the converter architecture, and the CDAl Viewer. C o Creating Compound Documents Using the DEC CDA Basee@ Services (AA-PHK2A-TE) provides a tutorial thatG describes how to use the CDA access routines to create)? CDA conforming compound document applications.t H o Writing Converters Using the DEC CDA Base Services (AA-H PHK1A-TE) provides a tutorial that describes how to useF the CDA access routines to write CDA conforming front- end and back end converters.r I Documentation Release Notes 3-1Y
s l # Documentation Release Notes 3.1 CDA Documentationm H o Reference Manual (Volume 1) (AA-PHJZA-TE) and ReferenceB Manual (Volume 2) (AA-PHKOA-TE) provide referenceC material that supplements the two CDA user guides. H These two manuals describe the DDIF and DTIF aggregatesG and syntax diagrams, the CDA access routines and user- F defined routines, converter routines, callable windowF and character-cell CDA Viewer routines, and converter! widget routines.s . 3.2 VMS DECwindows Motif Documentation E V1.1 VMS DECwindows Motif Version 1.1 provides both user anddI programming documentation. The user documentation describesoF the Digital user interface and the applications includedB with VMS DECwindows Motif. Programming documentationE describes the various libraries and software componentsf0 that make up VMS DECwindows Motif. E Because VMS DECwindows Motif contains industry-standard H software components (OSF/Motif, MIT Xlib, and Intrinsics),E Digital is also providing third-party documentation foraE those products. The remaining programming documentation F includes reference information for Digital extensions toG Motif, information on programming in non-C languages, and E tutorial information on programming with VMS DECwindows Motif. 1 The user manuals available include: G o VMS DECwindows Motif User's Guide describes how to usee< the user interface to VMS DECwindows Motif. I o VMS DECwindows Motif Applications Guide describes how torH use the applications bundled with VMS DECwindows Motif. 8 The programming manuals available include: B o DECwindows Extensions to Motif provides reference@ information on the Digital extensions to Motif. F o VMS DECwindows Guide to Non-C Bindings describes non-D C bindings for Xlib, Intrinsics, Motif Toolkit, and, Digital extension routines. I o DECwindows Companion to the OSF/Motif Style Guide covers8H style issues for Digital extensions to Motif and topics< not addressed in the OSF/Motif Style Guide. ' 3-2 Documentation Release Notess
$ I Documentation Release Notes I 3.2 VMS DECwindows Motif Documentations B o VMS DECwindows Transport Manual describes the VMSG DECwindows transport for users who want to write theirn) own transport interface. F o VMS DECwindows Guide to Xlib (Release 4) Programming:G MIT C Binding describes how to program with Xlib using MIT C bindings. F o VMS DECwindows Guide to Xlib (Release 4) Programming:I VAX Binding describes how to program with Xlib using VAXR bindings. F o VMS DECwindows Motif Guide to Application ProgrammingE describes how to program with the Digital extensionsOC to the Motif Toolkit. It supplements the OSF/MotifR$ Programmer's Guide. H o Porting XUI Applications to Motif describes how to portA an existing XUI DECwindows application to Motif.a H o X Window System (from Digital Press) provides reference% information on Xlib.l F o X Window System Toolkit (from Digital Press) provides9 reference information on the Intrinsics.O @ o X and Motif Quick Reference Guide (from DigitalE Press) provides quick reference information on Xlib, 3 Intrinsics, and the Motif Toolkit. E o OSF/Motif Style Guide describes style guidelines for 9 applications based on the Motif Toolkit. D o OSF/Motif Programmer's Reference provides reference2 information on the Motif Toolkit. F o OSF/Motif Programmer's Guide describes how to programF with the Motif Window Manager, Motif Toolkit, and the5 Motif User Interface Language (UIL).2 1 3.3 Corrections to Existing Documentation ? This section contains corrections to existing VMS - DECwindows Motif documentation.l I Documentation Release Notes 3-3M
h # Documentation Release Notesh1 3.3 Corrections to Existing DocumentationN ? 3.3.1 DECwindows Companion to the OSF/Motif Style Guides G V1.0 The first programming hint in Section 1.5.2 of DECwindowsaB Companion to the OSF/Motif Style Guide is incorrect.= Specifically, to use a 67-font-unit margin, setiD XmNunitType=Xm100th_font_units and specify a margin of 67 (not 6700). , 3.3.2 DECwindows Extensions To Motif I This section describes changes to the DECwindows Extensionsl To Motif manual. ' 3.3.2.1 DXmCSTextReplace Formati ? V1.1 In the DECwindows Extensions to Motif manual, then@ DXmCSTextReplace routine has the following format: D void DXmCSTextReplace(widget, from_pos, to_pos, value)# Widget widget; % int from_pos;C# int to_pos; " XmString value; < This routine should have the following format: D void DXmCSTextReplace(widget, from_pos, to_pos, value)- Widget widget; / DXmCSTextPosition from_pos;a- DXmCSTextPosition to_pos; , XmString value; C This change does not cause any problems with previous @ applications that declared the FROM_POS and TO_POSA arguments for DXmCSTextReplace to be int instead of DXmCSTextPosition. C 3.3.2.2 XmNmodifyVerifyCallback Resource Callback StructureO E V1.1 The XmNmodifyVerifyCallback resource callback structure E reference in Chapter 2, Section 2.2, DXmCreateCSText is E incorrect. The correct associated callback structure is , DXmCSTextVerifyCallbackStruct. ' 3-4 Documentation Release Notes
I Documentation Release Notes I 3.3 Corrections to Existing Documentation / 3.3.3 VMS DECwindows Motif User's Guideh H V1.1 The example in "Adding Target Screen Output to ApplicationB Menu Items" in the VMS DECwindows Motif User's GuideE is incorrect. Remove the first occurrence of the line $i! select_qualifiers:.i . 3.3.4 OSF/Motif Programmer's Reference D V1.0 Revision 1.1.1 changes have been made to the OSF/MotifC Programmer's Reference, Revision 1.1 reference pages. G Following is a list of the substantive changes, organizedD by reference page. # 3.3.4.1 Core Reference Pagen F V1.0 In the New Resources section of the DESCRIPTION section,) make the following changes:i ( o Core Resource Set table I - In the Default column, the values for xmNaccelerators > and XmNtranslations are dynamic, not NULL. 8 - In the Access column, the access for? XmNinitialResourcesPersistent is C, not CG.g A o In the descriptions of the widget resources thatoH immediately follow the Core Resource Set table, replace% the text as follows: I - For XmNheight, the description should read "Specifies C the inside height (excluding the border) of the_% widget's window." I - For XmNwidth, the description should state "Specifies B the inside width (excluding the border) of the% widget's window."n C - For XmNx, substitute the text "Specifies the x- G coordinate of the upper left corner of the widget's C window. The value is relative to the upper leftm8 inside corner of the parent window." I - For XmNy, the new text is "Specifies the y-coordinatetH of the upper left corner of the widget's window. TheH value is relative to the upper left inside corner of' the parent window."B I Documentation Release Notes 3-5n
o e # Documentation Release Notes 1 3.3 Corrections to Existing Documentation " 3.3.4.2 mwm Reference Page D V1.0 In the mwm Resource Description File Syntax section ofH the DESCRIPTION section, make the following changes to the table. E o In the Contexts column next to the f.lower function,C& delete the word root. I o In the Resources column next to the f.quit_mwm function, 7 add "(root only)" after the word menu.o E o In the Contexts column next to the f.raise function,t& delete the word root. H o In the Resources column next to the f.restart function,7 add "(root only)" after the word menu.f & 3.3.4.3 RectObj Reference Page
V1.0 In the New Resources section of the DESCRIPTION section,
make changes to the following descriptions of the widget
resources that immediately follow the RectObj Resource Set
table:
o For XmNheight, the description should read "Specifies
the inside height (excluding the border) of the widget's
window."
o For XmNwidth, the description should state "Specifies
the inside width (excluding the border) of the widget's
window."
o For XmNx, substitute the text "Specifies the x-
coordinate of the upper left corner of the widget's
window. The value is relative to the upper left inside
corner of the parent window."
o For XmNy, the new text is "Specifies the y-coordinate
of the upper left corner of the widget's window. The
value is relative to the upper left inside corner of the
parent window."
3-6 Documentation Release Notes
Documentation Release Notes
3.3 Corrections to Existing Documentation
3.3.4.4 VendorShell Reference Page
V1.0 In the DESCRIPTION section, add the following paragraphs to
the existing text:
o "Setting XmNheight, XmNwidth, or XmNborderWidth for
either a VendorShell or its child sets that resource
to the same value in both the parent and the child. An
application should always specify these resources for
the child, not the parent."
o "For a child of a VendorShell, setting XmNx or XmNy
sets the corresponding resource of the parent but does
not change the child's position relative to the parent.
XtGetValues for the child's XmNx or XmNy yields the
value of the corresponding resource in the parent. The
x and y coordinates of the child's upper left outside
corner relative to the parent's upper left inside corner
are both zero minus the value of XmNborderWidth."
o "The Inter-Client Communication Conventions Manual
allows a window manager to change or control the border
width of a reparented top-level window."
3.3.4.5 VirtualBindings Reference Page
V1.0 In the Virtual Key Bindings table found in the Virtual
Key section in the DESCRIPTION section, make the following
changes:
o For KExtend, replace the binding Shift<Key>Space with
"Ctrl Shift<Key>Space ."
o For KReselect, delete the binding Ctrl Shift<Key>Space.
3.3.4.6 WMShell Reference Page
V1.0 The definition of the widget resource XmNwmTimeout in the
New Resource section is expanded. Change the last sentence
in the paragraph to read, "The value is in milliseconds and
must not be negative."
Documentation Release Notes 3-7
Documentation Release Notes
3.3 Corrections to Existing Documentation
3.3.4.7 XmArrowButton Reference Page
V1.0 Make the following changes:
o In the Core Resource Set table of the Inherited Resource
section, change the default for XmNaccelerators and
XmNtranslations from NULL to "dynamic."
o In the Callback Information section, retain only the
first sentence of text of the description of event.
"The event in the callback struct is not NULL for
XmNactivateCallback callbacks."
o In the Action Routines section, for the
ArmAndActivate() action, change the text of the last
sentence of the description as follows:
"Arranges for the shadow to be drawn in the unselected
state and the callbacks for XmNactivateCallback and
XmNdisarmCallback to be called, either immediately or at
a later time."
3.3.4.8 XmArrowButtonGadget Reference Page
V1.0 Make the following changes:
o In the Callback Information section, retain only the
first sentence of text of the description of event.
"The event in the callback struct is not NULL for
XmNactivateCallback callbacks."
o In the Behavior section for the KActivate action, change
the text of the last sentence of the description as
follows:
" Arranges for the shadow to be drawn in the unselected
state and the callbacks for XmNactivateCallback and
XmNdisarmCallback to be called, either immediately or at
a later time."
3.3.4.9 XmBulletinBoard Reference Page
V1.0 Change the following information:
o In the New Resources section:
o Change the XmBulletinBoard Resource Set table to
indicated that the type for the XmNcancelButton and
XmNdefaultButton resources is Widget, not Window.
3-8 Documentation Release Notes
Documentation Release Notes
3.3 Corrections to Existing Documentation
o In the XmNdialogStyle resource description, add the
following sentence before the last sentence in the
first paragraph: This resource can be set only if the
BulletinBoard is unmanaged.
o In the same XmNdialogStyle resource description,
replace the last sentence of the last bulleted item
with the text, XmNdialogStyle is forced to have this
value when the parent of the BulletinBoard is not a
DialogShell.
o In the Inherited Resources section, change the Core
Resource Set table to indicate that the access for Core
resource XmNaccelerators is N/A, not CSG.
3.3.4.10 XmCascadeButton Reference Page
V1.0 In the New Resources section, the description of the
resource XmNmappingDelay has been expanded. Add the
following sentence to the end of the paragraph: The value
of XmNmappingDelay must not be negative.
XmPrimitive resource XmNtraversalOn is initialized to TRUE;
inside MenuBars, Popup MenuPanes, and Pulldown MenuPanes,
it is forced to TRUE.
3.3.4.11 XmCascadeButtonGadget Reference Page
V1.0 In the New Resources section, the description of the
resource XmNmappingDelay has been expanded. Add the
following sentence to the end of the paragraph: The value
of XmNmappingDelay must not be negative.
XmPrimitive resource XmNtraversalOn is initialized to TRUE;
inside MenuBars, Popup MenuPanes, and Pulldown MenuPanes,
it is forced to TRUE.
3.3.4.12 XmCommand Reference Page
V1.0 In the New Resources section, make the following changes to
the resource descriptions:
o In the description of the resource XmNhistoryItems, add
the following text to the end of the paragraph:
"XtGet Values for this resource returns the list
items themselves, not a copy of the list items. The
application must not free the returned items."
Documentation Release Notes 3-9
Documentation Release Notes
3.3 Corrections to Existing Documentation
o In the description of the resource XmNhistoryItemCount,
add the following sentence to the end of the paragraph:
The value of XmNhistoryItemCount must not be negative.
o In the description of the resource XmNhistoryMaxItems,
add the following text to the end of the paragraph: The
value of XmNhistoryMaxItems must be positive.
o In the description of the resource
XmNhistoryVisibleItemCount, replace the last two lines
of the paragraph with the following text:
"This is the XmNhistoryVisibleItemCount resource in
SelectionBox, renamed for Command. The value must be
greater than 0. The default is dynamic based on the
height of the list."
3.3.4.13 XmCreateOptionMenu Reference Page
V1.0 ToggleButtons and ToggleButtonGadgets are not allowed in
an OptionMenu's Pulldown MenuPane. The results of including
CascadeButtons and CascadeButtonGadgets are undefined.
3.3.4.14 XmCreatePromptDialog Reference Page
V1.0 The XmSelectionBox resource XmNdialogType is forced to
XmDIALOG_PROMPT.
3.3.4.15 XmCreateScrolledText Reference Page
V1.0 The results of placing an XmText widget with XmNeditMode
set to XmSINGLE_LINE_EDIT inside a scrolled window are
undefined.
3.3.4.16 XmCreateSelectionDialog Reference Page
V1.0 The XmSelectionBox resource XmNdialogType is forced to
XmDIALOG_SELECTION.
3.3.4.17 XmDialogShell Reference Page
V1.0 Setting Core resource XmNheight, XmNwidth, or
XmNborderWidth for either an XmDialogShell or its child
sets that resource to the same value in both the parent
and the child. An application should always specify these
resources for the child, not the parent. For a child of an
XmDialogShell, setting XmNx or XmNy sets the corresponding
resource of the parent but does not change the child's
position relative to the parent. XtGetValues for the
child's XmNx or XmNy yields the value of the corresponding
resource in the parent. The x and y coordinates of the
3-10 Documentation Release Notes
Documentation Release Notes
3.3 Corrections to Existing Documentation
child's upper left outside corner relative to the parent's
upper left inside corner are both zero minus the value of
XmNborderWidth. The Inter-Client Communication Conventions
Manual allows a window manager to change or control the
border width of a reparented top-level window.
3.3.4.18 XmDrawingArea Reference Page
V1.0 An application must not draw in the shadow and must
clear the old shadow when the widget is resized. For the
DrawingAreaInput() action, the XmNinputCallback callbacks
are not called when the input occurs in a gadget.
3.3.4.19 XmDrawnButton Reference Page
V1.0 The access for XmLabel resources XmNmnemonic and
XmNmnemonicCharSet is N/A, not CSG. The default value
for XmPrimitive resource XmNhighlightThickness is 2,
not 0. The event in the callback struct is not NULL for
XmNactivateCallback callbacks. For the ArmAndActivate()
action, the button is armed and the XmNarmCallback
callbacks are called immediately; the button is
activated and disarmed and the XmNactivateCallback and
XmNdisarmCallback callbacks are called, either immediately
or at a later time.
3.3.4.20 XmFileSelectionBox Reference Page
V1.0 The directory mask can contain zero or more wildcards.
Data returned by the XmNqualifySearchDataProc may be
modified by the XmNdirSearchProc.
The value of XmNdirListItemCount and XmNfileListItemCount
must not be negative.
XtGetValues for XmNdirListItems and XmNfileListItems
returns the list items themselves, not a copy of the list
items.
The access for XmNdirectoryValid, XmNdirListItems,
XmNdirListItemCount, XmNfileListItems,
XmNfileListItemCount, and XmNlistUpdated is SG, not CSG.
The default value for XmNnoMatchString is " [ ] " (with 4
spaces between the brackets, as shown).
Documentation Release Notes 3-11
Documentation Release Notes
3.3 Corrections to Existing Documentation
XmNdirSpec is the same as the XmSelectionBox resource
XmNtextString; XmNfileListItems is the same as
XmNlistItems; XmNfileListItemCount is the same as
XmNlistItemCount; and XmNfileListLabelString is the same
as XmNlistLabelString.
The default values for XmSelectionBox resources
XmNlistItems, XmNlistItemCount, and XmNtextString are
dynamic.
3.3.4.21 XmForm Reference Page
V1.0 For XmNbottomAttachment and XmNbottomPosition, when
XmNbottomAttachment is XmATTACH_POSITION, the position
of the bottom side of the child is relative to the top
side of the XmForm, not the bottom side of the XmForm.
For XmNrightAttachment and XmNrightPosition, when
XmNrightAttachment is XmATTACH_POSITION, the position of
the right side of the child is relative to the left side of
the XmForm, not the right side of the XmForm.
The type of XmNbottomWidget, XmNleftWidget, XmNrightWidget,
and XmNtopWidget is Widget, not Window.
The value of XmNfractionBase must not be zero.
The access for Core resource XmNaccelerators is N/A, not
CSG.
3.3.4.22 XmFrame Reference Page
V1.0 The XmFrame's width and height are the child's outer width
and height plus the XmFrame's margins and shadow thickness.
When the parent of the XmFrame is a shell, the default
value for the XmManager resource XmNshadowThickness is 1.
When the parent is not a shell, the default is 2.
3.3.4.23 XmGadget Reference Page
V1.0 The access for Core resource XmNborderWidth is N/A, not
CSG, for XmGadget and its subclasses.
3.3.4.24 XmGetPixmap Reference Page
V1.0 If the image_name argument begins with a slash (/), it is
taken to be a full path name specification and is the only
path name searched.
3-12 Documentation Release Notes
Documentation Release Notes
3.3 Corrections to Existing Documentation
3.3.4.25 XmLabel Reference Page
V1.0 If the parent is an XmRowColumn whose XmNisAligned is TRUE,
XmNalignment is forced to the value of the XmRowColumn's
XmNentryAlignment if the XmRowColumn's XmNrowColumnType is
XmWORK_AREA or if the widget is a subclass of XmLabel.
Documentation for XmNrecomputeSize no longer lists the
specific resources whose changes cause resizing when the
value of XmNrecomputeSize is TRUE.
XmPrimitive resource XmNtraversalOn is forced to FALSE
inside menus and defaults to FALSE otherwise.
3.3.4.26 XmLabelGadget Reference Page
V1.0 If the parent is an XmRowColumn whose XmNisAligned
is TRUE, XmNalignment is forced to the value of the
XmRowColumn's XmNentryAlignment if the XmRowColumn's
XmNrowColumnType is XmWORK_AREA or if the widget is a
subclass of XmLabelGadget.
Documentation for XmNrecomputeSize no longer lists the
specific resources whose changes cause resizing when the
value of XmNrecomputeSize is TRUE.
XmGadget resource XmNtraversalOn is forced to FALSE inside
menus and defaults to FALSE otherwise.
3.3.4.27 XmList Reference Page
V1.0 The value of XmNdoubleClickInterval, XmNitemCount, and
XmNselectedItemCount must not be negative. The value of
XmNtopPosition and XmNvisibleItemCount must be positive.
XtGetValues for XmNitems and XmNselectedItems returns the
list items themselves, not a copy of the list items.
The type for XmNvisibleItemCount is int, not short.
3.3.4.28 XmMainWindow Reference Page
V1.0 The type of XmNcommandWindow, XmNmenuBar, and
XmNmessageWindow is Widget, not Window.
The access for
XmScrolledWindow resources XmNscrolledWindowMarginHeight
and XmNscrolledWindowMarginWidth is N/A, not CSG.
Documentation Release Notes 3-13
Documentation Release Notes
3.3 Corrections to Existing Documentation
3.3.4.29 XmMenuShell Reference Page
V1.0 Setting Core resource XmNheight, XmNwidth, or
XmNborderWidth for either an XmMenuShell or its child
sets that resource to the same value in both the parent
and the child. An application should always specify these
resources for the child, not the parent. For a child of an
XmMenuShell, setting XmNx or XmNy sets the corresponding
resource of the parent but does not change the child's
position relative to the parent. XtGetValues for the
child's XmNx or XmNy yields the value of the corresponding
resource in the parent. The x and y coordinates of the
child's upper left outside corner relative to the parent's
upper left inside corner are both zero minus the value of
XmNborderWidth.
3.3.4.30 XmMessageBox Reference Page
V1.0 The access for Core resource XmNaccelerators is N/A, not
CSG.
3.3.4.31 XmProcessTraversal Reference Page
V1.0 It is not possible to use XmProcessTraversal to traverse to
MenuBars and Pulldown or Popup MenuPanes.
3.3.4.32 XmPushButton Reference Page
V1.0 The default value for XmNdefaultButtonShadowThickness
is dynamic. If XmNshowAsDefault is 0, the default is 0;
if XmNshowAsDefault is greater than 0, that value is the
default for XmNdefaultButtonShadowThickness.
The default value for XmLabel resource XmNlabelPixmap
is dynamic, not XmUNSPECIFIED_PIXMAP. If XmNlabelType is
XmPIXMAP and an initial value is specified for XmNarmPixmap
but not XmNlabelPixmap, the XmNarmPixmap value is used for
XmNlabelPixmap.
For the ArmAndActivate() action, the button is
armed and the XmNarmCallback callbacks are called
immediately. The button is activated and disarmed and the
XmNactivateCallback and XmNdisarmCallback callbacks are
called; inside a menu this happens immediately, and outside
a menu it happens either immediately or at a later time.
3-14 Documentation Release Notes
Documentation Release Notes
3.3 Corrections to Existing Documentation
3.3.4.33 XmPushButtonGadget Reference Page
V1.0 The default value for XmNdefaultButtonShadowThickness
is dynamic. If XmNshowAsDefault is 0, the default is 0;
if XmNshowAsDefault is greater than 0, that value is the
default for XmNdefaultButtonShadowThickness.
The default value for XmLabelGadget resource XmNlabelPixmap
is dynamic, not XmUNSPECIFIED_PIXMAP. If XmNlabelType is
XmPIXMAP and an initial value is specified for XmNarmPixmap
but not XmNlabelPixmap, the XmNarmPixmap value is used for
XmNlabelPixmap.
For the KActivate() action, the button is armed and the
XmNarmCallback callbacks are called immediately. The button
is activated and disarmed and the XmNactivateCallback and
XmNdisarmCallback callbacks are called; inside a menu this
happens immediately, and outside a menu it happens either
immediately or at a later time.
3.3.4.34 XmRowColumn Reference Page
V1.0 The access for XmNisHomogeneous is CG, not CSG. The value
is forced to TRUE when XmNrowColumnType is XmMENU_BAR, or
when XmNrowColumnType is XmWORK_AREA and XmNradioBehavior
is TRUE. It is forced to FALSE when XmNrowColumnType is
XmMENU_OPTION.
The value of XmNnumColumns must be positive. When
XmNrowColumnType is XmMENU_OPTION, XmNnumColumns is forced
to 1.
When XmNrowColumnType is XmMENU_OPTION, XmNorientation
defaults to XmHORIZONTAL. When XmNrowColumnType is XmMENU_
BAR, the results of specifying a value of XmVERTICAL for
XmNorientation are undefined.
When XmNrowColumnType is XmMENU_OPTION, XmNpacking is
initialized to XmPACK_TIGHT.
Button type XmCASCADEBUTTON is not allowed when creating
simple option menus.
The value of the simple menu creation resources
XmNbuttonCount, XmNbuttonSet, and XmNpostFromButton must
not be negative.
Documentation Release Notes 3-15
Documentation Release Notes
3.3 Corrections to Existing Documentation
When XmNrowColumnType is XmWORK_AREA, XmManager resource
XmNnavigationType defaults to XmTAB_GROUP. When
XmNrowColumnType is XmMENU_OPTION, XmNnavigationType
defaults to XmNONE. Otherwise, XmNnavigationType is not
applicable and its use is undefined.
When XmNrowColumnType is XmMENU_BAR, XmMENU_PULLDOWN,
or XmMENU_POPUP, XmManager resource XmNtraversalOn is
initialized to FALSE and cannot be changed by XtSetValues.
The XmManager resource XmNshadowThickness defaults to 2
when XmNrowColumnType is XmMENU_POPUP, XmMENU_PULLDOWN,
and XmMENU_BAR; it is N/A and its use is undefined when
XmNrowColumnType is XmWORK_AREA or XmMENU_OPTION.
If the parent is an XmMenuShell, the Core resource
XmNmappedWhenManaged is forced to FALSE on realization.
3.3.4.35 XmScale Reference Page
V1.0 The value of XmNdecimalPoints must not be negative.
XmNvalue is constrained to be between XmNminimum and
XmNmaximum, inclusively.
The default value for XmManager resource XmNshadowThickness
is 2, not 0.
3.3.4.36 XmScrollBar Reference Page
V1.0 The value of XmNincrement, XmNinitialDelay,
XmNpageIncrement, and XmNrepeatDelay must be positive.
The access for XmNpageIncrement is CSG, not C. The access
for XmNpageDecrementCallback is C, not CSG.
The default value for XmNsliderSize is (XmNmaximum -
XmNminimum) / 10, with a minimum of 1.
XmNvalue is constrained to be between XmNminimum and
(XmNmaximum - XmNsliderSize), inclusively.
For the the IncrementDownOrRight(), IncrementUpOrLeft(),
PageDownOrRight(), and PageUpOrLeft() actions, an argument
of 0 moves the slider only up or down; an argument of 1
moves the slider only left or right.
3-16 Documentation Release Notes
Documentation Release Notes
3.3 Corrections to Existing Documentation
3.3.4.37 XmScrolledWindow Reference Page
V1.0 The default values for XmNclipWindow,
XmNhorizontalScrollBar, and XmNverticalScrollBar are
dynamic, not NULL. Horizontal and vertical scroll bars
are created if XmNscrollingPolicy is XmAUTOMATIC. A clip
window is created if XmNvisualPolicy is XmCONSTANT.
The type of XmNclipWindow, XmNhorizontalScrollBar,
XmNverticalScrollBar, and XmNworkWindow is Widget, not
Window.
3.3.4.38 XmSelectionBox Reference Page
V1.0 The value of XmNlistItemCount must not be negative.
XtGetValues for XmNlistItems returns the list items
themselves, not a copy of the list items.
The default value for XmNlistLabelString is dynamic. The
default is Items unless XmNdialogType is XmDIALOG_PROMPT;
in this case the default is NULL.
The default value for XmNlistVisibleItemCount is dynamic
based on the height of the list. The value must be positive
unless XmNdialogType is XmDIALOG_PROMPT; in this case the
value is always 0.
The default value for XmNtextColumns is dynamic, not 20.
The value must be positive.
The default value for the XmBulletinBoard resource
XmNcancelButton is the Cancel button unless XmNdialogType
is XmDIALOG_COMMAND when the default is NULL. The default
value for the XmBulletinBoard resource XmNdefaultButton is
the OK button unless XmNdialogType is XmDIALOG_COMMAND when
the default is NULL.
3.3.4.39 XmSeparator Reference Page
V1.0 The access for XmPrimitive resource XmNtraversalOn is G,
not CSG.
3.3.4.40 XmSeparatorGadget Reference Page
V1.0 The access for XmGadget resource XmNtraversalOn is G, not
CSG.
Documentation Release Notes 3-17
Documentation Release Notes
3.3 Corrections to Existing Documentation
3.3.4.41 XmString Reference Page
V1.0 XtGetValues on a resource whose type is XmString yields
a copy of the resource value, which the application must
free.
3.3.4.42 XmText Reference Page
V1.0 The results of placing an XmText widget with XmNeditMode
set to XmSINGLE_LINE_EDIT inside a scrolled window are
undefined.
The value of XmNblinkRate, XmNselectionArrayCount, and
XmNselectThreshold must not be negative.
If no width is specified, XmNcolumns defaults to 20. The
value must be positive.
The values of XmNmarginHeight and XmNmarginWidth are not
forced when the widget is inside an XmScrolledWindow.
If no height is specified, XmNrows defaults to 1. The value
must be positive.
If the XmNeditMode is XmMULTI_LINE_EDIT, the line of text
that contains XmNtopCharacter is displayed at the top
of the widget without shifting the text left or right.
XtGetValues for XmNtopCharacter returns the position of the
first character in the line that is displayed at the top of
the widget.
3.3.4.43 XmTextField Reference Page
V1.0 The value of XmNblinkRate, XmNselectionArrayCount, and
XmNselectThreshold must not be negative.
If no width is specified, XmNcolumns defaults to 20. The
value must be positive.
The values of XmNmarginHeight and XmNmarginWidth are not
forced when the widget is inside an XmScrolledWindow.
3.3.4.44 XmTextSetTopCharacter Reference Page
V1.0 If the XmNeditMode is XmMULTI_LINE_EDIT, the line of text
that contains top_character is displayed at the top of the
widget without shifting the text left or right.
3-18 Documentation Release Notes
Documentation Release Notes
3.3 Corrections to Existing Documentation
3.3.4.45 XmToggleButton Reference Page
V1.0 The default value for XmNindicatorSize is dynamic. If no
value is specified, the size of the indicator is based
on the size of the label string or pixmap. If the label
string or pixmap changes, the size of the indicator is
recomputed based on the size of the label string or pixmap.
Once a value has been specified for XmNindicatorSize, the
indicator has that size, regardless of the size of the
label string or pixmap, until a new value is specified.
Initializing or setting XmNselectInsensitivePixmap also
sets the XmLabel resource XmNlabelInsensitivePixmap.
Initializing or setting XmNselectPixmap also sets the
XmLabel resource XmNlabelPixmap.
The translations for KActivate and KSelect in a menu invoke
the ArmAndActivate() action, not the KeySelect() action.
For the ArmAndActivate() action, the XmNarmCallback,
XmNvalueChangedCallback, and XmNdisarmCallback callbacks
are called.
3.3.4.46 XmToggleButtonGadget Reference Page
V1.0 The default value for XmNindicatorSize is dynamic. If no
value is specified, the size of the indicator is based
on the size of the label string or pixmap. If the label
string or pixmap changes, the size of the indicator is
recomputed based on the size of the label string or pixmap.
Once a value has been specified for XmNindicatorSize, the
indicator has that size, regardless of the size of the
label string or pixmap, until a new value is specified.
Initializing or setting XmNselectInsensitivePixmap also
sets the XmLabelGadget resource XmNlabelInsensitivePixmap.
Initializing or setting XmNselectPixmap also sets the
XmLabelGadget resource XmNlabelPixmap.
For the KActivate action, the XmNarmCallback,
XmNvalueChangedCallback, and XmNdisarmCallback callbacks
are called.
Documentation Release Notes 3-19
Documentation Release Notes
3.3 Corrections to Existing Documentation
3.3.4.47 XmVaCreateSimpleOptionMenu Reference Page
V1.0 Button type XmVaCASCADEBUTTON is not allowed when creating
simple option menus.
3-20 Documentation Release Notes
4
_________________________________________________________________
Version 1.1 New Features
This chapter describes the new features introduced with
the VMS DECwindows Motif Version 1.1 release. The following
major new features are included with this release:
o DECsound
o VMS DECwindows Motif Help System
o New MIT Utilities
4.1 DECsound
VMS DECwindows Motif Version 1.1 now includes DECsound.
DECsound is an easy-to-use layered product that lets
you play back recorded messages, record audio messages,
mail recorded messages, and include recorded messages in
compound documents.
4.1.1 Prerequisites
The DECsound audio editor, the enhanced CDA Viewer,
and DECwindows Mail use the built-in audio hardware
in a VAXstation 4000 as the audio user interface. The
prerequisites for using DECsound are:
o VMS Version 5.5
o A VAXstation 4000 Model 60 with either a phone handset
for I/O, or the internal speaker or phone headset for
output only
o A VAXstation 4000 VLC with either a phone handset or
phone headset to use as audio devices
Version 1.1 New Features 4-1
Version 1.1 New Features
4.1 DECsound
The VAXstation 4000 provides telephone circuitry for the
built-in audio port, which is supported in the DECsound
driver. The input is high level, high bias, and low
impedence. The output is low power. The port is intended
for use with a suitable telephone headset. Table 4-1
defines the electrical specifications.
Table_4-1_Electrical_Specifications________________________
___________________Input_Specifications____________________
Maximum Input Signal 2.5 Volts peak-peak
Input Bias Circuit 360 Ohms to +5 Volts
Input Impedence 120 Ohms
___________________________________________________________
___________________Output_Specifications___________________
Maximum Output 2.5 Volts peak-peak
Signal
Minimum Load 540 Ohms
Impedence
Maximum_Output_Power__0.01_Watts___________________________
4.1.2 Starting DECsound
You can start DECsound from:
o Session Manager
o CDA Viewer
o Mail
o DCL command line
4.1.2.1 Session Manager
To start DECsound from the Session Manager, select
DECsound from the Applications pull-down menu. This is
the recommended method of starting DECsound.
4-2 Version 1.1 New Features
Version 1.1 New Features
4.1 DECsound
4.1.2.2 Enhanced CDA Viewer
You can use the enhanced CDA Viewer to view documents that
contain DECsound recordings. To start DECsound with the
CDA Viewer, select CDA Viewer from the Applications pull-
down menu in the Session Manager and open a file that has
the .AUD file extension to hear and play back DECsound
recordings.
The character cell version of the CDA Viewer does not
support audio playback.
The CDA Viewer displays an icon that indicates the presence
of audio content in the document. Click on this icon to
play the audio content. If you want to stop the playback
before the end of the audio content, click on the icon
again.
4.1.2.3 Integration With Mail
VMS DECwindows Motif Version 1.1 also supports audio mail
messages. You can configure both DECwindows Mail and
ALL-IN-1 MAIL for VMS DECwindows to include DECsound as
one of the available editors in the Create window.
For DECwindows Mail, select the Send option from the
Options menu, click on Change Editor List, and complete
the fields in the dialog box, which is displayed with the
following information:
Editor Name: DECsound
Editor Command: SYS$SYSTEM:DECSOUND
Method: Direct Invocation
Click on Add to add DECsound to your list, then click on
OK to dismiss the dialog box. Be sure to save your new
settings before exiting mail.
For ALL-IN-1 MAIL for VMS DECwindows, add the following
lines to the A1MAIL$LIBRARY:A1MAIL$REGISTERED_EDITORS.TXT
file:
Version 1.1 New Features 4-3
Version 1.1 New Features
4.1 DECsound
#
DECsound # Display name
SYS$SYSTEM:DECSOUND.EXE # executable
aca # Invoke_By
native # File_IDs
ddif # File_Types
dw # UI
#
DECsound # Display name
SYS$SYSTEM:DECSOUND.EXE # executable image
aca # Invoke_By
native # File_IDs
ddif # File_Types
dw_read_only # UI
4.1.2.4 DCL Command Line
You can start DECsound from the DCL command line by
entering the command:
$ RUN SYS$SYSTEM:DECSOUND
The first time that you invoke DECsound, the Settings
dialog box is displayed with different options. You
must select the options that are appropriate for your
configuration. When you finish entering information in
the Settings dialog box, click on OK to dismiss the dialog
box.
The Device Type list box contains a list of audio devices
that are supported by DECsound. Select the device that is
appropriate for your configuration. For example, select the
VAXstation 4000 option if you are using a VAXstation 4000.
Table 4-2 describes each of the options that can be changed
from the Options menu.
4-4 Version 1.1 New Features
Version 1.1 New Features
4.1 DECsound
Table_4-2_Audio_Editor_Options_____________________________
Option______Description____________________________________
Device The Device Type allows you to select the type
Type of audio hardware that matches the hardware
that you have. For DECwindows Motif Version
1.1, select VAXstation 4000.
If you do not have a VAXstation 4000 and you
want to see the user interface, you can select
None for the device type. You cannot record or
play with this selection.
Play The Play Setting section of the Setting dialog
Settings box contains radio buttons that let you play
back recordings through the built-in speaker
on the workstation, or through headphones. This
section also contains a slider that lets you
control the volume of the recordings.
Use the switch on the front of the VAXstation
4000 to enable or disable the internal speaker.
If you select the internal speaker in the
Settings dialog box and cannot hear the
recording, check the hardware switch to make
sure that it is working correctly.
If you are using a VAXstation 4000 VLC, choose
the headphone jack. This selection is the
default.
Record The Record Settings section of the Settings
Settings dialog box contains sliders that let you
specify the maximum length of a DECsound
recording. This prevents long recordings from
being initiated by accidentally clicking on the
Record button. This section also has a slider
that lets you control the input level for the
recordings.
(continued on next page)
Version 1.1 New Features 4-5
Version 1.1 New Features
4.1 DECsound
Table_4-2_(Cont.)_Audio_Editor_Options_____________________
Option______Description____________________________________
If you try to make a recording that is longer
than the maximum record length, an error
message is displayed.
Telephone The audio editor calls the number at the
Settings beginning of the editing session to provide
the telephone link to the DECvoice board.
Automatic Hangup works only if the audio editor
is invoked using LiveLinks.
These settings should be used only with
DECvoice hardware, which is not supported for
____________DECwindows_Motif_Version_1.1.__________________
You can also define the following foreign command from
the DCL command line and specify qualifiers when you run
DECsound.
$ decsound :== $decsound
Table 4-3 describes the qualifiers that you can use to
control the session:
Table_4-3_Qualifiers_to_Control_DECsound_Sessions__________
Qualifier_____Description__________________________________
-file Starts a DECsound session. If the file
filespec exists, the DECsound window displays the
recording. If the file does not exist,
DECsound creates a new recording. If you
do not specify a file type, DECsound adds the
default .AUD file type.
(continued on next page)
4-6 Version 1.1 New Features
Version 1.1 New Features
4.1 DECsound
Table_4-3_(Cont.)_Qualifiers_to_Control_DECsound_Sessions__
Qualifier_____Description__________________________________
-icon Creates a DECsound file that includes
an icon. This qualifier is useful when
you make recordings that you want to
include in DECwrite documents or DECpresent
presentations, because the resulting data
block in the document or presentation will
display an icon that indicates the presence
of a DECsound recording.
If you do not insert the icon, the DECsound
data block can be difficult to locate in a
document. However, if you do insert the icon,
the icon is also displayed when you print the
document or presentation.
-play Plays the specified file without displaying
filespec the DECsound window.
-volume n Specifies the playback volume, where n is an
integer between 0 and 100. DECsound ignores
the -volume qualifier if you do not also
specify the -play qualifier.
-speaker Plays the DECsound recording on your
workstation's built-in speaker. DECsound
ignores the -speaker qualifier if you do not
also specify the -play qualifier.
-headphone Plays the DECsound recording on a headset or
headphones connected to your workstation's
headphone jack. DECsound ignores the -
headphone qualifier if you do not also
______________specify_the_-play_qualifier._________________
________________________ Note ________________________
You can specify either the -speaker qualifier or the
-headphone qualifier, but not both. If you specify
both of these qualifiers, DECsound uses the last one
that you entered on the command line.
______________________________________________________
Version 1.1 New Features 4-7
Version 1.1 New Features
4.1 DECsound
4.1.3 Using LiveLink Connections
You can include DECsound recordings in DECwrite documents
and DECpresent presentations by using LiveLink connections.
A LiveLink connection puts a DECsound recording into a
document or presentation. The following are examples of
when you might insert a DECsound recording in a document or
presentation:
o Your document includes a complex graphic showing a
machine part or a circuit diagram.
Instead of typing the description, you could create a
LiveLink connection to a DECsound recording.
o You want to comment on a draft presentation prepared by
a colleague.
Instead of inserting handwritten comments in the
presentation, you could use DECsound to insert your
comments at appropriate places in the presentation.
When you create a LiveLink connection to a DECsound
recording, the recording is maintained in a DECsound file.
If you update the recording, the document or presentation
is automatically updated to include the new recording.
When you insert a LiveLink connection to a DECsound file in
a DECwrite document or a DECpresent presentation, you can
optionally insert an icon that indicates the presence of a
DECsound recording in the document or presentation.
If you do not insert the icon, the DECsound data block
may be difficult to find in a document. However, if you do
insert the icon, the icon is also displayed when you print
the document or presentation.
4.1.3.1 LiveLink Connections from DECwrite
To create a LiveLink connection between a DECwrite document
and a DECsound recording, follow these steps:
1. Choose the Links option from the File menu.
DECwrite displays the Links submenu.
4-8 Version 1.1 New Features
Version 1.1 New Features
4.1 DECsound
________________________ Note ________________________
You must have the Full Menus option turned ON to
display the Links menu. To turn this option ON, choose
Full Menus from the DECwrite Options menu.
______________________________________________________
2. Choose the Link... option from the Links submenu.
DECwrite displays the Link dialog box. For information
about the Link dialog box, click on the Help button in
the dialog box.
3. Click on a file name in the list box. If you want to
create a new DECsound recording, enter the name of the
file in the Selection text-entry field.
4. Click on the Options... button in the dialog box.
DECwrite displays the Link Options subdialog box. For
information about Link Options, click on the Help button
in the subdialog box.
In the Link Options subdialog box, enter the following
LiveLink connection information:
a. Specify the file location type for the file that
contains the recording that you want to link to.
The location will also affect the way that the
audio file is treated if you mail the DECpresent
presentation.
b. Specify DECsound in the Application Name field in the
following format:
sys$system:decsound
c. If you want the DECwrite document to display an icon
to indicate the presence of the DECsound recording
in the document, specify the -icon qualifier in the
Parameters field in the format:
-icon
d. Click on OK to dismiss the Link Options subdialog
box.
5. Set the Invoke Application radio button to the On state
if you want to invoke DECsound.
Version 1.1 New Features 4-9
Version 1.1 New Features
4.1 DECsound
6. Set the Keep Natural Size radio button to the Off state
if you want to specify the size of the DECsound icon
that is displayed in the DECwrite document.
7. Click on OK in the Link dialog box.
8. Position the pointer in the document window where you
want the DECsound data block to be displayed, drag MB1
to size the data block, then click MB1.
4.1.3.2 LiveLink Connections from DECpresent
To create a LiveLink connection between a DECpresent
presentation and a DECsound recording, follow these steps:
1. Choose the Links option from the File menu.
DECpresent displays the Links submenu.
2. Choose the Link... option from the Links submenu.
DECpresent displays the Link dialog box. For information
about the Link dialog box, click on the Help button in
the dialog box.
3. Click on a file name in the list box. If you want to
create a new DECsound recording, enter the name of the
file in the Selection text entry field.
4. Click on the Options... button in the dialog box.
DECpresent displays the Link Options subdialog box. For
information about Link Options, click on the Help button
in the subdialog box.
a. Specify the file location type for the file that
contains the recording that you want to link to.
The location will also affect the way that the
audio file is treated if you mail the DECpresent
presentation.
b. Specify DECsound in the Application Name field in the
following format:
sys$system:decsound
c. If you want the DECpresent presentation to display
an icon to indicate the presence of the DECsound
recording in the presentation, specify the -icon
qualifier in the Parameters field in the format:
4-10 Version 1.1 New Features
Version 1.1 New Features
4.1 DECsound
-icon
d. Click on OK to dismiss the Link Options subdialog
box.
5. Set the Invoke Application radio button to On if you
want to invoke DECsound.
6. Set the Keep Natural Size radio button to the Off state
if you want to specify the size of the DECsound icon
that is displayed in the DECpresent presentation.
7. Click on OK in the Link dialog box.
8. Position the pointer in the DECpresent window where you
want the DECsound data block to be displayed, drag MB1
to size the data block, then click MB1.
4.1.4 Online Help for DECsound
Online help is available for DECsound. Use the pull-down
DECsound Help menu to access conceptual information, task-
oriented information, a tutorial, and context-sensitive
help.
4.1.5 Problems and Restrictions
The following problems and restrictions exist for the
DECwindows Motif Version 1.1 release of 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 position slider is not active when you first load an
audio file. If you play a portion of the file, you can
use the slider for positioning within the message.
o The Record operation does not work when you have
selected part of the waveform.
To correct this problem, do not select any part of the
waveform before you click on the Record button.
Version 1.1 New Features 4-11
Version 1.1 New Features
4.1 DECsound
o If you select None from the list of device types in the
Settings dialog box, you can access the DECsound user
interface even if your workstation does not have audio
hardware. Using this setting for other reasons, such
as editing messages, can cause erratic behavior within
DECsound and is not recommended.
4.2 VMS DECwindows Motif Help System
With VMS DECwindows Motif Version 1.1, the VMS DECwindows
Motif Help System uses the Bookreader interface to display
help and to retrieve Help information. This new system
includes a Table of Contents, links to hyperapplications,
and cross-referencing through the use of hotspots.
Most DECwindows out-of-the-box (OOTB) applications use the
VMS DECwindows Motif Help System in place of the Motif Help
Widget. When invoking help, either from a Help menu or from
context-sensitive help, Bookreader is started and a Help
topic is displayed.
The system is comprised of three routines, which are
provided in the DECwindows Motif Toolkit.
Help for the following applications is available when using
the VMS DECwindows Motif Help System:
o Bookreader
o Calculator
o Calendar
o Cardfiler
o CDA Viewer
o Clock
o DECsound
o DECterm
o FileView
o LinkWorks Manager
o Mail
o Message Window
4-12 Version 1.1 New Features
Version 1.1 New Features
4.2 VMS DECwindows Motif Help System
o Notepad
o Session Manager
o Paint
o Puzzle
4.3 New MIT Utilities
V1.1 Several new utilities that are supplied with X11 Release
4 from MIT are also included with the VMS DECwindows
Motif Version 1.1 kit. They are located in the DECW$UTILS
directory. This section includes a short description of
each utility.
To run each program, define a foreign symbol to invoke it;
then pass qualifiers on the command line.
Bitmap
The bitmap utility is used to create and edit rectangular
images that are made up of 1s and 0s. Bitmaps are used to
define clipping regions, cursor shapes, icon shapes, and
tile and stipple patterns.
Bitmap displays a grid in which each square represents a
single bit in the picture being edited. Squares can be
set, cleared, or inverted with the mouse buttons, and a
menu of higher level operations is provided to the side of
the grid. Actual size versions of the bitmap, as it would
appear normally and inverted, are displayed below the menu.
If the bitmap is used to define a cursor, one of the
squares in the images can be designated as the hotspot.
This determines where the cursor is pointing. For cursors
with sharp tips, such as arrows and fingers, this is
usually at the end of the tip. For symmetric cursors, such
as crosses and bullseyes, this is usually at the center.
Bitmaps are stored as small C code fragments that are
suitable for including in applications. They provide an
array of bits and symbolic constants that give width,
height, and hotspot, which can be used to create cursors,
icons, and tiles. See the X Window System Toolkit for more
information.
Version 1.1 New Features 4-13
Version 1.1 New Features
4.3 New MIT Utilities
The format for bitmap is:
bitmap [-options ...] filename [width x
height]
The bitmap options are described in Table 4-4.
Table_4-4_Bitmap_Options___________________________________
Option_______________Description___________________________
-help Creates a brief description of
allowable options and parameters to
be printed.
-display Specifies the X server to use.
-geometry Specifies the placement and size of
the bitmap window on the screen.
-nodashed Indicates that the grid lines in the
work area should not be drawn with
dashed lines. Dashed lines can be
slower on some servers.
-name variable_name Specifies the variable name to use
for writing out the bitmap file. The
default is to use the basename of the
file name command line argument.
-bw number Specifies the border width of the main
window in pixels.
-fn font Specifies the font used for text in
the buttons.
-fg color Specifies the foreground color.
-bg color Specifies the background color.
-hl color Specifies the highlight color.
-bd color Specifies the border color.
-ms_color____________Specifies_the_mouse_color.____________
The default WIDTHxSIZE is 16x16.
4-14 Version 1.1 New Features
Version 1.1 New Features
4.3 New MIT Utilities
Changing Grid Squares
Grid squares can be set, cleared, or inverted by pointing
to them and clicking on:
o MB1-used to set one or more squares. The corresponding
bit or bits in the bitmap are turned on (set to 1) and
the square is filled.
o MB2-used to invert one or more squares. The
corresponding bit or bits in the bitmap are flipped,
so 1s become 0s and 0s become 1s.
o MB3-used to clear one or more squares. The corresponding
bit or bits in the bitmap are turned off (set to 0) and
the square is emptied.
Multiple squares can be changed simultaneously by holding
the button down and dragging the cursor across the squares.
The bmtoa and atobm filters convert bitmap files to and
from ASCII strings. They are most commonly used to print
out bitmaps and generate versions to include in text files.
The format for atobm is:
atobm [-options ...] [filename]
The atobm options are described in Table 4-5.
Table_4-5_atobm_Options____________________________________
Option_______________Description___________________________
-chars cc Specifies the pair of characters to
use when converting string bitmaps
into arrays of numbers. The first
character represents a 0 bit and the
second character represents a 1 bit.
The default is to use dashes for 0s
and the number sign (#) for 1s.
(continued on next page)
Version 1.1 New Features 4-15
Version 1.1 New Features
4.3 New MIT Utilities
Table_4-5_(Cont.)_atobm_Options____________________________
Option_______________Description___________________________
-name variable Specifies the variable name to be used
when writing out the bitmap file. The
default is to use the base name of
the file name command line argument or
leave it blank if the standard input
is read.
-xhot number Specifies the x coordinate of the
hotspot. Only positive values are
allowed. By default, no hotspot
information is included.
-yhot number Specifies the y coordinate of hotspot.
Only positive values are allowed. By
default, no hotspot information is
_____________________included._____________________________
The format for bmtoa is:
bmtoa [-options ...] [filename]
The bmtoa option is described in Table 4-6.
Table_4-6_bmtoa_Option_____________________________________
Option_______________Description___________________________
-chars cc Specifies the pair of characters to
use in the string version of the
bitmap. The first character is used
for 0 bits and the second character is
used for 1 bits. The default is to use
dashes for 0s and the number sign (#)
_____________________for_1s._______________________________
Display Information
The xdpyinfo utility displays characteristics about an
X server. It is used to examine the capabilities of
the server, the predefined values of parameters used to
communicate between clients and servers, and the different
types of screens and visuals available. The format is:
4-16 Version 1.1 New Features
Version 1.1 New Features
4.3 New MIT Utilities
xdpyinfo [-display display]
Event Monitoring
The xev utility creates a window and writes output for each
event that is generated. These include pointer motion, and
enter and leave on the window.
The format is:
xev [-options ...]
The xev options are described in Table 4-7.
Table_4-7_xev_Options______________________________________
Option_______________Description___________________________
-displayname Specifies the X server to contact.
-geometry geom Specifies the size and location of
window.
-bw pixels Specifies the border width in pixels.
-bs {NotUseful, Specifies the backingstore attribute.
WhenMapped,Always}
-s___________________Sets_save-unders_attribute____________
List Atoms
The xlsatoms utility lists the interned atoms. By default,
all atoms starting from 1 (the lowest atom value defined in
the protocol) are listed until the unknown atom is found.
If an explicit range is given, xlsatoms tries all atoms in
the range regardless of whether they are undefined.
The format is:
xlsatoms [-options...]
The xlsatoms options are described in Table 4-8.
Version 1.1 New Features 4-17
Version 1.1 New Features
4.3 New MIT Utilities
Table_4-8_xlsatoms_Options_________________________________
Option_______________Description___________________________
-display display Specifies the X server to which to
connect.
-format string Specifies the print-style format to
use to list each atom <value,name>
pair that is printed in that order.
xlsatoms supplies a new line at the
end of each line. The default is
%ld\t%s.
-range [low]-[high] Specifies the range of atom values to
check. If low is not given, a value
of 1 is assumed. If high is not given,
xlsatoms stops at the first undefined
atom at or above low.
-name string Specifies the name of the single atom
to list. If the atom does not exist, a
_____________________message_is_printed.___________________
List Fonts
The xlsfonts utility lists the fonts that match the given
pattern. The wildcard character (*) can be used to match
any sequence of characters. The question mark (?) can be
used to match any single character. If no pattern id is
given, the wildcard character is assumed.
The format is:
xlsfonts [-options] [-fn pattern]
The xlsfonts options are described in Table 4-9.
Table_4-9_xlsfonts_Options_________________________________
Option_______________Description___________________________
-l[l[l]] Indicates that medium, long, and very
long listings should be generated for
each font.
(continued on next page)
4-18 Version 1.1 New Features
Version 1.1 New Features
4.3 New MIT Utilities
Table_4-9_(Cont.)_xlsfonts_Options_________________________
Option_______________Description___________________________
-m Specifies that long listings should
also print min and max bounds.
-C Specifies that listings should use
multiple columns. This is the same as
-n0.
-1 Forces a single column. This is the
same as -n1.
-u Keeps output unsorted.
-w width Specifies the maximum width in
characters that should be used to
determine the number of columns to
print. The default is 79.
-n columns Specifies the number of columns in
which to display the output. By
default, xlsfonts attempts to fit
as many columns of font names into the
number of characters that is specified
by -w width.
-display_display_____Specifies_the_X_server_to_contact.____
List Windows
The xlswins utility lists the window tree. By default,
the root window is used as the starting point, although a
specific window can be specified with the -id option. If
a window is not specified on the command line, the root
window is used.
The format is:
xlswins [-options ...] [window_id] ...
The xlswins options are described in Table 4-10.
Version 1.1 New Features 4-19
Version 1.1 New Features
4.3 New MIT Utilities
Table_4-10_xlswins_Options_________________________________
Option_______________Description___________________________
-display display Specifies the X server to contact.
-format {hex, Specifies the radix used to the print
decimal, octal} window id. The default is hex.
-indent number Specifies the number of spaces to
indent per level in the window tree.
The default is 2.
-l Specifies that a long listing should
be generated for each window. This
includes a number indicating the
depth, geometry relative to the
parent, and the location relative
to the root window.
-resources___________Prints_a_listing_of_widget_resources._
Magnify Portion of Screen
The xmag utility allows you to magnify the screen. If
the explicit region is not specified, a square centered
around the pointer is displayed indicating the area to
be enlarged. Once a region is selected, a window pops up
showing an enlargement of the region, in which each pixel
in the source image is represented by a small square of
the same color. Clicking MB1 in the enlarged window pops
up a small window that displays the position, number, and
RGB value of the pixel under the pointer for as long as MB1
is depressed. Pressing the space bar or any other pointer
button removes the enlarged image and another region can be
selected. Pressing q, Q, or Ctrl/C in the enlarged window
exits the program.
The format is:
xmag [-options ...]
The xmag options are described in Table 4-11.
4-20 Version 1.1 New Features
Version 1.1 New Features
4.3 New MIT Utilities
Table_4-11_xmag_Options____________________________________
Option_______________Description___________________________
-display display Specifies the X server to use for both
reading the screen and displaying the
enlarged version of the image.
-geometry geom Specifies the size and location of
the enlargement window. By default,
the size is computed from the size
of the source region and the desired
magnification. Only one -source and
-mag option can be specified if the
window size is given with this option.
-source geom Specifies the size and location of
the source region on the screen. By
default, a 64x64 square centered about
the pointer is provided for the user
to select an area of the screen. The
size of the source is used with the
desired magnification to compute the
default enlargement window size. Only
one -geometry and -mag option can be
specified if a source size is given
with this option.
-mag magfactor Specifies the integral amount by which
source region is enlarged. The default
magnification is 5. This is used with
the size of the source to compute the
default enlargement window size. Only
one -geometry and -source option can
be specified if a magnification factor
is given with this option.
-bw pixels Specifies the border width in
pixels of the border surrounding the
enlargement window.
-bd color Specifies the border color.
(continued on next page)
Version 1.1 New Features 4-21
Version 1.1 New Features
4.3 New MIT Utilities
Table_4-11_(Cont.)_xmag_Options____________________________
Option_______________Description___________________________
-bg color pixel_ Specifies the name of the color to
value be used as the background of an
enlargement window. If the name
begins with a percent size (%), it
is interpreted as an absolute pixel
value. This is useful when displaying
large areas, since pixels that are the
same color as the background do not
need to be painted in the enlargement.
The default is BlackPixel.
-fn font_name Specifies the name of font for
examining enlarged pixels used when
MB1 is pressed in the enlargement
window.
-z Grabs the server during dynamics
and the call to XGetImage. This is
useful for ensuring that clients do
not change their state as the result
of entering or leaving them with the
_____________________pointer.______________________________
Options may be abbreviated to the shortest unambiguous
prefix.
Modify Keymap
The xmodmap utility is used to edit and display the
keyboard modifier map and keymap table, which are used
by client applications to convert events and keycodes into
keysyms. This utility is usually run at session startup to
customize the keyboard.
This is a global change and affects all applications
connected to the server.
The format is:
xmodmap [-options ...] [filename]
The file name specifies a file that contains xmodmap
expressions to be executed.
4-22 Version 1.1 New Features
Version 1.1 New Features
4.3 New MIT Utilities
The xmodmap options are described in Table 4-12.
Table_4-12_xmodmap_Options_________________________________
Option_______________Description___________________________
-display display Specifies the host and server to use.
-verbose Indicates that xmodmap should print
logging information as it parses the
input.
-quiet Turns off the verbose logging. This is
the default.
-n Indicates that xmodmap should not
change the mappings but should display
what it would do.
-e expression Specifies an expression to be
executed. Any number of expressions
can be specified from the command
line.
-pm Prints the current modifier map to
SYS$OUTPUT.
-pk Prints the current keymap table to
SYS$OUTPUT.
-pp Prints the current pointer map to
SYS$OUTPUT.
-grammar Indicates that a help message that
describes the expression grammar used
in the files and with -e expressions
should be printed out to SYS$OUTPUT.
- Specifies that SYS$INPUT should be
_____________________used_as_the_input_file._______________
Display Properties
The xprop utility displays window and font properties in an
X server. One window or font is selected using the command
line arguments or by clicking on the desired window, in
the case of a window. A list of properties with formatting
information is then given.
Version 1.1 New Features 4-23
Version 1.1 New Features
4.3 New MIT Utilities
The format is:
xprop [-help] [-grammar] [-id id] [-root]
[-name name] [-frame] [-font font]
[-display display] [-len n] [-notype]
[-fs file] [-remove property_name]
[-spy] [-f atom format [dformat]]...
[format [dformat] atom]...
The xprop options are described in Table 4-13.
Table_4-13_xprop_Options___________________________________
Option_______________Description___________________________
-help Prints out a summary of command line
options.
-grammar Prints out full grammar for command
line options.
-display display Specifies the X server to contact.
-id id Selects the window id on the command
line instead of using the pointer
to select the target window. This is
useful in debugging X applications
where the target window is not mapped
to the screen or where the use of
the pointer might interfere with the
application.
-name name Specifies that the window named name
is the target window on the command
line instead of using the pointer to
select the target window.
-font font Specifies that the properties of the
font font should be displayed.
-remove property_ Specifies the name of a property to be
name removed from the indicated window.
(continued on next page)
4-24 Version 1.1 New Features
Version 1.1 New Features
4.3 New MIT Utilities
Table_4-13_(Cont.)_xprop_Options___________________________
Option_______________Description___________________________
-root Specifies that X's root window is the
target window. This option is useful
when the root window is completely
obscured.
-len n Displays or reads at most n bytes of
any property.
-notype Specifies not to display the type
field for each property.
-fs filename Specifies where to look for property
formats.
-frame Specifies that when selecting a window
by hand (i.e. if -name,-root, or -id
are not given), look at the window
manager frame instead of the client
window.
-f property_name Specifies that the format for name
format [dformat] should be format and that the dformat
for name should be dformat. If dformat
is missing, =$0+\n is assumed.
-spy Examines window properties forever,
_____________________looking_for_property_change_events.___
For each of these properties, the value on the selected
window or font is printed using the supplied formatting
information, if it exists. If no formatting information
is supplied, internal defaults are used. If a property is
not defined on the selected window or font, "not defined"
is printed as the value for that property. If no property
list is given, all the properties possessed by the selected
window or font are printed.
A window can be selected in one of four ways:
o If the desired window is the root window, the -root
argument can be used.
Version 1.1 New Features 4-25
Version 1.1 New Features
4.3 New MIT Utilities
o If the desired window is not the root window, it can be
selected in either of two ways on the command line, by
id number, or by name if the window possesses a name.
The -id argument selects a window by id number in either
decimal or hex (must start with 0x), while the -name
argument selects a window by name.
o If none of -font, -id, -name, and -root are specified,
a crosshairs cursor is displayed and you can choose
any visible window by clicking any mouse button in the
desired window. If it is desired to display properties
of a font as opposed to a window, the -font argument
must be used.
Other than these four arguments and the -help and -grammar
arguments, all the other command line arguments are used to
specify both the format of the properties to be displayed
and how to display them. The -len n argument specifies
that at most n bytes of any given property will be read and
displayed. This argument is useful when displaying the cut
buffer on the root window, which could be several pages if
displayed in full.
Usually each property name is displayed by printing the
property name then its type (if it has one) in parentheses,
followed by its value. The -notype argument specifies
that property types should not be displayed. The -fs
argument specifies a file containing a list of formats
for properties, while the -f argument specifies the format
for one property.
The formatting information for a property consists of two
parts, a format and a dformat. The format specifies the
formatting of the property, and the dformat specifies how
the property should be displayed.
Constructing Formats and Deformats The defaults contain
the formats and dformats required to display all the
standard properties. You should only have to specify
formats and dformats if you have a new property or if
you want to change the standard display format. It is
recommended that new users do not specify formats and
dformats.
4-26 Version 1.1 New Features
Version 1.1 New Features
4.3 New MIT Utilities
A format consists of one of 0, 8, 16, or 32 followed by a
sequence of one or more format characters. The 0, 8, 16,
or 32 specifies how many bits per field there are in the
property. Zero is an unique case meaning to use the field
size information associated with the property itself. The
zero is only needed for unique cases like type INTEGER,
which can be one of three different types depending on the
size of the fields of the property.
A value of 8 means that the property is a sequence of
bytes, while a value of 16 means that the property is a
sequence of words. The difference between the two is that
the sequence of words is byte swapped, while the sequence
of bytes is not when read by a machine of the opposite byte
order of the machine that originally wrote the property.
For more information on how properties are formatted and
stored, consult the Xlib manual.
Once the size of the fields has been specified, you must
specify the type of each field (that is, an integer, a
string, an atom). This is done using one format character
per field. If there are more fields in the property than
format characters supplied, the last character is repeated
as many times as necessary for the extra fields. The format
characters and their meaning are as follows:
o a-The field holds an atom number. A field of this type
should be of size 32.
o b-The field is a Boolean value. A 0 means FALSE while
anything else means TRUE.
o c-The field is an unsigned number, a cardinal number.
o i-The field is a signed integer.
o m-The field is a set of bit flags, 1 meaning On.
o s-This field and the following ones up to either a 0 or
the end of the property represent a sequence of bytes.
This format character is only usable with a field size
of 8 and is most often used to represent a string.
o x-The field is a hex number (such as 'c' but displayed
in hex). It is most useful for displaying window IDs.
Version 1.1 New Features 4-27
Version 1.1 New Features
4.3 New MIT Utilities
Modify Resource Database
The xrdb utility is used to get or set the contents of the
RESOURCE_MANAGER property on the root window of screen 0.
The X Toolkit uses the RESOURCE_MANAGER property to get
user preferences about color, and fonts for applications.
For compatibility, if there is no RESOURCE_MANAGER property
is defined, the resource manager looks for a file called
DECW$XDEFAULTS.DAT in DECW$USER.DEFAULTS.
The file name, or SYS$INPUT if an input file is not given,
is optionally passed through the C preprocessor with the
following symbols defined, based on the capabilities of the
server being used:
o BITS_PER_RGB=num-number of significant bits in an RGB
color specification. This is the log base 2 of the
number of distinct shades of each primary that the
hardware can generate. It is not usually related to
PLANES.
o CLASS=visual_class-one of StaticGray, GrayScale,
StaticColor, PseudoColor, TrueColor, DirectColor. This
is the visual class of the root window of the default
screen.
o COLOR-defined only if CLASS is StaticColor, PseudoColor,
TrueColor, or DirectColor.
o HEIGHT=num-the height of the default screen in pixels.
o SERVERHOST=host_name-the hostname portion of the display
to which you are connected.
o HOST=host_name-the same as SERVERHOST.
o CLIENTHOST=host_name-the name of the host on which xrdb
is running.
o PLANES=num-the number of bit planes (the depth) of the
root window of the default screen.
o RELEASE=num-the vendor release number for the server.
The interpretation of this number varies depending on
VENDOR.
o REVISION=num-the X protocol minor version supported by
this server (currently 0).
4-28 Version 1.1 New Features
Version 1.1 New Features
4.3 New MIT Utilities
o VERSION=num-the X protocol major version supported by
this server (should always be 11).
o VENDOR=vendor-a string specifying the vendor of the
server.
o WIDTH=num-the width of the default screen in pixels.
o X_RESOLUTION=num-the x resolution of the default screen
in pixels per meter.
o Y_RESOLUTION=num-the y resolution of the default screen
in pixels per meter.
Lines that begin with an exclamation mark (!) are ignored
and can be used as comments.
The format is:
xrdb [-options ...] [filename]
The xrdb options are described in Table 4-14.
Table_4-14_xrdb_Options____________________________________
Option_______________Description___________________________
-help Causes a brief description of the
allowable options and parameters to be
printed.
-display display Specifies the X server to use.
-n Indicates that changes to the property
(when used with -load) or to the
resource file (when used with -
edit) should be shown on the standard
output, but should not be performed.
-symbols Indicates that the symbols that are
defined for the preprocessor should
be printed onto the standard output.
It can be used in conjunction with
-query, but not with the options that
change the RESOURCE_MANAGER property.
(continued on next page)
Version 1.1 New Features 4-29
Version 1.1 New Features
4.3 New MIT Utilities
Table_4-14_(Cont.)_xrdb_Options____________________________
Option_______________Description___________________________
-query Indicates that the current contents of
the RESOURCE_MANAGER property should
be printed onto the standard output.
Since preprocessor commands in the
input resource file are part of the
input file, not part of the property,
they do not appear in the output from
this option. The -edit option can
be used to merge the contents of the
property back into the input resource
file without damaging preprocessor
commands.
-load Indicates that the input should
be loaded as the new value of the
RESOURCE_MANAGER property, replacing
whatever was there (i.e., the old
contents are removed). This is the
default action.
-merge Indicates that the input should be
merged with, instead of replacing, the
current contents of the RESOURCE_
MANAGER property. Since xrdb can
read SYS$INPUT, this option can
be used to the change the contents
of the RESOURCE_MANAGER property
directly from a terminal or from a
shell script. This option performs
lexicographic sorted merge of the
two inputs to ensure backwards
compatibility.
(continued on next page)
4-30 Version 1.1 New Features
Version 1.1 New Features
4.3 New MIT Utilities
Table_4-14_(Cont.)_xrdb_Options____________________________
Option_______________Description___________________________
-edit filename Indicates that the contents of the
RESOURCE_MANAGER property should be
edited into the given file, replacing
any values already listed there. This
allows you to put changes that you
have made to your defaults back into
your resource file, preserving any
comments or preprocessor lines.
-backup string Specifies the backup suffix for -edit
[.bak].
-remove Removes the RESOURCE_MANAGER from its
window.
-retain Indicates to avoid server reset if
xrdb is the first client.
-quiet Indicates that warnings about
duplicate entries should not be
_____________________displayed.____________________________
Refresh
The xrefresh utility causes all or part of your screen
to be repainted. Xrefresh maps a window on top of the
desired area of the screen and then immediately unmaps it,
causing refresh events to be sent to all applications. By
default, a window without a background is used to provide
faster repainting. Various options can be used to indicate
that a solid background of any color, or the root window
background, should be used instead.
The format is:
xrefresh [-options] [geometry] [display]
The xrefresh options are described in Table 4-15.
Version 1.1 New Features 4-31
Version 1.1 New Features
4.3 New MIT Utilities
Table_4-15_xrefresh_Options________________________________
Option_______________Description___________________________
-display display Specifies the server and screen to
refresh.
-geometry WxH+X+Y Specifies the portion of the screen to
be repainted.
-black Indicates to use a black background.
This can be disorienting, as
everything goes black for a moment.
-white Indicates to use a white background.
The screen appears to flash, then
repaint.
-solid color Indicates to use a solid background
of the specified color, for example,
green.
-root Indicates to use the root background.
-none Indicates to repaint all of the
_____________________windows._This_is_the_default._________
The default is xrefresh -none.
Set Options
The xset utility customizes various user preference options
of the display. These values are global to the X server and
affect other applications.
The format is:
xset [-display display] [-b] [b on/off]
[b volume pitch duration] [[-]bc]
[-c] [c on/off] [c volume]
[[-+]fp[-+=] path[,path[,...]]]
[fp default] [fp rehash] [[-]led integer]
[led on/off] [m[ouse] [acceleration [threshold]]]
[m[ouse] default] [p pixel color]
[[-]r] [r on/off] [s [length period]]
[s blank/noblank] [s expose/noexpose]
[s on/off] [s default] [q]
4-32 Version 1.1 New Features
Version 1.1 New Features
4.3 New MIT Utilities
The xset options are described in Table 4-16.
Table_4-16_xset_Options____________________________________
Option_______________Description___________________________
-display Specifies the server to use.
b Controls the bell volume, pitch,
and duration. This option accepts
up to three numerical parameters, a
preceding dash (-), or an on/off flag.
If no parameters are given, or the
on flag is used, the system defaults
are used. If the dash or the off flag
are used, the bell is turned off. If
only one numerical parameter is given,
the bell volume is set to that value,
as a percentage of its maximum. The
second numerical parameter specifies
the bell pitch, in hertz, and the
third numerical parameter specifies
the duration in milliseconds. The X
server sets the characteristics of the
bell as closely as possible to your
specifications.
c Controls the key click. This option
can take an option value, a preceding
dash (-), or an on/off flag. If no
parameter or the on flag is given, the
system defaults are used. If the dash
or the off flag is used, the keyclick
is disabled. If a value from 0 to
100 is given, it is used to indicate
volume as a percentage of the maximum.
The X server sets the volume to the
nearest value that the hardware can
support.
(continued on next page)
Version 1.1 New Features 4-33
Version 1.1 New Features
4.3 New MIT Utilities
Table_4-16_(Cont.)_xset_Options____________________________
Option_______________Description___________________________
fp=path[,path...] Sets the font path to the directories
specified in the path argument. The
directories are interpreted by the
server, not by the client, and are
server-dependent.
fp default Causes the font path to be reset to
the server's default.
fp rehash Causes the server to reread the font
databases in the current font path.
This is generally only used when
adding new fonts to a font directory.
-fp path[,path...] Removes elements to the current font
path. It must be followed by a comma-
separated list of directories.
fp- path[,path...] Removes elements to the current font
path. It must be followed by a comma-
separated list of directories.
+fp path[,path...] Prepends elements to the current font
path. It must be followed by a comma-
separated list of directories.
fp+ path[,path...] Appends elements to the current font
path. It must be followed by a comma-
separated list of directories.
(continued on next page)
4-34 Version 1.1 New Features
Version 1.1 New Features
4.3 New MIT Utilities
Table_4-16_(Cont.)_xset_Options____________________________
Option_______________Description___________________________
led Controls the keyboard LEDs. This
option controls the turning on or off
of the LEDs. It accepts an optional
integer, a preceding dash (-) or an
on/off flag. If no parameter or if
the on flag is given, all LEDs are
turned on. If a preceding dash or
the off flag is given, all LEDs are
turned off. If a value between 1 and
32 is given, that LED is turned on or
off depending on the existence of a
preceding dash. A common LED that can
be controlled is the Caps Lock LED.
Xset LED 3 would turn LED number 3 on,
while xset -LED 3 would turn it off.
The specific LED values can refer to
different LEDs on different hardware.
m Controls the mouse parameters.
The parameters for the mouse are
acceleration and threshold. The mouse,
or whatever pointer is used, travels
'acceleration' times as fast when it
travels more than 'threshold' pixels
in a short time. The mouse can then
be used for precise alignment when it
is moved slowly, yet it can be set to
travel across the screen rapidly when
desired. One or both parameters for
this option can be omitted, but if
only one is given, it is interpreted
as the acceleration. If no parameters
or if the flag default is used, the
system defaults are used.
(continued on next page)
Version 1.1 New Features 4-35
Version 1.1 New Features
4.3 New MIT Utilities
Table_4-16_(Cont.)_xset_Options____________________________
Option_______________Description___________________________
p Controls the pixel color values. The
parameters are the color map entry
number, in decimals, and a color
specification. The root background
colors may be changed on the same
servers by altering the entries for
BlackPixel and WhitePixel. These do
not have to be set to 0 or 1. A server
can also choose to allocate those
colors privately, but an an error
is generated. The map entry must not
be a read-only color, or an error is
generated.
r Controls the autorepeat. If a
preceding dash or if the off flag
is used, autorepeat is disabled. If no
parameters or if the on flag is used,
autorepeat is enabled.
(continued on next page)
4-36 Version 1.1 New Features
Version 1.1 New Features
4.3 New MIT Utilities
Table_4-16_(Cont.)_xset_Options____________________________
Option_______________Description___________________________
s Lets you set the screen saver
parameters. This option accepts up
to two numerical parameters, a blank
/noblank flag, an expose/noexpose
flag, an on/off flag, or the default
flag. If no parameters or if the
default flag is used, the system
is set to the default screen saver
characteristics. The on/off flags turn
the screen saver functions on or off.
The blank flag sets the preference
to blank the video (if the hardware
can do so) instead of displaying a
background pattern, while noblank
sets the preference to display a
pattern instead of a blank video.
The expose flag sets the preference
to allow window exposures, while the
noexpose flag sets the preference to
disable screen saver unless the server
can regenerate the screens without
causing exposure events. The length
and period parameters for the screen
saver function determine how long the
server must be inactive for screen
saving to activate, and the period to
change the background pattern to avoid
burn in. The arguments are specified
in seconds. If only one numerical
parameter is given, it is used for the
length.
q Gives you information on the current
_____________________settings._____________________________
Set Root Window Options
The xsetroot utility allows you to tailor the appearance of
the background root window on a workstation display running
X. If no options are specified or if -def is specified, the
window is reset to the default state. The -def option can
Version 1.1 New Features 4-37
Version 1.1 New Features
4.3 New MIT Utilities
be specified with other options, and only the nonspecified
characteristics are reset to the default state.
Only one of the background color or tiling options (-solid,
-gray, -grey, -bitmap, and -mod) can be specified at a
time.
The format is:
xsetroot [-help] [-def] [-display display]
[-cursor cursor_file mask_file]
[-cursor_name cursor_name] [-bitmap filename]
[-mod x y] [-gray] [-grey] [-fg color]
[-bg color] [-rv] [-solid color] [-name string]
The xsetroot options are described in Table 4-17.
Table_4-17_xsetroot_Options________________________________
Option___________Description_______________________________
-help Prints a usage message and exit.
-def Resets unspecified attributes to the
default values. Restores the background
to the familiar gray mesh and the cursor
to the hollow x shape.
-cursor cursor_ Lets you change the pointer cursor to
file mask_file whatever you want when the pointer cursor
is outside of any window. Cursor and mask
files are bitmaps and can be created with
the bitmap program. You might want the
mask file to be all black until you become
familiar with the way masks work.
-cursor_name Lets you change the pointer cursor to one
cursor_name of the standard cursors from the cursor
font. See the X Window System for more
information.
(continued on next page)
4-38 Version 1.1 New Features
Version 1.1 New Features
4.3 New MIT Utilities
Table_4-17_(Cont.)_xsetroot_Options________________________
Option___________Description_______________________________
-bitmap Indicates to use the bitmap specified in
filename the file to set the window pattern. You
can make your own bitmap files using the
bitmap program. The entire background is
made up of repeated tiles of the bitmap.
-mod x y Indicates to use a plaid-like grid pattern
on your screen. X and Y are integers
ranging from 1 to 16.
-gray Makes the entire background gray.
-grey Makes the entire background grey.
-fg color Indicates to use color as the foreground
color. Foreground and background colors
are meaningful only in combination with
-cursor, -bitmap, or -mod.
-bg color Indicates to use color as the background
color.
-rv Exchanges the foreground and background
colors. Normally the foreground color is
black and the background color is white.
-solid color Sets the background of the root window to
the specified color. This option is only
useful on color servers.
-name string Sets the name of the root window to
string.
-display Specifies the server to connect to.
display____________________________________________________
Window Dump
The xwd dumping utility allows you to store window images
in a specially formatted dump file. This file can then be
read by other X utilities for redisplay, printing, editing,
formatting, archiving, and image processing. The target
window is selected by clicking MB1 in the desired window.
The keyboard bell rings once at the beginning of the dump
and twice when the dump is completed.
Version 1.1 New Features 4-39
Version 1.1 New Features
4.3 New MIT Utilities
The format is:
xwd [-display host:dpy] [-debug] [-help]
[{-root|-id id|-font font|-name name}]
[-nobdrs] [-out file] [-xy] [-add value] [-frame]
The xwd options are described in Table 4-18.
Table_4-18_xwd_Options_____________________________________
Option___________Description_______________________________
-display Specifies the server to connect to.
display
-help Prints out the usage command syntax
summary.
-nobdrs Specifies that the window dump should not
include the pixels that compose the window
border. This is useful when you want to
include the window contents in a document
illustration.
-out file Specifies the output file on the command
line. The default is to output to
SYS$OUTPUT.
-xy Selects XY format dumping instead of the
default Z format. It applies to color
displays only.
-add value Specifies a signed value to be added to
every pixel.
-frame Indicates that the window manager frame
should be included when manually selecting
_________________a_window._________________________________
Display Window Information
The xwininfo utility displays information about a window
on an X server. Information is displayed depending on which
options are selected. If no options are chosen, -stats is
assumed.
You have the option of selecting the target window with the
mouse (by clicking any mouse button in the desired window)
or by specifying the window ID on the command line with the
-id option. You can also use the -name option to specify
4-40 Version 1.1 New Features
Version 1.1 New Features
4.3 New MIT Utilities
which window is desired by name. There is also a special
-root option to quickly obtain information about the root
window.
The format is:
xwininfo [-options...]
The xwininfo options are described in Table 4-19.
Table_4-19_xwininfo_Options________________________________
Option___________Description_______________________________
-help Prints the command syntax summary.
-display Specifies the X server to contact to.
display
-root Indicates to use the root window.
-id window_id Indicates to use the window with the
specified id.
-name window_ Indicates to use the window with the
name specified name.
-int Prints the window id in decimal. The
default is hexadecimal.
-tree Displays the root, parent, and children
windows' ids and names for the selected
window.
-stats Displays various attributes pertaining
to the location and appearance of the
selected window. Information displayed
includes the location of the window, its
width and height, its depth, border width,
class, colormap ID if any, map state,
backing-store hint, and location of the
corners.
(continued on next page)
Version 1.1 New Features 4-41
Version 1.1 New Features
4.3 New MIT Utilities
Table_4-19_(Cont.)_xwininfo_Options________________________
Option___________Description_______________________________
-bits Displays various attributes pertaining to
the selected window's raw bits and how the
selected window is to be stored. Displayed
information includes the selected window's
bit gravity, window gravity, backing-
store hint, backing-planes value, backing
pixel, and whether or not the window has
save-under set.
-events Displays the selected window's event
masks. Both the event mask of events
wanted by some client and the event mask
of events not to propagate are displayed.
-size Displays the selected window's sizing
hints. Displayed information includes: for
both the normal size hints and the zoom
size hints, the user-supplied location,
if any; the program-supplied location, if
any; the user-supplied size, if any; the
program-supplied size, if any; the minimum
size, if any; the maximum size, if any;
the resize increments, if any; and the
minimum and maximum aspect ratios, if any.
-wm Displays the selected window's window
manager hints. Information displayed may
include whether or not the application
accepts input, what the window's icon
window number and name is, where the
window's icon should go, and what the
window's initial state should be.
-shape Prints out the shape extents.
-frame Causes the window manager frames not to be
ignored when manually selecting windows.
(continued on next page)
4-42 Version 1.1 New Features
Version 1.1 New Features
4.3 New MIT Utilities
Table_4-19_(Cont.)_xwininfo_Options________________________
Option___________Description_______________________________
-english Causes all individual height, width, and x
and y positions to be displayed in inches
(and feet, yards, and miles if necessary),
as well as number of pixels. The -metric
and -english options can both be enabled
at the same time.
-metric Causes all individual height, width,
and x and y positions to be displayed
in millimeters, as well as number of
pixels, based on what the server thinks
the resolution is. Geometry specifications
that are in +x+y form are not changed.
-all Prints -tree, -stats, -bits, -events,
_________________-size,_-wm,_and_-shape_information._______
Window Undump
The xwud utility displays an image saved in a specially
formatted dump file produced by xwd.
The format is:
xwud [-in file] [-noclick] [-geometry geom]
[-display display] [-new] [-std map_type] [-raw]
[-vis vis_type] [-help] [-rv] [-plane number]
[-fg color] [-bg color]
The xwud options are described in Table 4-20.
Table_4-20_xwud_Options____________________________________
Option___________Description_______________________________
-bg color If a bitmap image (or a single plane of
an image) is displayed, this option can be
used to specify the color to display for
the 0 bits in the image.
(continued on next page)
Version 1.1 New Features 4-43
Version 1.1 New Features
4.3 New MIT Utilities
Table_4-20_(Cont.)_xwud_Options____________________________
Option___________Description_______________________________
-display Specifies the server to connect to.
display
-fg color If a bitmap image (or a single plane of
an image) is displayed, this option can be
used to specify the color to display for
the 1 bits in the image.
-geometry geom Specifies the size and position of the
window. Typically you should specify the
position, and let the size default to the
actual size of the image.
-help Prints out a short description of the
allowable options.
-in file Specifies the input file on the command
line. If no input file is given, the
standard input is assumed.
-new Forces the creation of a new colormap
for displaying the image. Matching the
image characteristics to those of the
display can get the image on the screen
faster, but at the cost of using a new
colormap (which on most displays causes
other windows to become Technicolor).
-noclick Clicking any mouse button in the window
terminates the application, unless this
option is specified. Termination can
always be achieved by typing q, Q, or
Ctrl+C.
-plane number Selects a single bit plane of the image
to display. Planes are numbered with zero
being the least significant bit.
(continued on next page)
4-44 Version 1.1 New Features
Version 1.1 New Features
4.3 New MIT Utilities
Table_4-20_(Cont.)_xwud_Options____________________________
Option___________Description_______________________________
-raw Forces the image to be displayed with
whatever color values currently exist on
the screen. This option is most useful
when undumping an image back onto the same
screen that the image originally came from
while the original windows are still on
the screen, and results in getting the
image on the screen faster.
-rv If a bitmap image (or a single plane of an
image) is displayed, this option forces
the foreground and background colors
to be swapped. Swapping might be needed
when displaying a bitmap image which has
the color sense of pixel values 0 and
1 reversed from what they are on your
display.
-std map_type Displays the image using the specified
standard colormap. The property name is
obtained by converting the type to upper
case, prepending RGB_, and appending _
MAP. Typical types are: best, default, and
gray.
-vis vis_type Specifies a particular visual or visual
or vis_id class. The default is to pick the best
one. A particular class can be specified:
StaticGray, GrayScale, StaticColor,
PseudoColor, DirectColor, or TrueColor.
Match can be specified to use the same
class as the source image. Alternatively,
an exact visual ID (specific to the
server) can be specified, either as a
hexadecimal number (prefixed with 0x) or
as a decimal number. The default can be
specified to use the same class as the
colormap of the root window. Case is not
_________________significant_in_any_of_these_strings.______
Version 1.1 New Features 4-45
_________________________________________________________________
Index
A CDA (Compound Document
_______________________________ Architecture), 3-1
Accelerators, 1-22 documentation for, 3-1
Access control, 1-2 CDA PostScript Converter, 1-5
Ada, 2-8 graphics objects, 1-6
Ada bindings files, 2-73 page problem, 1-6
Application CDA Viewer, 1-5, 4-3
started as icon, 1-22 DECfonts, 1-6
application identifier name, graphics objects, 1-6
1-16 page problem, 1-6
application startup error, viewing PostScript files with
1-16 errors, 1-5
Applications with Watch progress, 1-7
for DECwindows Motif, 1-3 CDA(Compound Document
audio editor, 4-4 Architecture), 2-3
Autostart customization, 1-28 data type definitions, 2-4
function prototypes, 2-4
B______________________________ item change lists, 2-5
Backingstore, 2-71 problems with XUI
disabling, 2-69 applications, 2-4
Bookreader, 1-3 user get or put routines,
bookshelf logical, 1-4 2-3
formal examples, figures, and Code shareable images, 2-15
tables, 1-4 Color name file, 2-69
incorrect text in message, Command files
1-4 for checking version, 1-29
Compatibility
C in display server, 2-70
_______________________________ of shareable images, 2-16
Calendar, 1-4 other Toolkit changes, 2-10
Cardfiler, 1-5 Compound Document Architecture
See CDA
Index-1
Configuration file, 1-20 DECwrite integration, 4-8
Context-sensitive Help, 2-11 Delete
controller communication and See FileView Delete
startup, 2-6 Diagnostic crash file
Cursor colors for DECterm, 1-10
updating, 2-71 Diagnostic crash messages
customized login logos, 1-3 for DECterm, 1-10
customizing colors, 1-22 Digital Release 3
D See MIT X11 Release 3
_______________________________ Intrinsics
DEC CDA Base Services, 2-3 Display Options..., 1-6
DECpresent bullet fonts, 2-18 Display PostScript Server
DECpresent integration, 4-8 Extension, 2-17
DECsound, 4-1 Documentation, 3-1
prerequisites, 4-1 for Compound Document
DECsound restrictions, 4-11 Architecture, 3-1
DECterm, 1-7 for VMS DECwindows Motif,
Condensed German Standard 3-2
font, 1-7 DXmCSTextReplace, 3-4
cursor blink, 1-7 DXmCSTextSetSelection, 2-31
default font size, 1-12 DXmFormSpaceButtonsEqually,
diagnostic crash file, 1-10 2-67
diagnostic crash messages, DXmHelpSystem status values,
1-10 2-32
graphics, 1-8 DXmNlayoutDirection, 2-33
nohangup support, 1-12
queued printing, 1-15 E
simultaneous multiple _______________________________
language performance, extensions, 2-29
1-16
text, 1-10 F______________________________
virtual terminal support, FileView, 1-26
1-12 problems, 1-28
DECterm controller, 1-7 FileView Delete, 1-26
DECterm initialization, 1-9 Font names
DECterm logicals, 2-7 lowercase, 2-71
DECterm resource usage, 1-10 Font sets
DECterm window position, 2-7 default, 1-12
DECW$CDPLAYER, 1-20 Fonts
DECwindows default character processing,
restarting, 1-28 2-71
DECwindows Toolkit 75 dpi, 2-68
See Toolkit 100 dpi, 2-68
for DECpresent, 2-18
Index-2
Fonts (cont'd)
for layered products, 2-18 M______________________________
metrics file for, 2-18 Mail, 1-17
FORTRAN, 2-8 arrow buttons in Read window,
Function keys, 1-20 1-17
word wrap option in, 1-17
H______________________________ Mail integration, 4-3
Help Callback routines, 2-11 MIT utilities, 4-13
MIT X11 Release 3 Intrinsics,
I______________________________ 2-16
Icon, 1-21 changes from, 2-8
for restored window, 1-25 MIT X11 Release 4, 2-69
with multiline text, 1-24 MIT X11 Release 4 Intrinsics,
Icon box 2-16
accelerators for icon, 1-22 conforming to, 2-8
colors for, 1-23 Mixing XUI and Motif widgets,
customizing, 1-23 2-15
customizing icon placement, Modal dialog boxes, 1-23
1-23 Monochrome monitors
moved off screen, 1-23 color-related resources for,
Window menu on, 1-25 1-22
Icon title Monocrome and gray-scale
truncated, 1-23, 1-25 systems
international keyboards, 1-21 icon box colors for, 1-23
Intrinsics key translator, Motif and XUI Widgets
2-12 mixing, 2-17
Item change lists, 2-5 Motif Window Manager
See Mwm
K______________________________ mouse actions, 1-26
keyboard actions, 1-26 Multihead systems
keyboards, 1-11 customizing colors, 1-24
Keycodes, 2-12 Next window on, 1-24
MUTEX hang bug, 2-6
Keysyms Mwm (Motif Window Manager),
See Virtual keysyms 1-20
configuration file, 1-20
L______________________________ icons, 1-21
languages, 1-11 problems with, 1-22
LinkWorks, 1-16 restarting, 1-25
LiveLink connections, 4-8 running earlier versions of
DECwindows, 1-21
Mwm default font, 1-25
Index-3
N______________________________ S______________________________
New view, 1-28 screen print services, 1-15
Session Manager, 1-26
O______________________________ problems, 1-28
OSF examples, 2-19 stopping process, 1-28
OSF/Motif Release 1.1.3, 2-8 Shareable images, 2-15
code, 2-15
P thin-layer, 2-16
_______________________________ two classes of, 2-15
Paint, 1-17 upward compatibility, 2-16
editing color images, 1-18 SIXEL, 1-14
private colormaps, 1-18 Structured Visual Navigation
saving a Paint file, 1-18 See SVN
slow performance with, 1-17 SVN
Parameter datasize, 2-74 horizontal separator line,
Pascal, 2-8 2-67
.PEN files for, 2-74 SVN (Structured Visual
PC interoperability, 1-13 Navigation), 2-67
.PEN files, 2-74 SVN widget, 2-67
POSIX support, 2-2
Print Screen, 1-18 T
default icon, 1-19 _______________________________
keyboard mnemonics, 1-18 Thin-layer shareable image,
limitations of Options menu 2-16
item, 1-19 Toolkit, 2-8
limitations of Queue Options context-sensitive Help, 2-11
dialog box, 1-19 debugging, 2-11
Reduce Only setting, 1-20 Help Callback routines, 2-11
resource values for, 1-20 Intrinsics key translator,
with Orientation option, 2-12
1-19 miscellaneous notes, 2-11
Private logo, 1-28 mixing Motif and XUI Widgets,
Public profiles 2-17
for layered products, 1-25 new shareable images, 2-15
non-C language binding
R______________________________ support, 2-8
Reference pages text widget translations,
Revision 1.1.1 changes to, 2-13
3-5 traversing a Motif menu bar,
ReGIS, 1-14 2-13
ReGIS locator report, 1-15 with Shift Lock key
combination, 2-13
XmText class widget, 2-13
Index-4
Toolkit (cont'd)
XmText widget interactive W______________________________
performance, 2-14 Widgets
XUI application linking insensitivity problem, 2-11
procedures, 2-14 mixing XUI and Motif, 2-15
Toolkit shareable images Window Manager
See Shareable images See Mwm
translation table, 2-40 multiscreen system, 1-24
Troubleshooting, 1-29 work-in-progress box, 1-16
_______________________________ X______________________________
UIL compiler, 2-67 X Image extension, 2-72
UIL extensions, 2-67 X11 Display Server, 2-68
User default resource file, backingstore disable, 2-69
1-27 backingstore problems, 2-71
compatibility, 2-70
V infinite loop, 2-71
_______________________________ updating cursor colors, 2-71
VAX C sample programs, 2-67 Xlib
VAX format toolkit bindings, client side library, 2-73
2-14 Xlib routines, 2-73
VAXstations 3520 and 3540 Ada bindings files, 2-73
with XTrap server extension, files for Pascal programs,
2-68 2-74
Version checking command files parameter datasize, 2-74
, 1-29 VAX C sample programs, 2-67
Virtual keysyms, 2-12 XmNblinkRate, 2-31
VMS DECwindows Motif Help XmNmodifyVerifyCallback, 3-4
System, 4-12 XSelectAsyncEvent, 2-75
XSelectAsyncInput, 2-75
XUI and Motif widgets, 2-15
XUI application linking
procedures, 2-14
Index-5