Dave Mielke <d...@mielke.cc> writes: > [quoted lines by Aura Kelloniemi on 2015/09/14 at 21:56 +0300]
>>So, here are the new results. Now I tested with emacs with up to four windows >>all updating the mode line continuously. I also tested with elinks which also >>has a "clock on status line" feature. >> >>Values 0 and 1 are too small - there is lots of screen flicker. I could not >>notice any difference between values 2 and 3. Even emacs with four windows >>displaying a clock on their mode lines works, even through ssh. > Okay, thanks. Just to be sure, I'll set it to 5. Do you think that's > reasonable? I think. I can imagine that this helps with cursor tracking problems when a slow telnet or ssh link is used. >>I also tried values 5, 10, 20, 40 and 100, but could not get top to behave >>well. > How did they behave poorly? >From 10ms onwards I started to notice slowdown of the updates. It gradually increases so that with value of 100 braille lags so much behind that I can accidentally activate a wrong link or menu item. Value of 100 is not bad though when scrolling by holding down a key, because anyways I need to stop pressing the key in order to see where I've landed. > The other value is already there, and parameterized as > UPDATE_SCHEDULE_DELAY. > It should be renamed now, given the new parameter. It's current value is 15. Great! Could you make these configurable at run time? I would like to set the later value to something between 50 and 100, but I think that it might be too much for some users. It probably suffices if it can be configured in brltty.conf - it does not need to be changed often. But perhaps it would be more in line with other preferences items (such as blinking times and key repeat intervals) if it was in the menu. -- Aura _______________________________________________ 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
