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
The Highlight feature's Tip Message doesn't evaluate. Things like $nick or $target or the $1- $highlight() text that was spoken, would be handy to know why you're being highlighted in the tip message. My current tip message is pretty boring and repetitive.

Other dialogs throughout mIRC tend to evaluate identifiers.


Well. At least I won lunch.
Good philosophy, see good in bad, I like!
Joined: May 2017
Posts: 14
Pikka bird
Offline
Pikka bird
Joined: May 2017
Posts: 14
Wow, I thought I was the only one that cared! Causing me to rewrite the notifications entirely.



Happy license owner. smile
Joined: Jan 2004
Posts: 2,127
Hoopy frood
Offline
Hoopy frood
Joined: Jan 2004
Posts: 2,127
Is it feasible to have access to additional local identifiers? If the highlight message in address book is:

$time $network $chan $nick $1-

...the $nick and $1- are not being evaluated, nor would $parms or $rawmsg.

To allow $myalias to identify which highlight triggered for that line, would be nice if either $target could be filled with the highlight's .text property, or $highlight(-1) could relate to the active highlight the way $send(-1) and $get(-1) refers to the send/get which triggered the FILESENT/FILERCVD event. Currently $highlight(N) for all negative numbers returns the same value as $highlight(0), which they don't need to do.

While testing this, I found that /aline works within $myalias but /echo did nothing, whether displaying -s or to @custom, as if it's in a .alias using the -q switch.

The highlight message is chopped at a comma due to being stored as a comma-delimited string in mirc.ini, but that can be worked around like [ $chr(44) ].


Link Copied to Clipboard