[ROOT] Confused about ExecuteEvent behavior

From: Brett Viren (bv@bnl.gov)
Date: Sun Dec 16 2001 - 18:19:48 MET


Hi,

It seems that when a pointer approaches a TObject in a TPad it gets
events (via ExecuteEvent) before the pointer actually reaches the
TObject.  It gets a kMouseEnter (52) when the pointer is about 4
pixels away.  Furthermore, this event is accompanied by a pixel
location of 0,0 (why??).

This makes it difficult to write accurate ExecuteEvent() methods.  Is
there some way I can know when the pointer has really entered the
object with outh keeping a bunch of pointer state information in my
TObjects?

I guess I can see the need for some kind of "proximity" event, but
this should be its own event (ie, kProximityEnter, kProximityLeave)
and kMouseEnter/kMouseLeave should only get delivered when the pointer
actually enters/leaves the object.

Any chance to fix this, or is there some design reason for it that I
am missing?

Thanks,
-Brett.



This archive was generated by hypermail 2b29 : Tue Jan 01 2002 - 17:51:12 MET