| Re: [AD] d3d filtering flags |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
It's a superfluous event. You don't need to wait for an event when
you already know what you wanted to achieve is done. al_resize_display
blocks until the display is resized. You don't need an event, and that's
all there is to it. Some famous smart guy once said (paraphrasing) the
goal isn't to accomodate for every programming situation possible, the
goal is to provide the minimum set of interfaces to make programming every
situation possible.. :P
--
Trent Gamblin
On 2010-11-10, at 7:57 PM, Michał Cichoń wrote:
> No, actually I prefer event driven solution. I think this is A5 way of
> doing things.
>
> al_resize_display(...); // sending event...
>
> case ALLEGRO_EVENT_DISPLAY_RESIZE:
> // handling all resize related stuff
> my_resize_event_handler();
> break;
>
> Allegro should acknowledge the resize after the resize event was handled.
Allegro doesn't know when the event is handled. It's just a pointer in
a queue.
> Actually ALLEGRO_EVENT_DISPLAY_RESIZE is send before or after the fact?
On windows it's send after the fact, presently.
Trent