Hi Arman, >> the reason why this threshold exists in the first place is that when you show the pairing list in your basic UI that the entries not keep jumping around like crazy. When we added this code 8 dBm made sense for that. That allows that you select an entry in the devices list successfully by touch or mouse. Since sorting close by devices at the top makes more sense than doing things alphabetical. >> > > Looks like we order them according to the order in which they were > discovered in Chrome OS :P Aside from that though, isn't it a bit > strange to set this threshold based on UI a use case? If I'm building > a UI around this and entries are jumping around like crazy, then this > seems like a UI problem and not a bluetooth daemon problem and I can > go and set a new threshold myself in the UI code. the D-Bus API have all been designed with user interaction in mind. So it makes sense to impose this kind of extra thresholds. That is why you can map D-Bus things 1:1 to your UI and it will all nicely work. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
