Re: NVDA remote
Hitoggle quoted messageShow quoted text
NVDA isn't interpreting the keystrokes, It's just behaving as normal in that it takes input from the keyboard and either sees it as an NVDA command, app input or operating system related. NVDA is just acting as a conduit, passing the keystrokes as if they had been typed locally, then passing back text strings output for voicing on the controllers machine.
From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Antony Stone
Sent: 10 May 2019 11:53
Subject: Re: [nvda] NVDA remote
It strikes me that it would be better for NVDA Remote to send not the
keystrokes themselves, which then need to be interpreted by the remote
machine, and rely on it having the same NVDA keyboard layout setting, but
instead to send the NVDA commands which result from those keystrokes, so that
the person on the controlling computer types some key combination on their
keyboard, and the command which this combination means to then gets sent to
the controlled computer, without caring what keyboard language or layout it
On Friday 10 May 2019 at 11:01:42, Chris Mullins wrote:
From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Ján--
"In fact I wanted to be John Cleese and it took me some time to realise that
the job was already taken."
- Douglas Adams
Please reply to the list;
please *don't* CC me.