From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Input service signals
Date: Sat, 16 Jun 2007 09:31:20 +0200 [thread overview]
Message-ID: <1181979080.6846.53.camel@aeonflux.inter-touch.com> (raw)
In-Reply-To: <467297DF.2030401@access-company.com>
Hi Frederic,
> I am using the Input service. It is very helpful.
>
> But Connected/Disconnected signals from Device interface are currently
> only sent when connection/disconnection are done through the Device
> interface methods. They are not sent when remote device
> connects/disconnects.
>
> I wrote a patch that move common code between server.c and device.c into
> a new file session.c. This allows to send those signals for all
> connect/disconnect.
I haven't looked at your patch, but I agree that we should send the
signals when the remote device re-connects. I wait for Claudio's or
Johan's comments on that patch.
Regards
Marcel
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-06-16 7:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 13:45 [Bluez-devel] Input service signals Frederic Danis
2007-06-16 7:31 ` Marcel Holtmann [this message]
2007-06-19 12:45 ` Frederic Danis
2007-06-19 14:44 ` Claudio Takahasi
2007-06-19 15:16 ` Frederic Danis
2007-06-19 16:32 ` Claudio Takahasi
2007-06-20 16:06 ` Frederic Danis
2007-06-21 12:36 ` Claudio Takahasi
2007-06-22 17:32 ` Claudio Takahasi
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=1181979080.6846.53.camel@aeonflux.inter-touch.com \
--to=marcel@holtmann.org \
--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