| Re: [AD] Preparing for RC2 |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] Preparing for RC2
- From: Chris <chris.kcat@xxxxxxxxxx>
- Date: Fri, 26 Aug 2005 19:40:50 -0700
- 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=m2uw8Kk08FqQVZ5H1jp0u/ULorgXJioj/WrcGt98uXnjdzRsbKZQ9YVSke0Laqt5k7a+BN4i3zj05GYbUC5M3EF0mh8pMDXD+kytVcC5eZv2o7dWpDGXtjY/FhZn9QkgTgqMQSHMLCnqknbV73uygFAyNdjWT3CYx1Rwr922M2E=
On Friday 26 August 2005 07:01 pm, Peter Wang wrote:
> I will be packaging up RC2 tomorrow. Please point out any patches which
> I've missed or if there are any showstoppers.
What's going to be done about using the mouse on non-video bitmaps? I don't
believe we reached a concensus about that. If you use show_mouse on a memory
bitmap, you'll get errors when you try to draw to the same area of the target
bitmap at the same time as the mouse timer since there is no mutex, nor does
scare_mouse effect the mouse on memory bitmaps.
IMO, we should disallow show_mouse on non-video bitmaps since there's really
no reason to have it (the async drawing won't be visible in real-time, which
is the whole point of it), and any current program that may be trying to most
likely has errors up the yin-yang because of these problems..