From: "David Stockwell" <dstockwell@frequency-one.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Cc: "Marcel Holtmann" <marcel@holtmann.org>,
"Johan Hedberg" <johan.hedberg@gmail.com>
Subject: Quick Check: calling ListDevices method of Adapter in DBus-GLib-C++
Date: Fri, 23 May 2008 23:40:33 -0500 [thread overview]
Message-ID: <025301c8bd58$5066df70$6701a8c0@freqonedev> (raw)
[-- Attachment #1: Type: text/plain, Size: 584 bytes --]
It appears to me that the proper GType that matches up with an Array of Object Paths is:
dbus_g_type_get_collection("GSList", DBUS_TYPE_G_OBJECT_PATH)
This returns a pointer to a singly-linked list (GSList), which one may iterate through using g_slist_foreach, which calls an iterator function for each Object Path in the list.
A gpointer passed to the iterator function contains the Device path: (e.g., /hci0/dev_00_00_00_00_00_00), and may be cast to a (const char *) for processing as a C/C++ string.
Do I have this right, or is there a better way to attack this?
DS
[-- Attachment #2: Type: text/html, Size: 1362 bytes --]
reply other threads:[~2008-05-24 4:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='025301c8bd58$5066df70$6701a8c0@freqonedev' \
--to=dstockwell@frequency-one.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=johan.hedberg@gmail.com \
--cc=marcel@holtmann.org \
/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