[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
I haven't investigated this much, but I just wanted to bring it up:
Currently processor-intensive operations using the X11 driver severely
delay the timer. I'm not sure how to describe this, but you can hear the
effect when running the demo game under X, choosing a largish screen
resolution, preferably using a truecolour mode so the palette morphs are
really slow.
If you have MIDI output the effect is noticable in the Ready, Set, Go!
sequence, where the music is "ramping up". Some notes will drag out
longer than usual, and the ones following will try to catch up. Digital
output may be affected as well (stuttering), but I can't be sure
(buffered).
I think it is because of the ENABLE(); DISABLE() pairs scattered
throughout the X graphics code, which would make Allegro miss SIGALRM.
Is it possible to localise the interrupts that are disabled, or maybe some
way to avoid disabling interrupts at all?
Peter
--
tjaden@xxxxxxxxxx - http://www.psynet.net/tjaden/
"There are no passengers on spaceship Free Software - we are all the crew."