Posted: Fri Aug 11, 2006 7:20 am
beakmyn wrote:1.0.2 fix works.
Great, thanks again for the hint.
beakmyn wrote:It appears then when you go into the transfer screen it does a scan...
Yes sir that's right. The reason for this is as follows:
Windows Mobile knows 2 ways to scan for devices. The first is the winsock way. You create a winsock and use the bluetooth subroutines to scan. The second one is the obex way. You initialize the obex subsystem and let it scan for you.
The first one is used in the main window of btcrawler and has the advantage that I can read out stuff like CoD and so on. The second one is implemented in the transfer window because I need obex involved. The way the obex scan works is that it permanently scans in the background until the obex subsystem is closed (in btCrawler that happens by closing the tranfer window). If a device has been found that does not support the methods I described in my last post it will not be listed again as new device because there is no need to. Due to that a rescan button is not needed. But I will implement a start/stop scan button and recode the message for the event when devices are dropped because they don't support the required methods in the next release.
beakmyn wrote:Send File/Send Message is a little awkward...
You are right. Great screenshots btw... I will create something like this for the next version. Since I'm writing in c++ creating window forms like this is not as easy as drag'n'drop like in vb but it shouldn't be too hard...
Thanks a million for your suggestions and your input!
Cheers