Talk:LlGetInventoryDesc

I forsee a major problem with this function. How does it determine which of several objects with the same name is the one that's required? The default name for all prims is 'Object', and I'm as guilty as the next party of leaving 'em named that way. Essentially, this function (and the list of related functions) is asking for individual functions to retrieve the information already available by using llGetObjectDetails with appropriate selections in the parameter list. Also, since llGetObjectDetails goes by UUID instead of name, the results are guaranteed to be specific to that one item, not anything else that may happen to have the same string name. --   ¥    Reynard  21:12, 8 April 2011 (PDT)

I don't see, either, what it does that llGetObjectDetails(id,[OBJECT_DESC]), llGetLinkPrimitiveParams(n,[PRIM_DESC])or llGetObjectDetails() won't do. Or is the idea to find out the description of an object in a prim's inventory? Innula Zenovka 05:40, 9 April 2011 (PDT)

The idea is that this function could get the descriptions of items inside a prim's inventory without rezzing them. Inventory items in a prim must have unique names, so that is not a problem. Kelly did recently change SVC-377 to 'unactionable', because it would be possible to retrieve but it would not be practical to make it read-write. SCR-11 for only the llGetInventoryDesc part is still on the table. --Cerise Sorbet 07:11, 9 April 2011 (PDT)

i see no problem with the object name issue as if you drop two objects with the same name into a prims inventory they get renamed automatically so the second object would be "Object 1" first being "Object", i think this would be a very useful feature for passing data to a script if updating an object in a product, currently llGetObjectDetails(llGetInventoryKey(name_of_object),[OBJECT_DESC]) returns nothing --#- moonbuggy -# 10:13, 3 August 2012 (PDT)