Shoutbox

Obviously, we can no longer change our display names in WLM 2011. So I'm wondering how this property is/will be implemented in Plus! 5... Will it be a read-only property? If so, in all versions of WLM, or only for versions >= 2011?

I'd imagine they'd want to preserve backwards compatibility (assuming the scripting engine is the same). The script would need to check for WLM version first, hopefully something MP5 can take care of its self.

Setting Messenger.MyName should trigger a silent error in the debug something like E_NOTSUPPORTED and then do nothing.

An error in the debugging window will cause problems to scripts, for example:

JScript code:

---

function DoSomething(sNewName) {
    [...]
    Messenger.MyName = sNewName;
    [...]
}

---

The third line of "code" within the function body will trigger an error, so the rest of the function won't be executed.

Of course, correct me of I'm wrong

quote:

---

Originally posted by Spunky
assuming the scripting engine is the same

---

It is entirely, for now.

quote:

---

Originally posted by SmokingCookie
so the rest of the function won't be executed

---

You can always decide to catch exceptions, like this:

jscript code:

---

function DoSomething(sNewName) {
    [...]
>>>    try {<<<
        Messenger.MyName = sNewName;
    }
>>>    catch(e) {<<<
        Debug.Trace("Setting MyName is not supported.");
    }
    [...]
}

---

quote:

---

Originally posted by SmokingCookie
An error in the debugging window will cause problems to scripts,

---

Hence why Spunky suggested a silent error I Think.
Silent errors do not halt further execution.

quote:

---

Originally posted by CookieRevised

quote:

---

Originally posted by SmokingCookie
An error in the debugging window will cause problems to scripts,

---

Hence why Spunky suggested a silent error I Think.
Silent errors do not halt further execution.

---

Yeah, to clarify, that's what I meant. I think we need more feedback in the debug window than just the "fatal" errors that halt the script.

@mynetx: Setting exceptions like that would work, but not for the scripts already released (in the database, on the forums or something someone has made for personal use)

An error message in the debug window would let the developer know straight away that they won't be able to set anything by using the property.

quote:

---

Originally posted by SmokingCookie
So I'm wondering how this property is/will be implemented in Plus! 5

---

I think it will just need some internal tweaking (or possibly already has... any beta testers want to shed some light?). Anything that requires us to go back and re-write code is going to break a lot of scripts on the database that are no longer being maintained.

quote:

---

Originally posted by Spunky
any beta testers want to shed some light?

---

Setting Messenger.MyName is currently possible. Also, using /name <stuff> is possible too. This is because internally the nickname still exists - Messenger 2011 just doesn't display it anymore. If you are talking with a contact who is using Messenger 2009, they will see when you change your name. Expect this Plus! behavior to be subject to change as the current beta is not a Release Candidate yet.

I would anticipate you would receive an error saying that the object doesn't support this operation which would halt execution. Maybe they can add a catch internally into the script engine that says 'Woah we can't do that but let's not stop your script'...

We'll have to just wait and see...
Guess the block functions have similar problems...

Actually the block functions are still working the same way they used to, except they trigger "appear offline to"  in WLM2011 instead of a proper "2009" block.