From: jan@ECHO.CANBERRA.EDU.AU (Jan Newmarch)
Newsgroups: comp.windows.x.motif
Subject: Motif FAQ (Part 1 of 5)
Summary: This posting contains a list of Frequently Asked Questions and their answers about Motif.
Keywords: FAQ question answer
Date: 17 Aug 92 14:51:50 GMT
Expires: 17 Oct 92 04:31:40 GMT
Reply-To: jan@ise.canberra.edu.au (Jan Newmarch)
Followup-To: comp.windows.x.motif
Distribution: inet
Organization: The Internet

Archive-name: motif-faq/part1
Last-modified: Tue July 14 1992
Version: 2.6



[Last changed: 15 July 92]

This article contains the answers to some Frequently Asked Questions (FAQ) 
often seen in comp.windows.x.motif. It is posted to help reduce volume in 
this newsgroup and to provide hard-to-find information of general interest.

		Please redistribute this article!

This article includes answers to the following questions. Ones marked with
a + indicate questions new to this issue; those with changes of content since
the last issue are marked by *:

 0) TOPIC: WHAT ARE OTHER RELEVANT NEWSGROUPS?
 1) TOPIC: FTP ARCHIVES
 2) Is the FAQ list available for FTP anywhere?
 3) Is this newsgroup archived?
 4) Is the mail list motif-talk archived?
 5) TOPIC: OSF AND MOTIF
 6)  What versions of Motif are there?
 7) Where can I get Motif?
 8) Is there a list of Motif bugs?
 9) Where can I get public domain Motif source?
