| Re: [AD] Problem with remove_mouse() and video bitmaps. |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] Problem with remove_mouse() and video bitmaps.
- From: Stef <stapostol@xxxxxxxxxx>
- Date: Fri, 30 Dec 2005 10:45:13 +0200
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:to:subject:references:message-id:date:from:content-type:mime-version:content-transfer-encoding:in-reply-to:user-agent; b=Ne1xYJlewTnCCJcMpFQmp+2Bf7KD4CC7Ix5xdNE4K6BFnYeSO+4Icr60mcqbuYNKUTowibIUhX9Zx5WnzVK8pVcw10mS+Mbq6FqWZSbzK87QYqfdsmSeFC7YHMoshBt9xGsmr3FLbQ+a2WQD37Mac/mCKdb2uCXWgbSvkpMF6vk=
On Fri, 30 Dec 2005 10:24:44 +0200, Peter Wang <tjaden@xxxxxxxxxx> wrote:
+ Note: you must not be showing a mouse pointer on a bitmap at the
time that
+ the bitmap is destroyed with destroy_bitmap(). This does not apply to
+ `screen' since you never destroy `screen' with destroy_bitmap().
If the destroy_bitmap() function automatically nulled out the bitmap
pointer, it would be trivial to add a check to avoid drawing onto an
invalid bitmap. While this wouldn't be the end of this kind of problems,
it would help allegro become more robust. It wouldn't break compatibility
either (though programs using an old dll would be more crash prone).
Is there an obvious reason against this that I missed? (very probable).
Otherwise, I think I could submit a patch for this one if the following
days.