integer llGetLinkNumberOfSides(integer num)

Pretty self-descriptive. Return number of sides of linked object num. LINK_SET returns maximum number.

Nothing incredible, but ehh... it's something that could be useful. After all the other functions we "need."

This can be done with a script in the linked prim, and a couple of llMessageLinked calls.

- Ace

I realize that, but it requires a script in each prim for the task.

I'm rather sympathetic toward most llGetLink- and llSetLink- proposals, to be honest. This sort of code would save time spent on server calls nicely for common operations.

Convenient? Of course.

But personally, if there is already a mechanism to accomplish a task, I'd rather LL work on something else.

My US$0.02...

- Ace

I'd have to agree with Jeffrey here. For a recent project, a game, I needed to update a large number of prims on the game board with new textures, colors, etc. The fact that I couldn't do it all from the parent prim meant that I had to use something on the order of 250 scripts, all told. Pretty big.

Then again, I did discover something interesting. Things like llSetLinkAlpha(), when done in a loop over 100 or so child prims at once, take a good 10-20 seconds, depending on the sim. Sending one message, "clear", to all child prims, and having each script in each child respond by changing itself appropriately happened almost instantaneously. llSetLink*() seems to involve some kind of overhead for finding each prim, and is ill-suited to iteration over a big link set. Draw whatever conclusions you'd like.

Right. If it's something done relatively commonly, and the current way of doing it is server intensive and laggy, it could stand to be revisited.

Guess that's what the feature voting thingie is for. Kinda.

neko
(Still boggled by the 23d proposal, with 166 votes... nothing against ponies, but why not ask for a general purpose quadruped animal while you're at it? Then you could combine the Mule proposal, not to mention.... ah, never mind.)