| Re: [AD] various questions about events (4.3) |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On 2007-05-22, 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.
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.
BTW, al_wait_for_event uses timeout value of "0" to mean "forever". I
was intending some time ago to change this to a proper constant, like
AL_WAIT_FOREVER. A timeout value of "0" should mean "don't wait", so
al_wait_for_event(0) == al_get_next_event().
Peter