10) Are the Motif examples publically available?
11)  Has anyone done a public domain Motif lookalike?
12) Does anyone from OSF pay attention to our questions/suggestions?
13) Does OSF have an application compliance validation service?  
14) What is the motif-talk mailing list?
15) What MIT patches do I use, and when do I use fix-osf?
16) How does Motif work with X11R5?
17)  How can I find which version of Motif I have?
18) TOPIC: LITERATURE
19)* What books should I read or do I need to program using Motif?
20) TOPIC: MWM
21) What is the difference between Motif and mwm?
22) Does anyone have an alternative set of 3-D defaults for a monochrome screen?
23)  How can I modify the Motif window manager decorations?
24)  How can I turn off the Motif window manager functions from the system menu?
25)  How can tell I if the user has selected the "Close" item on the system menu attached to the top-level shell?
26)+ Is there an mwm virtual desktop manager?
27) TOPIC: MOTIF GENERATORS
28)*  What prototyping tools are there to generate Motif code?
29) TOPIC: TEXT WIDGET
30) Why does  pressing  <return> in a text widget do nothing?
31) When I add text to a scrolling text widget how can I get the new text to show?
32) Does the text widget support 16 bit character fonts?
33) How can I stop the text widget from echoing characters typed?
34) How can I replace characters typed with say a `*'?
35) How can I best add a large piece of text to a scrolled text widget?
36) How can I highlight text in the Text widget?
37)  How can I select all of the text in a widget programmatically?
38) How can I change colours of text in the Text widget?
39) How can I change the font of text in the Text widget?
40) Is there an emacs binding for the text widget?
41) How can I use a file as the text source for a Text widget?
42) How can put Text in overstrike mode instead of insert?
43) How can I make the Delete key do a backspace?
44) TOPIC: LIST WIDGET
45) How do I best put a new set of items into a list?
46)  Can I have strings with different fonts in a list?
47) Can I get a bitmap to show in a list item like I can in a Label?
48) Can I have items with different colours in a list?
49) Can I grey out an item in a list?
50) TOPIC: FILE SELECTION BOX WIDGET
51) What is libPW.a and do I need it?
52) What are these compile errors: Undefined symbol _regcmp?
53) What's wrong with the Motif 1.0 File Selection Box?
54) TOPIC: FORM WIDGET
55) Why don't labels in a Form resize when the label is changed?
56) How can I center a widget in a form?
57) How do I line up two columns of widgets of different types?
58) TOPIC: PUSHBUTTON WIDGET
59) Why can't I use accelerators on buttons not in a menu?
60) TOPIC: LABEL WIDGET
61) How can I align the text in a label (button, etc) widget?
62) Why doesn't label alignment work in a RowColumn?
63)*  How can I set a multiline label?
64)  How can I have a vertical label?
65)+ How can I have a Pixmap in a Label?
66) TOPIC: DRAWING AREA WIDGET	
67) How can I send an expose event to a Drawing Area widget?
68) How can I know when a DrawingArea has been resized?
69) TOPIC: MENUS
70) What can I put inside a menu bar?
71) Can I have a cascade button without a submenu in a pulldown menu?
72) Should I have a cascade button without a submenu in a pulldown menu?
73) TOPIC: INPUT FOCUS
74) How can I direct the keyboard input to a particular widget?
75) How can I have a modal dialog which has to be answered before the application can continue?
76) TOPIC: MEMORY AND SPEED
77)* Why does my application grow in size?
78) Why does my application take a long time to start up?
79) My application is running too slowly. How can I speed it up?
80) TOPIC: XMSTRING
81) How can I get the Ascii text out of an XmString?
82) When can XmStrings used as resources be freed?
83) Why doesn't XmStringGetNextSegment() work properly?
84) TOPIC: DIALOGS
85) How do I stop my dialog disappearing when I press the help button?
86) How do I make my own dialog?
87) How come the title bars for my dialogs now have "_popup" or "<-popup" concatenated onto the widget name?
88) How can I force a dialog window to display?
89) How can I control placement of a popup widget?
90) TOPIC: LANGUAGE BINDINGS
91) Is there a C++ binding for Motif?
92) Is there a Common Lisp binding for Motif?
93)* Is there an Ada binding for Motif?
94) TOPIC: SPECIFIC PLATFORMS
95) Is it easy to build Motif for a Sun?
96) What compile errors/warnings might I get in both Sun 3 and Sun 4?
97) On a Sun 3, what are the mwm startup error messages about?
98) Are there problems making shared libraries on a Sun?
99) Has anyone made shared libraries on an IBM RS/6000?
100)  What is the error  "Unaligned access in XmString" under Ultrix?
101) TOPIC: KEYSYMS
102)* What is causing the messages "unknown keysym osfDown..."?
103) What happens if I can't install Motif Keysyms?
104) Why has OSF introduced Keysyms into Motif 1.1?
105) TOPIC: ICONS
106) How can I keep track of changes to iconic/normal window state?
107) How can I check if my application has come up iconic?
108) How can I start my application in iconic state?
109) How can an application iconify itself?
110) How can an application de-iconify itself?
111) TOPIC: MISCELLANEOUS
112)  What is IMUG and how do I join it?
113)+ How do I set the title of a top level window?
114)  Can I use editres with Motif?
115)  How can I put decorations on transient windows using olwm?
116) Why does an augment translation appear to act as replace for some widgets?
117) How do you "grey" out a widget so that it cannot be activated?
118) Why doesn't the Help callback work on some widgets?
119) Where can I get a Table widget?
120)*  Has anyone done a bar graph widget?
121)  Does anyone know of a source code of a graph widget
122)*  Is there a help system available, such as in Windows 3?
123) Can I specify a widget in a resource file?
124) Why are only some of my translations are being installed?
125)* Where can I get the PanHandler code?
126) What are these passive grab warnings?
127) How do I have more buttons than three in a box?
128)*  How do I create a "busy working cursor"?
129) TOPIC: ACKNOWLEDGEMENTS

If you have suggestions or corrections for any of these answers or any 
additional information, please send them directly to jan@ise.canberra.edu.au;
the information will be included in the next revision (or possibly the one 
after that; thanks for the many suggestions which haven't been incorporated 
yet).  The answers in this iteration are acknowledged to be partial.

This posting is intended to be distributed at approximately the beginning of 
each month.

The information contained herein has been gathered from a variety of sources. In
many cases attribution has been lost; if you would like to claim responsibility
for a particular item, please let us know. 

Conventions used below: telephone numbers tend to be Bell-system unless 
otherwise noted; prices on items are not included.







-------------------------------------------------------------------------------
Subject:  0) TOPIC: WHAT ARE OTHER RELEVANT NEWSGROUPS?

Answer: This newsgroup is comp.windows.x.motif.  The nearest related group is
comp.windows.x.  It also maintains an FAQ, which deals in all sorts of X, Xlib
and Xt questions. Look there for answers to questions such as "How do I get a
screendump of my application?", "where do I get X11R4", etc.  Other groups which
may have relevant information are comp.windows.news, comp.windows.misc and
comp.windows.open-look.

-------------------------------------------------------------------------------
Subject:  1) TOPIC: FTP ARCHIVES

-------------------------------------------------------------------------------
Subject:  2) Is the FAQ list available for FTP anywhere?

Answer: A number of FAQ's (including this one) are available for anonymous ftp
at pit-manager.mit.edu, 18.172.1.27 under the directory pub/usenet.  (Motif is
under pub/usenet/comp.windows.x.motif) There is also a mail server called mail-
server@pit-manager.mit.edu.  To retrieve a file send mail to the server with a
subject or body similar to

        send usenet/comp.windows.x.motif/Frequently_Asked_Questions_About_Motif_(Part_1_of_3)

This service is looked after by Jonathan Kamens (jik@pit-manager.mit.edu).

It has also been placed in contrib/Motif-FAQ at export.lcs.mit.edu.

-------------------------------------------------------------------------------
Subject:  3) Is this newsgroup archived?

Answer: A number of individuals are archiving the group for their own records,
but no-one has set up an FTP-able archive yet.
[Does anyone have a free 10Meg or so?]


-------------------------------------------------------------------------------
Subject:  4) Is the mail list motif-talk archived?

Answer: If you have purchased support from OSF then you have access to their
archive server for motif-talk.

-------------------------------------------------------------------------------
Subject:  5) TOPIC: OSF AND MOTIF

-------------------------------------------------------------------------------
Subject:  6)  What versions of Motif are there?

Answer: Motif 1.0 is based on the R3 toolkit.  There are patch releases to 1.0:
1.0.1, 1.0.A, 1.0.2 and 1.0.3, 1.0.4, 1.0.5. 1.0.A was a fairly major patch, as
it involved a complete re-engineering of UIL and Mrm.  Almost everyone who has
1.0.x has either 1.0.A or 1.0.3.  There are not expected to be further patches
to 1.0.

Motif 1.1 is based on the R4 toolkit.  The current version is Motif 1.1.0, plus
a couple of patches available to full support contract holders. Motif 1.1.1 has
been released as a patch to licensees with Full Support or Technical Update
service.  Motif 1.1.2 is a patch release which contains the necessary changes to
fix over 80 bugs reported against Motif. It is available to support contract
holders (including both full support and update service).  The 1.1.3 release
fixes a further 150 bugs and is available from August 1991 to support contract
holders (including both full support and update service).  1.1.4 offers X11R5
support, but is not an X11R5 product.  Future 1.1 patch releases are tentatively
scheduled as follows:

        1.1.5   1st half 1992


Motif 1.2 was released in April 1992 and is based on the X11R5 toolkit.  It
offers increased compatibility with international standards,  PC-style behavior
and binary compatibility with OSF/Motif 1.1 applications.  New features include
drag-and-drop, tear- off menus, toolkit enhancements and new documentation.
toolkit.

From dbrooks@osf.org: "Motif 2.0 will ship well before the sun burns out, unless
we decide to change the name first, and will contain a free plastic spaceman in
every box."

-------------------------------------------------------------------------------
Subject:  7) Where can I get Motif?

Answer:
    Various hardware vendors produce developer's toolkits of binaries, header
files, and documentation; check your hardware vendor, particularly if that
vendor is an OSF member. Systems known to be shipping now: HP (sans UIL), Apollo
(sans UIL), SCO, ICS, Mips (RISCwindows=X11R3 + full Motif), IBM, Data General
for AViioNs (includes UIL), Bull (?), Concurrent Computer Corporation 5000,
6000, 8000 series machines, Convex, Sequent.

    In addition, independent binary vendors produce Motif toolkits . ICS makes
several binary kits, notably for Sun, DEC, Apple; Quest (408-988-8880) sells
kits for Suns, as well; IXI (+44 223 462 131) offers kits for Sun3 (SunOS 3.5 or
later, and Sun4 (SunOS 4.0.1 or later). Unipalm XTech (+44 954211797; or Aurora
Technologies 617-577-1288 in USA) offers a binary kit for Suns based on Motif
1.1, with shared libraries.  NSL (+33 (1) 43 36 77 50; requests@nsl.fr) offers
kits for the Sun 3 and Sun 4.  [An FAQ is for "personal opinions" on these
toolkits.  I don't think it is appropriate to give such opinions through this
particular posting, so I haven't included any.] In Australia, Information
Technology Consultants Pty Ltd has Motif 1.1.2 for Sun Sparc 4.1 ( phone on (02)
360 6999, fax on (02) 360 6695 or e-mail to motif@itcsyd.itc.oz.au)


  The kits include varied levels of bug-fixing and support for shared libraries.
BIM (Fax : +32(2)759.47.95) offer Motif 1.1 for Sun-3, Sun-4, Sun-386i. Includes
shared libraries.  Metrolink Inc. (+1-305-566-9586, sales@metrolink.com; in
Europe contact ADNT, (33 1) 3956 5333) ships an implementation of X11R4 and
Motif 1.1 for several 386 systems.

    An OSF/Motif source license must be obtained from OSF before source can be
obtained from the Open Software Foundation. Call the Direct Channel Desk at OSF
at 617-621-7300 or email direct@osf.org for ordering information.  In addition
to the full Motif source, "option C" allows you to purchase source for the
window manager mwm to run on X terminals.


-------------------------------------------------------------------------------
Subject:  8) Is there a list of Motif bugs?

Answer: With each patch release of Motif shipped, there is a list of known bugs
provided.  The filename on the tape is "./OPENBUGS".  There is also a list of
all the issues closed/resolved in that patch.  That is found as part of the
"./README-1.1.n" (where n is the patch number) file.

These are the only OSF published lists.

No-one else seems to publish a list.


-------------------------------------------------------------------------------
Subject:  9) Where can I get public domain Motif source?

Answer: You cannot.  Motif source is not publically available.


-------------------------------------------------------------------------------
Subject: 10) Are the Motif examples publically available?

Answer: OSF has produced a list of which of the example programs can be
distributed. Call OSF Direct for a copy of it.  Most of the example programs
have been freed from distribution limitations so should be available.

In addition to these, many programs on export.lcs.mit.edu in the contrib
directory use Motif.  Source code posted to comp.sources.x often uses Motif.
The examples from Dan Heller's book are on export in
/contrib/OReilly/motif/examples.tar.Z.  The examples from Doug Young's book are
on export in /contrib/young.motif.Z The examples from Thomas Berlages's book are
on export in /contrib/berlage.motif.Z The examples from Donald L. McMinds's book
are on export in /contrib/mastering.motif.tar.Z



-------------------------------------------------------------------------------
Subject: 11)  Has anyone done a public domain Motif lookalike?

Answer: Not yet.  The specification is available (AES), and the validation suite
can be bought, but no-one has taken up the challenge.  There are some commercial
lookalikes (Looking Glass and Neuron Data), but no workalikes.  Tcl is available
for ftp from allspice.berkeley.edu, and although implemented without Xt, is
reported to look like Motif.  Strom Sytems (18666 Redmond Way o-2118, Redmond,
WA 98052-6725) have a Simple Toolkit for X-Windows (sic) that appears to follow
the AES even though it doesn't quite look like Motif.  MOOLIT is a USL product
that can be runtime switched between the Sun Open Look and Motif appearance.  It
is based on  OLIT 4i.


-------------------------------------------------------------------------------
Subject: 12) Does anyone from OSF pay attention to our questions/suggestions?

Answer: Yes, and they quite often post answers too. But they may not respond to
*your* problem because they have other things to do as well.  This newsgroup is
not run by OSF, and has no formal connection with OSF.  OSF is a member-driven
company.  The membership (and anyone can be a member) provides the primary input
for future development of Motif.

-------------------------------------------------------------------------------
Subject: 13) Does OSF have an application compliance validation service?

Answer: They have a checklist and a certification process which you can request
from them.  Ask for the Level One Certification Checklist.  The process is one
of self-certification.  It tests only the appearance and behavior of the
application against Motif style.  The product will also be put in the OSF
reference listing.  There's a one-time fee of $250.  According to the master
license agreement, you can't use any OSF identifying mark unless you have done a
certification.


-------------------------------------------------------------------------------
Subject: 14) What is the motif-talk mailing list?

Answer: The motif-talk mailing list is only for those who have purchased a Motif
source code license. You can be placed on this list by emailing to motif-talk-
request@osf.org, citing your Company name and source license number.



-------------------------------------------------------------------------------
Subject: 15) What MIT patches do I use, and when do I use fix-osf?

Answer: The Motif 1.1.0 tape contains MIT patches 1-14. Apply these and any
others you can get.  If your MIT patch level only goes up to fix-16, you also
need to apply fix-osf.  Fix-osf was an emergency patch for a problem that
existed when the Motif 1.1 tape was cut, The MIT fix-17 completely superseded
osf-fix, so if you have applied fix-17 do not apply fix-osf.  The 1.1.1 tape
contains MIT fixes 15-18, as well as an OSF-developed fix that deals with a
subtle bug in the Selection mechanism of the Intrinsics.  Most people will have
fix-15 to 18 by now; if you don't have them:

        Back out fix-osf if you have applied it
        Apply fix-15 to 18
        Apply fix-osf-1.1.1

The Selection fix was submitted to MIT, who came up with a different fix.  It
will not be made into an R4 fix but should be in R5. The MIT fix was posted to
motif-talk.


-------------------------------------------------------------------------------
Subject: 16) How does Motif work with X11R5?

Answer: Motif 1.1.X is only intended to be built with X11R4.  Motif 1.2.X is for
X11R5.  however, Motif 1.1.4 has been set to also work with X11R5.

For Motif 1.1.1, 1.1.2 and 1.1.3 you will need to compile Xlib and Xt with a
MOTIF_BC flag set to YES (page 8, section 3.3 of the R5 release notes), or
you'll also have a link problem (LowerCase) and a fatal run time problem
(XContext manager).  If your applications come up with "Unknown keysym name:
osfActivate" errors, check the variable ProjectRoot. The name
/$PROJECTROOT/lib/XKeysymDB will have been wired into your Xlib.

In Motif 1.1.0, XtCallCallback uses NULL as the first argument instead of a
widget ID. This was ok under R4, but must be changed in the source for R5. It
was changed by OSF from Motif 1.1.1 onward.

Mrm won't work at all (can't link since it uses an X private variable that has
disappeared in R5).  Thre is an MIT patch that may fix this??  [I confess
ignorance of Mrm and UIL].

-------------------------------------------------------------------------------
Subject: 17)  How can I find which version of Motif I have?

Answer: The macro XmVERSION gives you the version number.  The macro XmREVISION
gives you the major revision number.  The macro XmVersion combines these e.g. a
value of 1002 is Motif 1.2.

To find the minor revision number is not easy.  From Motif 1.1.3 onwards, try
this:

   'strings `which mwm` | grep OSF'.

to get the full version number e.g. 1.1.3.


-------------------------------------------------------------------------------
Subject: 18) TOPIC: LITERATURE

-------------------------------------------------------------------------------
Subject: 19)* What books should I read or do I need to program using Motif?

Answer: Ken Lee of the DEC Western Software Laboratory (klee@wsl.dec.com)
regularly posts to comp.windows.x and ba.windows.x a list of reference books and
articles on X and X programming.  In FAQ comp.windows.x an extract of his list
appears. Specifically for Motif programming, though:

OSF/Motif Programmers Guide, Prentice-Hall 13-640525-8 (Motif 1.0) ISBN 0-13-
640681-5 (Motif 1.1) (NB: This makes use of the demo programs that you get with
a Motif source license.  The programs are not included and may or may not be
available on your system.)

OSF/Motif Programmers Reference Manual, Prentice-Hall 13-640517-17 (Motif 1.0)
 ISBN 0-13-640616-5 (Motif 1.1) You will need this for the system calls.

OSF/Motif Style Guide, Prentice-Hall 13-640491-X (Motif 1.0) ISBN 0-13-640673-4
(Motif 1.1) You will need this to get some idea of how to write programs with
the correct `look and feel'.

