Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!ccut!kogwy!new1!roger From: roger@zuken.co.jp (Roger Meunier) Newsgroups: comp.windows.x.motif Subject: Re: Menu Bars Message-ID: Date: 7 Dec 90 04:50:57 GMT References: <1990Nov9.223934@eos.ncsu.edu> <4df75675.20b6d@apollo.HP.COM> <2659@exodus.Eng.Sun.COM> <12085@ibism.uucp> Sender: news@new1.zuken.co.jp Organization: ZUKEN Inc. Yokohama, JAPAN Lines: 23 In-reply-to: lcp@ibism.UUCP's message of 16 Nov 90 15:02:42 GMT In article <12085@ibism.uucp> lcp@ibism.UUCP (Larry Poleshuck) writes: > 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. > > Has anyone else seen this? I haven't seen any response to this one yet, so let me give it a whirl. I got bit by this one, too. It's not because you violated any style rules, but because Motif grabs both the pointer and the keyboard while a CascadeButton is active, and doesn't ungrab until after any callback is complete. I got around this by calling XUngrabPointer() and XUngrabKeyboard() (don't forget to XFlush()!) on entry to the callback(s) and then setting a breakpoint on a subsequent statement. Not very elegant, but it gets the job done. Hope this helps. -- Roger Meunier @ Zuken, Inc. Yokohama, Japan (roger@zuken.co.jp)