llSetInventoryName

Template:Needs Translation/LSL/de Template:Needs Translation/LSL/es Template:Needs Translation/LSL/el Template:Needs Translation/LSL/fr Template:Needs Translation/LSL/he Template:Needs Translation/LSL/it Template:Needs Translation/LSL/ja Template:Needs Translation/LSL/ko Template:Needs Translation/LSL/nl Template:Needs Translation/LSL/hu Template:Needs Translation/LSL/no Template:Needs Translation/LSL/da Template:Needs Translation/LSL/sv Template:Needs Translation/LSL/tr Template:Needs Translation/LSL/pl Template:Needs Translation/LSL/pt Template:Needs Translation/LSL/ru Template:Needs Translation/LSL/th Template:Needs Translation/LSL/uk Template:Needs Translation/LSL/zh-Hans Template:Needs Translation/LSL/zh-Hant

/LSL

SetInventoryName

llSetInventoryName

	LSL Feature Request
	The described function does not exist. This article is a feature request.

Summary

Function: llSetInventoryName( string old, string new );

0.0	Forced Delay
10.0	Energy

Tries to renames the inventory object old to new. Useful for vendors wishing to hand out customized versions of objects.

• string	old	–	an item in the inventory of the prim this script is in
• string	new	–	desired inventory name

Caveats

• If old is missing from the prim's inventory then an error is shouted on DEBUG_CHANNEL.

Examples

See Also

Functions

•	llGetInventoryName
•	llGetInventoryDesc
•	llSetInventoryDesc

Deep Notes

Signature
//function void llSetInventoryName( string old, string new );

Comments

A few things that came to mind:

• What happens with a name collision?
• When used in a vendor it would be more useful to change the name of the item when giving, this would avoid the name collision problem (and having to change the name back after giving it).
• A better name for this function would be llRenameInventory (for which there is at least one JIRA).

P.S. I changed the syntax, using inventory numbering to access items is hazardous, names are less prone to change. -- Strife ^{(talk|contribs)} 19:03, 21 March 2009 (UTC)

Possibly should use key, not names source. And it should work as copy/rename/give function. In case of collision - either add number to it's name or return error (should be a flag parameter). --Zidan Foxdale 14:00, 20 June 2010 (UTC)

Key support is a no-go. Multiple instances of an asset can exist in a prim's inventory. All those instances will all share the same key. -- Strife ^{(talk|contribs)} 23:52, 20 June 2010 (UTC)