| |
| |
| |
|
Page: 1 2 3 4 5 6
Comments:
<0> if mIRC 5.61 can start DCC chats and sends, but mIRC 6.16 can't on the same computer, and the DCC ports are the same, and all firewalls/antiviruses are turned off, what is causing the problem?
<0> the mIRC 5.61 has an old polaris script, the mIRC 6.16 is a plain vanilla mirc install
<1> maybe polaris is setting your ip/host ?
<1> setting/correcting*
<0> newer polaris with mirc 6.16 also doesn't work
<2> type /localinfo -u
<2> then try again
<3> ooo
<0> its not my computer, im trying to diagnose a problem for a fserv in an...fserving-type channel
<2> good luck
<0> it sends out the WAN address correctly during the dcc chat or dcc send handshake
<2> and how would you know that
<0> the status window does the "DCC Chat ([ip address])" thing
<0> when i receive a DCC chat or send attempt from him
<0> with mirc 5.61, it then initiates the chat or send and all is fine
<0> with 6.16, it times out
<4> eww.. "fserving-type channel"
<0> so, any ideas?
<5> hey quick question, is there a simple func/lib that lets you read from "ini" files? ie lets you parse "categories" and such on the fly
<0> mirc has that built in...readini, writeini...
<4> $readini ?
<0> except ther eis no writeini
<0> its just called something else
<0> wait i lied
<0> there is
<1> there is /writeini
<0> i just forgot how to type correctly in the help index (ill shut up now)
<1> /writeini -n <inifile> <section> <item> <value>
<1> Writes to files in the standard INI file format.
<5> ohh
<5> awesome
<5> thanks !
<1> type /help /writeini
<4> /help $readini
<1> there is quite alot of information there, including for $readini
<5> tyty
<3> Your welcome
<6> hello
<7> hey...
<5> how would I use a ":)" in a string? it seems to screw things up
<2> a "string"?
<2> mirc has no strings
<2> mirc has variables :P
<5> when I read from the ini file
<5> any line works, unless it starts with a smiley face
<2> no idea
<0> htat would be breaking the rules for the .ini format
<0> probably
<5> hm
<5> any way to get around that?
<0> use a diffferent character
<2> use korean smilies
<2> ^^
<0> maybe escape it...make your script replace a phrase like @SMILE@ with :)
<2> that's not escaping it, that's just replacing it :P
<2> but korean smilies are nice anyway
<2> Q(-_-Q)
<0> why are you using ini?
<0> will a hash table saved to disk do the job better?
<5> seems the problem isnt the smileys, its readini'ing from the ini :P
<5> hm
<5> I want to save parseable strings under a certain category
<5> is a function not allowed to call the same function?
<8> hi all..........
<0> it is in newer mirc versions, but its not recommended unless you have a good grasp of recursion programming
<5> if I use var %temp, it'll be local for every function right?
<0> yes, i think so
<5> I'll paste what I got, one sec
<5> http://www.rafb.net/paste/results/102pjf80.html
<5> http://www.rafb.net/paste/results/O27FPx17.html
<5> second paste is the correct one ><
<0> it may be because you are asking mirc to do a readini within a readini command
<0> and it may be trying to open the ini twice
<5> yeah :/ hmm
<5> you mentioned hash tables, do you think it would be more viable to use that to do what I want?
<0> hmm im not sure
<2> it's not doing a readini within a readini
<2> the first readini return $getinput
<2> when that gets returned, it gets evaluated
<0> there is something that simply will read a random line from a plain text file i think
<0> $read(file.txt) will get a random line from file.txt
<5> I know xc but why shouldnt that work?
<0> but that wont do the second random thing
<5> I know, but that would require me to have a sep. file for every category
<5> and that
<0> maybe you could use $eval($read(file.txt),2)
<2> I don't know JennS, but not for the said reason
<0> then in file.txt, do two lines:
<0> 1: test $me
<0> 2: test $read(file2.txt)
<0> in file2.txt, you have:
<0> 1: category 2 line 1
<0> 2: category 2 line 2
<0> (the 1: and 2: won't actually be in the txt files)
<5> yeah but I'd have loads of files
<5> cool thing about this would be a single file with everything in it
<0> fair enough
<2> JennS try using a getinput2 function for the cat2 text and see if that works
<2> if it does, you know the problem is the recursive function call
<5> k
<5> good idea
<5> hmm that works
<5> damnit ><
<0> just for kicks
<0> copy and paste your getinput alias
<0> and call it getinput2
<5> thats what xc just said :P
<5> and it works
<0> then, change the conf.ini [cat1] items to $getinput2(
<0> oh
<0> haha
<0> i thought he meant trying it outside the ini with cat2...
<5> :P
<2> JennS: /help aliases
<2> An alias cannot call itself recursively mainly because this seems to cause more problems for users than it solves.
<2> :)
<5> awww
<0> i think theres a workaround tho
<0> just make na alias that calls the alias
<5> I would need an alias for every category
<5> right?
<0> alias getinput2 { return $getinput($1-) }
<5> wait
<5> let me think about this
<9> JennS: You can also use a timer to make recursive calls: alias recurse { var %n = $iif($1,$1,1) | if (%n >= 10) { echo -a DONE } | else { timer 1 0 recurse $calc(%n + 1) } }
<2> but that's not really a recursive call
<9> why not?
<9> satisfies all the requirements for recursivity
<9> including a terminating condition :)
<2> not really. when a "recursively" called funtion ends in your case, it does not return to the calling function
<2> therefore it's not really recursive
<9> Oh, I see. yeah. You can't do that without two aliases in mIRC
<5> its ok
<5> works with those 2 aliases
<5> thanks
<0> re :[17:31:27] <5> works with those 2 aliases
<0> it should, mirc's inability to do recurison directly is not because of limitations of the script engline
<0> *engine
<0> its just because otherwise too many programmers that are inexperienced would use it incorrectly
<10> how would igo about making a command so that when i say /idiot theres an action text that says "thwacks himself over the head with a cast iron skillet"
<0> go into aliases
<0> then add a line that says:
<11> Liek omg.
<0> /idiot /me thwaks himself over the head with a cast iorn skillet
<10> thanks
<0> except spell iron right
<0> because i didn't
<10> hehe
<10> top or bottom or anywhere in there?
<0> anywhere
Return to
#mirc
or
Go to some related
logs:
#linuxhelp
#nhl
#beginner
#windows
#politics
#visualbasic
#beginner
#politics
#computers
chipolte + dividend
|
|