Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!exodus!argv
From: argv@turnpike.Eng.Sun.COM (Dan Heller)
Newsgroups: comp.windows.x.motif
Subject: Re: Menu Bars
Message-ID: <2659@exodus.Eng.Sun.COM>
Date: 13 Nov 90 18:36:44 GMT
References: <1990Nov9.223934@eos.ncsu.edu> <4df75675.20b6d@apollo.HP.COM>
Sender: news@exodus.Eng.Sun.COM
Organization: O'Reilly && Associates
Lines: 21

In article <4df75675.20b6d@apollo.HP.COM> kumorek@apollo.HP.COM (James Kumorek) writes:
> Menu bars require that all the children of the menu bar be the same 'type'
> of widget (or gadget).  To get around this problem, use a cascade button or
> gadget for the button that will invoke the dialog box;  just don't set the
> subMenuId resource.  It should then act just like a push button.

Please don't do this -- this was not the intent of the GUI's use of
menubars.  You must keep in mind that the intent of a GUI is to
maintain consistency across all applications that use that GUI.
If you start doing things like this, users who are using stictly
Motif-based applications are going to get confused when they get to
yours because it's doing something differently from the others.

As one poster pointed out some weeks ago, a common thing to do is
to "drag thru the menubar" to examine all the submenus within to get
a preview of what sort of functions are available.
--
dan
----------------------------------------------------
O'Reilly && Associates   argv@sun.com / argv@ora.com
Opinions expressed reflect those of the author only.