Linux bluetooth development
 help / color / mirror / Atom feed
From: "Claudio Takahasi" <cktakahasi@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Input service usage
Date: Thu, 19 Apr 2007 13:35:20 -0300	[thread overview]
Message-ID: <e1effdeb0704190935j7252456fu5677f66d39e2dcd9@mail.gmail.com> (raw)
In-Reply-To: <462794A6.6000503@access-company.com>

On 4/19/07, Frederic Danis <frederic.danis@access-company.com> wrote:
> Hello,
>
> I am trying to use the new "input" service.
>
> When I use new Service interface, all works fine :
>   ~ # dbus-send --system --print-reply --dest='org.bluez' /org/bluez
> org.bluez.Manager.ListServices
>   method return sender=:1.48 -> dest=:1.55
>      array [
>         string "/org/bluez/service_input"
>      ]
>   ~ # dbus-send --system --print-reply --dest='org.bluez'
> /org/bluez/service_input org.bluez.Service.GetName
>   method return sender=:1.48 -> dest=:1.54
>      string "Input service"
>
> But, I can not access to the input service :
>   ~ # dbus-send --system --print-reply --dest='org.bluez.input'
> /org/bluez/input org.bluez.input.Manager.ListDevices
>   Error org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.bluez.input was not provided by any .service files
>
>   ~ # dbus-send --system --print-reply --dest='org.bluez'
> /org/bluez/input org.bluez.input.Manager.ListDevices
>   Error org.bluez.Error.UnknownMethod: Method "ListDevices" with
> signature "" on interface "org.bluez.input.Manager" doesn't exist
>
> Did I made a mistake ?
>
> Thanks
>
> Fred
>
> --
> -----------------------------------------------
> It is not by improving the oil lamp that one invents the electric bulb!
> -----------------------------------------------
> Danis Frederic                   Access Company
> Software engineer
> Mail : mailto:frederic.danis@access-company.com
> -----------------------------------------------
>
>

Hi Frederic,

Services don' t have a well known name, you can' t send a message to
'org.bluez.input'. You have to call ActivateService to get the Bus id
and send the message to that address.

'org.bluez' doesn't implement input paths or interfaces. I will try
update the BlueZ wiki to explain how the input service works. Give me
some hours.
http://wiki.bluez.org/wiki/Input

btw, the network service has a similar behavior and its documentation
is more complete. Check the wiki: http://wiki.bluez.org/wiki/Network

BR,
-- 
---------------------------------------------------------
Claudio Takahasi
Instituto Nokia de Tecnologia - INdT

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2007-04-19 16:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-19 16:11 [Bluez-devel] Input service usage Frederic Danis
2007-04-19 16:35 ` Claudio Takahasi [this message]

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=e1effdeb0704190935j7252456fu5677f66d39e2dcd9@mail.gmail.com \
    --to=cktakahasi@gmail.com \
    --cc=bluez-devel@lists.sourceforge.net \
    /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