diff options
| author | Bastien Nocera <hadess@hadess.net> | 2017-10-18 03:58:05 +0200 |
|---|---|---|
| committer | Szymon Janc <szymon.janc@codecoup.pl> | 2017-10-27 09:58:06 +0200 |
| commit | c50a8a397d4abd994a9115230279d5fe922b4aa5 (patch) | |
| tree | 496f43c82baea8a96145fe4a4f37308d85c44f28 /doc/agent-api.txt | |
| parent | bdfe5fcee3c8a3013d4866ebf573abb1a3e342be (diff) | |
| download | bluez-c50a8a397d4abd994a9115230279d5fe922b4aa5.tar.gz | |
adapter: Add btd_request_authorization_cable_configured()
Add btd_request_authorization_cable_configured() function to allow
cable configured devices to ask the user straight away about whether the
device should be allowed to connect to the computer.
This allows us to ask the user at the time of the USB connection and
initial setup, rather than when the first Bluetooth connection is made.
The fact that the device might not be connected to the adapter when
this event is triggered is mentioned in the Agent API docs.
Diffstat (limited to 'doc/agent-api.txt')
| -rw-r--r-- | doc/agent-api.txt | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/agent-api.txt b/doc/agent-api.txt index 801ccb665..0d9347cab 100644 --- a/doc/agent-api.txt +++ b/doc/agent-api.txt @@ -163,7 +163,10 @@ Methods void Release() This method gets called to request the user to authorize an incoming pairing attempt which would in other circumstances trigger the just-works - model. + model, or when the user plugged in a device that + implements cable pairing. In the latter case, the + device would not be connected to the adapter via + Bluetooth yet. Possible errors: org.bluez.Error.Rejected org.bluez.Error.Canceled |