Usenet 1994 January/usenetsourcesnewsgroupsinfomagicjanuary1994.iso/answers/motif-faq/part1

Internet Message Format | 1993-10-25 | 42KB

Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!medusa.hookup.net!news.kei.com!yeshua.marcam.com!usc!howland.reston.ans.net!europa.eng.gtefsd.com!news.umbc.edu!cs.umd.edu!kong.gsfc.nasa.gov!vilya.gsfc.nasa.gov!not-for-mail
From: [e-mail] (Brian Dealy)
Newsgroups: news.answers,comp.answers
Subject: Motif FAQ (Part 1 of 5)
Followup-To: poster
Date: 25 Oct 1993 16:09:37 -0400
Organization: NASA/Goddard Space Flight Center
Lines: 933
Sender: [e-mail]
Approved: [e-mail]
Expires: +1 months
Message-ID: <2ahbq1$[e-mail]>
Reply-To: [e-mail] (Brian Dealy)
NNTP-Posting-Host: vilya.gsfc.nasa.gov
Summary: This posting contains a list of Frequently Asked Questions and their answers about Motif.
Keywords: FAQ question answer
Xref: senator-bedfellow.mit.edu news.answers:13924 comp.answers:2409

Archive-name: motif-faq/part1
Last-modified: Oct 15, 1993
Version: 3.6


Motif FAQ

[Last changed: 15 Oct 93]

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 FAQ is maintained by Brian Dealy <[e-mail]>.  Send
updates and corrections to him at that mail address.  It would help if
the subject line contained the phrase "FAQ".

From November 89-July 93 the FAQ was maintained by Jan Newmarch
<[e-mail]>

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 accessible via email?
 4)  Is this newsgroup archived?
 5)  Is the mail list motif-talk archived?
 6)  TOPIC: OSF AND MOTIF
 7)  Because of COSE, is Motif now in the public domain?
 8)  What versions of Motif are there?
 9)  Where can I get Motif?
10)  Is there a list of Motif bugs?
11)  Where can I get public domain Motif source?
12)  Are the Motif examples publically available?
13)  Has anyone done a public domain Motif lookalike?
14)  Does anyone from OSF pay attention to our questions/suggestions?
15)  Does OSF have an application compliance validation service?
16)  What is the motif-talk mailing list?
17)  What MIT patches do I use, and when do I use fix-osf?
18)  How does Motif work with X11R5?
19)  How can I find which version of Motif I have?
20)  TOPIC: LITERATURE
21)+ What books should I read or do I need to program using Motif?
22)  TOPIC: MWM
23)  What is the difference between Motif and mwm?
24)  Does anyone have an alternative set of 3-D defaults for a monochrome
     screen?
25)  How can I modify the Motif window manager decorations?
26)  How can I turn off the Motif window manager functions from the system
     menu?
27)  How can tell I if the user has selected the "Close" item on the system
     menu attached to the top-level shell?
28)  Is there an mwm virtual desktop manager?
29)  Why does mwm 1.2 crash on startup?
30)  TOPIC: MOTIF GENERATORS
31)  What prototyping tools are there to generate Motif code?
32)  TOPIC: TEXT WIDGET
33)+ What is the difference between a XmTextField widget and a single line
     XmText widget?
34)  Why does  pressing  <return> in a text widget do nothing?
35)  When I add text to a scrolling text widget how can I get the new text
     to show?
