llSetLinkColor acting odd

I am using a script that uses LinkColor a lot. It works like I want it to, and every thing in the object I have...up until I have 2 or more coppys of the object out.....every link #15 will change color in every coppy out....what am I doing wrong?

here is a coppy of typical code you'll find this in

Check that you are not also broadcasting via chat which is getting relayed because of a common channel number. If it definitely isnt that then I'd say its a rather nasty bug in the latest release.

yup, I had the chat diolog brodcasting...if I make the channel "0" will it stop doing that?

Nope, will make it worse! You will get all chat.
Firstly does the listen need to be open all the time or can it be touch activated?
Most configuration type controls dont really need to be always on, just when you are actually configuring the item.

If its a touch activate dsystem then use a timer to clear down the listen after you have finished processing the commands.

Are you using a dialog or just text chat control?

For text chat I generally use either a notecard controlled channel number or a low range random channel number between 1 and 100 selected at rez time.

If it is a dialog then I'd suggest that you use a randomised channel number and a timer to limit the length of time the chat is open.


here is the simplified code I generally use for Dialogs

integer Listening = 0;
integer listenchannel;


UpdateListen(key id) 
{ 
    CancelListen(); 
    Listening = llListen(listenchannel,"",id,""); 
    llSetTimerEvent(30); 
} 

CancelListen() 
{ 
    if(Listening > 0) llListenRemove(Listening); 
    Listening = 0; 
    llSetTimerEvent(0); 
} 

// Owner Conversation Dialog 
ShowMainMenu(key id) 
{ 
       
    listenchannel =  0 - (integer) llFrand(2147483646);
    string text = "Main Menu\nPlease Select an Option"; 
    // finally show the dialog 
    llDialog(id,text,MenuChoices,listenchannel); 
    UpdateListen(id); 
} 

You will also need a Timer event handler to clear the listen down.

    timer() 
    { 
        CancelListen(); 
    }           

Add the same code in the start of the listen event handler

    listen( integer channel, string name, key id, string message ) 
    { 
        CancelListen(); 
        // Process messages
    }

Its reasonably good practise to use a control script for the chat stuff and have it communicate to the main script(s) via linked messages.

what I have is menue driven dialog, were the selection woud triger multi things to happen at once. I crammed 3 menues into 1 script, with 10 options each. Basically the first menue is used, followed by the second, followed by the 3rd. there is 10 if's per menue and 30 llLinkColor's per menue. (making a total of 60+ if's and 120+ change colors in 6 states.)
I may try llFrand to make the channels random, so there isn't so much script being rewritten, but will keep that in mind when dealing with less bulky scripts.

Thats a pretty high concentration of if's, you could possibly reduce it somewhat by using lists for the sub menu handlers but it would be dependant upon exactly what your code is trying to accomplish.