| Re: [AD] XIM patch for Allegro 4.1.x |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] XIM patch for Allegro 4.1.x
- From: Chris <chris.kcat@xxxxxxxxxx>
- Date: Tue, 26 Oct 2004 17:16:36 -0700
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=C0KdhO/9RrTkg/VgSkzkFt5ud2BK7UjHmiK+ghx4/epb6bZJpr7usez26M/1hiEo1+uuUWka6WTz7jq6X+PjTgJNWTor4eVyJvlq5trZZShGP2ulhq6Ru6etickl6S5s1TYwssKRRzK4w7nh2gr8b1OhDbTnW0P71H0/dbx7wHo=
On Tue, 26 Oct 2004 20:03:04 +0200, Elias Pschernig <elias@xxxxxxxxxx> wrote:
> It's interesting that this doesn't happen with current CVS. Maybe it is
> connected to now using the MMX for color conversion. I don't know which
> of the examples triggered it.. I was going through all of them to test
> the XIM patch, and one example triggered it. I'll put back vsync and see
> which one it is.
Please note that it's probably going to be an extremely rare
occurance. Not that we shouldn't fix it, but you'll probably almost
never run into it (since when the offending code is executed in the
main thead, it'll most likely be while that thread is sleeping. And
when the timer thread wakes up, the retrace counter will more than
likely be incremented before the mouse timer is run.
Another solution may be to do what Doom does/did.. make the vsync
function always wait for (1000/refresh_rate) milliseconds regardless.
Though that does seem ugly, it may be the only clean way to do it.
Unless X does provide a vsync function somewhere?
- Kitty Cat