Re: [AD] various questions about events (4.3)

[Peter Wang <novalazy@xxxxxxxxxx>]

On 2007-05-23, Matthew Leverton <meffer@xxxxxxxxxx> wrote:
> On 5/22/07, Peter Wang <novalazy@xxxxxxxxxx> wrote:
> > I can actually only think of one event type I'd like to filter, which is
> > mouse movement events in a GUI program, and even that is dubious if you
> > want widgets to highlight when you hover the mouse cursor on top of
> > them.  So we can probably just take the whole thing out.
> >
> At this point, I don't think we need any filtering capabilities. Not
> registering the event source is already one level of filtering. It
> will be easier to add it in the future than remove it.
> 
> >
> > Should we remove al_wait_for_specific_event?  It also requires event
> > types to be bitfields.  I never liked that design much anyway.  The user
> > can implement a more application specific filter using al_wait_for_event.
> >
> To me, it seems like it could be useful. I was using it as a readkey()
> replacement for simple test programs. (That is, when I didn't even
> care about the return result.)
> 
> But again, it's always easier to add features down the road, than to
> remove them (after they go into a release).

I've now removed the event masking-related stuff, including
al_wait_for_specific_event.  I've also changed al_wait_for_event() so
that the caller must pass AL_WAIT_FOREVER if he wants to wait
indefinitely.

Peter