[quoted lines by Jason White on 2013/12/15 at 11:57 +1100] >I think this exerpt is what you're looking for. Let me know if there's >anything I've missed.
You got it!. That's the right part. Thanks. >I happen to have the skip blank windows feature enabled and set to "all", >which may be relevant here. Yes, it's very relevant. I now understand the issue. The good news is that the code is actually doing the right thing. The question, however, is is it being too good. :-) Things used to be synchronous. The code would scan forward to find a non-blank window, hit the end of the screen, play the alert tune for that, go back to where it was, and then update the display. oiw things happen asynchronously. Waiting for each note of the alert tune to complete opens up an opportunity for other events to run. What's happening is that a screen update is running in the middle of the alert tune, before the braille window coordinates have been restored to their original position. i'm wondering if it's worth suspending the screen update thread during an alert tune. -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: d...@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.com/ _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
