Congrats to LL for finalllllly giving up Bulk Perm Tool!!!!

Here is something that works like a charm. Bulk Perms can now be set inside your Box and on upload !


Nice work!

Anything that saves me clicking and making perms errors makes me happy

Same here. But how does it work exactly?

Any prim object, single prim or linkset, rezzed in-world:

Select the item in edit. There is a choice to set permissions.

This results in a dialog similar to doing a fiiltered search of inventory. You can select any or all content types, such as "Scripts, landmarks, textures, clothing, but not notecards", and can set the perms on ALL of them at once, with the usual three checkboxes, no matter where they are in the linkset.

What you still can NOT do is make a similar sweeping change while something is in inventory. So if you inport 1000 new textures, you have to put them all in a box prim in-world, set perms there, and take the changed textures back intoinventory, rather than just changing them all at once IN your inventory.

IN inventory ability would be cooler.

This function has been in Cool Viewer for a while - and let me tell you - it is a godsend when it comes to packing up stuff with lots of scripts and prims with stuff in different prims and - oh my. Love it.

Careful to still double check everything though. Things like to revert when you pick them up. And attachments are even more likely to go wonky on you.

Huge leap forward though! Yay!

There is an option for notecards, does that not work? Or do you mean parent type of object?

What I meant was you can pick and choose. Like leaving the notecard no-mod intentionally while changing all the scripts. It has options for any inventory item type, just like in the Inventory filters.

Ah sorry, can see what you meant now, yes it's all checkboxes, you don't have to select them all.

Wow! This is great! Thank you, Ceera.

Very cool. Now if only we had a way to change perms on all objects in a region at once.

This thing is months old and was implemented in alternative viewers for a very very long time. Great to see how you all applaud LL for finally getting things they did not invent but were ask to implement for months in the official viewer through their oh so complicated QA process *ROFL*

Would be very useful, from what I've seen Boy Lane's Cool viewer still has the edge because of how it allows you to set perms on parent prims, so although you can't do a region at once, it should still be less time consuming than the official viewer.

Your point is well taken, Boy. Still, for those of us who do use the official viewer, no matter how far behind it may be from your point of view, this is good news.

actually there is an option to set permission before you upload textures (I think it is in the RC not sure about the reg client)

not logged in at the moment to describe how, I will edit in a bit and explain

Edited to add:

when you click the upload option at the bottom of the uploads list is a set default permissions. Very handy for when uploading a large amount of textures.

I refuse to use any 3rd party viewers, so when LL does implement things into the official viewers it makes me happy

I don't care if it was their idea, or if a 3rd party viewer had it first, for me, it is still new and an improvement to the viewer I choose to use.

I have used nothing but the CV for a very long time, I wont used the 'official' viewer

Of all the annoying mistakes I make over and over, forgetting to set the perms correctly on textures is the one that happens most. I need a button that prompts me to set perms each time I upload...

Oh? Great! I'll have to look for that. I don't think I have yet tried using the RC to upload new textures.

And I am happy to acknowledge that Cool Viewer and other independant clients for SL have repeatedly come up with some of the best innovations in the client, and that LL has been very laggardly in adopting these changes, even when handed to them on a silver platter by creative people like Boy Lane and others.

However, my own preference is not to use "unofficial" client software. While I am sure that many of the developers of such clients, such as Boy Lane, are fine and concientious individuals, and would not release "dangerous" code, there are far too many others out there who are far less ethical. I don't trust hacked code that I can't read, and I am not skillful enough in the programming languages that the client is written in for me to parse every line of some hacker's source code to be certain it is not malware.