On Tue, 2007-07-24 at 23:10 +0100, Bastien Nocera wrote:
> On Tue, 2007-07-24 at 23:14 +0200, Marcel Holtmann wrote:
<snip>
> > 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.

If the default adapter changes but we didn't start a discovery using the
default adapter, then it's up to the application to start/stop it
anyway.

It will also make all the functions taking an adapter use the default
adapter when NULL is passed.

We should also kill discovery on all the devices when the object goes
away, and move the treestore, and dbus connection to the class, rather
than using statics. But that's for another patch.

That should allow the rest of the wizard cleanups getting in, as well as
the device selector, and then the browse menu implementation.

Cheers

-- 
Bastien Nocera <hadess@hadess.net>