maemo.org - Talk - View Single Post

ajalkane	2012-09-21 , 06:10
Posts: 1,313 \| Thanked: 2,978 times \| Joined on Jun 2011 @ Finland	#103

Originally Posted by jalyst

Bummer, I was hoping we could set conditions based on the BT profile being used...

I know really badly about Bt use cases so I gladly listen to ideas to see what's possible. Of course at the same time I'd like to make as generic condition as possible, so that it would be flexible for different use cases.

Maybe I'm wrong, but I thought having a condition on defined Bluetooth device would be such flexible condition.

Maybe they all are to some extent? In which case it'd be more prudent to set conditions based on whether BT is: "off", "on" or "on & visible".

That one at least would be possible. But I would avoid such a condition if there are alternatives, since there is action for putting Bluetooth off/on/on&visible. Reason being it could cause unfortunate loops of re-evaluating the rules.

I think condition based on whether device is paired or not is way too generic, you usually only need to pair a BT device once :-/

I see, thanks for that. Shows how little I know of using Bluetooth. I thought pairing is like connecting the devices. Unfortunately I see nothing in the APIs to detect when a Bluetooth device is connected. I did see such message in D-Bus, but that won't help if I can't catch the D-Bus messages.

__________________
My N9/N950 projects:

Quote & Reply |

The Following User Says Thank You to ajalkane For This Useful Post:
jalyst