SundanceHaiku
commented
6 years ago Okay. Figured it out. I ended up using the following:
changed(integer change)
{
if (change & CHANGED_TEXTURE)
{
//
}
}
Unfortunately, the change event doesn't tell you where the texture change is taking place, i.e. which prim is being changed. To find out where it occurs, it's necessary to create a list of prims and their textures during the State Entry event.
After a change is detected, loop through the prims and compared textures with the original list. Look for a texture that is different from the original list. When the texture is different, that's the prim where the change occurred. If it's a texture you don't want changed, then replace the changed texture with the original texture,
It seems like there must be an easier way, but not discovering anything better, this solution ended up working for me:
aiaustin
typhartez
Shin, or anyone who might have a solution . . .
I've been working on a HUD which allows you to drop in different fingernail textures: little hearts, zebra designs, etc.. It uses Shin's cool idea of dropping skins via the Skin applier.
I found, however, that if one happens to accidentally drop, say a zebra texture, in the root prim (the backdrop of the HUD), then the backdrop picks up the texture. There's no way of backing out it. Your backdrop now has a zebra design on it.
I'd like to restrict it so people can only drop textures to the prims designed to receive them and not the backdrop.
I tried using llAllowInventoryDrop set to FALSE in the backdrop. However, if you have full permissions (and I want to provide this HUD with full permissions), it won't stop you from dropping a texture into the backdrop. (With full permission, you can drop anywhere.) It is possible to use llAllowInventoryDrop, but only if the HUD is set to No Modify. (This still allows people to drop textures to the prims designed to receive them.) If possible, I'd like to keep things set to No Modify.
Can anyone suggest a way of doing this?
Sundance