Release Notes for DECwindows
Developer Kit for OSF/Motif V1.1
September, 1990
_______________________________________________________
Contents
_________________________________________________
1 NEW FEATURES AND CHANGES IN THIS
RELEASE 1
1.1 AES/UE and Style Guide
Compliance ____________________ 1
1.2 Other Enhancements ____________ 1
1.3 OSF/Motif and the Xt
Intrinsics ____________________ 4
1.4 Compound String Changes _______ 5
1.5 Internal Changes ______________ 6
1.6 ANSI C and C++ Compliance _____ 6
1.7 Resource Names Changed ________ 6
1.8 Default Font List Changes _____ 7
1.9 XmNtextTranslations To Be
Removed from BulletinBoard ____ 7
1.10 Help Translations Added _______ 7
1.11 Traversal Enabled by Default __ 8
1.12 Mnemonic Type Changed to
KeySym ________________________ 9
1.13 Mnemonic Underlining is Case
Sensitive _____________________ 9
1.14 MrmFetchInterfaceModule
Removed _______________________ 9
1.15 Compound String Resources
Inconsistently Copied _________ 9
1.16 Clipboard Workaround __________ 10
1.17 Problem with Clicking in
Borders _______________________ 10
1.18 Documentation Enhancements ____ 10
_________________________________________________
2 DIGITAL-SPECIFIC CONCERNS FOR MOTIF 11
iii
Contents
2.1 DECwindows/Motif Window Manager
(MWM) _________________________ 11
2.1.1 How to Set Up the Motif Window
Manager, 12
2.1.1.1 How to Set Up the Resource
Files, 13
2.1.1.2 How Mwm Finds Resources, 16
2.1.1.3 The Configuration File, 17
2.1.1.4 Button and Key Bindings, 17
2.1.1.5 Workspace Menu, 18
2.1.1.6 How to Run the Window Manager on a
Multiscreen System, 19
2.1.1.7 Icons, 19
2.1.1.8 Running DECwindows Version 1.0,
2.0, and 2.1 Applications, 19
2.1.1.9 Motif Bindings File, 20
2.1.1.10 Bitmap Directory File, 20
2.1.1.11 Known Problems, 20
2.2 DECwindows/Motif UIL __________ 21
2.3 Callable UIL __________________ 21
2.4 DECwindows/Motif Mrm (DRM) ____ 22
2.5 DECwindows/Motif Intrinsics ___ 25
_________________________________________________
3 DIFFERENCES BETWEEN XUI AND
DECWINDOWS/MOTIF WIDGETS 26
3.1 Text Editing __________________ 26
3.1.1 Bit Gravity, 27
3.1.2 Keyboard Accelerators, 27
3.1.3 RowColumn (Menu) Widget, 27
3.1.4 Scale Widget, 28
3.1.5 Toggle Button Widget, 28
3.1.6 Bulletin Board Font Units, 28
3.1.7 Help Widget, 29
3.1.8 XmString Resources, 29
3.2 User-Defined Widgets __________ 30
iv
Contents
_________________________________________________
4 INTEROPERABILITY OF XUI AND MOTIF 31
_________________________________________________
5 PORTING TOOLS, XUI TO
DECWINDOWS/MOTIF 32
5.1 How The Filters Work __________ 32
5.2 Marking Strings Definitions ___ 33
5.2.1 Developer decision, 33
5.2.2 Mapping unknown, 34
5.2.3 Mapping unsupported for this
symbol, 34
5.2.4 Future feature, 34
5.2.5 Motif Transition, 34
5.3 The Filters ___________________ 34
5.3.1 Running the filters on VMS, 35
5.4 Running the filters on ULTRIX _ 36
_________________________________________________
6 KIT CONTENTS 36
6.1 VMS ___________________________ 36
6.1.1 Logicals, 37
6.1.2 Compilation, 37
6.1.3 Libraries, 38
6.2 ULTRIX (VAX and RISC) _________ 38
6.2.1 Road Map, 38
6.2.2 Compilation, 39
6.2.3 Libraries, 39
_________________________________________________
7 INFORMATION ON ULTRIX 40
_________________________________________________
8 BUG REPORT SUMMARY 41
v
Contents
_______________________________________________________
TABLES
1 Accelerators __________________ 17
2 Known Bugs in Motif 1.1 _______ 42
vi
__________________________________________________________________
1 New Features and Changes in this Release
The following sections summarize new features and
changes in this release. This information has been
provided by the Open Software Foundation (OSF).
___________________________
1.1 AES/UE and Style Guide Compliance
Motif 1.1 is compliant with the Revision B of the
User Environment Volume of the Application Environment
Specification (AES/UE) and with the OSF/Motif Style
Guide. We (OSF) have made many changes in this release
and incorporated changes in the AES/UE to achieve
compliance.
___________________________
1.2 Other Enhancements
Motif 1.1 contains a number of enhancements that
are not included in the AES. Among these are the
following:
o New routines for creating simple menus. Each type
of menu supported by these routines has two simple
creation functions, one with a fixed argument list
and one with a variable-length argument list.
See the manual pages for routines whose names
begin with XmCreateSimple and XmVaCreateSimple
(for example, XmCreateSimplePopupMenu and
XmVaCreateSimplePopupMenu.
o A new widget, XmTextField , and associated
convenience routines, for single-line text.
o A new routine, XmProcessTraversal , to set keyboard
focus.
o New routines for getting and setting a routine to
calculate default colors.
o A new routine for finding the widget that has the
destination cursor.
1
o New routines for traversing a font list.
o The use in many translation tables of virtual
keysyms that can be bound at run time to user-
or vendor-specific keysyms.
o A change to the Motif Window Manager (MWM) to read
a file, .Motifbind , with bindings for virtual
keysyms.
o Enhancements to the User Interface Language (UIL),
including these:
- Widget Meta-Language (WML) support for resource
synonyms.
- Allowing forward references for all UIL named
elements.
- Providing names for all objects.
- SINGLE_FLOAT and RGB data types.
- KEYSYM function.
- Supporting enumeration values for resources (UIL
and WML).
- Using $LANG to determine base character set.
- Supporting toolkit object names for gadgets.
The following new manual pages exist in Motif 1.1 for
features not included in the AES/UE:
2
XmCreateSimpleCheckBox
XmCreateSimpleMenuBar
XmCreateSimpleOptionMenu
XmCreateSimplePopupMenu
XmCreateSimplePulldownMenu
XmCreateSimpleRadioBox
XmCreateTextField
XmFontListCopy
XmFontListFreeFontContext
XmFontListGetNextFont
XmFontListInitFontContext
XmGetColorCalculation
XmGetDestination
XmResolveAllPartOffsets
XmSetColorCalculation
XmSetFontUnits
XmTextField
XmTextFieldClearSelection
XmTextFieldCopy
XmTextFieldCut
XmTextFieldGetBaseline
XmTextFieldGetEditable
XmTextFieldGetInsertionPosition
XmTextFieldGetLastPosition
XmTextFieldGetMaxLength
XmTextFieldGetSelection
XmTextFieldGetSelectionPosition
XmTextFieldGetString
XmTextFieldInsert
XmTextFieldPaste
XmTextFieldPosToXY
XmTextFieldRemove
XmTextFieldReplace
XmTextFieldSetAddMode
XmTextFieldSetEditable
XmTextFieldSetHighlight
XmTextFieldSetInsertionPosition
XmTextFieldSetMaxLength
XmTextFieldSetSelection
XmTextFieldSetString
3
XmTextFieldShowPosition
XmTextFieldXYToPos
XmVaCreateSimpleCheckBox
XmVaCreateSimpleMenuBar
XmVaCreateSimpleOptionMenu
XmVaCreateSimplePopupMenu
XmVaCreateSimplePulldownMenu
XmVaCreateSimpleRadioBox
___________________________
1.3 OSF/Motif and the Xt Intrinsics
Motif 1.1 uses Version 11, Release 4 of the X Window
System (tm), including the X11R4 X Toolkit Intrinsics.
This section lists some implications of this change
for application programs.
Values of type Position and Dimension are now 16-bit
quantities.
Applications should use the X11R4 Xt programming
interface, as described in Appendix C ("Conversion
Notes") of the X Toolkit Intrinsics-C Language
Interface document. In particular, applications
should use XtAppInitialize, XtAppCreateShell,
and XtAppMainLoop instead of XtInitialize,
XtCreateApplicationShell, and XtMainLoop.
Whenever a widget grabs the keyboard, it should
use the Xt grabbing functions instead of the Xlib
functions, because Xt maintains internal state
indicating whether or not the keyboard is grabbed.
Applications that do not use the Xt grabbing functions
are not guaranteed to work in future versions of
OSF/Motif.
Use of some Intrinsics functions by applications may
conflict with internal use of those functions by
Motif 1.1. In such cases Motif provides equivalent
functions. In particular, applications should avoid
using the following functions:
4
o XtSetKeyboardFocus-This routine might break Motif
keyboard traversal. An application should use
XmProcessTraversal to set keyboard focus.
o XtRemoveAllCallbacks-Calling this routine from an
application removes all callbacks from a widget,
including those added internally by Motif code.
An application should use XtRemoveCallback or
XtRemoveCallbacks to remove particular callbacks.
Applications should use appropriate Xt routines for
managing, realizing, and mapping children. Managing a
widget implies that geometry is totally recomputed.
Unmanaging and managing a widget simply to make
it appear or disappear without geometry changes is
inappropriate. An application should use XtMap and
XtUnmap for this purpose.
___________________________
1.4 Compound String Changes
The internal implementation of the XmString data type
has changed. Applications that used the internals of
the opaque data structure are likely to break.
Motif 1.1 has introduced a number of extensions with
the intent of providing backward compatibility for the
next internationalization release. In particular:
o XmStringCreate is included in Revision B of the AES
as a temporary-use element and might be changed or
removed from the AES in future revisions.
o A new routine, XmStringCreateSimple , creates a
compound string, deriving the character set from
the language environment of a widget passed as
an argument. Applications should use this routine
instead of XmStringCreate to create a compound
string using the default character set.
5
o Some applications have been using the character set
identifier in a compound string as a specific tag
meaningful only to the application, not as a real
character set identifier. Such applications are
likely to be broken in the future releases.
___________________________
1.5 Internal Changes
The OSF has made changes to the internal Gadget
caching code and the clipboard code. These internal
changes do not affect the application programming
interface.
___________________________
1.6 ANSI C and C++ Compliance
Motif 1.1 is compliant with ANSI C. All external
functions are prototyped.
You can compile an application for C++ using Motif
1.1 public header files, and this C++ program can
link with the Xm, Uil, and Mrm libraries. All external
functions use the extern "C" clause.
___________________________
1.7 Resource Names Changed
The names of three resources have been changed because
of conflicts with resource names in other widgets.
In XmPanedWindow , XmNminimum has been renamed to
XmNpaneMinimum , and XmNmaximum has been renamed to
XmNpaneMaximum. In XmText, XmNtopPosition has been
renamed to XmNtopCharacter .
The MWM selectColor icon box resource has been renamed
to troughColor.
6
___________________________
1.8 Default Font List Changes
The value of the XmNfontList resource now obtains its
default dynamically. The default value is obtained by
looking up the parent hierarchy of the widget for an
ancestor that is a subclass of the XmBulletinBoard,
VendorShell, or XmMenuShell widget class. If such an
ancestor is found, the font list is initialized to
the appropriate default font list of the ancestor
widget (XmNdefaultFontList) for VendorShell and
XmMenuShell; XmNbuttonFontList, XmNlabelFontList,
or XmNtextFontList for XmBulletinBoard. The three
XmBulletinBoard font list resources obtain their
defaults in the same way.
___________________________
1.9 XmNtextTranslations To Be Removed from BulletinBoard
The XmNtextTranslations resource in XmBulletinBoard
exists in Motif 1.1 but may be removed in a future
release. BulletinBoard no longer overrides the KReturn
translation for multiline text.
___________________________
1.10 Help Translations Added
Every widget has a translation for KHelp. The Help
action calls the XmNhelpCallback callbacks if they
exist. If they do not exist, the Help action looks up
the parent hierarchy until it finds an XmNhelpCallback
and then calls it. Applications no longer need provide
translation table entries for <F1>.
7
___________________________
1.11 Traversal Enabled by Default
Traversal for many controls is enabled by default in
this release; the XmNtraversalOn resource defaults
to True for these widgets. The default value of
XmNtraversalOn is False for the following widgets and
gadgets:
XmLabel
XmLabelGadget
XmScrollBar
XmSeparator
XmSeparatorGadget
The default is True for all other widgets (except that
it is forced to False in an empty List). This is a
change to the following widgets and gadgets:
XmArrowButton
XmArrowButtonGadget
XmCascadeButton
XmCascadeButtonGadget
XmDrawnButton
XmPushButton
XmPushButtonGadget
XmToggleButton
XmToggleButtonGadget
XmList
XmText
This change can affect the layout of applications, as
many controls are larger to accommodate the traversal
highlight. In most cases the Motif 1.1 appearance can
be restored by setting the following resources:
*traversalOn: false
*highlightOnEnter: false
*highlightThickness: 0
8
___________________________
1.12 Mnemonic Type Changed to KeySym
The type of the XmNmnemonic resources in XmLabel,
XmLabelGadget, and XmRowColumn has been changed to
KeySym. The size of this type is different from that
of the Motif 1.1 type, char, for these resources.
___________________________
1.13 Mnemonic Underlining is Case Sensitive
In order to be underlined when a mnemonic is used, a
character in a label string must match the mnemonic
exactly. However, to activate the mnemonic, the user
can press either the shifted or the unshifted key that
corresponds to the mnemonic.
___________________________
1.14 MrmFetchInterfaceModule Removed
The MrmFetchInterfaceModule routine has been removed
in Motif 1.1.
___________________________
1.15 Compound String Resources Inconsistently Copied
In this release, XtGetValues for a resource whose
value is a compound string sometimes does and
sometimes does not copy the returned string.
Following is a list of some known resources whose
XmString values are not copied (this list may not be
exhaustive):
XmBulletinBoard XmNdialogTitle
XmFileSelectionBox XmNdirectory
XmNnoMatchString
XmRowColumn XmNlabelString
XmScale XmNtitleString
9
In addition, the XmList resources XmNitems and
XmNselectedItems, which are of type XmStringTable,
are not copied.
You must be careful not to free the compound strings
returned by XtGetValues for these resources; you
should free the compound strings returned for other
XmString resources, using the XmStringFree routine.
___________________________
1.16 Clipboard Workaround
All XmClipboard routines require a window ID
parameter. If the window ID is obtained from a Text
widget or if XtOwnSelection has been called on the
widget used to obtain the window ID, paste requests
from non-Motif clients will fail. The problem is
caused by a bug in the Intrinsics selection mechanism.
To get around it use a different widget, such as the
parent, to obtain the window ID.
___________________________
1.17 Problem with Clicking in Borders
Pressing BSelect in the border of an Arrow,
DrawnButton, PushButton, or ToggleButton widget has
undefined behavior. You should not change the value
of the XmNborderWidth resource from its default of
0. This applies also when the buttons are inside any
RowColumn widget whose XmNentryBorder resource is
greater than 0. The result of pressing BSelect in the
RowColumn entry border area is undefined.
___________________________
1.18 Documentation Enhancements
The following documents have been substantially
revised for Motif 1.1:
o The OSF/Motif Style Guide has been rewritten.
10
o A new revision of the Application Environment
Specification User Environment Volume (AES/UE)
accompanies Motif 1.1.
Note: since the AES/UE is a subset of the
Programmer's Reference, it has not been provided
as a separate document for this release.
o The OSF/Motif Programmer's Reference has been
updated for this release, and the format of the
descriptions of translations and actions has
changed.
o The OSF/Motif Programmer's Guide has been made
accurate for Motif 1.1.
o Customers using this product on the ULTRIX
operating system can find reference pages in the
/usr/man directory.
__________________________________________________________________
2 Digital-Specific Concerns for Motif
The DECwindows Developer Kit for OSF/Motif Version
1.1 runs on the VMS operating system Version 5.3 or
higher. It also runs on ULTRIX on RISC systems and
ULTRIX on VAX systems version 3.1 or higher.
The following sections describe differences between
the DECwindows Developer Kit for OSF/Motif and Motif
as it might be purchased elsewhere.
___________________________
2.1 DECwindows/Motif Window Manager (MWM)
To set up your system so that MWM will execute, follow
the directions below:
11
VMS 5.3 or higher:
In the session manager choose "Customize Window." When
the dialog box pops up:
1 Choose "Other" under the Window Manager heading.
2 Type SYS$COMMON:[DECW$MOTIF.CLIENTS.MWM]MWM.EXE in
the input text field next to "Other."
3 Click on "OK."
4 Choose "Save Current Settings" from the customize
pull down menu.
ULTRIX 3.1 or higher:
In the session manager choose "Customize Window." When
the dialog box pops up:
1 Choose "Other" under the Window Manager heading.
2 For ULTRIX on a RISC system, type
/usr/lib/DXM/clients/mwm/mwm in the input text
field next to "Other."
For ULTRIX on a VAX system, type
/usr/lib/DXV/clients/mwm/mwm in the input text
field next to "Other."
3 Click on "OK."
4 Choose "Save Current Settings" from the customize
pull down menu.
_____________________
2.1.1 How to Set Up the Motif Window Manager
The subsequent sections contain information on the
following:
o How to set up the resource files
o How Mwm finds resources
o The configuration file
o Button and key bindings
12
o The workspace menu
o How to run the window manager on a multiscreen
system
o Icons
o Running previous DECwindows applications
o The Motif bindings file
o Known problems
_____________________
2.1.1.1 How to Set Up the Resource Files
The kit includes the default Motif window manager
resource files for customizing the appearance and
behavior of the window manager.
For VMS
For VMS, these files are in
SYS$COMMON:[DECW$MOTIF.CLIENTS.MWM]
DECW$SYSTEM_DEFAULTS
The resources for color, black and white, and gray-
scale displays are in the following directories:
DECW$MWM_COLOR.DAT
DECW$MWM_BW.DAT
DECW$MWM_GRAY.DAT
The default is DECW$MWM.DAT, which is the color
version.
For ULTRIX on a RISC System
For ULTRIX on a RISC system, these files are in
/usr/lib/DXM/clients/mwm
/usr/lib/X11/app-defaults
13
For ULTRIX on a VAX System
For For ULTRIX on a VAX system, these files are in:
/usr/lib/DXV/clients/mwm
/usr/lib/X11/app-defaults
The resources for color, black and white, and gray-
scale displays are in:
Mwm_color
Mwm_bw
Mwm_gray
The default is Mwm, which is the color version.
If your system is not a color workstation, you should
copy the appropriate file to DECW$USER_DEFAULTS for
VMS or your home directory for ULTRIX.
The kit also includes general Motif resources for
customizing such resources as the screen color and the
colors inside of the window.
For VMS
For VMS, these files are in
SYS$COMMON:[DECW$MOTIF.CLIENTS.MWM]
DECW$SYSTEM_DEFAULTS
The resources for color, black and white, and gray
scales are in
DECW$XDEFAULTS_COLOR.DAT
DECWXDEFAULTS_BW.DAT
DECW$XDEFAULTS_GRAY.DAT
For ULTRIX on a RISC System
For ULTRIX on a RISC system, the file is
/usr/lib/DXM/clients/mwm/Xdefaults_Motif
/usr/lib/X11/app-defaults/Xdefaults_Motif
14
For ULTRIX on a VAX System
For ULTRIX on a VAX system, the file is
/usr/lib/DXV/clients/mwm/Xdefaults_Motif
/usr/lib/X11/app-defaults/Xdefaults_Motif
Xdefaults_Motif contains the resources for color,
black and white, and gray-scale displays.
You should merge in the appropriate Xdefaults file
with the current one in DECW$SYSTEM_DEFAULTS for VMS
or /usr/lib/X11/app-defaults on ULTRIX.
The kit also contains the default configuration file,
which includes the definitions of the window manager
menus as well as key and button bindings.
For VMS
For VMS, the file is
SYS$COMMON:[DECW$MOTIF.CLIENTS.MWM]DECW$MWM_RC.DAT
DECW$SYSTEM_DEFAULTS:DECW$MWM_RC.DAT
For ULTRIX on a RISC System
For ULTRIX on a RISC system, the file is
/usr/lib/DXM/clients/mwm/system.mwmrc
/usr/lib/X11/ system.mwmrc
For ULTRIX on a VAX System
For ULTRIX on a VAX system, the file is
/usr/lib/DXV/clients/mwm/system.mwmrc
/usr/lib/X11/ system.mwmrc
If you have previously installed versions of Motif
and you have tailored any of the resources for your
system or for your personal account, you should merge
any changes into these files. In particular, for the
default colors to work properly, you must merge in the
new Xdefaults and mwm resource files.
15
Also, all mwm resources should be defined as
Mwm*resourcename rather than Mwm.resourcename.
If you make a private copy of the configuration file,
you must modify the Mwm*configFile resource in the mwm
resource file to point to the new file specification.
_____________________
2.1.1.2 How Mwm Finds Resources
For VMS
For VMS, mwm first searches for DECW$USER_
DEFAULTS:DECW$MWM.DAT and then for DECW$SYSTEM_
DEFAULTS:DECW$MWM.DAT for all the mwm resource files.
For ULTRIX
For ULTRIX, Mwm first searches in your home directory
for the mwm resource file. If the resource file is not
found there, it searches using an algorithm specified
in the intrinsics manual. It uses such environment
variables as XFILESEARCHPATH and the XtResolvePathname
intrinsic call. Please see the description for this
routine for further details. A typical place for this
file is /usr/lib/X11/app-defaults.
A resource that is defined in the Xdefaults file will
override any resource defined in Mwm.
For new resources as defined in the mwm file to take
effect, you must select Restart from the Workspace
menu to restart the window manager. For new resources
that are defined in the Xdefaults file, you must
restart the session by exiting the session manager
and logging in. It is therefore advisable to place all
the mwm resources in the mwm resource file rather than
the xdefaults file.
16
_____________________
2.1.1.3 The Configuration File
The configuration file defines the window manager use
of the function keys. Most of accelerators are in the
form Alt (compose) function key. If any application
uses these keys, you must either comment them out by
placing "#" at the beginning of the line or create
new keyboard bindings and change Mwm*keyBindings:
DefaultKeyBindings in the mwm resource file to point
to the new bindings.
The Motif binding, Alt (or Compose) Space, which
brings up the window menu has been commented out
because it interferes with Compose sequences in
DECterm. Alt (or Compose) Escape (F11) will also bring
up the window menu. This problem will be addressed in
a future release.
_____________________
2.1.1.4 Button and Key Bindings
The following table lists some of the accelerators
for window manager operations as defined in the
configuration file.
Table_1__Accelerators__________________________________
Restore Alt F5 or MB1 double-click on icon
Move Alt F7
Size Alt F8
Minimize Alt F9 or MB1 double-click on title
Maximize Alt F10
Lower Alt F3 or Shift MB1 on border or icon
17
Table_1_(Cont.)__Accelerators__________________________
Close Alt F4
Window menu Shift Escape or MB3 on border or icon
Workspace menu MB1 or MB3 on screen
Next window Alt Tab or Alt Escape or Ctrl MB1 on
icon, border, or screen
Previous window Alt Shift Tab or Alt Shift Escape
Set behavior Alt Ctrl !
Next transient Alt F6 or Alt MB1 on icon, border, or
window screen
Previous Alt Shift F6
transient
window
Raise_window_____MB1___________________________________
_____________________
2.1.1.5 Workspace Menu
The workspace (or root) menu is activated by
pressing MB1 or MB3 on the screen. This menu contains
additional window manager operations such as shuffle
up and down that are not found in the window menu on
the border.
18
_____________________
2.1.1.6 How to Run the Window Manager on a
Multiscreen System
You can not run the window manager on multiple screens
from the DECwindows V2.0 or V2.1 session manager.
You must stop the current window manager, and run the
window manager from a DECterm and pass "multiscreen"
as a parameter.
For VMS,
$ MWM = "$SYS$COMMON:[DECW$MOTIF.CLIENTS.MWM]MWM"
$ MWM -MULTISCREEN
For ULTRIX on a RISC System
/usr/DXM/clients/mwm/mwm -multiscreen &
For ULTRIX on a VAX System,
/usr/DXV/clients/mwm/mwm -multiscreen &
_____________________
2.1.1.7 Icons
Icons with bitmaps of depth greater than 1 are no
longer supported. The window manager will report a
warning in this case and will attempt to display the
icon.
_____________________
2.1.1.8 Running DECwindows Version 1.0, 2.0,
and 2.1 Applications
The resource Mwm*useDECMode allows version 1.0, 2.0,
and 2.1 DECwindows applications to behave correctly
with the Motif window manager. In particular, this is
19
used to handle focus, icons, window placement, and the
window's initial state (normal or minimized).
_____________________
2.1.1.9 Motif Bindings File
The Motif virtual bindings are virtual button and key
bindings that link buttons or keys to X Window events.
For VMS
For VMS, the file is DECW$USER_
DEFAULTS:DECW$MOTIFBIND.DAT.
For ULTRIX
For ULTRIX, the file is ~/.Motifbind.
_____________________
2.1.1.10 Bitmap Directory File
The default bitmap directory is used when searching
for icon images. This can be defined by specifying the
Mwm*bitmapDirectory resource.
For VMS
For VMS, by default, this is DECW$USER_DEFAULTS.
For ULTRIX
For ULTRIX, by default, this is
/usr/include/X11/bitmaps.
_____________________
2.1.1.11 Known Problems
o F.exec on VMS
F.exec, which runs an image or command
procedure, will not work if you run the
window manager from the session manager. You
must stop the window manager and start it
from a terminal using run/detach/input=nl:
SYS$COMMON:[DECW$MOTIF.CLIENTS.MWM]MWM.
20
If you restart the window manager from the
workspace menu, f.exec will not work.
o Feedback window
If an application sets the minimum size of a
window, then the feedback window that is displayed
when resizing a window may show a size of 0,0 when
the minimum size is reached.
o Starting the window manager
On VMS if the window manager does not start
from a version 2.0 or 2.1 session manager,
please add the following statement to the end of
SYS$MANAGER:DECW$SYLOGIN.COM.
$ wait 00:00:10.00
If this fails, please increment the time to
00:00:20.00.
o Keyboard Traversal of the Workspace menu
At present, there is no keyboard traversal for the
Workspace menu. Therefore, you must use the mouse
the access this menu.
___________________________
2.2 DECwindows/Motif UIL
The UIL compiler in the kit is a later version than
the OSF Motif V1.1 compiler. The changes should be
transparent to users.
___________________________
2.3 Callable UIL
If you want to use callable UIL, you will need to do
the following:
VMS
1 Link the library
21
You can find the library in the following location:
SYS$COMMON:[DECW$MOTIF.CLIENTS.UIL]UIL.OLB
ULTRIX
1 Link the library.
You can find the library in the following location:
/usr/lib/DXM/clients/uil:libUil.a
2 You may also need to link Mrm.
You can find Mrm in the following location:
/usr/lib/DXM/lib/Mrm:libMrm.a
For more information on using callable UIL, see the
OSF/Motif Programmer's Reference.
___________________________
2.4 DECwindows/Motif Mrm (DRM)
The following routines and macros which were available
in DECwindows DRM have been superseded in Motif MRM:
Routines:
DwtDrmHGetIndexedLiteral
DwtDrmGetIndexedLiteral
DwtDrmGetResourceContext
DwtDrmResizeResourceContext
DwtDrmFreeResourceContext
Macros:
22
UrmRCBuffer
UrmRCSize
UrmRCGroup
UrmRCType
UrmRCAccess
UrmRCLock
UrmRCErrRpt
UrmRCErrCod
UrmRCErrStg
UrmRCSetSize
UrmRCSetGroup
UrmRCSetType
UrmRCSetAccess
UrmRCSetLock
UrmRCSetErrRpt
These routines were provided with DECwindows V1.0 in
order to allow applications to fetch literals from UID
files.
In DECwindows V2.0, the following new routines were
added to simplify fetching literals from UID files:
DwtFetchLiteral
DwtFetchIconLiteral
DwtFetchColorLiteral
In Motif V1.1, only the Motif equivalents of the
simpler fetch literal routines are available:
MrmFetchLiteral
MrmFetchIconLiteral
MrmFetchColorLiteral
Note that for MrmFetchLiteral the display parameter is
only used when fetching font or fontlist literals, and
may safely be NULL if the literal is any other type.
23
V1.0 DECwindows applications would typically have used
code similar to the following to retrieve literals:
DwtDrmGetResourceContext(
NULL, /* Allocation routine */
NULL, /* Deallocation routine */
100, /* Size of buffer */
& resource_ctx); /* Address of resource context */
DwtDrmHGetIndexedLiteral(
hierarchy_id, /* UID hierarchy id */
index, /* UIL name of literal */
resource_ctx); /* Resource context */
value = DwtDrmRCBuffer (resource_ctx);
/* Value is pointer to the actual literal value to */
/* be retrieved */
DwtDrmFreeResourceContext(
resource_ctx); /* Resource context */
/* Context should be freed AFTER value no longer */
/* needed */
Applications can perform the same function by simply
using one of the following routines:
/* To fetch non-icon or color literals */
MrmFetchLiteral (
hierarchy_id, /* UID hierarchy id */
index, /* UIL name of literal */
display, /* pointer to the display */
value_return, /* pointer to actual literal value */
type_return); /* MRM code of type of return value */
/* To fetch icon literals */
24
MrmFetchIconLiteral (
hierarchy_id, /* UID hierarchy id */
index, /* UIL name of literal */
screen, /* pointer to the screen */
display, /* pointer to the display */
fgpix, /* foreground pixel */
bgpix, /* background pixel */
value_return); /* pointer to pixmap value */
/* To fetch color literals */
MrmFetchColorLiteral (
hierarchy_id, /* UID hierarchy id */
index, /* UIL name of literal */
display, /* pointer to the display */
cmap, /* color map */
value_return); /* pointer to pixel value */
___________________________
2.5 DECwindows/Motif Intrinsics
The Intrinsics included with the DECwindows Developer
kit for OSF/Motif includes the latest updates to
the MIT X11 R4 Intrinsics. The R4 Intrinsics are
NOT compatible with the Intrinsics included with the
DECwindows XUI toolkit. You must compile and link with
the Motif Intrinsics provided with this kit.
On both ULTRIX on VAX and RISC systems, the filenames
for the application-specific xdefaults files are named
differently than under XUI. With XUI, the files were
normally stored in the user's home directory with the
filename comprised of a period followed by the class
name. For an application such as clock, the file would
be something like:
/usr/users/fred/.DXclock
25
Under Motif, the system-wide application defaults
file, which is read-only, are in
/usr/lib/X11/app-defaults
For the application default files which you can
modify, the leading period has been removed under
Motif. This is to conform with MIT R4 (MIT X Window
Intrinsics Revision 4). The Motif file would be
something like:
/usr/users/fred/DXclock
__________________________________________________________________
3 Differences Between XUI and DECwindows/Motif Widgets
The following sections outline a few difficulties
associated with moving an application, or user, from
DECwindows to Motif.
___________________________
3.1 Text Editing
The Motif text widget editing bindings conform to
Version 1.1 of the Motif Style Guide. If you want to
use the editing bindings of the XUI Style Guide, you
can add the following lines to your Xdefaults file:
*XmText.translations: #override\
Shift<>F12: end-of-line()\n\
~Shift<>F12: beginning-of-line()\n\
Shift<>Delete: delete-next-character()\n\
~Shift<>Delete: delete-previous-character()\n\
Shift<>F13: delete-next-word()\n\
~Shift<>F13: delete-previous-word()\n\
26
_____________________
3.1.1 Bit Gravity
The default bit gravity for a number of the widgets
has changed. In XUI the default was 'Forget', in some
cases this has changed to 'NorthWest'. This may result
in missing "expose" events when windows are resized to
be smaller.
_____________________
3.1.2 Keyboard Accelerators
The OSF Motif toolkit only allows you to place
keyboard accelerators on direct children of a
RowColumn class widget. In addition, the RowColumn
parent must be a popup or pulldown type. Setting
accelerators in other situations is silently ignored.
_____________________
3.1.3 RowColumn (Menu) Widget
The callback structure that a row column widget uses
when executing the entry callback has had the member
field names changed. The 's__mumble' fields have been
changed to just 'mumble'.
The Motif popup menu widget defaults to being
controlled by MB3 (mouse button 3), rather than by
MB2 as in DECwindows. You can reset control to MB2 by
using the XmNwhichButton as in
XtSetArg (al[ac], XmNwhichButton, 2); /* default = 3 */
Also note that the vertical and horizontal offsets,
used in DECwindows to cause popup menus to appear
with the last selection under the cursor, are not a
feature of Motif. Popup menus will always appear with
the upper left corner under the cursor unless they
would appear off the display, in which case the menu
is moved onto the display.
Motif menu bar widgets only allow children of class
cascade button widget; no gadgets are allowed.
27
_____________________
3.1.4 Scale Widget
Some of the default values for the scale widget have
changed from the XUI toolkit to the DECwindows/ Motif
toolkit. The defaults are:
XmNorientation: XUI - horizontal
Motif - vertical
XmNprocessingDirection: XUI - left to right
Motif - right to left
XmNshowValue: XUI - true
Motif - false
The behavior of the widget has also changed in
that clicking in the trough in XUI produced a value
proportional to where you clicked. In DECwindows/Motif
this increases/decreases the current value.
Also, when a scale widget is positioned within a
bulletin board dialog box, the default for the space
that shows the value above the widgets is too small.
It causes the scale widget to overlay the buttons
below it.
_____________________
3.1.5 Toggle Button Widget
The name of the field member of the callback data
structure that a toggle button widget/gadget uses has
been changed from "value" to "set." The porting tools
do not deal with this transformation.
_____________________
3.1.6 Bulletin Board Font Units
The Motif toolkit font units are not, by default,
equivalent to the XUI font units. To achieve nearly
the same font units, see the OSF Porting Guide.
28
_____________________
3.1.7 Help Widget
Motif contains an equivalent of every XUI V1.0
widget except for the Help widget. This release
includes a help widget with the same functionality
of the XUI V2.0 Help widget. Use the XUI Help Widget
documentation along with the following notes:
1 Include the file DXmHelpB.h in your application.
2 All Help widget resource names begin with DXmN
instead of DwtN (for example DwtNfirstTopic is
DXmNfirstTopic).
3 The Help widget resource DwtNfont has been
replaced by the Xm resources XmNlabelFontList
and XmNbuttonFontList. The Help widget resource
DwtNhelpFont has been replaced by the Xm resource
XmNtextFontList. You cannot change these resources
by using XtSetValues.
4 The Help widget resource DwtNdirectionRToL has been
replaced by the Xm resource XmNstringDirection.
_____________________
3.1.8 XmString Resources
Some, but not all, XmString resources need to be
freed after a call to XtGetValues. This is because
the toolkit generates the external format string in
a set-values hook, and there is no place where the
toolkit can free this. The application must do it.
The following list of XmString resources need to be
freed after being fetched using XtGetValues:
Command Box
XmNpromptString, XmNcommand
File Selection Box
XmNfilterLabelString, XmNdirMask, XmNdirSpec
Label
XmNlabelString, XmNacceleratorText
29
Label Gadget
XmNlabelString, XmNacceleratorText
Message Box
XmNmessageString, XmNokLabelString, XmNcancelLabelString,
XmNhelpLabelString
Selection Box
XmNselectionLabelString, XmNlistLabelString, XmNtextString,
XmNokLabelString, XmNapplyLabelString, XmNcancelLabelString,
XmNhelpLabelString
The following XmString resources DO NOT need to be
freed:
Bulletin Board
XmNdialogTitle
Row Column
XmNlabelString
Scale
XmNtitleString
Help
All XmString resources
___________________________
3.2 User-Defined Widgets
User-written widgets layered on top of DwtCommon are
converted by the filters to use XmPrimitive. However,
the number and type of the fields within the DwtCommon
and XmPrimitive class record are different, and you
must change the class record initalization.
Here's the original code fragment:
30
...
{ /* dwt common class */
/* Pad0 */ _XtInherit,
/* Pad1 */ _XtInherit,
/* Pad2 */ _XtInherit,
/* extension */ NULL,
},
...
and here's the new code
...
{ /* XmPrimitive class */
/* XtWidgetProc border_highlight */ NULL,
/* XtWidgetProc border_unhighlight */ NULL,
/* XtTranslations translations */ NULL,
/* XtActionProc arm_and_activate */ NULL,
/* XmGetValueResource * get_resources */ NULL,
/* int num_get_resources */ NULL,
/* caddr_t extension */ NULL,
},
...
__________________________________________________________________
4 Interoperability of XUI and Motif
Digital does not guarantee that this kit is
interoperable with the current XUI version of the
DECwindows toolkit. Although XUI applications should
work under the Motif window manager and vice versa,
there is no commitment that it will work.
Motif application widgets which are 'modal' will not
be 'modal' when run with an XUI window manager. It is
possible to get an application into the state where
application shell windows are unmapped from the window
manager window. Such application shell windows are
displayed as transparent.
31
__________________________________________________________________
5 Porting Tools, XUI to DECwindows/Motif
The kit contains a set of filters which convert
original XUI files to DECMotif files. You should apply
these filters before attempting to compile any source
against DECwindows/Motif.
___________________________
5.1 How The Filters Work
The filters replace all instances of the old names in
the code. Occurrences in quoted strings and comments
are also modified.
Filtering is done in several passes. Each filter can
be executed independently of the other filters; there
are no dependancies between the filters.
The filters work by replacing names in the input
source file with the DECwindows/Motif names. In many
cases, there is a direct translation from XUI names to
DECwindows/Motif names. These translations are made in
the input source without comment by the filter.
Some XUI names have no direct translation in DECMotif.
The filters attempt to make the "best" translation
possible, however, the application developer must
review these changes and judge what is best for the
application.
In most cases the filters are insensitive to the
programming language that the input is coded in; note
however, that the transformations are only designed to
work correctly with 'C' and .UIL files.
One of the filters translates high level XUI
subroutine calls to Motif low level creation calls.
This filter writes new low level code directly into
the input source file. Application developers must
look at these sequences because the translation will
not be syntactically correct.
32
The sections of code that the developers should
evaluate are flagged with marking strings:
>>>Developer decision:
>>>Mapping unknown:
>>>Mapping unsupported for this symbol:
>>>Future feature:
>>>Motif Transition: Routine conversion
The original section of code is left in the source,
but is surrounded by the condition ORIGINAL__CODE.
The flagged section of code immediately follows the
marking string and is surrounded by braces. An example
of a translated section of code:
#ifdef ORIGINAL_CODE
DwtSetArg("TRUE",arglist,0,XtNallowShellResize)
#endif
>>>Motif Transition : Routine conversion
XtSetArg(arglist[0],XtNallowShellResize,"TRUE")
___________________________
5.2 Marking Strings Definitions
The following sections discuss marking strings
definitions.
_____________________
5.2.1 Developer decision
Developers should be aware that functionality for this
section of code has changed; they must judge whether
the new functionality is appropriate. Some examples
of decisions: there are two types of modality for
dialog boxes in DECMotif; applications that contained
modal dialog boxes will need to choose between them.
Another example: some subroutine have more parameters
than there were in XUI entry points. The filters will
suggest values for the new parameters.
33
_____________________
5.2.2 Mapping unknown
There is no comparable DECMotif name. The developer
will need to determine what to do; the filter cannot
suggest any action.
_____________________
5.2.3 Mapping unsupported for this symbol
The symbol is most likely one that is not documented
for the XUI toolkit.
_____________________
5.2.4 Future feature
Digital intends to provide this functionality in
the Motif toolkit at a later time. We suggest you
conditionally compile this section; since a later
baselevel may provide it.
_____________________
5.2.5 Motif Transition
In translating from XUI to DECMotif, we needed to
rearrange parameters, generate a new one, or perform
some other action. This translation is most likely
correct and will work the same as it did in XUI, but
you should be aware that there have been changes.
___________________________
5.3 The Filters
DXm_port_call - transforms callbacks
DXm_port_resources - transforms toolkit resource names
DXM_port_lolevels - transforms low-level entry point names
DXm_port_hilevels - replaces hi-level entry points with low level
DXm_port_class - transforms toolkit class structure names
DXm_port_includes - transforms toolkit include file names
DXm_port_data - transforms toolkit data types
DXm_port_drm - transforms Drm entry points
DXm_port_uil - transforms UIL source
A wrapper is supplied which will execute all filters
on either a single file or a directory of files.
34
_____________________
5.3.1 Running the filters on VMS
A command file, DXM__PORT.COM, in the tools
subdirectory allows you to convert a single file or
a directory of files. It runs all the filters on the
input source.
The command
$ @DECW$MOTIF$TOOLS:DXM_PORT INPUT_DIR OUTPUT_DIR
will convert all .c, .h and .uil files in the
input directory and place the results in the output
directory.
The command
$ @DECW$MOTIF$TOOLS:DXM_PORT FOO.C NEW_FOO.C
will run all the filters on the single file foo.c
producing the file new__foo.c
An optional third parameter of "log" will create
a running commentary of the process of the
transformation.
It is possible to run individual filters directly.
Each filter expects the input to be sys$input and
writes output to sys$output. For example
$ DEFINE/USER SYS$INPUT FOO.C
$ DEFINE/USER SYS$OUTPUT NEW_FOO.C
$ RUN DECW$MOTIF$TOOLS:DXM_PORT_INCLUDES
will run only the include filter on the file foo.c
producing new__foo.c.
35
___________________________
5.4 Running the filters on ULTRIX
A script file, DXm__port, in the tools/filter
subdirectory allows you to pass an entire directory
through all of the filters with a single command:
> DXm_port source_directory
The script will filter all *.c, *.h, and *.uil files
in the source directory. The output files will have
a '.dec' appended. For example, the output from
filtering main.c is named main.c.dec.
It is possible to run individual filters directly.
Each filter expects the input to be stdin and writes
output to stdout. For example
> DXm_port_includes <foo.c >foo.c.dec
will run only the include filter on the file foo.c
producing foo.c.dec
__________________________________________________________________
6 Kit Contents
Complete listings of the files included with the
VMS and ULTRIX kits are included in the appropriate
installation guides.
___________________________
6.1 VMS
The following sections discuss logicals, compilation,
and libraries for VMS.
36
_____________________
6.1.1 Logicals
The following logicals are useful for accessing the
various directories when using the kit:
DECW$MOTIF$DEMO: - various demonstration programs
DECW$MOTIF$MWM: - Motif window manager (MWM)
DECW$MOTIF$UIL: - UIL compiler
DECW$MOTIF$XT: - Intrinsics (Xt)
Xt: " (for ULTRIX compatability)
X11: " (for ULTRIX compatability)
DECW$MOTIF$XM: - Motif widget set (Xm)
Xm: " (for ULTRIX compatability)
DECW$MOTIF$MRM: - Motif Resource Manager (Mrm)
Mrm: " (for ULTRIX compatability)
DECW$MOTIF$DXM: - Digital extensions to Motif (DXm)
DXm: " (for ULTRIX compatability)
DECW$MOTIF$TOOLS: - XUI to Motif porting tools
For compatability between ULTRIX and VMS, it is
recommended that ULTRIX "#includes" are used in C
source programs; for example:
#include <X11/Intrinsic.h>
will include the file "Intrinsic.h" from the directory
which the logical "X11" points to.
Executing the
file SYS$COMMON:[DECW$MOTIF]DXM__LOGICALS.COM will
define these logicals.
_____________________
6.1.2 Compilation
You should compile applications as usual after running
the DXM__LOGICALS.COM file. The logical C$INCLUDE will
be extended to allow searching of the Motif toolkit
for include files.
37
Use following commands to run the kit's UIL compiler:
$ UIL/Motif fname.uil
_____________________
6.1.3 Libraries
The shareable images used when linking Motif
applications are found in the appropriate
subdirectories under SYS$COMMON:[DECW$MOTIF].
A linker options file which specifies these
shareable images and other appropriate options may
be included when linking by specifying the file
SYS$COMMON:[DECW$MOTIF]DXM_LINK.OPT with the linker
/OPTIONS qualifier.
XT:DECW$MOTIF$XTSHR.EXE - Xt (intrinsics) library
XM:DECW$MOTIF$XMSHR.EXE - Xm (Motif widgets) and
Mrm (Motif resource manager) library
DXM:DECW$MOTIF$DXMSHR.EXE - DXm (Digital extended Motif) library
___________________________
6.2 ULTRIX (VAX and RISC)
The following sections provide a road map, and
information on compiling and libraries.
_____________________
6.2.1 Road Map
The kit consists of a tree which is similar to
the tree supplied by OSF. It has the following
directories:
38
demos/ - various demonstration programs
doc/ - documentation (this file)
clients/mwm/ - Motif window manager (MWM)
clients/uil/ - UIL compiler
lib/Xt/ - Intrinsics (Xt)
lib/Xt/X11/ - Intrinsics include files
lib/Xm/ - Motif widget set (Xm)
lib/Mrm/ - Motif Resource Manager (Mrm)
lib/DXm/ - Digital extensions to Motif (DXm)
tools/filters - XUI to Motif porting tools
_____________________
6.2.2 Compilation
Applications must be compiled with command line
switches to allow include files to be found. For
example, for a RISC ULTRIX system, the following
should be used as a cc command:
cc foo.c -I/usr/lib/DXM/lib/Xt/X11 -I/usr/lib/DXM/lib/Xm \
-I/usr/lib/DXM/lib/Mrm -I/usr/lib/DXM/lib/DXm
To run the UIL compiler, type the following command:
For ULTRIX on RISC Systems:
/usr/lib/DXM/clients/uil/uil foo.uil
For ULTRIX on VAX Systems:
/usr/lib/DXV/clients/uil/uil foo.uil
_____________________
6.2.3 Libraries
When linking the following libraries will be needed:
For ULTRIX on RISC Systems:
/usr/lib/DXM/lib/Xt/libXt.a
/usr/lib/DXM/lib/Xm/libXm.a
/usr/lib/DXM/lib/DXm/libDXm.a
/usr/lib/DXM/lib/Mrm/libMrm.a
39
For ULTRIX on VAX Systems:
/usr/lib/DXV/lib/Xt/libXt.a
/usr/lib/DXV/lib/Xm/libXm.a
/usr/lib/DXV/lib/DXm/libDXm.a
/usr/lib/DXV/lib/Mrm/libMrm.a
__________________________________________________________________
7 Information on ULTRIX
The OSF/Motif documentation (other than the
installation guide) describes how to use DECwindows
Developer Kit for OSF/Motif as it runs on an ULTRIX
operating system. For those of you who are running
the product on a VMS operating system, we have
provided a short document, "Instant ULTRIX," with the
installation kit.
You can find this document in the following location:
SYS$COMMON:[DECW$MOTIF.DOCS]ULTRIX.ps
SYS$COMMON:[DECW$MOTIF.DOCS]ULTRIX.ln3
If you would like further information concerning the
similarities and differences between Unix and VMS, you
may want to purchase the following:
Unix for VMS Users
by Philip E. Bourne
Digital Press, 1990
Order number EY-C177E-DP
40
__________________________________________________________________
8 Bug Report Summary
This section contains a summary of known bugs in
OSF/Motif 1.1.
In the tables, the PIR entry is the number assigned
to the bug report in OSF's bug-tracking database. The
Region entry is the major area within OSF/Motif where
the bug is suspected to reside. The Status entry uses
the following codes:
P Posted, new to the buglist. Still needs to be
evaluated, assigned, and fixed or closed.
I Under investigation. Usually, a bug in this
category is doubted; a tester is assigned to
verify that the bug can still be reproduced.
Most bugs of status I after investigation are
found to have been already fixed.
A Assigned. An engineer has been assigned to
fix this bug. Since bugs are fixed based on
priority, some bugs may remain assigned for
some time. Fixes for assigned bugs that are
made between major releases are often sent out
as patches.
D Deferred. Bugs are usually deferred for one of
two reasons: they require extensive work that
was no longer possible by the time they were
discovered, or they are considered relatively
unimportant. Deferred bugs are reviewed at
the beginning of each release cycle. Some are
incorporated into the plan for new work; the
remainder are closed.
41
Table_2__Known_Bugs_in_Motif_1.1_______________________
PIR_____SeverityStatus__Region__Bug_Description________
1444 Fatal D XM Setting
XmNinsertPosition
leads to SEGV in
Xt/Composite.c in
CompositeInsertChild
if compiled with cc
-O. Bug in optimizer.
1664 Fatal A Managers do not keep
correct selection
state on destroys, if
a button is destroyed
while mouse button is
still down.
1670 Fatal A XM CascadeBG child
of non-row column
parent segs when
you click MB1 on the
button. Warnings were
displayed earlier.
1746 Fatal A XM RowColumn geometry
management is
incorrect (I have a
test) Setting margin
width 1 can cause
XProtocol Error.
1842 Fatal P XM Xm/TextIn.c:
RemoveToEndOfLine (^k)
can corrupt memory.
42
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
712 CriticalA XM Possible to have
no radio buttons
depressed, or more
than one.
813 CriticalD XM Arrow button which is
child of a row column
only grows larger and
does not shrink when
resized. Same problem
with scale.
886 CriticalA XM Creating lots of
dialog shells and
destroying them
highlights a memory
leak.
1044 CriticalD MWM The default behavior,
keyboard traversing
to a icon in explicit
mode should popup the
window menu. This is
PM behavior.
1074 CriticalA XM List widget checks
to see if its parents
class is ScrolledWind
and not if its parent
is a subclass of
scrolled window.
1094 CriticalA XM selectedItemCount not
set on double click
43
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1116 CriticalA XM In a multiline text
widget, drag selecting
(Btn1Drag) off the
bottom of the text
area should scroll the
text.
1317 CriticalD UIL Should be able to
use widget name as
parameter to its or
parent's or child's
callback routine.
1391 CriticalD MWM Expose event bug when
raising overlapping
secondary windows.
Other windows redraw
unneccessarily
1396 CriticalD MWM OSF virtual key
bindings should work
in .mwmrc. Also,
the default Mwm key
bindings should use
osfMenu instead of F4.
1547 CriticalA XM Redisplay routines
need to check if
widget is being_
destroyed before
redrawing, with
potentially fatal
results!
44
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1638 CriticalA XM The text cursor
flashes (i.e. quickly
changes from a caret
to a I-beam) or just
disappears when typing
in text.
1650 CriticalA XM In a 2-D menu,
arrowLeft and Right do
NextMenu and PrevMenu
instead of traversing
left or right within
the 2D menu.
1669 CriticalD XM Arrow Button Gadget
should grey when it
becomes insensitive.
1697 CriticalA XM I've ArrowButtons
under RowColumn
widget & I'm clicking
MB1 in entryBorder
region..activates
AB visually by no
activation CBs.
1721 CriticalA RowColumn adds
entryBorder to its
children widget's
window, instead
of modifying its
children's border!
45
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1761 CriticalI XM Text widget does
not always process
pastes from other text
widgets properly.
1778 CriticalA XM XmToggleButton does
not work correctly
if XmNlabelPixmap and
XmNselectPixmap are
different sizes.
1787 CriticalA These managers do not
search up ancestors
for help callback:
BulletinB, MessageB,
SelectionB, FileSB.
1802 CriticalA XM Text actions with new
extended arguments
don't actually handle
those arguments.
1805 CriticalA XM When mwm runs on the
overlay screen on
the HP, it does not
set the bottom shadow
color to black. Leaves
it as background.
1811 CriticalA XM List does not
refreshing screen
right. See testing
program in report_
p....
46
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1843 CriticalP XM List size doesn't
change when visible
count is modified.
1860 CriticalA MRM Pointer returned to
the function is a
pointer to an int,
rather than a struct,
so there are no
meaningful contents
to use.
1865 CriticalP Text in multi-edit
seg faults or gives X
proto error.
1866 CriticalP MWM Mwm gets confused
when interacting with
large point fonts. In
PanedWin4 it causes
the application to not
fully initialize.
1869 CriticalP Geometry requests are
repeatedly/unnecessarily
made.
635 Severe D DOC Translations by
default are not
null; They are really
dynamic, set in widget
code at create time.
47
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
654 Severe A XM/XT Popup menu entries
should be selective
withH BTN1 when posted
by F4. Style Guide
conformance issue.
684 Severe A XM The XmNcursorPosition
resource cannot be set
simultaneously with
XmNvalue on the XmText
widget.
776 Severe D MRM MrmCloseHierarhy seems
to not free all memory
all the time, very
random failures.
779 Severe D MRM When MrmOpenHierarchy
fails, it should free
all the memory used
so far for the open,
loop test shows random
failure.
836 Severe A XM Can't set Scrolled
Window's margin width
after creation.
855 Severe A DOC Document that users
must free memory
used by XmString
resource after call
to XtGetValues.
48
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
936 Severe I XM On machines with small
static colormaps , the
Motif color selection
routines can return
same colors for forg,
backg, bord.
943 Severe D MWM The property field
flags returns a 0
which is not a valid
return value.
1105 Severe D XM Shadow colors
improperly generated
when pixmap provided.
1117 Severe A MWM If an icon is dragged
to the edge of the
icon box, the icon box
should scroll in the
dragged direction.
1121 Severe A XM Double clicking on a
menu item can cause
multiple callbacks
i.e. menu doesn't
unpost before second
click.
49
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1129 Severe D XM With patch 108 to fix
PIR 943, other sashes
move slightly when one
sash is moved, with R4
server and 1.0 Motif.
1.1 ok.
1138 Severe P XM Unmanaging and
remanaging a gadget
in a DA widget, causes
several exposes to the
gadget when remanaged.
1139 Severe D XM When changing the
background color
of the parent of
a push button
gadget, armColor and
shadowColor do not
change.
1221 Severe A XM In a vertical scale
with a large shadow
thickness (8), slider
erases portion of
shadows, redrawn if
expose occurs.
1305 Severe A XM Any read-only string
of the form static
char blahblah[] =
" "; should use the
"const" keyword to
save memory.
50
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1308 Severe A TESTS (HP CISlx02636)
TestSuite: declares
wait var which
overrides wait().
1324 Severe D MWM Setting
mwm*passButtons should
not pass buttons to
windows oth er than
the one in which the
original button was
pressed.
1339 Severe D XM Color cache is only
looking at pixels
values, should be
looking at RGB values.
1348 Severe D XM Text Primary selection
should respond to,
and provide text in
COMPOUND_TEXT format.
1359 Severe D MWM Framing box is not
always visible - i.e.
black frame on black
background. Should
adapt itself to black
bkgd: be white.
51
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1438 Severe P XM SelectionBox
subclasses use a long
default, UNSPECIFIED,
for both integers
and XmStrings. See
attached file.
1463 Severe D TESTS Write a Xdefaults/app-
defaults test suite.
1464 Severe A TESTS Investigate how List
and Text calculate
their initial size.
1465 Severe A TESTS Complete XmString test
suite.
1467 Severe A TESTS Write test suite
for Resolution
Independence code.
1468 Severe A TESTS Write tests for Pixmap
Pathnames, as detailed
in 1.1 spec and later
mail. Use NL test
approach?
1469 Severe A TESTS Add a more
comprehensive set
of tests for Drawing
Area.
1471 Severe A TESTS Add tests for resource
converters.
52
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1472 Severe A TESTS Write a suite of tests
for SimpleCreate and
VA routines.
1510 Severe A XM When setting sensitive
to False, the
ScrollBar should
become grayed out.
1591 Severe D XM Navigation within
forms is inconsistent.
When a bttn is
destroyed the next
is different than the
TAB.would
1597 Severe P XM The messageString
in a MessageBox is
being indented and
does not line up with
the beggining of the
pushbuttons.
1599 Severe D UIL Assigning an
identifier as an
element in an integer
list generates a UIL
compile-time error.
1618 Severe A XM Attempt to compare
semantically identical
strings using
Xmstringcompare yield
incorrect result.
53
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1651 Severe A MWM There are several bugs
in the Icon Box focus
policy and scroll
window.
1675 Severe A Margin/thickness
requests can cause
label to be mis-
placed.
1677 Severe A XM List doesn't calculate
geometry when font or
spacing changes this
doesn't update the
scrollbar properly.
1680 Severe A XM Toggle buttons in Form
have the wrong height.
See periodic.
1683 Severe A XM Menus within a MenuBar
should always be able
to be traversed no
matter if there are
specific call to
XmAddTabGroup().
1691 Severe A XM/XT Because primary modal
dialogs flush the
grab list when they
are unposted, can
get warnings when 2+
primary modals used.
54
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1694 Severe D XM When specifing a
width and height to
a MessageBox (any),
Prompt or SelectioBox
Dialogs,width and
height are not
honored.
1703 Severe A XM Resource classes and
types don't agree
between code and
documentation.
1705 Severe A MWM Iconbox should support
PageUp and PageDown
when location cursor
is in the icon, and
paging should provide
overlap.
1719 Severe A XM Clipboard ICCCM
INCREMENTAL copies
can occasionally
fail, depending on
how application is
coded.
1720 Severe A XM AddInternalElement
does not always
increment LastItem.
Could possibly cause
item to be inserted in
wrong position.
55
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1725 Severe A UIL SINGLE_FLOAT types
are not type converted
properly in arithmetic
expressions or as
arguments to other
functions.
1732 Severe A TESTS There are still some
functions not called
from the testsuite.
1739 Severe A XmProcessTraversal
does not work
correctly when only
child of Shell is
destroyed, restored,
focus set to it.
1741 Severe A XM Clicking in a ToggleB
border toggles visual,
but not internal
state. ValueChanged
callback is not
called.
1772 Severe A XM valueChanged callback
being called begore
modifyVerify callback.
56
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1782 Severe A XM Widgets pass NULL as
first parameter of
XtCallCallbackList.
Should be a widget
pointer. Will be a
problem with R5.
1786 Severe A XM Should UngrabButton
when pop down a popup
a popup menu.
1788 Severe A MWM Mwm built the standard
way loses cursors.
Cannot be built
without -DLARGECURSORS
bz of Digital server
bug.
1792 Severe A Drawing Area calls
input callback when
gadgets have focus.
1797 Severe A XM The RowColumn's entry
class is of the wrong
type.
1808 Severe A XM When posting a
Option Menu which
has children with
accelerator text, the
posted pushbutton will
not appear raised.
57
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1810 Severe A XM Text widget selects
bad colors for text
cursor.
1819 Severe P XM Enhanced highlight
thickness is refreshed
using Button's color
instead of parent's.
1821 Severe P XM If a menu bar uses
shared menu panes,
NextMenu and PrevMenu
when a shared pane is
posted, don't work as
expected.
1822 Severe P XM Menu bar with wide
border (>=26) or very
long label (2/95)
displays as tiny box
instead of long menu
bar.
1828 Severe P XM Doing XtGetValues for
XmNscaleMultiple gives
incorrect values like,
64285720, 44000000,
etc. Expected value is
something nea.
58
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1830 Severe P XM When attaching widgets
to a form (which is
a child of an app
shell) the widgets are
attached to the inner
shadow not outer.
1832 Severe P XM Scale does not resize
by itself event though
its Lable and value
are longer than its
size at create time.
Creating scale.
1837 Severe P XM On a monochrome system
(pmin) when a list
is in ADD mode, the
highlight should be a
dashed box, it is not.
1846 Severe P DEMOS When Motifburint is
used with hebrew or
kanji, the list box
that shows the order
is initally highlighed
incorrectly.
1850 Severe P XM When changing unitType
via a SetValues call,
the width and height
of the widget are
not update to the new
type.
59
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1851 Severe P XM If a menu mnemonic
is the same as the
menmonic of the
posting cascade
button, it cancels
the post, doesn't
activate.
1852 Severe P BeginLine & EndLine
give reversed
callbacks.
1853 Severe P XM Setting
XmNwidth/XmNheight
may have no effect if
XmNunit_type is set to
Xm100TH_MILLIMETERS.
1856 Severe P XM Secondary selection
doesn't automatically
scroll on multiline
text widgets.
1858 Severe P XM After a double click
on a word, shift
left/right extends
by words, and can only
go in one direction.
1859 Severe P XM KSelect/Ctrl-KSelect
does not grab
ownership of the
primary selection.
60
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1861 Severe P XM in a pushbutton
gadget, a double click
with a release outside
of the pushbutton
leaves the pushbutton
armed (pressed in).
1862 Severe P XM When overriding
<BTN1DOWN> and
<BTN1UP> on a
messageBox, a double
click should activate
once. Default button
does not.
1864 Severe P XM On an HP ONLY, when
unitType is set at
1000TH_INCHES or
100TH MILLIMETERS,
the widget does not
display with correct
size.
1867 Severe P XM If I create RadioBox
with numColumns=1 &
packing=pack tight
then it displays all
children that can be
displayed in 1 col.
61
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1868 Severe P XM Cut a selection via
button. Paste in text
widget using MB2. The
terminating null of
selection is displayed
as garbage char.
1870 Severe P XM In a Text widget,
if you use osfCut to
cut a string to the
clipboard and editable
is set at false the
string IS cut.
1875 Severe P XM MenuBar resizes to
accommodate its small
child (CascadeButton
widget) but does not
redraw top & bottom
shadow correctly.
1876 Severe P XM If a client is
f.kill'd while it
has a lock on the
clipboard, the lock
is not removed and
clipboard calls can
fail.
887 ImportanA XM LabelGadget's label
appears with the top
and bottom bits of the
words chopped off.
62
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1098 ImportanD XM Setting
acceleratorText
resource to null does
not shrink button
size.
1188 ImportanA Motif type
XmMultiClick is
not defined in Xm.h
even though they are
mentioned in the AES.
1202 ImportanA XM Mangers should
draw the border
around their gadget
children. Try setting
XmNentryBorder on RC
with PBGad children.
1368 ImportanA XM when unmanaging a
button the cursor will
default to another
unexpected button.
1411 ImportanA XM Changing label string
corrupts pushbutton
display, for gadget
or widget when
defaultButton exists.
1446 ImportanA UIL UIL demos do not
compile on HP s800
63
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1470 ImportanA TESTS Add a test(s) for
XMGetVisualPixmap.
1488 ImportanD XM When XmNsensitive is
set to False in any
Text or TextField
widget, the widget
should become grayed.
1581 ImportanA XM When fractionBase
is modified via
SetValues, the form
doesn't ask or get
right resize from its
shell; un/re/realize
fixes it.
1596 ImportanA XM All the boxgetchild
functions have the
second argument
being unsigned
chars except for
xmselectionboxgetchild
which is int.
1654 ImportanA XM Separator SetValues
doesn't recalculate
width and height when
shadow or highlight
thickness changes.
64
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1655 ImportanA XM XmUnhighlightBorder
and XmHighlightBorder
don't set/reset
highlighted flag if
highlight_thickness is
0.
1674 ImportanA XM Highlight is left
behind if panes are
resized so small
buttons aren't
visible, then buttons
activated which sets
them insens.
1682 ImportanA XM Overriding a
translation for
a PushButton or a
Togglebutton does a
replace instead of an
override.
1684 ImportanA XM SetValues of
XmNuseAsyncGeometry
doesn't reset
XmNwaitForWm or
XmNwmTimeout.
1685 ImportanA XM Automatic selection
makes sense in
"browse" and "extened"
mode when using mouse.
It should not have any
affect on KB nav.
65
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1688 ImportanA XM adding or deleting
xmlist entries while
list is in use will
result in selection
(highlight) of extra
item.
1692 ImportanD MWM Color control/support
in the icon box is
limited and confusing.
1700 ImportanA XM Narrow Scrollbars draw
slider badly.
1717 ImportanA XM doesn't unmanage
its separator
when children are
unmanaged.
1728 ImportanI XM Xm demos compiled on
the HP s800 dump core
1748 ImportanD MWM When app with 2
toplevel windows quits
via exit(0), no other
window is given the
focus. Alt<KEY>Tab
moves you somewhere.
1780 ImportanA XmNmessageString
should be NULL, but
is set to 'message'.
1789 ImportanA DEMOS Needs a README.
66
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1799 ImportanA XM Too much space left
for PBs in menu when
it also contains a
separator.
1803 ImportanA TESTS when re-running mwm
the placement of the
windows is off from
where it used to be.
1818 ImportanP XM ShadowThickness
dose not work in
separator widget using
SetValues.
1823 ImportanP XM Some combinations
cause test to appear
with menu bar border
slightly clipped on
bottom or right.
1824 ImportanP XM Widget attached to
form is attached
to outside of
its shadow, ugly.
Workaround: offset
all ATTACH_FORMs by
shadowThickness.
67
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1827 ImportanP XM At create time XmScale
displays scrollbar &
label and after few
seconds it clears the
label and redisplays
it again!
1835 ImportanP XM When max/min or
size of children
are changed, then a
sash is dragged, the
sash often highlights
and stays that way
wrongly.
1836 ImportanP XM If PanedWin is managed
before its children,
it doesn't end up the
correct size after all
children are managed.
1840 ImportanP XM XmDIALOG_APPLICATION_
MODAL should be same
as XmDIALOG_FULL_
APPLICATION_MODAL
(Page 3).
1844 ImportanP XM When rotation speed
set to 0, there is no
refresh from expose
events.
68
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1845 ImportanP XM In Xm.h XmDIALOG_
APPLICATION_MODAL
should be defined
as XmDIALOG_FULL_
APPLICATION_MODAL.
1847 ImportanP XM Arrow button doesn't
get enough space
in RowColumn to be
visible, when space
is tight due to size
setting of shell, mgr.
1854 ImportanA XM In 1.1, focus cycles
through explicit
(XmAddTabGroup)
controls when a non-
TabGroup control is
clicked. Didn't cycle
in 1.0.
1857 ImportanP XM The end data action
(end-of-file) on
a single line text
widget jumps to the
character after the
last character.
1863 ImportanP BUILD Please add static to
the char * getcwd()
declaration in
Xm.h so it doesn't
conflict with our bsd
emulation.
69
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1874 ImportanP XM Forward-word to the
end of file stops one
character short of the
end.
431 Minor A MWM Icon image is redrawn
when input focus is
changed to the icon.
463 Minor D XM Compiler Warnings
487 Minor D Compiler warnings,
some optimization,
some alignment
related.
495 Minor D MRM MRM compilation
errors. 36 unused
automatic variables.
496 Minor D XM Xm compilation errors.
207 unused automatic
variables.
497 Minor D UIL UIL compilation
errors. 19 unused
automatic variables.
558 Minor A MRM MRMTIME includes the
.H when it should use
XOS.H.
70
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
740 Minor A XM Some XmList functions
which take XmString
as arguments perform
their tasks on the
first item in a list.
817 Minor A XM Arrow Button Activate
action performs visual
change that should
be done in disarm()
action.
875 Minor A DOC The documentation
does not describe the
resources conversion
routines.
971 Minor A XM Failure to set text
format for modify-
verify callbacks.
1050 Minor A MWM mwm title
backgroundPixmap
can override window
outline.
1087 Minor A TESTS The result of the
test is a segmentation
fault. (verified on
PMAX 1.0.2 build-DWB).
71
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1089 Minor D XM RowColumn doen't
behave correctly with
AUTOMATIC Scrolled
Window and static
scroll bars.
1099 Minor A XM The effect of setting
borderWidth is not
described.
1203 Minor D XM When multiple items
are selected via
arglist in a single
select list, no
warning is generated.
1213 Minor P In the demo mre, when
the color screen is
displayed, any change
in color values are
not being reflected in
the color PB.
1289 Minor A MWM Mwm resource specified
in the form "Mwm.some_
resource" is not
backward compatible
with 1.0.
1310 Minor D MWM The Iconbox scrollbar
is hard to see on a
monochrome system.
72
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1330 Minor A XM XmClipboardRegisterFormat
has undocumented re-
turn values for use
by internal func-
tions - code should be
changed.
1331 Minor A XM It is possible to re-
register a format with
a new format_size.
Maybe ok for user-
formats, but not for
predefined formats!
1455 Minor A XM Arrow inside frame
has 0 height if
created after Realize
(PushButton works ok,
Scrollbar and text
don't).
1475 Minor A TESTS Define an XtOrderProc
for use as a
XmNinsertPosition
resource. Have it
return an index that
would insert a child
ordered...
1506 Minor A XM Data type for
mnemonics should
be XmMnemonic, not
KeySym.
73
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1519 Minor A XM The definition of
XmNupdateSliderSize
seems not to be used
anywhere. If so it
should be deleted from
Xm.h
1673 Minor D XM When a Separator
gadget is specified
as child of a PanedW,
the sep doesn't get a
pane; instead appears
as glitch at top.
1686 Minor A XM You should get a beep
if you click in non-
descendent dialog
when a FULL_APP modal
dialog is posted.
1687 Minor I XM/MWM Window manager
shouldn't give focus
to dialogs which are
non- accessible due to
another modal dialog.
1695 Minor I XM/MWM Mwm allows focus on
non-parent toplevel
shell when a full
app modal dialog is
up (but input is not
accepted).
74
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1702 Minor A XM If width and
height are set and
recomputeSize is
set to true in a
cascade button, the
labelString is being
left justified.
1731 Minor A TESTS Write a test for
multiple cascade
button gadgets in
a MENU_OPTION Row
Column.
1743 Minor A XM When creating
pulldown, popup, and
option menus with
NO children, and
"popping" them up
gives a small empty
menu.
1760 Minor A XM When using with 1
scrollbar (either vert
or horiz) it makes
the working window too
small by 4 pixels and
not centered.
75
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1766 Minor A DEMOS Mre should not
check for SYSV
defined to choose
between string.h and
strings.h. It should
just use string.h
(include).
1774 Minor A XM Overlapping of widgets
(or gadgets) in a form
can sometimes cause
sensitivity area to be
different than size of
the widget.
1776 Minor A XM Problem changing color
with bitmap labels.
1809 Minor A TESTS Rewrite OptionMenu2
test so that toggles
are not used in menu.
Or, have select and
unselect pixmap info
moved to another test.
1814 Minor A MWM Mwm does not display
hourglass cursor on
other screens in mult
iscreen mode.
76
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1826 Minor P XM _XmHighlight and
_XmUnhighlight
should set and reset
Primitive highlighted
even if the highlight_
thickness is 0.
1841 Minor P XM When you first move
a sash which has just
been widened, the
track line shows in
the wide sash w/ hole
for old sash.
259 Build A XM Several files assume
system V compatibility
memory functions
a presence of
<memory.h>, which is
not on this machine.
260 Build A Assumes STRCHR/STRRCHR
presence.
462 Build D UIL Compiler Warnings
466 Build D XM Compiler Warnings Etc.
492 Build A BUILD Additions to make
ncludes to allow XENIX
IMAKE to function.
1100 Build D DEMOS Compile errors in de-
mos/Motifshell/Motifshell.h.
77
Table_2_(Cont.)__Known_Bugs_in_Motif_1.1_______________
PIR_____SeverityStatus__Region__Bug_Description________
1101 Build D DEMOS Compiler errors in de-
mos/Motifgif/Motifgif.h.
1102 Build D DEMOS Compile errors in
demos/mre/mre.c.
1103 Build D DEMOS Compile errors in de-
mos/widgetView/widgetView.h.
1205 Build A DEMOS demo source should not
need private non-demo
source.
1225 Build A TESTS Motif.rules and
Motif.tmpl need
#ifndef and shared
lib support.
1435 Build A UIL UilLexParse.c is
missing from the tape.
Can be created with
________________________________wml.___________________
78