Unfortunately there are still many inconveniences related to using the scriptcontrol in mIRC. As it stands, it serves a purpose, but it is handicapped. Some issues are related with the threading model of the script control being different from mIRC's model. K told me it would require too much work, so using $comcall with the scriptcontrol will never be possible. That alone for me is a huge handicap.
There's also a memory leak when using the scriptcontrol. Additionally, on larger code, you run into the problem of the string too long limit, which means you are forced to split your code up in different functions, whereas you wouldn't need to worry about it with a .vbs file.
One last thing that is unfortunate (though out of Khaled's hands) is that the WSH isn't available in the scriptcontrol, so no wscript.sleep and the likes.
Oh well, it's still better than nothing!
To the original requester: you know you can create a scripting file like .vbs .js .wsf etc. right? That already gives you access to other scripting engines. The biggest problem with this approach is that when you want to release code like that to the public, that many people have Norton etc. running which often disable windows scripting, or atleast show a warning, which is something I really detest. Another drawback is getting the results relayed back to mIRC, usually this needs to go through a file which means disc access, although fortunately I have some sneaky other way to get this done without using a file
So yes, I would prefer to see support for other scripting languages like VBScript.
alias test {
using VBScript {
msgbox "Hello World"
}
using JScript {
var shell = new ActiveXObject("Wscript.Shell");
shell.popup("Hello World");
}
}This is simplistic code of course for illustration purposes.
Haha anyway, the above code will more than likely never happen, but it was fun imagining what it could look like.
