| Re: [AD] d3d filtering flags |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On 10 Nov 2010, at 21:57 , Michał Cichoń wrote:
> No, actually I prefer event driven solution. I think this is A5 way of
> doing things.
For handling asynchronous events or input, yes, I agree (although for most things there are polling functions as an alternative), but not as the result of a direct function call.
It would sound to me like al_destroy_display() firing off an ALLEGRO_EVENT_DISPLAY_CLOSE event to indicate that the display was destroyed (not a 100% accurate analogy, I know). Or like al_use_transform() generating an event to say there's a new transformation in effect.
Just my opinion, of course.
Evert