🚀 go-pugleaf

In article <ld6a9iINNae8@news.bbn.com>, jpalmucc@bbn.com (Jeff Palmucci) writes:
|> bennett@mozart.redwood.com (Michael Bennett) writes:
|> >  The Button, as an ActiveHandler,
|> >grabs events while the cursor is within the Button.  It grabbed my
|> >keystroke events and ignored them.  Shouldn't the Button somehow send
|> >along keystrokes since it doesn't care about them?  
|> 
|> I ran into the same problem with a Drag around an ActiveHandler. As
|> soon as the mouse enters the ActiveHandler extension, the
|> ActiveHandler grabs all the events, including the middle button press
|> that was meant to start the drag.
|> 
|> >And, possibly
|> >related, why does Handle::event() now return a boolean?  What does it
|> >mean?  Is this what the button event grabber should use to indicate
|> >that it didn't handle the keystroke event so it can be dispatched to
|> >someone who wants it?
|> 
|> It looks like the boolean is ignored. I'd like to know what future
|> versions will do with it.
|> 
|> >Anyone know what I should be doing to accomplish this?
|> 
|> Yeah, anyone?

I fixed a problem in beta3 that should fix the case where buttons
eat keyboard events.  If the problem is still occuring, please send
me an example program.