You should read at least one of the the non-OSF books on Motif:

Young, Doug. "The X Window System: Applications and Programming with Xt (Motif
Version)," Prentice Hall, 1989 (ISBN 0-13-497074-8). The excellent tutorial "X
Window Systems Programming and Applications with Xt," (ISBN 0-13-972167-3)
updated for Motif. [The examples from the Motif version are available on export
in ~ftp/contrib/young.motif.tar.Z]

Marshall Brain at brain@adm.csc.ncsu.edu posted a set of simple and useful Motif
tutorials.

Berlage, Thomas Berlage, OSF/Motif: Concepts and Programming, Addison-Wesley,
UK, 1991. ISBN 0-201-55792-4.

Johnson, Eric F. and Kevin Reichard, Power Programming Motif, MIS: Press,
Portland, OR, 1991. ISBN 1-55828-059-6. Book with disk, ISBN 1-55828-061-8.

Heller, Dan, The Motif Programming Manual, Volume 6 of the O'Reilly series on X.
This is the most complete volume on Motif programming available.

Barkakati, Nabajyoti, W Window System Programming, SAMS. ISBN 0-672-22750-9.
This contains a section on Motif.

You will also need books and references on Xt such as:

Asente, Paul J., and Swick, Ralph R., "X Window System Toolkit, The Complete
Programmer's Guide and Specification", Digital Press, 1990.  The bible on Xt. A
treasury of information, excellent and invaluable.  Distributed by Digital
Press, ISBN 1-55558-051-3, order number EY-E757E-DP; and by Prentice- Hall, ISBN
0-13-972191-6.

