Shoutbox

Also, rather than using loads of else if statements, try using switch:

js code:

---

switch (Messenger.MyStatus)
{
    case 4: // busy
        // do something here
        break;
    case 5: // BRB
        // do something here
        break;
    // repeat for each status...
}

---

I noticed it was possible, i just don't see the difference...
It's only easyer to read for people who... well...
it's just easyer for me >:l

quote:

---

Originally posted by billyy
I noticed it was possible, i just don't see the difference...
It's only easyer to read for people who... well...
it's just easyer for me >:l

---

Using Switch is shorter code and it is much faster code in execution.

Each time you do Else If Messenger.MyStatus, the interpreter needs to look up Messenger.MyStatus. This is of course useless because that variable isn't going to change between the If Then Else's.

Using a Switch statement makes that Messenger.MyStatus only needs to be looked up once.

A lot of those statuses are depreciated though, your only choices now are "Available, Away, Busy and Offline"

So there's really only 2 of those that you could use the script for

Thank you all, yes I know it could be annoying so I added some code that it will check if this user should get the msg or not.

quote:

---

Originally posted by djdannyp
A lot of those statuses are depreciated though, your only choices now are "Available, Away, Busy and Offline"

So there's really only 2 of those that you could use the script for

---

Various clients still show the old statuses IIRC and they are still sent correctly through the protocol, so some people will still see it correctly.

But it's about the status of the user of the script O_o
They are totally right xD

quote:

---

Originally posted by billyy
But it's about the status of the user of the script O_o

---

Since they are still supported by Windows Live Messenger (eventhough, on screen, you don't see a visible difference between the various busy/online statusses), it is still possible that the user will have such a specific status. eg: by using another script which sets those statusses for example. Hence they should still be supported in the script (and in any other script for that matter).

Oh yeh >_<
Well it won't happen much but at least those lines of code are justified :/

Plus! still supports assigning these status through the conversation.

/outlunch
/onphone
etc.

You can capture these messages in the OnEvent_ChatWndSendMessage and assign any DP or PSM you need to.