-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Renaming edit/pose bones breaks the drivers using them. #195
Comments
This could be tricky. I need to see if and how I could solve this issue |
How come when renaming and object the driver is updated but not when renaming a bone ? Is it because Prop is a PointerProperty & Path a StringProperty ? Anyway, wouldn't getting a list of all drivers be enought to loop over them & update their variables' path ? Sure it might slow down a bit the renaming if there are lots of drivers, but a check box to enable driver updating for bones, lets the user decide. When doing a renaming operation I think, to get a list of driver's variables to update, something like that should be done:
|
The second part is durring the renaming loop, changing the driver's data_path.
As I'm not familiar with the addons' code and dabbled only recently with blender python api, thoses snippets are just drafts, not even properly tested. I hope this is still a good starting point and thanks for your work on this amazing addon :) |
When renaming a bone (in pose & edit mode alike), the drivers using the bone break:
The bone name is put in the
path
section of the driver (Single Property type)When renaming, the bone's name is not updated in the driver making it invalid, or worst, getting unwanted values from an other bone.
I Think the excpected behaviour would be to update the bone name in the driver.
The text was updated successfully, but these errors were encountered: