[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On March 25, 2010, Peter Wang wrote:
> On 2010-03-24, Evert Glebbeek <eglebbk@xxxxxxxxxx> wrote:
> > On 24 Mar 2010, at 11:53 , Elias Pschernig wrote:
> > > One feature I think we still need:
> > >
> > > - Capabilities querying API. Among others it should report:
> > >
> > > ALLEGRO_HAVE_SET_BITMAP_TARGET
> > >
> > > If this is not available, al_set_target_bitmap cannot be (reasonably)
> > > used except for using our software rasterizer for drawing to memory
> > > bitmaps.
> > >
> > > ALLEGRO_HAVE_SET_SEPARATE_ALPHA_BLENDER
> > >
> > > If this is not available, al_set_separate_blender cannot be used (it
> > > will just ignore the alpha values passed in and work like
> > > al_set_blender otherwise).
> >
> > Ok.
> > Shouldn't be hard to add, right?
>
> ALLEGRO_HAVE_ is used for the build system so better rename it to
> ALLEGRO_CAP_* or something.
>
> > > Dario (I think) seems to have hit a stumbling block with enabling
> > > texture stages or something. It would be really nice to have of
> > > course, but we could release 5.0 without it.
> >
> > I think we can import it without that and worry about it after that.
> > Ok, so it'a not bug-free. If we let it sit, it'll just bit-rot.
> > Or we take the position that it should be a separate addon.
>
> It's too late for this. Leave it for 5.2.
Or earlier, I'm not sure why addons can't be added in minor releases.
> Peter
>
> -------------------------------------------------------------------------
> ----- Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
>
--
Thomas Fjellstrom
tfjellstrom@xxxxxxxxxx