| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2668.1 | come from grabs | TOOLEY::B_WACKER | | Thu Apr 26 1990 17:17 | 2 |
| It is intended behavior. See Scheifler... p.227 section 8.4.2.2 on
grabs.
|
| 2668.2 | Scheifler ?? | SCOTMN::WOOD | El Vaquero | Fri Apr 27 1990 04:42 | 7 |
|
Thanks for the info, I'll do some reading, although I don't know that
particular book ( is it worth getting ?). Would the only way of handling
this be to ignore <Enter> and <Leave> when associated with
<MB1down> ?
Richard
|
| 2668.3 | Order # EY-6737E-DP | SCAM::DIAL | | Fri Apr 27 1990 09:57 | 4 |
| X Window System, C Library and Protocol Reference, by Robert W.
Scheifler, James Gettys and Ron Newman. Digital Press, order #
EY-6737E-DP, ISBN 1-55558-012-2. A good, very technical book about X.
|
| 2668.4 | | GILROY::klee | Ken Lee | Fri Apr 27 1990 14:17 | 2 |
| This book also appears, with very minor differences, on the X tape from
MIT and in the DEC UWS (VMS too?) document set.
|
| 2668.5 | Any Work Around | SCOTMN::WOOD | El Vaquero | Mon Apr 30 1990 09:55 | 7 |
|
Thanks for the replies,
Does anybody know a way around this problem. Would the only way be to
write code to filter out the '<Leave><Enter>' events that precede <MB1Down> ?
Richard
|
| 2668.6 | event tells all | TOOLEY::B_WACKER | | Mon Apr 30 1990 11:24 | 2 |
| I'm pretty sure the event structure, itself, has enough information to
figure out if it is "real" or not, but don't remember the details.
|
| 2668.7 | Ignore events you are not interested in... | LEOVAX::TREGGIARI | | Mon Apr 30 1990 11:43 | 13 |
| > I'm pretty sure the event structure, itself, has enough information to
> figure out if it is "real" or not, but don't remember the details.
That is correct. If you look in X.h you'll see a number of Notify*
literals that come back in one of the fields of the event and will
allow you to distinguish between different types of Enter/Leave events.
But only worry about it if you need to handle Enter/Leave events for
some other reason. The toolkit, for example, uses and encourages a style
of programming where you specify the events that you are interested in
(via event handlers or translation management) and just "drops" any other
event "on the floor".
Leo
|
| 2668.8 | Check the mode field of Event Structure | CSC32::B_KEMP | I just answer the phone | Mon Apr 30 1990 13:20 | 14 |
| The way to test if there is an actual entry/leave event or a
'pseudo' leave/entry event is to check the mode field of the
event structure.
pages 227-228 of Scheifler:
" Pseudo-motion mode EnterNotify and LeaveNotify events are generated
when a pointer grab activates or deactivates. Events in which the
pointer grab activates are identified by XEnterWindowEvent or
XLeaveWindowEvent structures whose mode member is set to NotifyGrab.
Events in which the pointer grab deactivates are identified by
XEnterWindowEvent or XLeaveWindowEvent structures whose mode member is
set to NotifyUngrab(see XGrabPointer)."
-Bill
|
| 2668.9 | Another Problem solved !! | SCOTMN::WOOD | El Vaquero | Thu May 03 1990 08:48 | 9 |
|
Thanks to all concerned, checking the 'mode' field in the XCrossingEvent
data structure for 'NotifyNormal' enables filtering of these particular
events.
Cheers for now
Richard
|