dhamlinmusic

@NVAccess @main @mastoblind Yeah, I found that placing the focus over something like the system clock prevents it from requiring pulling out the qwerty keyboard to get the display working after a few hours, the object updating every minute seems to be enough to get the display out of just showing "braille display" when it reconnects and I enter terminal mode. It just seems to need something to trigger the focus enough to need it to update the display.

@main @mastoblind I did find making sure the focus is over the system clock when disconnecting the display and leaving the PC idle does work for this, the clock causes #NVDA to update every minute which will update the display and bring it back to working without needing to do anything with the qwerty.

@NVAccess @main @mastoblind This a applies to screen savers as well, the braille display cannot wake the PC from it.

@NVAccess @main @mastoblind Ok so the braille display not working on secure screens I'm thinking is a microsoft being stupid issue, I realize that this also happened when using a display over USB with narrator itself, bet they are blocking peripherals beyond m&k from interacting with those. The issue where the display is unable to do anything when the PC is first turned on, or has been disconnected for more than like 10min until something is pressed on the qwerty however seems to be #nvda, I checked all the bluetooth and power settings and they are correct.

@NVAccess @main @mastoblind Oh additionally if the PC is left idle for a while or restarts the braille display will just read "braille display" until focus is moved with the qwerty.

@NVAccess @main @mastoblind Not sure, this is the first time I have had a working PC and time to get the display set up with it and NVDA, but this happened' right away. Best I can tell is it's the same issue. Also where do I go to clear the secure screen profile, cannot figure that out, do not need it if it's not fixing this.

@NVAccess @main @mastoblind Ok found this issue being reported back over a decade. https://github.com/nvaccess/nvda/issues/2315

I found a handful of others that were closed for being duplicates of this original issue, or one of a couple other identical ones.

@NVAccess @main @mastoblind Yeah I will try and get to that, the consistant things are that any screen that is flagged as secure cannot be acted on by the #brailledisplay, even if #nvda is running with elevated permissions, examples are the lock screen and the windows UAC dialogues, such as the one that pops when giving NVDA permission to run on the lock screen. Saving a config to use on secure screens did not make any difference.

@NVAccess @main @mastoblind Assuming April 2024, whatever one is downloaded from the main download page, and using a Bi40x, the display connects and shows the information o the lock screen, but cannot move focus or do anything itself.

@main @mastoblind @NVAccess additionally, even after enabling #NDA on the login screen it refuses all input from a connected braille display, preventing unlocking the PC. Also, interacting with Windows UAC dialogues does not work either, and was not accepting qwerty input, which meant to place focus on the desired choice required someone to move focus with the mouse.

Windows 11 Pro 2024h2 latest updates, and latest version of NVDA downloaded today.

@fastfinge @thistledown I did not realize we’re basically same age, also yes I use UEB but have only been using #braille for just under 2 years, and have also been learning the older codes because of written works not being in UEB.