|
Originally Posted by able_onar
|
Bryan, (hey let me know if I'm bugging you with too many Q's)
re:
what was the issue there? The reason I ask is that I want to add a BT headset to my current setup with incudes a BT RS-232 (serial io) transmitter. This latter being more important to me than the headset. I wouldn't want to jeapordize the serial communications if the widcomm drivers are not compatible...
re:
I'll look into this one (I need the same functionality) and let you know. I believe it is now possible.
Alex
|
Thanks I'll wait for your findings with regards to the BT headset activating voice command.
As for my BT keyboard problem. It wasn't anything major, it was just annoying to use the Widcomm drivers. See Thinkoutside had their own stowaway keyboard driver which allows their bluetooth keyboard to execute special commands that the generic Widcomm driver cannot understand. Well if I opt to use the Thinkoutside driver in conjunction with the Widcomm driver, I would have to setup my bluetooth keyboard to talk with the Thinkoutside driver each and everytime I plan to use it. But with the MS Bluetooth stack, I only need to set it up once and everytime I activate the bluetooth on my pocket pc, it will automatically be able to communicate with my keyboard. I just thought that if I had to do the setup time and time again, it was just too annoying, which would be fine if there was a reason for me to keep the Widcomm driver like a working BT Headset that can activate voice command for example :) But for now, there was no reason for me to do that, so I opted to revert back. But hey, maybe you can prove me wrong and then I would be glad to reinstall the Widcomm drivers. :approve: