leonardder / rdaccess Goto Github PK

To reproduce the problem, run a portable version of NVDA with this add-on installed in a Parallels VM running windows 11 ARM. I hear NVDA's startup sound and sometimes the message please wait. NVDA doesn't crash, it keeps running, but there is no speech or braille. I have reviewed the log in debug mode and there is no error message generated by the add-on.

NVDA version: I have tried 2023.1 and latest alpha.

Windows version: Windows 11 Pro ARM Version 22H2

This is not yet tested. There is some information from Citrix on how to find out the appropriate channel name by inspecting the event log, but I was unable to dig this up for RdPipe.

There is a long standing NVDA issue about braille on secure screens, see nvaccess/nvda#2315
With the protocol in this add-on, it should be pretty trivial to implement this. As soon as the user session enters a secure desktop, it should start a Named Pipe Server (the basics for named pipe servers are already implemented in addon/lib/namedPipe.py). The NVDA instance on the secure screen should connect to that pipe. The rest should be the same as for Remote Desktop.

As the title says, I use mstsc to connect to the remote desktop, open the NVDA settings panel located on the server, and I find that the options in the 'server' group under the 'Remote Desktop' category are not displayed correctly.

Steps to reproduce

1. The following operations are completed on the remote server.
2. Select remote speech speech synthesizer;
3. Try changing the state of the options checkbox in NVDA Documentation Settings with a space.

Expected performance

It should always be possible to consistently report state changes.

On the server, using nvda+space to switch browse mode or focus mode has no sound.

Steps to reproduce

1. Open a browser and load any web page.
2. After the web page is loaded, press NVDA +Space to switch focus or browse mode.

actual performance

NVDA has no audio feedback and the user does not know which mode is currently in.

expected performance

NVDA provides audio feedback as expected.

There's a problem with braille we can read braille on braille display but we can't use the command thumb braille key etc to use to be able to move the braille display around the screen.

I think that Voice dictionaries aren't coming through (whether local or remote) because the remote side sees the remote synth as its own synth and so generates a different speech dictionary for those, but I can copy over the file as desired.

Originally posted by @tmthywynn8 in #2 (comment)

Steps to reproduce:

1. Make sure the "Capital pitch change percentage" is set to 30 on both the server and the client.
2. On the server, open notepad and try typing uppercase letters and then try typing lowercase letters.

Actual performance

NVDA can't distinguish capital letters by pitch change

Expected performance

NVDA should use speech synthesizer pitch changes to indicate capital letters.

VMware Horizon works in theory, but I have no environment to test it.

The VMware SDK says that every appliance has the vdp_rdpvcbridge.dll bundled with it. Therefore when it is available, it should replace twsapi32 calls. This is implemented properly and I tested that on a non-VMware VM by simply adding vdp_rdpvcbridge.dll to C:\Windows\SysWOW64. However we need to test a real situation for sure.