Path: utzoo!attcan!uunet!know!zaphod.mps.ohio-state.edu!van-bc!ubc-cs!uw-beaver!cornell!batcomputer!excalibur!darmstro
From: darmstro@excalibur.tn.cornell.EDU (Doug Armstrong)
Newsgroups: comp.windows.x.motif
Subject: Re: Menu Bars
Message-ID: <1990Nov12.154623.25047@batcomputer.tn.cornell.edu>
Date: 12 Nov 90 15:46:23 GMT
Sender: news@batcomputer.tn.cornell.edu
Reply-To: darmstro@theory.tn.cornell.EDU (Doug Armstrong)
Followup-To: 1461
Organization: Cornell National Computer Facility
Lines: 17
Nntp-Posting-Host: excalibur.tn.cornell.edu

In 1461 Lance Lovette mentions a problem with MenuBar children.

Perhaps the RTFM theory has kept others from responding to his 
problem, but I spent half a day tracking down the same problem
when I was first writing a real menu bar. Its a hard line to find.
My ancient (1989) Motif Reference Manual has the following under
XmRowColumn: XmNentryClass:  "When XmNrowColumnType is set to 
XmMENU_BAR, then the value of XmNentry is **forced** to 
xmCascadeButtonWidgetClass."  (emphasis mine) All is not lost,
however, since (to my surprise) Cascade Buttons support a
activate callback list and do not require a submenu.  Since I
don't need the arm and disarm callbacks that PushButtons support,
I've never missed them on my menu bars.

Doug Armstrong
darmstro@theory.tn.cornell.edu
CNSF / Technical Integration Group