| RE: [AD] Feature request: Add missing GFX_VTABLE entries |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: <alleg-developers@xxxxxxxxxx>
- Subject: RE: [AD] Feature request: Add missing GFX_VTABLE entries
- From: "Robert Ohannessian" <ROhannessian@xxxxxxxxxx>
- Date: Sun, 3 Oct 2004 13:46:22 -0700
- Thread-index: AcSpUBP/oDm3W+mPTriEorfhoHA19AAOecDg
- Thread-topic: [AD] Feature request: Add missing GFX_VTABLE entries
Calc_spline is still there. I also noticed that stretch_masked_blit is
gone...
> -----Original Message-----
> From: alleg-developers-admin@xxxxxxxxxx [mailto:alleg-
> developers-admin@xxxxxxxxxx] On Behalf Of Evert Glebbeek
> Sent: Sunday, October 03, 2004 6:46 AM
> To: alleg-developers@xxxxxxxxxx
> Subject: Re: [AD] Feature request: Add missing GFX_VTABLE entries
>
> On Sunday 26 September 2004 21:20, Evert Glebbeek wrote:
> > stretch_blit, masked_stretch_blit and stretch_sprite all use the
same
> > do_stretch_blit function as a workhorse (src/i386/istretch.c), or
> > _al_stretch_blit from src/c/cstretch.c. It's probably good enough to
> make
> > a vtable entry for this function.
> >
> > > For the set_*_blender functions, maybe we can just have one driver
> entry
> > > for all of them that takes an enum (or define) to select the
blender?
> >
> > Makes sense.
> > I'll see if I can make those changes later tonight.
>
> Time flies when you have a job...
> anyway, revised vtable patch attached. This just adds hooks to the
> vtables,
> and doesn't actually make the functions call those yet. I'll add
support
> for that and an enum with possible blender modes later today (I will!)
>
> Evert