In addition to what theRat said, the answer depends on the keys, for example you can capture F-keys. If thats what you wanted then /help function keys. If thats not what you wanted, then theRat is correct.
I'm hopeful, that the next version of mIRC will let you work with the tab key. That feature has been requested numerous times, so maybe Khaled will add it in the next version.
I wouldn't settle for just the tab key. I see no logical reason to prohibit KEYUP/DOWN events from working in #channel windows (which capture ALL keystrokes). Other means already exist to write "spy scripts", and due to the nature of these scripts the scripter has no remorse for using resource intense methods like /timers and $editbox.
I don't believe KEY* events will have any negative impact or amplify the problems that already exist. It's just really annoying that we have to write Custom @Window Channel Scripts enable to use this resource.
- Raccoon
Well. At least I won lunch. Good philosophy, see good in bad, I like!
Well Khaled (who is the person I'll believe on the matter) seems to think it will. He says it will signifigantly impact performance. I take this to mean he at one point tested ON KEYUP/KEYDOWN for all windows and found it to slow things down.