Forums Scripts & Popups Keeping a custom window open.

My script has a single custom output window that is more or less vital to the script... I'd like to keep this window open at all times if it's possible, but can't seem to get it to work. Here's what I tried:

on 1:CLOSE:@DCCSTATUS:/window -k0mz @DCCSTATUS

And for some reason it doesn't trigger. If I put some other test command in there like a simple /echo -a TEST it triggers that just fine when I close the custom window.

Any ideas?

If you insist on such a setup then use /.timer 1 0 window -k0mz @DCCStatus as the command. So as not to aggravate the script's users who may want to close it, you might want to consider using that as a hidden window and a more customizable form of output

Thanks for the help, your code worked wonderfully!

...and I don't really need to worry about annoying people. I'm just writing this script for myself and prolly won't reach a level that I'd be confortable sharing it...

[i]Edit: Removed code.

That will not work, it is not possible to re-open the window in the close event. And yes, you can specify the window name in the target part of the event, as well as wildcards

[i]Edit: Removed code again.

Look closely at my timer, it was 1 repitition with 0 sec. delay and I meant it as a replacement for the command that already existed in the event

lol .. you've got me from all directions don't you.
After looking again I now see that. I saw it the first time as
/.timer 0 1.
My apologies.

* RoCk goes back to his corner

That timer is a disgusting bandaid though, and uses 100% CPU.

Fix the problem by correcting the script which closes the window.
Fix the problem by having the script /window before /echoing to it.

If they can't fix the script properly, they have no business using it.

LOL!
If a single repetition timer caused 100% CPU usage I think the computer would be better off being a doorstop.

If such a computer was used as a doorstop I'm sure there would still be people complaining about its performance... $+(*,$me,*)