mIRC Home    About    Download    Register    News    Help

Print Thread
#142224 17/02/06 12:22 AM
Joined: Nov 2004
Posts: 842
Jigsy Offline OP
Hoopy frood
OP Offline
Hoopy frood
Joined: Nov 2004
Posts: 842
idano if this has any use what-so-ever but on *:DEBUG:{ } would be nice.


What do you do at the end of the world? Are you busy? Will you save us?
#142225 17/02/06 12:29 AM
Joined: Sep 2003
Posts: 4,230
D
Hoopy frood
Offline
Hoopy frood
D
Joined: Sep 2003
Posts: 4,230
thats pretty much what the /debug -i identifier.alais option does now.

However I can see the advantage of an ON DEBUG since you can only have one /DEBUG -i identifier.alais per server.

#142226 17/02/06 12:34 AM
Joined: Jan 2003
Posts: 2,523
Q
Hoopy frood
Offline
Hoopy frood
Q
Joined: Jan 2003
Posts: 2,523
Again, this is something signals can/should do. Just make the debug alias issue a /signal debug


/.timerQ 1 0 echo /.timerQ 1 0 $timer(Q).com
#142227 17/02/06 02:14 AM
Joined: Dec 2002
Posts: 580
N
Fjord artisan
Offline
Fjord artisan
N
Joined: Dec 2002
Posts: 580
Agreed, but an option for debug to specify a signal name instead, would be nice...
Code:
;Until then
on *:connect:{ .debug -i debugident debugident }
alias debugident { .signal DEBUG $1- }
on *:signal:DEBUG:{ echo -a debug: $1- }


NaquadaBomb
www.mirc-dll.com
#142228 17/02/06 05:56 AM
Joined: Sep 2003
Posts: 4,230
D
Hoopy frood
Offline
Hoopy frood
D
Joined: Sep 2003
Posts: 4,230
That of course assumes every other script is going to be happy to work on that princible, and while /DEBUG isnt an overly common command i would ever expect to find in a script, it would only take one /!DEBUG command to shut down the identifier alias thats enabling the signals, same for the suggestion of having debug itself trip a signal, it only takes another debug command to no longer be tripping the signal.

The reply arguement of course can be said, dont lets scripts in that do things unless you know what there doing and agree to that, and for this i doubt it would be overly hard to locate the problem script replacing/disabling debug and fix it. And of course there really is only so much that one would really need do in a debug alias anyway, log the debug, adjust mirc settings, ignore an unliked ctcp or dcc (such as the old crash ya with to bigger filename bug a version had).

Personally Im not unhappy with how it is, but i wouldnt be unhappy if the suggested method was offered as well.

#142229 17/02/06 11:49 AM
Joined: Jan 2003
Posts: 2,523
Q
Hoopy frood
Offline
Hoopy frood
Q
Joined: Jan 2003
Posts: 2,523
Oh so you meant that on DEBUG would trigger always, that is regardless of whether you did a /debug on before? In that case, yes, there is a difference but it's too small to be an issue imo.


/.timerQ 1 0 echo /.timerQ 1 0 $timer(Q).com
#142230 17/02/06 01:06 PM
Joined: Feb 2005
Posts: 681
M
Fjord artisan
Offline
Fjord artisan
M
Joined: Feb 2005
Posts: 681
I have always wanted ON DEBUG .. this should trigger
whether or not the /debug command was used. However,
I don't believe the output of the /debug command should
have the ability to be altered or halted in any way, this imo
would defeat the purpose of debug. It should first be
displayed in the output window, then call the specified
alias and then trigger the event. I would love to have this
event.

~ Edit ~
Also the specified alias (if any) should not be able
to alter or halt the output to the window or the event.

Last edited by mIRCManiac; 17/02/06 01:11 PM.

Link Copied to Clipboard