@Boomkop3 Ah I was using it right up until I lost my sight in early 2020

@main @mastoblind So I ended up using DragonsCave itself installed As a PWA with the advanced web interface enabled.

Edit: Turned the advanced web interface off as it made reading replies clunky.

@Kaliah @main @mastoblind Any idea why boosting is not going through? I boosted a few things and when I checked on my phone they were not.

@Kaliah @main @mastoblind With the display and braille extender the hotkeys do not work, and most of them still do not but I can arrow down my feed without it stopping on every mention, link, and button.

@Kaliah @main @mastoblind Ok lol logged in, hotkeys did not work, realized I was in focus mode, had to look up how to get out of it with the display, realized most of my problems with the standard client were because of that…’

@Kaliah @main @mastoblind Not at all, I would rather a Web App over installing software, I looked through the windows store before asking but the options were scarce.

@KaraLG84 @main @mastoblind ah ok, that’s what I get for trusting search engines these days.

@KaraLG84 @main @mastoblind That one I have looked at before and am not sure where you get it, it’s a GitHub thing?

@pixelate @main @mastoblind That did not allow other instances I thought.

@main @mastoblind going on 3 weeks, extremely happy with it.

@NVAccess @main @mastoblind Android so no Siri here lol, yeah my Bi40x is what I use to operate my PC.

@fastfinge Yeah maybe, the machine I got should be able to handle some of that.

@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.