Bug in Save Back to Object Contents
tracked
Pazako Karu
Issue: An item rezzed by a rezzer, or rezzed by dragging out of a prim, can be grouped and coalesced back into the object, incorrectly updating the last-selected object as a coalesced one. It reasons that each selected which were rezzed separately be placed back in the object separately.
Now that we can pick up objects as a group but still separated, the Build > Object > Save Object back to Object Contents should respect the form it was rezzed in and put it back as singles of the same name as well.
Why?
Right now we can make really simple rezzers that just let us organize stuff willy nilly but to save updates made (like recoloring, relinking, etc) we have to Save Back to Object Contents, one at a time. If we could do it as a group, we could select a whole build and choose the option, any anything which has an object_rezzer key still around can be updated in one stroke.
This would be phenomenal for keeping builds organized and updated!
Note: This may create issues with mixed coalesced and linked items. In that case, it should be prudent to take the coalesced items first, and then go through the rest of the selected list. If this is unfeasible, a warning is in order if saving a previously coalesced set back.
Reproduction:
Rez 3 prims, name 2 of them uniquely
Pick the named ones up separately
Place them in the object inventory
Drag them out of the inventory to rez them, one at a time
Select both of them and Build > Object > Save back to object contents
Attempt to drag each out again.
The last selected one before saving is now coalesced as both, and the other is not updated.
Log In
Atlas Linden
tracked
Thanks for the reproduction steps, Pazako!
I was also able to reproduce this odd behaviour.
This issue is now being tracked here: https://github.com/secondlife/viewer/issues/3834