| Re: [AD] Alleg5 - new driver structure idea |
[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]
Angelo Mottola wrote:
Or supply a default "blit2" entry, only used when the driver doesn't provide it, which wraps around the original "blit" call.There is also the issue of supporting older interfaces. What if weadd a parameter to blit() for example? We can make a "blit2" entry inthe driver, but then we also need to support the old "blit" interface.Even better: the proposed AL_DRIVER_VTABLE_ENTRY structure has a "version" parameter that could be useful here. Suppose we have Allegro 5.0 and a gfx driver that has "blit" version 5.0. On startup, Allegro would connect the driver hook with the internal AL_GFX_DRIVER_VTABLE version 5.0.
That's the idea. The problem is if we ever end up with some interface for which emulating the old (possibly broken) behavior would be too much work.
| Mail converted by MHonArc 2.6.19+ | http://listengine.tuxfamily.org/ |