First of all I would like to thank all of you to bring support for protocol converter into NVDA.
Here is one problem: Alva Satellite has 2 Satellite keypads, one on the leftside of display and one on the rightside with 6 keys on the each keypads, but NVDA treats them as one keypad. I do not know if it is bug of NVDA or bug of protocol converter, so I have opened this ticket as @LeonarddeR suggested in private conversation.
Steps to reproduce:
- connect Alva Satellite to computer via protocol converter
- wait system to install it on the system if it was not installed already
- from the braille settings choose Optelec bc6...
- turn input help on
- play with keys on Satellite display
Expected behavior:
NVDA should differentiate between Satellite keypads, so NVDA could emulates most of keys which are on bc6 displays.
Actual behavior:
Now NVDA emulates: sp1, sp4, and sp left, right, up and down on both satellite keypads. So there are not: sp2, sp3, spEnter, etouch1, etouch3 and etouch4.
System configuration:
NVDA version:
next: 14941,891a9c9e
NVDA Installed or portable:
installed
Other information:
Windows version:
Windows 10Ver1709 (64-bit) build 16299.248
Other questions:
Does the issue still occur after restarting your PC?
yes
Have you tried any other versions of NVDA?
no
First of all I would like to thank all of you to bring support for protocol converter into NVDA.
Here is one problem: Alva Satellite has 2 Satellite keypads, one on the leftside of display and one on the rightside with 6 keys on the each keypads, but NVDA treats them as one keypad. I do not know if it is bug of NVDA or bug of protocol converter, so I have opened this ticket as @LeonarddeR suggested in private conversation.
Steps to reproduce:
Expected behavior:
NVDA should differentiate between Satellite keypads, so NVDA could emulates most of keys which are on bc6 displays.
Actual behavior:
Now NVDA emulates: sp1, sp4, and sp left, right, up and down on both satellite keypads. So there are not: sp2, sp3, spEnter, etouch1, etouch3 and etouch4.
System configuration:
NVDA version:
next: 14941,891a9c9e
NVDA Installed or portable:
installed
Other information:
Windows version:
Windows 10Ver1709 (64-bit) build 16299.248
Other questions:
Does the issue still occur after restarting your PC?
yes
Have you tried any other versions of NVDA?
no