| Re: [AD] This Allegro app can freeze under Windows 2000 |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] This Allegro app can freeze under Windows 2000
- From: Chris <chris.kcat@xxxxxxxxxx>
- Date: Wed, 28 Dec 2005 15:22:20 -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=g4w63TLmSauyQNIrmEftgCb4QzaoHdlwdUXwBgXMOZmnooVS1tQ6mgcCVvEi7zRmY3S8xawA0bu5mxVJxHip/FIaAEBA+BPyUpEpcUxOX02gF/Kb8rbWhE8t1pOacgxNhXZWhyxCZWa3+2pUIr37kU0udyz6e+GjVvkxPwO1acI=
On Wednesday 28 December 2005 14:38, Andrei Ellman wrote:
> I tried removing scare/unscare_mouse and the problem did not appear. I
> also tried nesting scare/unscare_mouse outside of the
> acquire/release_bitmap and the problem went away as well.
As expected. scare/unscare_mouse aren't drawing operations, but instead are
used to hide/show the mouse cursor, so shouldn't be used in the
acquire/release pair. Given that acquire_screen could have the timer thread
locked, anything that waits for the timer thread (including scare/unscare) to
do something will freeze the program indefinitely. Solution: Don't Do
That. ;)