| Re: [AD] al_get_frontbuffer() |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On 2010-11-06, Evert Glebbeek <eglebbk@xxxxxxxxxx> wrote:
> On OS X, calling al_get_frontbuffer() crashes because the vtable entry is not set.
> On Windows and X11, the vtable entry for al_get_frontbuffer is set to the same value as for al_get_backbuffer().
> Is this the correct behaviour? If so, I can easily do the same on OS X, but it seems a bit odd.
> For what it's worth, the D3D port seems to always return NULL from this function.
>
> My conclusion is that at the moment, this function doesn't do anything useful at all. I would say it should either be fixed (maybe this is a part of the API that never got implemented?), or removed.
>
Yeah, I can't make sense of it.
Maybe it was to be used with the ALLEGRO_SINGLE_BUFFER? Or designed to
be used in the way that I did for SPEED, to take a screenshot (which
actually is buggy as al_get_frontbuffer might return NULL).
If no explanation is forthcoming, I think we should remove it for now.
Peter