Why not make it so the user can make their own custom message. I wouldn't want to tell people to go **** themselves.

I think you're in the wrong room ;)

Out of curiousity, is there a need to set a %tab variable, since each tab has its'own id?

Rated and clicked :)

your did -fu $dname is missing a dialog id number

When you use the -x flag you only need to name the dialog once, and in fact, the way you have that at the moment you can just use did -x $dname

The dialog -ma test test is fine, except what if the dialog is already open? You'll get an (ugly imo) error message.Check to see if the dialog is open using an $iif

alias _test dialog $iif($dialog(test),-x,-ma test) test

You shouldn't really have a need for one since the info re the state of the check box is being recognised on init. To refresh while the dialog is open just use

You could play around with these $iifs too if you felt like it.



I know there is noting suckier than someone telling you to read the help file, but the dialog part of the help file covers alot of good stuff.

There's no need for the f flag either as -c will check the box
I used to use:

but even then I don't like it, it's too long and messy for such basic code. $iif would work just as well to clean it up as well.

You're missing a closing bracket. I'd think twice about assigning the * to all the popups, plus, when you're not connected you don't need to see the dialog on the popup menu..

A cleaner way to open the dialog would be to use an $iif so as you don't get "the dialog <name> already in use error message by using:





What if the $active window was the status window?
if ($active ischan) or if ($active == $chan) can sort that out nicely. then you can use a return if the $active window isn't the #channel

When using dialog flags you can condense control id's, for example:



Can be:



makes it neater and you can also separate clumps with a comma like 63-66,74-82 etc

This is correct:

05:30pm                • Vista

Though I am running Windows 7 ultimate 64bit.

I'm probably just being pedantic, bbut I'd much rather use $chr(3) $chr(2) & $chr(31) respectively to bold, underline or colour text. Still a neat little snippet.

Is it working for you now?

How old would the topic be? Look at RAWS 331-333 and have a look there for possible errors/conflicts.

I went cold turkey about 6 weeks ago. I was at a pack a day. Surprisingly I found it really easy, and I have no problem seeing people smoke etc.

If you right click in the status or a channel window the options to use it will be available.

If the allinfo alias wasn't local (-l) you could type //allinfo to get the info.

Looks good.

I actually just started using Russel's script and I love it!

Yes, that is correct. I was wondering if it would sound weird lol

Fordlawnmower posted a comprehensive one two days ago.

http://www.hawkee.com/snippet/7069/

use the -m flag on you timer for milliseconds.

Sorry, but this is amazing! I am in total love with these iomages. I had a quick look for pr0n, didn't find it (the Flight Mania tricked me at first). I saw two lots of medication.

Is that a 14" monitor? I saw 3" & 5" floppy drives. Amazing! Even a disc was there too!

Dude, how much did youi used to smoke?

@Hawkee Hi Hawkee, and you're welcome. It just made me quite mad. Russel is a genius, and like so many ppl on sites such as these, they volunteer their time to help ppl learn etc so it really pissed me off to see this guy not only claim Russel's work as their own but then had the nerver to tell us not rip his work!! </rant>

PS - I should remove a snippet I posted then. It was not written by me, but I gave the author 100% credit plus he gave me permission to share it. The reson being I find it such a helpful alias and wanted to share it with my peers.

Touche ;)

space between else and if (Redundant either way)

Ummm, /youtube <topic> but the alias is "yt" so shouldn't the trigger be /yt <topic>

also got
Which is:



would look nicer as: