llOwnerSay Can you stop it putting the objects name on screen?

When you use the llSay or llOwnerSay command, before the text you want to display it puts the name of the item (prim) at the start.

Is there any way to stop this happening?

Or some other command that will pass text to your screen from your script.

For example, say you have something called "Wonderfull Giant Glowing Chandelier" and you are adjusting the brightness of it.

You might end up on screen with messages such as:

Wonderfull Giant Glowing Chandelier: Brightness = 1
Wonderfull Giant Glowing Chandelier: Brightness = 2
Wonderfull Giant Glowing Chandelier: Brightness = 3
Wonderfull Giant Glowing Chandelier: Brightness = 4

As you touch the item and your script cycles thru the levels.

When all you really want on screen as you click your prim light is:

Brightness = 1
Brightness = 2
Brightness = 3
Brightness = 4

You are looking at it, clicking on it and you don't need to be told on screen the name of it again and again.

Anyway around this?

Thanks

you would need to temporarily change the name to "" and then if you want to get rid of the colon you need to use /me before the message. ie:

default
{
touch_start(integer num)
{
string name = llGetObjectName();
llOwnerSay("/me Touched");
llSetObjectName(name);
}
}

this (untested) little script should just say the word Touched in the chat without a name or colon before it. you might want to put a delay before reverting the name back to the original

Forgot a line:

default {
    touch_start(integer num) {
        string name = llGetObjectName();
        llSetObjectName("");
        llOwnerSay("/me Touched");
        llSetObjectName(name);
    }
}

You really need to llSetObjectName() to the first word od what you want to say, no?

llSetObjectName("Brightness";
llSay(0,"/me 1";

etc...

Thanks to you both for this help and sample code.

Very much appreciated.

you can, but not really, i think it will just leave a space at the beginning with my method, but if it's ownersay, is it that big of a deal?

whoops, yep, thanks