Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!ibism!ibism.UUCP!lcp
From: lcp@ibism.UUCP (Larry Poleshuck)
Newsgroups: comp.windows.x.motif
Subject: Re: Menu Bars
Message-ID: <12085@ibism.uucp>
Date: 16 Nov 90 15:02:42 GMT
References: <1990Nov9.223934@eos.ncsu.edu> <4df75675.20b6d@apollo.HP.COM> <2659@exodus.Eng.Sun.COM>
Sender: news@ibism.uucp
Reply-To: ibism!lcp
Organization: Citibank IBISM
Lines: 34

In article <2659@exodus.Eng.Sun.COM>, argv@turnpike.Eng.Sun.COM (Dan Heller) writes:
> 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

We have tried this technique (i.e., using a cascade button with no subMenuId
and with an activate callback, even though it is not consistant with Motif
style.  To get even with me Motif would not let me step into the code executed
by the activate callback.  When I set a breakpoint in the callback routine and
hit the cascade button, my interface freezes.  No window will accept input 
from keyboard or mouse.  The application is locked in my debugger, but
the debugger will not accept input.

I am using TeleUSE (Motif 1.0.3) on SunOS and the problem occurs when
the callback is a D-routine being debugged with the TeleUSE D debugger and
when the callback is a c routine being debugged with dbxtool.

Has anyone else seen this?

-- 

Larry Poleshuck
Citibank
111 Wall Street
New York, NY  10043

Phone:  212-657-7709
Fax:    212-657-0068
E-Mail: uunet!ibism!lcp