Is there a gadget to list my textures I've put out

Is there any gadget to list all the names, of all my textures that I've put out, on each of my parcels, so I can see which ones I've forgot?

Can you specify a bit more? you mean textures applied to objects such as houses??

Yes, I mean textures I've put on display on walls.

It would have to be a script you include in the root prim of every object you want texture information on, since there's no scriptable ability for one object to know about another objects texture details.

The script would have to
(1) walk through each prim in the object
(2) walk through each face in each prim
(3) report out the current texture for that face; it would probably be the texture's UUID and not its name - I don't know if there's a way to get the name of a texture from its UUID

It would also be very chatty since there's no scripted way to store the information in a file. Ideally the script would write to a non-public channel and another script would listen, test to see if the texture has been "chatted" before, and if not add it to a list of textures. You might also want the script to output various parameters such as repeats. I don't think you can get permissions for a texture, however, so if your goal is to see if a badly-permed texture is going to break a desired permission level, you're better off with alt testing.

So ... doable, but a lot of scutwork.

I'm afraid it's even worse than that, as a scripting exercise. There's no llGetLinkTexture() nor llGetLinkPrimitiveParams(), so the script would have to be in every prim, not just the root prim of each linkset. Also, the functions llGetTexture() and llGetPrimitiveParams() treat textures very specially regarding permissions--although for textures placed on one's own full-perm objects, that probably wouldn't be a problem.

I hate to say it, but the only way I can think of to do something like this that's even halfway general would be a customized client very (*very*) similar to a copybot. (And then it would still be texture UUIDs, not names.)

On the other hand, if the problem is very specialized--"picture" prims in galleries, say-- scripting each picture would work.