From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Bastien Nocera To: BlueZ development In-Reply-To: <1185347068.7111.91.camel@violet> References: <1185293793.3641.129.camel@cookie.hadess.net> <1185311688.7111.72.camel@violet> <1185315051.3641.189.camel@cookie.hadess.net> <1185318541.3641.195.camel@cookie.hadess.net> <1185347068.7111.91.camel@violet> Date: Wed, 25 Jul 2007 08:33:23 +0100 Message-Id: <1185348803.3641.213.camel@cookie.hadess.net> Mime-Version: 1.0 Subject: Re: [Bluez-devel] [PATCH] Make BluetoothClient work on all adapters Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net On Wed, 2007-07-25 at 09:04 +0200, Marcel Holtmann wrote: > Hi Bastien, > > > > > However this includes that we have to monitor if the default adapter > > > > changes or one adapter gets removed while being in the adapter selector > > > > widget or device selector widget. > > > > > > Fair enough, I knew this would be a sticky point. I'm trying to fix it > > > up so that we use the default adapter by default with "NULL" passed as > > > the adapter. > > > > Here goes. This should correctly kill the disco on the old default > > adapter and re-enable it on the new default adapter, when the default > > adapter changes. > > you patch is wrong. You are messing up a DBusConnection object with the > BluetoothClient object in the callbacks of the DefaultAdapterChanged > signal. > > Actually I also don't like this way, we should store the default path > globally since that is what really counts. The tree storing all > information should be fully valid as long as we have an instance of the > BluetoothClient object and it can store the information about the > default adapter for us. The tree storing all information is still valid, there's no information there as to which is the default adapter. And to be able to use the default_adapter in the instances, you need to connect to the signal in the instances. If you're not interested in stopping the existing discoveries on the default adapter when the default adapter changes, or transferring those discoveries to other devices, then it will be much easier. I'm not sure why we would carry on discovering devices if the model showing the devices is going away though. So, the only thing I'm supposed to do, is change the model automatically, so that when we get the model for the default adapter, the model should change automatically. That will require the DefaultAdapterChanged signal to live in the instance, as in my patch, as globally, we don't have any knownledge of the instances. -- Bastien Nocera ------------------------------------------------------------------------- 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