I was just trying out some of my scripts in 6.20 and one of them was acting a bit rouge
Simplified its designed to have a window with lines of text in it and by simply moving the mouse over a line that line well appear in the editbox
You can then edit that text etc etc etc just like normal (assuming u dont move the mouse over the window again)
In 6.20 this was acting rouge, in that it kept placeing the full line into the editbox every 5 seconds or so, namely the ON ^*:HOTLINK was tripping with out mouse movement
I tracked this down to triggering imeditately following another script that goes off every 5 seconds, which was hiding dcc get and send windows, and was a totally unrelated script.
I thought it must have been something in 6.20 but from investigating it appears to exist in 6.17 (cant understand why i never saw it before)
It triggers off on the hiding of windows using -h or -nw0 (maybe others)
Here is an example script
alias ex {
window -c @ex | window -e @ex
echo @ex $+(line,$chr(9),number,$chr(9),one)
echo @ex $+(line,$chr(9),number,$chr(9),two)
echo @ex $+(line,$chr(9),number,$chr(9),three)
}
alias ex2 { timerex2 0 7 window -h @ex2 $(|,) echo -st timer to hide a window going off! }
on ^*:HOTLINK:*:@ex:{
echo -st ^HOTLINK : Last event was $calc($ticks - %hotlink.ticks) ticks ago : $!hotlinepos = $hotlinepos : $!1 = $1
editbox ex1 $hotline
set %hotlink.ticks $ticks
}run /ex
Then select the @ex window and move the mouse over the text, it well display the line in the editbox, and also display a message in the status window
Remove some of the text using backspace (without moving the mouse off the text in the window) and it remains gone
All Normalrun /ex2
Then select the @ex window and move the mouse over the text, it well display the line in the editbox, and also display a message in the status window
Remove some of the text using backspace (without moving the mouse off the text in the window) as the timer goes off the text well reapair becuase the ^hotlink event was triggered
Now heres something thats even more disturbingI was running 6.16 and 6.17 and 6.20 all at once trying this out, and the /EX2 set off in any of them was causing the tripping of the ^HOTLINK event in 6.17 and 6.20
* It would seem that something is making mirc think the mouse has moved, becuase a window has been hidden (99% of the time these windows are already in a hidden state), and this thing might be in the OS becuase it effects other mircs also running on the same machine
(i did once think i saw this problem in 6.16, but i cant reproduce that, so i might have just been in one of the other mircs and thought it was 6.16)