36)  Does the text widget support 16 bit character fonts?
37)  How can I stop the text widget from echoing characters typed?
38)  How can I replace characters typed with say a `*'?
39)  How can I best add a large piece of text to a scrolled text widget?
40)  How can I highlight text in the Text widget?
41)  How can I select all of the text in a widget programmatically?
42)  How can I change colours of text in the Text widget?
43)  How can I change the font of text in the Text widget?
44)  Is there an emacs binding for the text widget?
45)  How can I use a file as the text source for a Text widget?
46)  How can put Text in overstrike mode instead of insert?
47)  How can I make the Delete key do a backspace?
48)  TOPIC: LIST WIDGET
49)+ Should I create an XmList widget as a child of automatic  XmScrolledWindow
     or use the XmCreateScrolledList() convenience function?
50)  How do I best put a new set of items into a list?
51)  Can I have strings with different fonts in a list?
52)  Can I get a bitmap to show in a list item like I can in a Label?
53)  Can I have items with different colours in a list?
54)  Can I grey out an item in a list?
55)  Can I have multi-line items in a list?
56)  How can I tell the position of selected items in a list?
57)  TOPIC: FILE SELECTION BOX WIDGET
58)  What is libPW.a and do I need it?
59)  What are these compile errors: Undefined symbol _regcmp and _regex?
60)  What's wrong with the Motif 1.0 File Selection Box?
61)  TOPIC: FORM WIDGET
62)  Why don't labels in a Form resize when the label is changed?
63)  How can I center a widget in a form?
64)  How do I line up two columns of widgets of different types?
65)  TOPIC: PUSHBUTTON WIDGET
66)  Why can't I use accelerators on buttons not in a menu?
67)  TOPIC: LABEL WIDGET
68)  How can I align the text in a label (button, etc) widget?
69)  Why doesn't label alignment work in a RowColumn?
70)  How can I set a multiline label?
71)  How can I have a vertical label?
72)  How can I have a Pixmap in a Label?
73)  TOPIC: DRAWING AREA WIDGET
74)  How can I send an expose event to a Drawing Area widget?
75)  How can I know when a DrawingArea has been resized?
76)  TOPIC: MENUS
77)  What can I put inside a menu bar?
78)  Can I have a cascade button without a submenu in a pulldown menu?
79)  Should I have a cascade button without a submenu in a pulldown menu?
80)  What is the best way to create popup menus?
81)  How do popup menus work?
82)  Should I use translation tables or actions for popup menus?
83)  What are the known bugs in popup menus?
84)  Can I have multiple popup menus on the same widget?
85)  TOPIC: INPUT FOCUS
86)+ How can I specify the widget that should have the keyboard focus when my
     application starts up?
87)  How can I direct the keyboard input to a particular widget?
88)  How can I have a modal dialog which has to be answered before the
     application can continue?
89)  TOPIC: MEMORY AND SPEED
90)+ When can I free data structures passed to or retrieved from Motif?
91)  Why does my application grow in size?
92)  Why does my application take a long time to start up?
93)  My application is running too slowly. How can I speed it up?
94)  Why is my application so huge?
95)  TOPIC: XMSTRING
96)  How can I get the Ascii text out of an XmString?
97)  When can XmStrings used as resources be freed?
98)  Why doesn't XmStringGetNextSegment() work properly?
99)  Why does using XmStringDraw cause a Bad Font error?
100)  TOPIC: DIALOGS
101)  How do I stop my dialog disappearing when I press the help button?
102)  How do I make my own dialog?
103)  How come the title bars for my dialogs now have  "_popup"  or  "<-popup"
      concatenated onto the widget name?
104)  How can I force a dialog window to display?
105)  How can I control placement of a popup widget?
106)  TOPIC: LANGUAGE BINDINGS
107)  Is there a C++ binding for Motif?
108)+ How can I have a C++ member function in a callback?
109)  Is there a Common Lisp binding for Motif?
110)  Is there an Ada binding for Motif?
111)  Is there a Poplog binding for Motif?
112)  TOPIC: SPECIFIC PLATFORMS
113)  Is it easy to build Motif for a Sun?
114)  How do I build Motif 1.2.2 on Solaris 2.1 with Sun C?
115)  What compile errors/warnings might I get in both Sun 3 and Sun 4?
116)  On a Sun 3, what are the mwm startup error messages about?
117)  Are there problems making shared libraries on a Sun?
118)  The OpenWindows server hangs when I popup a menu with Button 3.
119)  Has anyone made shared libraries on an IBM RS/6000?
120)  What is the error  "Unaligned access in XmString" under Ultrix?
121)  TOPIC: KEYSYMS
122)+ What is causing the messages "unknown keysym osfDown..."?
123)  What happens if I can't install Motif Keysyms?
124)  Why has OSF introduced Keysyms into Motif 1.1?
125)  TOPIC: ICONS
126)  How can I keep track of changes to iconic/normal window state?
127)  How can I check if my application has come up iconic?
128)  How can I start my application in iconic state?
129)  How can an application iconify itself?
130)  How can an application de-iconify itself?
131)  TOPIC: MISCELLANEOUS
132)+ How can I identify the children of a manager widget?
133)+ How do I tell if a scrolled window's scrollbars are visible?
134)+ How can I programatically scroll a XmScrolledWindow in XmAUTOMATIC mode?
135)+ What functions can an application use to change the size or position
      of a widget?
136)+ What widgets should I use to get the look of push buttons, but
      the behaviour of toggle buttons?
137)+ Can  I  use  XtAddTimeOut(), XtAddWorkProc(), and XtAddInput() with
      XtAppMainLoop()?
138)+ Why does XtGetValues() XmNx and XmNwidth return extremely large values.
139)+ Can I specify callback functions in resource files?
140)  How do I specify a search path for ".uid" files?
141)+ XtGetValues() on XmNx and XmNy of my top level shell  don't  return  the
      correct root window coordinates.  How do I compute these?
142)+ Can I use XmGetPixmap() with widgets that have non-default visual types?
143)+ How can I determine the item selected in a option menu or a RadioBox?
144)  What is the matter with Frame in Motif 1.2?
145)  What is IMUG and how do I join it?
146)  What is the X Professional Organization
147)  How do I set the title of a top level window?
148)  Can I use editres with Motif?
149)  How can I put decorations on transient windows using olwm?
150)  Why does an augment translation appear to act as replace for some
      widgets?
151)  How do you "grey" out a widget so that it cannot be activated?
152)  Why doesn't the Help callback work on some widgets?
153)  Where can I get a Table widget?
154)  Has anyone done a bar graph widget?
155)  Does anyone know of a source code of a graph widget
156)  Is there a help system available, such as in Windows 3?
157)  Can I specify a widget in a resource file?
158)  Why are only some of my translations are being installed?
159)  Where can I get the PanHandler code?
160)  What are these passive grab warnings?
161)  How do I have more buttons than three in a box?
162)  How do I create a "busy working cursor"?
163)  Can I use the hourglass that mwm uses?
164)  What order should the libraries be linked in?
165)  How do I use xmkmf for Motif clients?
166)  How do I make context sensitive help?
167)  How do I debug a modal interaction?
168)  Where can I get info on the Motif drag and drop protocol?
169)  TOPIC: ACKNOWLEDGEMENTS

If you have suggestions or corrections for any of these answers or any
additional information, please send them directly to [e-mail];
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).

This posting is intended to be distributed at approximately the beginning of
each month. But sometimes it will slip abit.

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?

[Last modified: Feb 93]

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.x.pex,
comp.windows.x.apps, comp.windows.x.intrinsics, comp.windows.news,
comp.windows.misc and comp.windows.open-look.  The intrinsics and open-look
groups also have an FAQ.

The newsgroup news.answers contains *lots* of FAQs (including this one).  Look
there for oodles of info on everything.

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

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

[Last modified: May 93]

Answer: A number of FAQ's (including this one) are available for anonymous ftp
at rtfm.mit.edu, 18.70.0.226 (the IP may change soon) under the directory
pub/usenet.  (Motif is under pub/usenet/comp.windows.x.motif and also under
pub/usenet/comp/windows/x/motif) There is also a mail server called mail-
[e-mail].  To retrieve a file send mail to the server with a
subject or body similar to

        send usenet/comp.windows.x.motif/Motif_FAQ_(Part_1_of_5).Z

This service is looked after by Jonathan Kamens ([e-mail]).

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

The FAQ is also available from csc.canberra.edu.au (137.92.1.1) by anonymous
ftp.  It is in the file /pub/motif/Motif-FAQ

This files are also accessible from WAIS (Wide Area Information System) under
UC-Motif-FAQ, allowing keyword-based searches of the FAQ.

-----------------------------------------------------------------------------
Subject:  3)  Is this newsgroup accessible via email?

[Last modified: April 93]

Answer: An email link is maintained by Brian Dealy.  To join, send mail to
[e-mail].

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

[Last modified: November 1992]

Answer: The newsgroup files from August 1991 are available from
csc.canberra.edu.au (137.92.1.1) by anonymous ftp.  They are in the directory
/pub/motif/comp.windows.x.motif.

These files are also accessible from WAIS (Wide Area Information System) under
comp.windows.x.motif, allowing keyword-based searches of the newsgroup
articles (this time on machine services.canberra.edu.au (137.92.1.12)).

-----------------------------------------------------------------------------
Subject:  5)  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:  6)  TOPIC: OSF AND MOTIF

-----------------------------------------------------------------------------
Subject:  7)  Because of COSE, is Motif now in the public domain?

Answer: The *specification* for Motif is no longer controlled by OSF, but by
X/Open.  This does not affect the *implementation*. The implementation is
still in the hands of OSF, and will not be released into the public domain.
So no, the OSF source code will still only be available to those who buy a
source code license from OSF.

The specification does not include UIL or obsolete features (ie 1.0 bugs in
design), but these will continue to be supported by the OSF code.

Subject:  8)  What versions of Motif are there?
[Last modified: March 93]

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.

Motif 1.1 is based on the R4 toolkit.  The intial version was Motif 1.1.0.
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 fixed a further 150 bugs and was 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.  1.1.5 was released
in June 92 to licensees who hold a Motif Full Support or Update Support
contract

Motif 1.2.0 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.  The code is totally ANSI C.  OSF distributes a 10
pages sheet entitled "OSF/Motif R1.1 to R1.2: detailed overview of changes",
which is available from OSF Motif direct channels.  (617-621-7300 or email
[e-mail])

Motif 1.2.1 was released September 92.  Due to an optimisation from 1.2.0 to
1.2.1 object code compiled under 1.2.1 (that is, using 1.2.1 header files)
will not link with 1.2.0 libraries (and, very probably, clients that use
shared libraries and are linked against 1.2.1 won't startup against 1.2).

Motif 1.2.2 was released March 93.  This release contains over 250 bug fixes,
improved text, drag-and-drop features and has less than one reported defect
per 1000 lines of code.

from [e-mail] Motif 1.2.3 was released on September 13, 1993.  The
defect density is measured at < 0.8 known reports per thousand lines.  In this
release, we have paid particular attention to memory leaks, and have improved
drag-and-drop performance greatly.


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

[Last modified: October 93]

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 .

[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.]

ICS makes several binary kits, notably for Sun, DEC, Apple;

Quest (408-496-1900) sells kits for Suns, as well;

IXI ([phone]) offers kits for Sun3         (SunOS 3.5 or later, and
Sun4         (SunOS 4.0.1 or later).         (Solaris 2.1 or later ( both
SPARC  and Intel ))         ( both M1.1.5 and Motif 1.2.2 for SPARC, Motif
1.2.2 for Intel ).

Sun Microsystems is now shipping a version of Motif also.

NSL ([phone]; [e-mail]) offers kits for the Sun 3 and Sun
4.


In Australia, Information Technology Consultants Pty Ltd has Motif 1.1.2 for
Sun Sparc 4.1 ( phone on [phone], fax on [phone] or e-mail to
[e-mail])

SILOGIC (+33 61.57.95.95), 78 chemin des Sept Deniers - 31200 TOULOUSE FRANCE
sells Motif 1.1 and 1.2 on Sun4 machines. They also provide customers with
Motif maintenance and support, and do consulting on the X window System at
large, including software development.


Metro Link is now selling Motif 1.2.2 for Linux at the introductory price of
$199.00 (US) complete.  Regular pricing will be $199.00 for Runtime and
$299.00 for Development (which includes Runtime.)  BTW, we include a shared
library version of libXm.

For more information please contact [e-mail] or call
+1.305.970.7353. (Fax: [phone]  Email: [e-mail]) The kits
include varied levels of bug-fixing and support for shared libraries.

BIM (Fax : [phone]) offer Motif 1.1 for Sun-3, Sun-4, Sun-386i.
Includes shared libraries.

Metrolink Inc. ([phone], [e-mail]; 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 [e-mail] 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: 10)  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: 11)  Where can I get public domain Motif source?

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


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

[Last modified: March 93]

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 Thomas Berlages's
book are on export in /contrib/berlage.motif.tar.Z The examples from Donald L.
McMinds's book are on export in /contrib/mastering.motif.tar.Z The examples
from Jan Newmarch's book are export in /contrib/newmarch.tar.Z The examples
from Jerry Smith's book are on export in contrib/smith.motif.tar.Z



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

[Last modified: March 93]

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.

Applications that follow the Style Guide might be certified Motif-compliant
through the checklist process, even though they're not using OSF/Motif
binaries.

Tcl/Tk is available for ftp from allspice.berkeley.edu, and although
implemented without Xt, has a "strict Motif" mode.

Strom Sytems (18666 Redmond Way o-2118, Redmond, WA 98052-6725) have a Simple
Toolkit for X-Windows (sic) that appears to follow the Style Guide 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.

Interviews (also known as Fresco) is a C++ based product with appearance
similar to Motif.  A ftp-able version is on interviews.stanford.edu.  A
commercial version is available as InterViews Plus.


-----------------------------------------------------------------------------
Subject: 14)  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: 15)  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: 16)  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
[e-mail], citing your Company name and source license
number.



-----------------------------------------------------------------------------
Subject: 17)  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: 18)  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
MOTIFBC 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: 19)  How can I find which version of Motif I have?

[Last modified: October 93]

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.

In Motif 1.2, the macro XmUPDATE_LEVEL was added to give the minor revision
number.

+ ( above also known as the patch level).  + In addition there was a macro
string added,  XmVERSION_STRING which has all + the above info in a char
string.

+ grepping through a strings of libXm.a for OSF can also sometime give +
something useful.

thanks to [e-mail] Mike Hopkirk

-----------------------------------------------------------------------------
Subject: 20)  TOPIC: LITERATURE

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

[Last modified: April 93]

Answer: Ken Lee of the DEC Western Software Laboratory ([e-mail])
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 ISBN 13-640525-8 (Motif 1.0), ISBN
0-13-640681-5 (Motif 1.1), ISBN 0-13-643107-0 (Motif 1.2) (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 ISBN 13-640517-17 (Motif
1.0),
 ISBN 0-13-640616-5 (Motif 1.1), ISBN 0-13-643115-1 (Motif 1.2) 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), ISBN 13-643123-2 (Motif 1.2) 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.

Marshall Brain at [e-mail] 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.

Ferguson, Paula M, The Motif Reference Manual, Volume 6B of the O'Reilly
series on X.  This is the new volume of a two volume set on Motif programming.
ISBN 1-56592-038-4 (Motif 1.2)  (Volume 6A is expected to ship soon)

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

Smith, Jerry, Designing X Clients with Xt/Motif, ISBN 1-55860-255-0 Morgan
Kaufmann Publishers This adopts a higher-level approach to many of the objects
that commonly occur in Motif but are not in the Motif API.


Newmarch, Jan, The X Window System and Motif - A Fast Track Approach.
Addison-Wesley, ISBN 0-201-53931-4.

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).

Dan Heller's version of the Motif Programming Manual is still a widely used
and useful book. It is being replaced by Volume 6a and 6b but is a very useful
resource. Volume 6, Oreilly and Associates, Motif Edition.

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.

If you want to learn about UIL, look in the Motif Programmers's Guide.  This
seems to be the only information.


-----------------------------------------------------------------------------
Subject: 22)  TOPIC: MWM

-----------------------------------------------------------------------------
Subject: 23)  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: 24)  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, [e-mail], [e-mail]
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: [e-mail] (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: 25)  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: 26)  How can I turn off the Motif window manager functions from the
system menu?
[Last modified: October 92]

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

Note that mwm will have to be restarted after putting this in their resource
database.


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.

        #include <Xm/MwmUtil.h>

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



-----------------------------------------------------------------------------
Subject: 27)  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.

[Last modified: May 93]

Answer:          This works with R4 Intrinsics

        #include <Xm/Protocols.h>

        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 ([e-mail]) 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: 28)  Is there an mwm virtual desktop manager?

Answer: Peter E. Wagner ([e-mail]): 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.  [e-mail] 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: [phone]
216 The Science Park                    Fax:   [phone]
CAMBRIDGE
CB4 4WA



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

-----------------------------------------------------------------------------
Subject: 29)  Why does mwm 1.2 crash on startup?

[Last modified: March 93]

Answer: From David Brooks: The commonest cause of early mwm demise is as
follows:

- You, or someone, built Xlib in the default way using the Xsi
  internationalization functions.

- Your Xlib wasn't installed completely (or at all).

- Early on, mwm calls the function XmbTextListToTextProperty, which calls
  _XConvertMBToCT, which looks for the Xsi locale database, finds it
  missing, ignores this fact and tries to dereference zero.

The workaround is to find the database *somewhere*, and point the environment
variable XNLSPATH at it.  For example, in my personal X source tree:

        setenv XNLSPATH /home/X11r5src/mit/lib/nls/Xsi


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