mIRC Home    About    Download    Register    News    Help

Print Thread
Joined: Feb 2003
Posts: 2,812
Raccoon Offline OP
Hoopy frood
OP Offline
Hoopy frood
Joined: Feb 2003
Posts: 2,812
Dear Khaled,

I was pondering the idea of an $EventOutput identifier and whether it would be a useful feature to suggest for people that are attempting to customize the echo'd output of a given event.

Then it occurred to me: What if we make it writable &binvar instead of a read-only $identifier?

Would you be able to supply users with a binary variable that magically exists in all events, pre-populated with the event's output text, that users can modify with /bset, etc? Any changes the script makes to &EventOutput will directly alter the message that mIRC displays?

Using &binvars as internal memory pointers to quickly hack the way mIRC functions!

Code:
On *:TEXT:*:#mIRC: {
  echo -tic info $chan $bvar(&EventOutput,1-).text
  bset -t &EventOutput 17 W
  bset -t &EventOutput 22 !
  bset -t &EventOutput 1 (
  bset -t &EventOutput $bfind(&EventOutput,1,>) )
}

[01:23] <MadGoat> Hello world.
[01:23] (MadGoat) Hello World!


Well. At least I won lunch.
Good philosophy, see good in bad, I like!
Joined: Feb 2003
Posts: 2,812
Raccoon Offline OP
Hoopy frood
OP Offline
Hoopy frood
Joined: Feb 2003
Posts: 2,812
Addendum: This would only work in the ^-prefixed events prior to text being printed to the window. (As pointed out by Ouims)

On ^*:TEXT:*:#mIRC: {


Well. At least I won lunch.
Good philosophy, see good in bad, I like!

Link Copied to Clipboard