Page MenuHome

Batch renaming of objects and associated datablocks
Closed, ArchivedPublic

Description

Project: Blender Extensions
Tracker: Py Scripts Contrib
Blender: 2.55
Author(s): Florian Meyer (tstscr)
Script name: Batch Rename Datablocks
Wiki page: http://wiki.blender.org/index.php/Extensions:2.5/Py/Scripts/Object/Batch_Rename_Datablocks
Category: Object
SVN Download: https://svn.blender.org/svnroot/bf-extensions/contrib/py/scripts/addons/object_batch_rename_datablocks.py
Status: Open
Related: 21681 25214

another batch renaming operator.

This is my personal batch renamer because the one already here didn't fit my needs.

It allows various things:
Batch rename multiple objects to a custom name
Rename associated datablocks after the naming base (can be any datablock or custom) .

The main purpose is mainly this scenario:
You have many objects which have good names,
but neither the meshdata nor the materials are named accordingly.
This operator than takes care of those.

At the moment it ignores multiuser data because there is no obvious way which object should be used
after which to rename the data.

Event Timeline

hey florian,

there are other two batch renamers! See related field above.

Best not going straight contrib, but discuss first, this would have popped up.
I'd prefer we merge the 3 scripts instead of going with 3 different approaches.
This is what we did also for copy attributes, so we have the best from all the scripts.
Please get in contact with them and discuss the best strategy with them, possibly here so people not in irc can follow too.

Also, the script in svn has weird category and no wiki/tracker url, no good eh... :)

Hi!
Since your script is now in bf-extensions\' svn (contrib|trunk) we have deleted the current attachments to avoid that end-users could reach this page and get the wrong version of your script.
Note that your script may have api changes or small maintenence changes applied in SVN.
Please retrieve your script from SVN before updating SVN to avoid mis-versioned scripts.
Thanks!

Rev 42306
This script does not rename data.

Hi,
Due to changes to the api including the merging of bmesh, several addons are outdated.
Please, if you are the author of an addon check your script with blender revision 44256 or newer.
That is builds made After blender 2.62 official release.
I would ask that updates be made to your addon before the Blender 2.63 release.
6-8 weeks away.
This allows time for the api to become more exposed & bmesh to stablize furthur.
If you need help, drop into irc freenode #blenderpython or #blendercoders & feel welcome to ask questions.
At the time of 2.63 release, scripts that are not repaired or in active developement will have their tracker page marked "Closed"
this will not affect your links to the tracker, similar to closing scripts in 2.49b, the page will be still availible & can be re-opened.

Thanks for your understanding & patience during these Exciting Times.
Brendon.

This task was automatically closed as archived as part of migration, because it was determined to be no longer active.

The authoritative list of addons is on the wiki, we no longer have a report for each addon to track bugs and updates. Bugs can be reported individually and assigned to the addon developers. See the Add-ons (Community) project page for more information on the workflow.

Nobody (None) changed the task status from Unknown Status to Unknown Status.Dec 15 2010, 7:23 PM

Any chance to port it to 2.8?