quote:
Originally posted by deAd
The API can be used with the ActiveXControl object.
code:
var MessengerAPI = new ActiveXObject("Messenger.UIAutomation.1");
This might not work on all machines, and some features (like groups) will not be accessible/may crash wlm.
Never use the ".1", ".2" or whatever as a reference. This is part of the reason why it doesn't work on some machines. Those identify the versions so to speak, of the activex objects. Specifiying them will cause Windows quite often to not find the proper 'versions'.
see
CookieRevised's reply to [Question] Any way I can get a Winsock ActiveXObject working ?
Also note that each time you use 'ActiveXObject("Messenger.UIAutomation")' a new object is created which will lead to out of memory problems, and maybe even crashes, etc very rapidly.
Hence, I suggest to not use this in scripts...
related:
http://forum.mess.be/index.php?s=73b0a25dcb617f93...5b&showtopic=19108
http://forum.mess.be/index.php?showtopic=55 (<= SpunkyLoveMuff, read this also)
http://forums.fanatic.net.nz/index.php?showtopic=5799
http://www.devhood.com/tutorials/tutorial_details.aspx?tutorial_id=478
quote:
Originally posted by SpunkyLoveMuff
I've been working in VB6 all night figuring out the API commands so I could write a DLL to use or something. That seems likes a good solution that you posted, but why does it make Messenger run in the background?
If you want to use a DLL, you don't need what has been posted before. See forums like MSNFanatic for more info on how to create a DLL which references the Messenger API.
Or you can also find a lot of examples in the plugins section on this forums.
Also, in VB6, you can use the object browser to get all the available objects, properties, functions, etc at your disposal (after you have created a reference to the Messenger API).
Messanger API
/ 
