I was looking at that sort of EVENT and I’ve noticed that it couldn’t be
used within a the SDL_SetEventFilter()
Because SDL never gets rid off that event automatically.
We must call SDL_PushEvent() in order to make SDL gets rid off but then
the event can’t pass anymore within SDL_SetEventFilter()
The event filter runs before events are pushed into the queue. This is
a feature. However, perhaps in 1.3 the filter can be run from within
SDL_PushEvent() instead at the higher level it is being called from now.
See ya!
-Sam Lantinga, Lead Programmer, Loki Entertainment Software
Yeah it could be great because it could be a real powerful feature i think !
Sam Lantinga a ?crit:> > Hi,
I was looking at that sort of EVENT and I’ve noticed that it couldn’t be
used within a the SDL_SetEventFilter()
Because SDL never gets rid off that event automatically.
We must call SDL_PushEvent() in order to make SDL gets rid off but then
the event can’t pass anymore within SDL_SetEventFilter()
The event filter runs before events are pushed into the queue. This is
a feature. However, perhaps in 1.3 the filter can be run from within
SDL_PushEvent() instead at the higher level it is being called from now.
See ya!
-Sam Lantinga, Lead Programmer, Loki Entertainment Software
Anyway, why can’t the filter read SDL_USEREVENT event ? Can it only read from
device event ?
Sam Lantinga a ?crit:> > Hi,
I was looking at that sort of EVENT and I’ve noticed that it couldn’t be
used within a the SDL_SetEventFilter()
Because SDL never gets rid off that event automatically.
We must call SDL_PushEvent() in order to make SDL gets rid off but then
the event can’t pass anymore within SDL_SetEventFilter()
The event filter runs before events are pushed into the queue. This is
a feature. However, perhaps in 1.3 the filter can be run from within
SDL_PushEvent() instead at the higher level it is being called from now.
See ya!
-Sam Lantinga, Lead Programmer, Loki Entertainment Software