home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1993 #1 / NN_1993_1.iso / spool / comp / windows / x / 20765 < prev    next >
Encoding:
Internet Message Format  |  1993-01-05  |  1.0 KB
  1. Xref: sparky comp.windows.x:20765 comp.windows.x.intrinsics:712 comp.windows.x.motif:8345
  2. Path: sparky!uunet!munnari.oz.au!spool.mu.edu!hri.com!noc.near.net!gateway!miki!oj
  3. From: oj@miki.pictel.com (Oliver Jones)
  4. Newsgroups: comp.windows.x,comp.windows.x.intrinsics,comp.windows.x.motif
  5. Subject: Re: X/Xt/Motif Event Interleaving?
  6. Summary: OwnerGrabButtonMask!
  7. Message-ID: <1993Jan5.151850.628@miki.pictel.com>
  8. Date: 5 Jan 93 15:18:50 GMT
  9. References: <BUZZ.93Jan4135708@lion.bear.com>
  10. Organization: PictureTel Corporation
  11. Lines: 12
  12.  
  13. In article <BUZZ.93Jan4135708@lion.bear.com> buzz@bear.com (Buzz Moschetti) writes:
  14. >    XtAddEventHandler(widget,
  15. >        EnterWindowMask | 
  16. >        ButtonPressMask | ButtonReleaseMask | Button1MotionMask,
  17. >              FALSE, my_event_proc, client_data);
  18. >
  19. >What we thought would happen is while, say, widget 1 was dragged over
  20. >widget 2, the latter's EnterNotify event would appear in the "stream" of
  21. >widget 1's MotionNotify events...
  22. >We do *not* see this behavior.
  23.  
  24. Put OwnerGrabButtonMask in your list of mask bits.
  25.