[BRLTTY] Windows First Run

[Oriana Neulinger]

Thank you so much for your help so far! She is indeed using NVDA, and Jaws.
The Alva's buttons didn't do anything individually, so that's why i was
hoping to get some keyboard shortcuts... But it looks like once we get it
connected to NVDA she can find out what the buttons do, and a bunch of
other stuff, at least according to the NVDA users here (sharing link for
posterity... and my own later reference)

https://nvda.groups.io/g/nvda/topic/brltty_anything_new/32508993?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,0,0,32508993

What do you mean by enable the API? I'm assuming it's enabled by default,
right? What does it mean that "no-api off" is commented? Or do I need to do
things like run the api executable, create the key, uncomment the path to
the key in the config, etc? Does this executable need to be run every time
brltty is started?

Did we need to use the windows screen driver or will NVDA take care of that?

On Sat, Oct 26, 2019, 7:16 PM Dave Mielke <Dave at mielke.cc> wrote:

> [quoted lines by Oriana Neulinger on 2019/10/26 at 17:27 -0400]
>
> >Ok, so it sounds like the display is "focused" on the command window.
>
> We're getting into an area where I have no personal practical experience. I
> believe the default is for brltty to follow the focused window. The screen
> driver has a FollowFocus parameter that controls this - it defaults to
> yes. See
> the Sticking to the Console section of the document.
>
> >After some research in the documentation I realized i needed to enable
> some
> >sort of keyboard control, so i enabled the keypad one.
>
> No, for two reasons. The first one is that support for keyboard tables
> hasn't
> yet been implemented for the Windows platform. The other one is that a
> keyboard
> table is just another way to do what can already be done from the braille
> device - navigate the screen.
>
> I don't know how well brltty navigates non-console windows on Windows. Most
> users, as I recall, set the screen driver parameter that makes brltty only
> take
> control when on a console window, and then let their normal screen reader
> take
> over when on a non-console window. For example, the documentation
> describes how
> to do this when using JAWS.
>
> Which screen reader is your friend using? If she isn't using one, and if
> she'd
> rather not spend a million or so to purchase one of the commercial ones,
> then
> she might consider using NVDA (which is free). With NVDA, the way would be
> to
> enable brltty's brlapi service, and then to select brltty as NVDA's braille
> driver.
>
> --
> I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
> Dave Mielke            | 2213 Fox Crescent | WebHome: http://Mielke.cc/
> EMail: Dave at Mielke.cc  | Ottawa, Ontario   | Twitter: @Dave_Mielke
> Phone: +1 613 726 0014 | Canada  K2A 1H7   |
> _______________________________________________
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY at brltty.app
> For general information, go to: http://brltty.app/mailman/listinfo/brltty
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://brltty.app/pipermail/brltty/attachments/20191026/b6ebad7e/attachment.html>