Device Disconnect events

[2inept]

Hi

Running the WifiDirectSoftApp demo the disconnect events do not fire until you click stop.

I've attached a screen shot, where I connected then disconnected, then connected and disconnected.

As you can see the 2 disconnect events fired together and this was when I clicked stop.

Any ideas why this would be happening?

Thanks

Chris

[Mike Petrichenko]

Hi

I have just tested (using latest WiFi Framework version) and it works as expected. However it takes some time (about 1-2 seconds) before OnDisconnect event fires (that is absolutely normal for any wireless connection).

If you click stop when devices are connected than the disconnect event fires for any connected device (cause in fact it is really disconnected).

What OS, .NET version and WiFi Framework version do you use to run the demo?

[Mike Petrichenko]

By the way, how often does your device reconnect? I mean time interval between disconnect and connect?

[2inept]

Hi Mike

I'm using the latest version I downloaded today.

It's compiled as .net 3.5, currently using a Windows 10 machine to test it on.

I have left it disconnected for some time before reconnecting but I don't seem to be getting the disconnect event.

Chris

[Mike Petrichenko]

Can you please rebuild it for .NET 2.0 and test? Win 10: 32 or 64 bit?

[Mike Petrichenko]

Just sent you a fixed version. That should solve the issue with disconnect event. Please, let me know how it works on your side. The version has 7.4.9.0 version number.

[2inept]

Hi Mike

When you say you've sent it to me, where have you sent it too?

Thanks

Chris

[Mike Petrichenko]

By e-mail to address used to purchase.

[2inept]

Hi Mike
I think it

[2inept]

Hi Mike
I think it has been blocked, is it possible to attach it to a PM or PM me a link to download please.
Thanks
Chris

[Mike Petrichenko]

Done

[2inept]

Hi Mike
I'm getting both connect and disconnect now, thanks!
Chris

[Mike Petrichenko]

You are very welcome.

If you installed latest security update for Win 10 you may probably get new issue (that added by the latest update). We are now working on fix for that. I will let you know when we finished with the fix.