From 6a36d0fcf9c819cf5fdcfd7cfc235075639f0d5a Mon Sep 17 00:00:00 2001 From: Johan Hedberg Date: Tue, 7 Mar 2006 21:43:21 +0000 Subject: More fixes to dbus-api.txt --- hcid/dbus-api.txt | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/hcid/dbus-api.txt b/hcid/dbus-api.txt index 8a5fdf58..ca34f2e0 100644 --- a/hcid/dbus-api.txt +++ b/hcid/dbus-api.txt @@ -4,8 +4,8 @@ D-Bus API description for BlueZ Copyright (C) 2004-2006 Marcel Holtmann -Error hierachy -============== +Error hierarchy +=============== Interface org.bluez.Error @@ -569,7 +569,7 @@ Signals void ModeChanged(string mode) This signal can also be triggered by low-level HCI commands. - void DiscoveryStart() + void DiscoveryStarted() This signal indicates that a device discovery procedure has been started. @@ -593,7 +593,7 @@ Signals void ModeChanged(string mode) void RemoteNameFailed(string address) - This signal will be send every time the service daemon + This signal will be sent every time the service daemon tries to resolve a remote and this fails. void RemoteAliasChanged(string address, string alias) @@ -642,8 +642,8 @@ Methods string Connect(string address, string service) string ConnectByChannel(string address, byte channel) This creates a connection to a remote RFCOMM based - service. In comparison to Connect a channel number - is needed. + service. In contrast to Connect a channel number is + needed. The return value will be the path of the newly creates RFCOMM TTY device (for example /dev/rfcomm0). -- cgit