Well, not really, lately there have been some questions on how events are processed specifically when attaching to Skype via the Skype4COM lib.
Sure, this could have been done with message boxes or some list of events displayed as they are received, but this is more fun to use, no breakpoints you get them all.
Current Events supported are:
Attach
ConnectionStatus
UserStatus
You can hear how to avoid timeouts and what events come in what order.
You can hear what happens if you need to start Skype.
You can hear what happens when you start Skype and the user is not logged in yet, what happens then?
You can hear what happens when Skype is already running and you attach.
You may be amazed at how events come in, and in what order, they are not always the same order, this can help you plan for the unexpected events and make your code do proper initialization during your attach requests in all cases, when Skype is already started and when Skype is not running and you need to start Skype.
More events will be added, currently this supports events you will need to be concerned about during initialization with Skype using the Skype4COM lib.
Did you know for example that the simple act of looking at what programs are in the list of programs allowed will generate a API Available attachement event? Can your code handle that?
This is very easy to use, new events can be added easily for testing, It is based much on the ULRTCS - Universal Real-Time Chat Speaker logic.
It is Internet Explorer based and uses the Skype4com lib.
Note: Because the Skype4COM lib is also in Beta if it is not already installed and you wish to have it installed via ActiveX, you will need to change your Internet Explorer security settings to prompt for unsigned ActiveX controls.
If you open the page and nothing happens you will need to download and install these 2 additional downloads from Microsoft:
http://activex.microsoft.com/activex/contr...api/spchapi.exe
http://activex.microsoft.com/activex/contr...nt2/tv_enua.exe
Here is the link feel free to look at the HTML source to see what it is doing:
http://testing.onlytherightanswers.com/sky...SESforSkype.htm
Try using it multiple ways:
1. Without Skype running. Launching Skype with auto-logon.
2. Without Skype running. Launching Skype without auto-logon.
3. With Skype running.
4. Change User status.
5. Sign out. Sign back in.
6. Quit Skype.
This will give you and idea of the Skype4COM events that are available to your program when the above things take place.
If you have any questions, please post them here.
Eventually ("No pun intended
") this tool will support ALL Skype4COM events so it can be used as a test tool, as good as some of the other tools are like msgapitest and SkypeTracer they do not announce Skype4COM events so if you are having problems with your code, you can also run this along side your code while you are testing to see if your code in fact is processing the Skype4COM lib events as it should be.