dave@objy20.Objy.COM (Dave Hu) (01/27/91)
It seems like there's been more traffic about VMS & Motif lately so
here's a list of some things I've picked up from experience...
1) System Application Specific Resource Files
For an application with class name className, VMS DECwindows searches
for the file DECW$SYSTEM_DEFAULTS:className.dat for system default
resources.
2) User Application Specific Resource Files
For an application with class name className, VMS DECwindows searches
for the file DECW$USER_DEFAULTS:className.dat for any user specified
resource values.
3) User Resource File
The DECwindows Session Manager loads the resources specified in the
file SYS$LOGIN:DECW$XDEFAULTS.DAT into the resource database when
you log in.
4) Resource Lookup Order
DECwindows looks for resources in this order...
a) DECW$SYSTEM_DEFAULTS:className.dat
b) DECW$USER_DEFAULTS:className.dat
c) resource database
5) XBMLANGPATH
VMS uses the logical XBMLANGPATH to find bitmaps requested by
XmGetPixmap(). The form of the logical is Unix-like, thus
if the bitmaps are located in mnt:[foo.bitmaps] you define it as
define XBMLANGPATH "/mnt/foo/bitmaps/%B"
6) Motif Backspace Problem
The LK201 VAX keyboard doesn't have a backspace key (only a delete
key). The standard Motif text widget treats backspace and delete
differently, thus in many cases you can't backspace. One work
around is to change the translation table so that Motif text widgets
treat the delete key like a backspace key. To do this, add the
following lines to your DECW$XDEFAULTS.DAT file:
*XmText.translations:\
#override \n\
<Key>Delete: delete-previous-character()\n
\n
Dave.