| Re: [AD] Screen update API again |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Looks cool as a start.
Missing update methods like dirty rects can be added later...
This however poses a doubt to me: how to internally deal with the API
changes we're supposed to make all over the lib?
I mean, take your suggested screen update API code. It relies on
current functions to work. Will this change, so that we'll have for
example no more virtual screens (changing internal init() gfx drivers
hook) as they're not needed anymore? If we change it radically, the
whole set_gfx_mode code could be put inside the al_create_display
code... Then a small compatibility set_gfx_mode function could be made,
so that it calls al_create_display.
Basically my question is: are we going to emulate the new API using the
old API calls, or are we going to emulate the old API using new API
calls?
Sorry maybe this was already addressed lately, but I really had no time
to check out all messages yet.
--
Angelo Mottola
a.mottola@xxxxxxxxxx
http://www.ecplusplus.com