| [AD] Screen destruction documentation update |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: [AD] Screen destruction documentation update
- From: Tore Halse <gnolam@xxxxxxxxxx>
- Date: Fri, 9 Sep 2005 13:11:06 +0200
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type; b=RpmK076fHX3dCc6RUvUOmXaIcxar22dR232Z7pk00WjWFT6MOPFsGFwRVKTSMJY4/6odp6o0k0SGZxmjIdN8Sf61XcdPdlNCIMPb95tHDAdZDc9x3qg455xT65Gutl1BDTgutb4mw7w7AzHgXoY2JiGkqKKJy37InMCpk+EL4Kk=
After seeing several instances of people calling
destroy_bitmap(screen) over at allegro.cc, I thought perhaps the
documentation wasn't clear enough on the subject.
Attached is a tiny documentation update to hopefully remedy this problem.
/T
--
Feed me a stray cat.
--- docs/src/allegro._tx Thu Sep 8 19:21:06 2005 UTC
+++ docs/src/allegro._tx Fri Sep 09 11:05:07 2005 UTC
@@ -4570,7 +4570,8 @@ Allegro supports several different types
<ul><li>
The `screen' bitmap, which represents the hardware video memory.
Ultimately you have to draw onto this in order for your image to be
- visible. It is destroyed by any subsequent calls to set_gfx_mode().
+ visible. It is destroyed by any subsequent calls to set_gfx_mode(),
+ so you should never attempt to destroy it yourself.
<li>
Memory bitmaps, which are located in system RAM and can be used to
store graphics or as temporary drawing spaces for double buffered