public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH]	bluez-gnome:	"search"	button	for	the	device selection
Date: Fri, 27 Jul 2007 22:16:17 +0200	[thread overview]
Message-ID: <1185567377.13228.38.camel@violet> (raw)
In-Reply-To: <1185565304.2848.56.camel@cookie.hadess.net>

Hi Hadess,

> > > > patch has been applied. However I am not okay with some of the callback
> > > > names, but we can fix that later.
> > > 
> > > Let me know what you want renamed to what, and I'll fix it up.
> > 
> > I disabled the search button support. I crashes the applet. Main issue
> > is your handling of starting and stopping discover process and then
> > listening for the complete signal to change the button state. That is
> > wrong we have to track the state for an adapter being in discovery or
> > not inside the tree model. Otherwise we end up with a lot of race
> > condition. We also need to check if an adapter is already running a
> > discovery or is using periodic inquiry.
> 
> How else do you want to implement it? What's the backtrace from the
> applet that you've seen?

the Bluetooth client should exists only once per application. We don't
need multiple. So it is needed that we create that object only once and
then keep it alive until end of application.

We also need to track the status of the discovery procedure inside the
tree store. Then we only have to check for that there. The tree store
has a reference count and so we can't run into problems there.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2007-07-27 20:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26 18:49 [Bluez-devel] [PATCH] bluez-gnome: "search" button for the device selection Bastien Nocera
2007-07-26 20:17 ` Bastien Nocera
2007-07-27  9:18   ` Bastien Nocera
2007-07-27 15:30     ` Bastien Nocera
2007-07-27 17:09       ` Marcel Holtmann
2007-07-27 18:39         ` Bastien Nocera
2007-07-27 19:02           ` Marcel Holtmann
2007-07-27 19:41             ` Bastien Nocera
2007-07-27 20:16               ` Marcel Holtmann [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=1185567377.13228.38.camel@violet \
    --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