Change to llOwnerSay: what on earth were they thinking?

Ok so when I read that they were going to make the text output of llOwnerSay more obvious, I was happy. It's always been hard to tell if it's going out to everyone, or just to you. However after today's server patch, I'm just dumbfounded. Defaulting to this horrible purple color that has zero contrast against the chat window's background (and don't get me wrong, I love purple). And most quizzical of all, changing it to talk like an English class dropout:

"Object say, hello world!"

O.O

wouldn't "says," have been the correct way to put this? Or has the net fried my brain that bad? LL what were you thinking!!!

It's actually a resident "contribution": https://jira.secondlife.com/browse/VWR-120

Not only that but who picked that color? Seriously it make my head hurt trying to view med magenta on a med/dark gray background

This may sound like a frivlous whine but when using that feature to debug a complex script, the last thing a coder needs is to not be able to read the debugging output clearly

BTW, Yes you can change it in the prefs->chat windows, but light purple would have been a far better default and really should be changed. No reason to FORCE people to have to update a color pref for no reason.

I know I'm wrong for this but hey, it's funny!

Courtesy: http://atom.smasher.org/chinese/

I agree. The colour is very bad and hard to read. If they are going to have a colour change at least make it an option. The purple is definitely NOT an improvement.

- D

Preferences > Chat > Owner
Click the color patch and choose yours.
Works in version 1.17.0.2

Edit > Preferences, Communication or Chat tab (don't remember), you can change the color there.

*Help*

Can't see that colour at all on the chat background !

Is there *any* way to change it to another colour ? Or change it back ?

A bright colour is needed, not a dark dark purple on dark brown, that's unreadable.

Edit->Preferences->Chat

Ty

Phew..... I can see again !

Not an acceptable solution.

I'm going to be explaining to all my buyers how to change their settings to be able to read messages that they could see OK before this poorly thought out and badly implemented upgrade.

You've got to be kidding.

- D

Well it works, I'm not kidding, and that was the only way to change the color back to something readable before the rolling restart if I remember correctly.

Backing out to the previous version of the viewer works too. However, that's not the issue.

Why should the user have to jump through hoops to get back to something that wasn't broken in the first place. And that still doesn't fix the illiterate "Object say, hello world!".

I am most disappointed in this change also. Luckily I wait until I am forced to update my viewer so the purple is news to me. All I can think was someone needed to show that they had done some work and shoved this change out.

ok LOL XD.

At least we can change the color, but what about the grammar? That grates on me even more. I guess I have to admit I'm something of a grammar Nazi. I can't stand misspellings or improper grammar, unless used for effect.

SO LL, please buy a spell checker, and perhaps you should read this guide to grammar and style:
http://andromeda.rutgers.edu/~jlynch/Writing/

So that means they don't even look at the code before implementing it I guess. Plop it in, spelling errors and all...

****************************************************************************

Ok, this has been opened as a new issue on JIRA. if you hate the color and the bad grammar, go vote:

https://jira.secondlife.com/browse/SVC-371


***************************************************************************

It's not actually a spellng error, but an oversight:

The change split llOwnerSay messages into a whole new chat type of their own, CHAT_TYPE_OWNERSAY, but noone remembered to add it to the switch below so it falls through to the default block with the grammatically impaired "say, ".
The bad spelling should have been a warning sign on testing, in addition to the warning being reported, but most likely the actual testing step was just skipped.

First response: Torley's chart will look all pink again.

Not just a bug, it's advertising to the entire world that Americans can't speak proper English. Everyone already knows that's true, but we don't have to make it that obvious.

Do we really need the slang? Does Linden Lab have such low expectations of their employees? Have we come to the age where criminal background check and credit score have become far more important than the simple ability to speak and write proper English and the latter isn't even a job requirement anymore? Isn't it bad enough that we now all have to learn Spanish in order to understand Linden's blog posts?

Is anyone still testing new releases or is LL just throwing them out fresh from the compiler, just to make sure Torley can use lots on pink in the charts?

While this is being fixed, do away with the additional color. Or even better: forget about the whole new Communicate interface, revert everything to what it was, and slap everyone on the fingers who dares messing around with that particular code ever again. At least until all the bugs are fixed and LL cannot come up with anything else to pester resis.

Give our children a fair chance in the world and teach them proper English.

If new code turns out to have a bug but you never find it because you didn't test, then instead of just "added feature X" you can say "added feature X *and* fixed a bug".

2 things > 1 thing so the result must be that not testing anything makes developers more productive .

It's also illogical, all tools were programmed for different output, now i get messages without sense from f.e. my radar like "[15:33] Long Range say, XXXX YYYYY [44m]". I mean that's really annoying and hurts my eye as well as my brain.

Thanks Kitty. Good to know it's a bug and not a purposeful change llOwnerSay for some obscure reason that they'll get stuborn about fixing.