Hi All,
I want to trap inRange and outRange event of the bluetooth device i.e. paired with my windows7 machine.
Thanks in advance.
Hi All,
I want to trap inRange and outRange event of the bluetooth device i.e. paired with my windows7 machine.
Thanks in advance.
So do you have an actual question?
Or do you just need hand-holding through MSDN Library
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
Originally Posted by Salem
Hi salem,
thanks for your interest.
i want to know how to achieve this goal.
inRange means that windows7 machine equiped with bluetooth can search the device and outRange means that machine cant search the device.
I am using the various bluetooth api's of windows7.
like BluetoothAPIs.h, bthdef.h,winsock2,Ws2bth etc.
i am able to trap the event when any new device is getting ad to my machine or removed from machine.
but not able to trap the situation once the authenticated device is getting out side the range of my machine. or comes inrange of my windows machines bluetooth.
Did you even bother to follow the link Salem gave you?
In less than 5 minutes I found this... Bluetooth and WM_DEVICECHANGE Messages (Windows)
HI,
I am already go through with this library.
and i have tried it as well. through this library i have able to get the event at time of pairing and removing from windwos machine, while i have a paired device with my bluetooth enabled windows 7 machine and i m taking away the device out side the range of my machine's bluetooth that time i am not able to receive the any event same way when i am bringing my device close to my machine that time also i am not able to receive any event like inRange. i have also used with the same GUID as provided in your link.
I am affraid about is it possible or not?
for a mean while to accomplish this i am trying to connect the device after some time that device is in range or not by performing a connection to it.
any suggestion.
But isn't that what BT is supposed to do - if it's in-range, it gets paired automatically and the pair is broken when the device moves out of range.
Yes, there will be some very low level event saying in-range, but my guess this immediately triggers pairing where this is allowed.
You could try seeing what happens when you use a non-registered device. The "in-range" event would then appear as the "new device detected" or something like that.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
