- Amsterdam, NL
- https://stuvel.eu/
-
Blender developer working at Blender HQ. Module owner of Animation & Rigging, project lead of Character Animation 2025 and Flamenco.
- Joined on
2004-09-12 -
-
Implementing this via RNA seems a bit heavy with the definition, callbacks ... etc, I think it's worth considering adding a UI-template that can show these read-only properties for any…
A bit of analysis:
Since this is audio and not video, it runs at a way higher rate, so I can imagine that only updating the volume on the frame itself can cause issues (24 FPS volume changes…
It took some digging, but I found the culprit. Baking the custom properties also bakes the current value of object.action_settings_index. So switching to the baked action will immediately switch…
That's the info I was missing, indeed -- the current PR doesn't remove any #include yet, so I was a bit 'hmmmmmmm'.
What's the reasoning behind this change? Why is it ok to remove this condition?
@ideasman42 I'd value your opinion on the approach taken here. To make the Blender GUI framework work for us, I think this is the right approach. However, I'm not too fond of having the Object.parent_inverse_transform property available to any other script. What do you think, would it be enough to prefix the property with an _? Or do you think there's a different approach?
Since this is a simple getter, better to make it a read-only property: