You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
LSL: Add a script function for a script to get the prim number of another prim than the one it is in, from the name.
I don't know why this was not implemented by Linden Labs. Perhaps because it would bring an ambiguity when several prims have the same name (like "primitive"...) This is manageable by a builder, with avoiding identical names. However, even so, the script engine would still have to go through all the prims in real time, to check for doubles. We can still assume that this is faster than the routine solution.
A solution may be to have a task started at each modification of the build (there already exist changed events for that), and warning that a double occurred. If so, the script can safely assume that there is only one prim with this name, without having to check all each time.
The text was updated successfully, but these errors were encountered:
LSL: Add a script function for a script to get the prim number of another prim than the one it is in, from the name.
I don't know why this was not implemented by Linden Labs. Perhaps because it would bring an ambiguity when several prims have the same name (like "primitive"...) This is manageable by a builder, with avoiding identical names. However, even so, the script engine would still have to go through all the prims in real time, to check for doubles. We can still assume that this is faster than the routine solution.
A solution may be to have a task started at each modification of the build (there already exist changed events for that), and warning that a double occurred. If so, the script can safely assume that there is only one prim with this name, without having to check all each time.
The text was updated successfully, but these errors were encountered: