Signals are a simple way of triggering signal
events in multiple scripts at the same time.
Whereas, simple aliases can't be called in multiple scripts at the same time.
The way I understand it, mIRC doesn't do 2 things at the same time. It does 1 right after the other.
So let's talk about multiple scripts. If I have a /dothisalias that triggers for an on text, join, and quit event, and all 3 happened, then mIRC will perform the alias 3 times in a row, in the order the server sent in /debug @debug. So isn't this the way mIRC performs an alias in multiple scripts? Is this what you meant by multiple scripts? How does the signals make the advantage?
By default the signal is triggered after all current
scripts have finished executing. You can however use -n to make the script trigger immediately.
Okay, so this is a way to get the more important stuff done first. I see that as a benefit. But so using the -n switch is pretty much the same as calling an alias?
This statement clearly shows that in some particular cases, signal events are better
to use than any other method.
For example, in a protection script, you could just use a signal with the -n switch.
This will make your protection script react before all other scripts.
Okay, seems like signals are all about order.
-Neal.
