Creating hash tables in place of global variables, even single infrequently used ones? I don't like this idea, even if there are 3 or 4 cpu cycles saved. In the long run it's sloppy (to me), and harder for newbies to work with.
I'd stick with the global variable /sets, changing them to /set -e (unsets when client is closed), and check if the variable has been initialized yet. Such that a version reply is selected at random the first time you are /ctcp versioned, and the same reply is sent for the entire session of multiple version requests.
Sending a different reply seconds apart will only prove you're faking it.
Looks like a lot of nice work. I'm going to test this one tomorrow. Though, it appears the bottom of the script might be cut off... at least a closing } anyway.
Oh Wow. Yeah, AHK is much more capable than this. For starters, you could reuse most of that code by letting each 'hotkey' fall-through to the next. But ultimately a key logger in AHK is no more than 5 to 15 lines, natively or by cheating with WinAPI hooks.
SunnyD: don't blame AHK. It's really much more elegant.
I have never tested this script or any version of AutoHotkey on Windows 7. You may have to run it as Administrator for it to poke at other processes' window properties.
Whole thing has been re-arranged to a simple inline structure, and stripped and reduced the overly wordy commenting. Also fixed a bug with the flood prevention, and added awareness for other higher-than op modes.
Bizarre. I just noticed in all the time I've had this script up (and everyone who's commented positively on it), I only have 3 reviews for an average of score of 2.7 of 10. If you're one of the dozens of people who use, like, praised or have joined my channel asking for features to customize it, might I suggest a rating of "10 (Best)"? ^_^ Thanks.
I would never post a script open to the public that didn't educate the user about how it works, line by line, to teach them how to script and to protect them from rogue code. It is my intention to make this a common practice to the point where users demand it or find someone else's script, or better yet, write their own from the knowledge gleaned by cleverly crafted and commented example.
gooshie: Indeed, for two different cases. $0 indicates that parameters have been passed, so display the error message along with the help. Otherwise, no parameters have been passed... so just display the help (no error).
gooshie: Interesting find. I'll have to fix that. It -should- be passing the variable contained string as the first parameter of the identifier ($camel) and not as a naked string across parameters. Oops. :)
