Path: utzoo!attcan!uunet!lll-winken!sun-barr!olivea!mintaka!mit-eddie!bbn.com!cjross From: cjross@bbn.com (chris ross) Newsgroups: comp.windows.x.motif Subject: Motion/button events (not) appearing where they should(n't) Message-ID: <60396@bbn.BBN.COM> Date: 28 Oct 90 21:46:07 GMT Sender: news@bbn.com Reply-To: cjross@BBN.COM (chris ross) Organization: Bolt Beranek and Newman Inc., Cambridge MA Lines: 33 I and several coworkers have encountered some bizarre problems with delivery of mouse events to Motif widgets. They _seem_ to be related, so I'm posting four of them in this one article. None are reliably reproducible. All are annoyances at best, and at worst, potential show-stoppers for our product. The environment: SparcStation 1 with Sun/OS 4.0.3, dual monitors (cgsix & cgthree) OpenWindows 2.0 Motif 1.0.3 from ICS Mwm with KeyboardFocusPolicy == explicit 1. Button events go to the wrong PushButton. I click down on a button, causing a menu bar to appear. I release the button, move to the menu bar, and push a button there. The first button arms, rather than the button under the cursor. 2. Button events go to the wrong window. I click in a DrawingArea, release, move to a window on the other monitor, and click again. The button event goes to the DrawingArea on the first monitor. 3. A MessageDialog is created in response to a button click in a Drawing Area widget, but no amount of clicking or cursing will arm the buttons in the dialog; the events get picked up by the DrawingArea. 4. ScrollBars randomly stop tracking mouse events that occur outside the widget. I click down on the slider and begin moving the cursor; the slider only moves while the cursor is in the scroll bar. Please let me know if you've encountered any of the above, and if you know of workarounds. Thanx. chris ross cjross@bbn.com BBN Advanced Simulations #include