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] add device selector widget
Date: Wed, 25 Jul 2007 12:34:00 +0200	[thread overview]
Message-ID: <1185359640.7111.118.camel@violet> (raw)
In-Reply-To: <1185356252.3641.236.camel@cookie.hadess.net>

Hi Bastien,

> Here's an updated patch to common/, with the new widget name. I added
> the bluetooth- to the filenames, as it's the GNOME way to show the whole
> namespace in the header filename.

the patch is in the CVS now. Thanks.

> I think we'll need some changes to the client for when there's no
> default adapter (ie. no adapter) and we show the widget, then plug in an
> adapter. Any ideas how you would want that 

If the adapter gets removed we should make the widget insensitive. For
me that looks like the only sane way to do it. We can send a signal to
inform the user and then they can do whatever they think is right.
However any selection itself becomes invalid at that point.

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-25 10:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-24 16:27 [Bluez-devel] [PATCH] add device selector widget Bastien Nocera
2007-07-25  8:04 ` Marcel Holtmann
2007-07-25  8:14   ` Bastien Nocera
2007-07-25  8:26     ` Marcel Holtmann
2007-07-25  9:37       ` Bastien Nocera
2007-07-25 10:34         ` 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=1185359640.7111.118.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