Something else I forgot to mention. Using On :Dialog:KillKline::*: really seams like a good idea but in reality it isnt. The reason is the fact that the dialog event covers mouse movements so any time the mouse is moved over any pixel in the dialog it triggers an event. This normally is no big deal when we dont monitor it but using your on dialog event you are and it actually has to process 6 lines before it knows it doesnt need to do anything.

To see what I mean you can try one of two things, either open the task manager in windows and have a look at the mirc.exe cpu usage and see what its at then open your dialog and move the mouse around on it and youll see this actually impacts the CPU. Depending on the pc will have a lot to do with the % but for me it seems to be about 3-10 percent because Im on a laptop. The other way to really visually see how much information this is would me to go ahead and make a little test by adding a new line at the top of your dialog event to echo every line to a window or the status window. IF you do that Im sure youll be amazed at the amount of events that fly by wjen you move your mouse.

Anyhow I just thought I should let you know. This is the one case where I actually think that multile events are better than one.