From: Marcel Holtmann <marcel@holtmann.org>
To: David Stockwell <dstockwell@frequency-one.com>
Cc: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] UPDATE: org.bluez.Adapter Methods/Signals
Date: Tue, 8 Apr 2008 20:56:47 +0200 [thread overview]
Message-ID: <7698E157-DB74-482D-9442-2B9C035B5A62@holtmann.org> (raw)
In-Reply-To: <00f801c899a1$946db020$6701a8c0@freqonedev>
Hi David,
> To be clear, I have registered the RemoteDeviceFound and
> RemoteNameUpdated signals against both "/org/bluez/hci0" AND "/
> hci0" (both
> with "org.bluez.Adapter" interface). Signals for these signals
> always come back against "/org/bluez/hci0", and NOT against "/hci0"
> (path retrieved with dbus_g_proxy_get_path).
why don't you actually read the API documentation. Nobody said that
you can expect RemoteDeviceFound and RemoteNameUpdated on /hci0 and
you really can't. They are not sent. You get a DeviceFound signal.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-04-08 18:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 22:45 [Bluez-devel] UPDATE: org.bluez.Adapter Methods/Signals David Stockwell
2008-04-07 22:58 ` Marcel Holtmann
2008-04-08 17:54 ` David Stockwell
2008-04-08 18:56 ` Marcel Holtmann [this message]
2008-04-08 23:07 ` David Stockwell
2008-04-08 23:36 ` Marcel Holtmann
2008-04-09 0:08 ` David Stockwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7698E157-DB74-482D-9442-2B9C035B5A62@holtmann.org \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=dstockwell@frequency-one.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox