Ancestors

Written by Jamie Teh on 2024-11-19 at 06:48

Okay. I finally had enough of git pull and the like making my entire system unusable thanks to UIA event flooding that I took the plunge and switched to Windows Terminal with UIA notification events. I was having trouble with Windows Terminal previously, but that was with diffing. Notification events seem to be working fairly well so far. Let's see how it goes.

One concern I do have is that NVDA necessarily registers for notification events globally, which means that a notification event flood from a background terminal is going to impact performance. Hopefully terminal manages notification events better than it does text events. We shall see.

=> More informations about this toot | More toots from jcsteh@aus.social

Written by Jamie Teh on 2024-11-19 at 07:09

Well that didn't take long. Spamming the console still makes the system pretty much unusable if the console is focused when it happens. But interestingly, if the spam starts in the background or I can manage to alt+tab out (which is very difficult because it's so slow), it seems to behave. That either means that Terminal is smart enough not to send notification events while in the background (but then I'm not sure why NVDA has explicit code to ignore those) or that the poor performance is entirely due to NVDA struggling to process the notification events (but ignoring them is okay).

=> More informations about this toot | More toots from jcsteh@aus.social

Written by Jamie Teh on 2024-11-19 at 07:13

Nope, Terminal notification events are causing a bunch of stuff that isn't actually changing (just scrolling) to be read, so I'm back to conhost. There are no good options. I hate this so much.

=> More informations about this toot | More toots from jcsteh@aus.social

Written by Jamie Teh on 2024-11-19 at 11:33

Ah. My issues with UIA notification events reading text they shouldn't are almost certainly due to me using tmux. I guess it redraws the screen when text overflows or something? Or maybe that's a bug in Windows Terminal's UIA implementation.

=> More informations about this toot | More toots from jcsteh@aus.social

Written by x0 on 2024-11-19 at 17:00

@jcsteh Screen does something like this for me too when I exit a screen, and in fact due to scrollback it causes the entire scrollback buffer in WT to be read out when that happens. Which can hit the speech large chunk delay.

=> More informations about this toot | More toots from x0@dragonscave.space

Written by Jamie Teh on 2024-11-19 at 21:02

@x0 Is this with NVDA set to use UIA notification events? I'm not surprised by it reading a whole bunch of text, but I've discovered it shouldn't delay too badly if you're using UIA notifications, Windows Terminal and have NVDA log level set to info.

=> More informations about this toot | More toots from jcsteh@aus.social

Toot

Written by x0 on 2024-11-19 at 21:03

@jcsteh No diffing, which makes sense I suppose, it un-paints. I didn't think using UIA notification events was stable yet for small updates, especially with progress bars and the like.

=> More informations about this toot | More toots from x0@dragonscave.space

Descendants

Written by Jamie Teh on 2024-11-19 at 21:05

@x0 It definitely has some rough edges. See other posts and replies from me recently regarding tmux settings necessary to make Windows Terminal's UIA notifications behave correctly when text scrolls off the screen in tmux.

=> More informations about this toot | More toots from jcsteh@aus.social