Re: [Bluez-users] enabling/disabling in response to ThinkPad hotkey

[Ben Liblit <liblit@cs.wisc.edu>]

Marcel Holtmann wrote:
> The reason for this is that the Bluetooth on/off switches are all
> different and HAL and rfkill is the way to abstract it into a common
> interface. It is not the job of hcid to abstract this.

OK, I see your point.  HAL is supposed to keep other daemons from having 
to worry about such things.  I've conveyed your reply back to the HAL 
mailing list.

That said, it's unfortunate that the end result is an Fn+F5 key which 
does *nothing* useful out of the box.  Even if different users would 
want it to do slightly different things, right now it does *nothing* by 
default.  I'm savvy enough to write my own script that runs as root, 
hooks into HAL D-BUS signals, and responds accordingly.  Most users 
won't do that, so for them, this key is useless.

Oh well.  Between HAL and Bluez, things are much better now than they 
ever were before.  We're not done yet, but at least we're making progress.

-------------------------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users