Register Log In

Forums Bug Reports ON INPUT haltdef vs. DCC Server 'get'

Print Thread

ON INPUT haltdef vs. DCC Server 'get' #237619 22/05/12 08:33 AM
Joined: Aug 2006 Posts: 167 P pishposh OP Vogon poet
OP pishposh Vogon poet P Joined: Aug 2006 Posts: 167	Normally when connected to somebody else's DCC Server (e.g. 1.2.3.4:59), typing the 'get' command causes your mIRC to initiate a separate port 59 connection to 1.2.3.4:59 in order to get the specified file. Code: on :INPUT::{ echo $target $+(<,$me,>) $1- .msg $target $1- haltdef } However the event above prevents that from happening. My understanding of haltdef is that it is only supposed to halt the default text associated with an event, not "everything," so reporting this as a probable bug.

Re: ON INPUT haltdef vs. DCC Server 'get' pishposh #239125 23/09/12 10:17 PM
Joined: Dec 2002 Posts: 5,502 London, UK Khaled Hoopy frood
Khaled Hoopy frood Joined: Dec 2002 Posts: 5,502 London, UK	The reason for this is that the on INPUT event is processed prior to any command and/or script processing. In order to propagate a /haltdef to all subsequent routines, every routine that displays text would need to be modified to take account of /haltdef, which would be an enormous task, if not a little tricky, eg. should /echos also be halted, and so on. So in the context of on INPUT, /haltdef has always behaved just like /halt and it is left up to the script to issue any required commands.

Link Copied to Clipboard