Nye, Adrian, and Tim O'Reilly, "X Toolkit Programming Manual, Volume 4,"
O'Reilly and Associates, 1989. The folks at O'Reilly give their comprehensive
treatment to programming with the MIT Intrinsics; R4 versions are now available,
as is a Motif 1.1 version (Volume 4M).


Flanagan, David, ed.,  "X Toolkit Reference Manual, Volume 5," O'Reilly and
Associates, 1992a, Third Edition. A professional reference manual for the MIT
X11R4 and X11R5 Xt.

Books and reference manuals on Xlib may also be useful.



-------------------------------------------------------------------------------
Subject: 20) TOPIC: MWM

-------------------------------------------------------------------------------
Subject: 21) What is the difference between Motif and mwm?

Answer: mwm is a window manager. Motif itself is made up of four parts: a User-
Interface Guideline, an API toolkit of `C' routines which helps in the building
of applications which conform to the Guideline, the window manager mwm, and a
language UIL which is designed to ease user interface development.  In general
mwm will run an application built with any X-windows API, and in general an
application built using the Motif toolkit will run under any window manager.


-------------------------------------------------------------------------------
Subject: 22) Does anyone have an alternative set of 3-D defaults for a
monochrome screen?

Answer: This is obviously a matter of taste. Some alternatives suggested include

!Benjamin Schreiber, bs@osf.osf.org, bs@cs.brandeis.edu
Mwm*foreground:                 black           ! Actually, when a window is
Mwm*background:                 white           ! deactivated, the background
Mwm*backgroundPixmap:           50_foreground   ! becomes white, insted of
Mwm*topShadowPixmap:            white           ! 50% foreground (grey)

Mwm*activeForeground:           black
Mwm*activeBackground:           white
Mwm*activeBackgroundPixmap:     50_foreground
Mwm*activeTopShadowPixmap:      white

Mwm*menu*backgroundPixmap:      background
Mwm*menu*topShadowPixmap:       50_foreground

Mwm*title*foreground:                   black
Mwm*title*background:                   white
Mwm*title*backgroundPixmap:             white
Mwm*title*topShadowPixmap:              50_foreground
Mwm*title*activeForeground:             white
Mwm*title*activeBackground:             black
Mwm*title*activeBackgroundPixmap:       black
Mwm*title*activeBottomShadowPixmap:     50_foreground

Mwm*feedback*backgroundPixmap:          white

or

! From: tsang@isi.com (Kam C. Tsang)
Mwm*background:                      White
Mwm*activeBackground:                White
Mwm*activeBackgroundPixmap:          25_foreground
Mwm*foreground:                      Black
Mwm*activeForeground:                Black
Mwm*menu*background:                 white
Mwm*menu*foreground:                 black
xterm*Foreground:                    black
xterm*Background:                    white


or

! From: ucsd.edu!usc!snorkelwacker!paperboy!yee  (Michael K. Yee)
Mwm*cleanText:                          True

Mwm*activeBackground:           white
Mwm*activeForeground:           black
Mwm*background:                 white
Mwm*foreground:                 black

Mwm*client*activeBackgroundPixmap:      50_foreground
Mwm*client*activeTopShadowPixmap:       foreground
Mwm*client*activeBottomShadowPixmap:    background

!Mwm*client*background:                 white
!Mwm*client*foreground:                 black
Mwm*client*backgroundPixmap:            75_foreground
Mwm*client*topShadowPixmap:             foreground
Mwm*client*bottomShadowPixmap:          background

!Mwm*feedback*background:               white
!Mwm*feedback*foreground:               black
Mwm*feedback*backgroundPixmap:          50_foreground
!Mwm*feedback*topShadowPixmap:          25_foreground
!Mwm*feedback*bottomShadowPixmap:       background

!Mwm*menu*background:                   white
!Mwm*menu*foreground:                   black
Mwm*menu*backgroundPixmap:              foreground
!Mwm*menu*topShadowPixmap:              foreground
!Mwm*menu*bottomShadowPixmap:           background

!Mwm*icon*background:                   white
!Mwm*icon*foreground:                   black
Mwm*icon*activeBackgroundPixmap:        50_foreground
Mwm*icon*activeBottomShadowPixmap:      foreground
Mwm*icon*backgroundPixmap:              75_foreground



-------------------------------------------------------------------------------
Subject: 23)  How can I modify the Motif window manager decorations?

Answer: In resource files, use the window manager's client resource (which is
the application) and the resource clientDecoration:

Mwm*XClock.clientDecoration:   none

turns off all clock decorations.  See the mwm(1) entry for other possibilities.

Programmatically, set the VendorShell resource XmNmwmDecorations to appropriate
values: MWM_DECOR_NONE (or a bitwise or of values).

-------------------------------------------------------------------------------
Subject: 24)  How can I turn off the Motif window manager functions from the
system menu?

Answer: The user of an application can control functions in the system menu for
an application using the mwm resource clientFunctions:

        mwm.application_name.clientFunctions: -resize -close


Answer: The writer of an application can only remove items.  Be warned that your
users will probably gnash their teeth, swear furiously at your product and stop
using it if they discover that you have done this.  (Especially if you have
removed the Close button, your application has hung and it has taken up all of
memory and swap so it can't be killed.) Much better is to catch the action
gracefully as in the next question.

        XtVaGetValues(shell, XmNmwmFunctions, &int_val, NULL);
        int_val &= ~MWM_FUNC_CLOSE;
        XtVaSetValues(shell, XmNmwmFunctions, int_val, NULL);



-------------------------------------------------------------------------------
Subject: 25)  How can tell I if the user has selected the "Close" item on the
system menu attached to the top-level shell?  I need to do some clean up before
exiting.

Answer:          This works with R4 Intrinsics

        void FinalCleanupCB(w, client_data, call_data)
        Widget   w;
        caddr_t  client_data, call_data;
        {
                /* tidy up stuff here */
                ...
                /* exit if you want to */
                exit (0);
        }

        main()
        {
                Atom wm_delete_window;

                ...
                XtRealizeWidget(toplevel);
                ...
                wm_delete_window =
                        XmInternAtom(XtDisplay(toplevel),
                                "WM_DELETE_WINDOW", False);
                XmAddWMProtocolCallback(toplevel, wm_delete_window,
                        FinalCleanupCB, NULL);
                XtMainLoop();
        }

This will still kill the application.  To turn this behaviour off so that the
application is not killed, set the shell resource XmNdeleteResponse to
XmDO_NOTHING.  This means that users cannot kill your application via the system
menu, and may be a bad thing.

If you are running R3, Bob Hays (bobhays@spss.com) has suggested this: "Trapping
on the delete window atom does not work as I cannot force my action routine to
the top of the action list for the activity desired, so the window manager kills
my window anyway BEFORE I can do anything about it.  And, to make matters worse,
the window manager (Motif in this case) tacks its atoms and handlers onto the
window at some unknown point down the line after the creation of the shell
widget as far as I can tell.  So....

I have a procedure as an action routine for ClientMessage.  Then, if I get a
property change event on the window manager protocols, I then tack on
WM_SAVE_YOURSELF.  If I get this request, I clean up (it seems to happen on
WM_DELETE_WINDOW, BTW, if you remove WM_DELETE_WINDOW from the WM protocols
atom) and exit.  Works great and is less filling overall:-)."


-------------------------------------------------------------------------------
Subject: 26)+ Is there an mwm virtual desktop manager?

Answer: Peter E. Wagner (pew@cs.brown.edu): Imagine that your "desktop" extends
beyond the view provided by your monitor.  A virtual window manager gives you
access to the space beyond your viewport (i.e. your screen) by allowing you to
move the viewport to other areas of the extended desktop.

The first one is Solbourne's swm, which spawned vtwm/tvtwm/olvwm.

David B. Lewis created one.  suresh@unipalm.co.uk has further developed it into
the UniPalm product DOORS, which is only available as a source code extension to
the MOTIF window manager.  The price of the source and unlimited right to
distribute binaries is 10,000 pounds Sterling.  Alternately, source and right to
use within one company is 2,000 pounds Sterling.  Contact Peter Dawe

Unipalm Limited                         Voice: +44 (0) 223 420002
216 The Science Park                    Fax:   +44 (0) 223 426868
CAMBRIDGE
CB4 4WA



An enhancement request for such an object has been filed with OSF.

-------------------------------------------------------------------------------
END OF PART ONE