| 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:04:01 -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=kDMsm5P4pbsfGcTrcwhOvmAc1XLz/1C7Qm2QZD6hB6mt78cT9HbV+RkwoyO6CNLF+UKW5fKM2IgJ2ZmwaNTpugfZZiLxx5Ljt7XDi2R48RKeDh9MVF5+7UzVPtj41KGG3UptBbeJFkccT2mwP/qUzW3UeISNcMd7Uoa2DMHxDzE=
On Tue, 26 Oct 2004 19:57:25 +0200, Elias Pschernig <elias@xxxxxxxxxx> wrote:
> I think it may be connected to the way Allegro flushes the output from
> the input thread. I.e. there's a call to XFlush() 100 times / second. A
> better approach would be to allow the user to control when XFlush is
> called, maybe in release_screen(). Or maybe this is done already - it
> needs investigation in any case.
Peter supplied a patch that calls XFlush on release_screen (when the
screen is actually released). Results were promising, although it had
worse performance than just having the programmer call rest(0)
regularly.
- Kitty Cat