[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: Coordination of admins/developers of the game programming library Allegro <alleg-developers@xxxxxxxxxx>
- Subject: Re: [AD] initialization
- From: Elias Pschernig <elias@xxxxxxxxxx>
- Date: Tue, 18 Dec 2007 19:01:47 +0100
On Sun, 2007-12-16 at 14:32 +0000, Peter Hull wrote:
> OK , first things first! Is there an explanation of how Allegro's
> initialization is supposed to work?
> al_init() calls allegro_init, which does an old-style* init via
> _system_driver_list, and then calls _al_init, which does a new-style
> init via _al_register_system_interfaces and findsystem
We still use some A4 stuff like load_bitmap - the initialization of the
old system drivers should go once everything is converted to the new API
of course. And then also untangle it a bit, and only use the simple way
for the new drivers. (Feel free to change it for one port and don't care
about others - I'll adjust the linux port to work again with the new
system..)
> What should be done in each part? Has the option to do SYSTEM_NONE for
> non-gui apps gone now?
No, I think we still want that, I for one would find it useful.
--
Elias Pschernig <elias@xxxxxxxxxx>