| Re: [AD] stretch_blit GFX_HW_VRAM_BLIT ? |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] stretch_blit GFX_HW_VRAM_BLIT ?
- From: Chris <chris.kcat@xxxxxxxxxx>
- Date: Fri, 27 Jan 2006 15:05:00 -0800
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=U8V4nY9uHv/A4mEprqNw76mZAEPjMRF78B93PYw4p4aRGK5g5S8JijBoZzVC1TCS+ljxJElJ9KZvKAwrGbGg0orh21chTvP+Ln7P5vS72cXQMMrBXF34T0Y+GxS3QSI6/YXVdQwo8OKBJP7QfDdYJHPxxVJRyWGpMCGWnMCM3+I=
On Friday 27 January 2006 14:40, Evert Glebbeek wrote:
> Yes. This actually raises another problem: the gfx_capabilities flags are
> almost all taken. What do we do with new capabilities that we might add?
Deprecate gfx_capabilities and make a get_gfx_cap_status() function. You'd
pass it the same flags as it has now. For the flags, if the top bit is not
set on the given flag, it'd basically just check gfx_capabilities and return
TRUE of FALSE. If the top bit *is* set, it'd check against an internal
gfx_capabilities2 variable and return TRUE or FALSE.
int get_gfx_cap_status(uint32_t flag)
{
if(!(flag&0x80000000))
return (flag&gfx_capabilities) ? TRUE : FALSE;
flag &= ~0x80000000;
return (flag&gfx_capabilities2) ? TRUE : FALSE;
}
This would give 62 potential flags, which should be enough for the 4.2 branch,
while something better can be done for 4.3+.