From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: Claudio Takahasi <cktakahasi@gmail.com>
Subject: Re: [Bluez-devel] [PATCH] Attempt bonding with keyboards.
Date: Sat, 22 Sep 2007 20:57:15 +0200 [thread overview]
Message-ID: <1190487435.5133.66.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <1190483342.7150.224.camel@pmac.infradead.org>
Hi David,
> My Nokia SU-8W keyboard will never attempt to reconnect to the computer
> after a power cycle unless we actually pair with it. With the input
> service as it currently stands, we don't -- so it works once, but then
> next time I want to use it I need to go through the whole search and
> 'add new input device' process again (and the bluetooth-properties
> applet crashes when you try to add a device which already exists, which
> is not so cute).
the main questions is if we wanna make that policy of pairing a device
first part of the input service or the the UI creating the device.
I think it should be part of the UI and it should create the pairing
before connecting the input device.
With the move to CreateDevice and CreatePairedDevice this all will
become obsolete anyway.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-09-22 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-22 17:49 [Bluez-devel] [PATCH] Attempt bonding with keyboards David Woodhouse
2007-09-22 18:57 ` Marcel Holtmann [this message]
2007-09-22 21:00 ` David Woodhouse
2007-09-22 23:10 ` David Woodhouse
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=1190487435.5133.66.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=cktakahasi@gmail.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