Giving textures to other (linked?) objects...

Hi all... in wayyy over my head

Object 1 has textures in it. I want object 1 to "give" or "loan" or otherwise cause one of the textures in its inventory, to appear as a texture on another, object, linked to it.

Is this possible?

thanks so much

Yes, the simple method is to communicate the texture UUID/key to the other prim using a linked message and the llGetInventoryKey() function. Then, have the other prim call llSetTexture() with the UUID received, to place the texture on a face.

yes this is possibal

Textures
http://secondlife.com/badgeo/wakka.php?wakka=texture

LinkedMessages
http://secondlife.com/badgeo/wakka.php?wakka=ExampleLinkMessage

integer side = ALL_SIDES;
default
{
touch_start(integer total_number)
    {
        key texture = llGetTexture(ALL_SIDES); // select the side
        llMessageLinked(LINK_THIS, 0, "Touched.", NULL_KEY);
    }

     link_message(integer sender_num, integer num, string str, key id)
    {
        llSetTexture(side,id);
    }
}

Also, I think that the texture you send must have full permissions.

Not quite - to _use_ a texture by using its key, you do not need any permissions on it - in fact, you don't even need to have the texture, just the id.


to _find_ the key of a texture, you need to have full permissions on it, or to have the key told to you by someone who does have those perms.

Same is true for any asset... sound, anim, object, not just textures.

Some assets can only be used by name, and _have_ to physically be in the inventory of the prim with the script (animations?)

Others you can use by key, and for those, yeah, all the above applies

Yup, animations have to be there and used by name - it proved to be too easy to steal them if you could use the keys. Sounds and textures you can certainly do by key and keep the original in your inventory, or someone else's if they'll share the key with you.

What if the asset is in another prim that is linked to the one that uses the texture?
Can it be used that way? By either key or name?

If a script is using an asset by key then it can be anywhere or nowhere - you don't even EVER have had to have a copy.

If a script is using an asset by name then the asset with that name must be in the same prim as the script period. No exceptions (that I am aware of).

Linked objects are NOT the same prim.

Consider the case where, say, a texture called "wood" exists in two out of three linked prims, but it is a different texture in each case.

Which one should a script in the third prim use?

What happens if someone unlinks the prims?

It would be impossible for the scripting engine to sensible sort out the mess that resulted, quite apart from the several orders of magnitude of delay that would be introduced into every single inventory lookup.

That makes total sense..... thanks.

Now, what would be the cause of an error like :

"Object: Couldn't find texture 00000000-0000-0000-0000-000000000000"

This would be the key of a texture contained in a prim... and then passed on by linked message to a child that tries to load the texture... would this be an example of a texture that does not have permissions needed to get the key in the first place?

Probably as it's returning NULL_KEY. Either you do not have permissions or you do not give it the correct spelling of the name.