| Re: [AD] Preparing 4.2.1, issues |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] Preparing 4.2.1, issues
- From: Chris <chris.kcat@xxxxxxxxxx>
- Date: Sun, 29 Jan 2006 16:56: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=OsEp6GnUNvKHaf1XuEdlb362KjODwa1jzAtRYfMlqejPXpBRY9uyRIUOrG3vY9NJ98Md0u9OC6ZVP20UVCWyRe6ADnQv85xRnjyPDV329X6KiClEafthPHgAo+giPEMoPXPYDhats6Ux5I9arqx9+lpPmnbEVuuwKYQRSV+Rar0=
Are we going to add a get_gfx_cap_status()-type function? Might be better to
introduce it now so people start getting used to using it, in-case we start
needing it in 4.2.2 or later.