mIRC Home    About    Download    Register    News    Help

Print Thread
identifier for editbox history #141838 13/02/06 08:21 AM
Joined: Dec 2002
Posts: 211
T
Talon Offline OP
Fjord artisan
OP Offline
Fjord artisan
T
Joined: Dec 2002
Posts: 211
we all know that an editbox has a history. you can use up or down to browse through things that were previously typed, but why not have an identifier that can return these inputted lines of text? $EHistory(#mIRC,1,1)

$EHistory(window,line,x)
x defines which edit box, if left blank, it assumes the main, else it assumes its the second edit box in a channel.

Re: identifier for editbox history #141839 13/02/06 11:47 AM
Joined: Sep 2003
Posts: 4,230
D
DaveC Offline
Hoopy frood
Offline
Hoopy frood
D
Joined: Sep 2003
Posts: 4,230
Not a bad idea, cant really think of a use for it, but the data is stored in mirc, why not let us have access to it.

I once wrote something that pulled that data out, but it was messy at best, i think it used a key press generator to up arrow to the value, then a timer to read the contents, becuase the uparrows had to complete, so i had to timer wait for them etc etc, was gonna post it, but i cant find it, cant even remeber what i wrote it for, something someone asked for i think, was pretty lame really.

Re: identifier for editbox history #141840 14/02/06 05:43 AM
Joined: Dec 2002
Posts: 211
T
Talon Offline OP
Fjord artisan
OP Offline
Fjord artisan
T
Joined: Dec 2002
Posts: 211
I have a working version but it only keeps track of 50 entries.. it uses an on *:input:*: to store the entries in a hash table. I shoulda posted i got a viable working solution to most of these posts but it would be much faster if it were built in rather than scripted.. compiled code is better

Re: identifier for editbox history #141841 15/02/06 04:53 AM
Joined: Sep 2003
Posts: 4,230
D
DaveC Offline
Hoopy frood
Offline
Hoopy frood
D
Joined: Sep 2003
Posts: 4,230
OH i never expected your were looking for a work around, it wouldnt take much to make a ON INPUT that records every single command entered ever and from where etc etc.
But even if u did that doesnt help when the purpose of the script thats running might be a one off execution, as it wont have any on input to use, as you have said an internal identifier would be very much nicer idea.