You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: extras/controllerClient/readme.md
+11-2Lines changed: 11 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,21 @@
1
-
# NVDA Controller Client API 1.0 Documentation
1
+
# NVDA Controller Client API 2.0 Documentation
2
2
3
3
## Introduction
4
4
5
-
This client API allows an application to communicate with NVDA, in order to do such things as speak text or braille a message.
5
+
This client API allows an application to communicate with NVDA 2024.1 and above, in order to do such things as speak text or braille a message.
6
6
7
7
The client API is implemented as a dll (dynamic link library). The functions in this dll can be called from any programming language that supports looking up and calling of any symbol in a dll (such as ctypes in Python), or by linking to it for languages like C and C++.
8
8
9
+
## Compatibility notice
10
+
11
+
Version 2.0 of the controller client was introduced in NVDA 2024.1, offering the following additional functions compared to version 1.0:
12
+
- nvdaController_getProcessId
13
+
- nvdaController_speakSsml
14
+
15
+
These functions are supported in NVDA 2024.1 and newer. On older versions, they return error code 1717 (RPC_S_UNKNOWN_IF).
16
+
9
17
## Security practices
18
+
10
19
Developers should be aware that NVDA runs on the lock screen and [secure screens](https://www.nvaccess.org/files/nvda/documentation/userGuide.html#SecureScreens).
11
20
Before providing information to the end user (e.g. via `nvdaController_speakText`), developers should check if Windows is locked or running on a secure screen to prevent secure data being leaked.
0 commit comments