mIRC Home    About    Download    Register    News    Help

Print Thread
#116806 09/04/05 05:30 AM
Joined: Dec 2004
Posts: 12
V
Pikka bird
OP Offline
Pikka bird
V
Joined: Dec 2004
Posts: 12
on *:OPEN:*:*:{ command here }
(fully right according to the help file)

gives me .. *:{ unknown command (and then the command doesnt run anyway)

if i leave off the *: for the matchtext, it doesn't work at all.

on CLOSE seems to work okay, as long as i don't put a matchtext thing in there. is this a bug or am i stupid?

#116807 09/04/05 05:48 AM
Joined: Aug 2003
Posts: 314
S
Fjord artisan
Offline
Fjord artisan
S
Joined: Aug 2003
Posts: 314
The only time you'd include the matchtext part is solely for a query open event (on *:open:?:*:{). For :!: :=: or :*: don't include the second field, on *:open:*:{ in this case

You say if you leave off the matchtext it doesn't work, what type of window are you testing it with? On open won't trigger when a custom window is opened, but then again you wouldn't have gotten the initial '*:{ unknown command' error

On close doesn't take the matchtext parameter, it wouldn't make much sense since there's never any text assosciated with the events it triggers for

#116808 09/04/05 06:06 AM
Joined: Dec 2004
Posts: 12
V
Pikka bird
OP Offline
Pikka bird
V
Joined: Dec 2004
Posts: 12
on ^*:OPEN:*:.timer -m 1 100 ssbar.refresh

^the exact code i'm using. nothing happens. i'm trying to catch the opening of query windows. i've tried using :?: and :?:*: and leaving off the ^ prefix and changing the * level to 1, and nothing seems to work.

*edit : btw, i noticed the *:{ unknown command .. was when i was trying to use the matchtext with the on CLOSE event.. that's working fine now. the TIMER is there because if i don't use it, the on CLOSE event doesn't register that anything has changed.

Last edited by vexation; 09/04/05 06:11 AM.
#116809 09/04/05 06:20 AM
Joined: Aug 2003
Posts: 314
S
Fjord artisan
Offline
Fjord artisan
S
Joined: Aug 2003
Posts: 314
Your code is fine for me (Windows XP, mIRC 6.16). For it not to trigger at all I can only guess that you're opening the query window on your side via /query? If so, note that the event isn't made to trigger when you open it yourself


Link Copied to Clipboard