Riamus2, the ON INPUT event was the first thing I thought about and considered the & prefix, but I can't know what scripts have other people loaded in their mIRC, so I had to forget about it. My script can stop its execution when detecting CTRL+V, but won't stop the other ones.
argv0, I know this is not a clean solution. Several considerations here.
- I wouldn't change the state for this confirmation inside ON INPUT event, but ON ACTIVE. When a channel windows is activated, the Global Status, as you called it, would be changed.
- I have created a separate script, an addon which is loaded by the user, with its own option window. That's the way I programmed it, that's the point. You told about toggling this setting by channel... that's what I want to do but I haven't found any way to do it. Consider I disable the confirm in a one-time basis. Ok, on LOAD that's done, perfect, restarting mIRC one time suppose no problem, of course. The question is: How could I activate this for (simplifying) one channel, from a script?. If the confirmation is disabled and I shouldn't change this global setting, the only "path to follow" is working with ON INPUT, but when there are many ON INPUT catchers through several scripts, it doesn't work: my ON INPUT can have a HALT command embedded which avoids the text being sent to the channel (using $inpaste, for example) but the others ON INPUT would continue their execution normally. Many people use ircap as their main script on mIRC, and this addon have to live with it (or any other script)
If there's a way to avoid pasting for a channel, that would be great, because that's exactly what I'm looking for, but I haven't found other way to do it. This addon I'm programming have to cohabit with the rest of present scripts in the user's client.
Concerning modifying global options. I think the same way, local behaviour shouldn't change global behaviour, but as I told you... find no other way to do it. The same thing could be said about commands which allow changing global options in mIRC. The "correction" of having such commands available is another question as, for example, as long as a single script can change the global DCC aception policy in mIRC.
