bug in tkinter canvas event handling?

[Garry Hodgson]

Doug Hellmann wrote:

> This behavior surprised me at first, too.  It's as though the first
> canvas object is grabbing the pointer so that all events go to it.  I
> got around the problem by looking for the x,y coords of the release
> event and then finding the object(s) under that point on the canvas.

well, some earlier code i had did its own hit detection.  but it
seemed silly to do it myself when the canvas oughta do it for me.
i've yet to peruse the source, per Fredrik's suggestion, so i don't
know whether Tk considers this bug or feature.  i know how i'd vote.

-- 
Garry Hodgson				And it's just a box of rain
Software Innovation Services		I don't know who put it there		
AT&T Labs				Believe it if you need it
garry at sage.att.com			Or leave it if you dare