- Amsterdam, Netherlands
- https://cessen.com
-
Animator, rigger, and software developer. Currently working at the Blender Institute as a developer on Blender's animation system.
Been using Blender since 1998, and worked on Big Buck Bunny and Sintel (two of Blender's open movie projects).
- Joined on
2003-03-21 -
-
No meaningful difference, just didn't find get_action() when I was looking for a function that did that. Thanks!
The rearrangement of the logic here appears to just change what situations get misleading error messages. Now if autoexec fails, invalid expressions that don't otherwise require Python also get displayed as not working due to "Python restricted for security", which isn't really the cause. Example file attached.
Is the G_FLAG_SCRIPT_AUTOEXEC_FAIL flag always the inverse of G_FLAG_SCRIPT_AUTOEXEC (used before)? That seems redundant to me, which makes me a little suspicious that they might be subtly different.
AnimationEvalContextmay be obsolete now. At least at that level.
Oh, interesting. Yeah, it looks to me like we may want to make this a more pervasive change, including e.g. `insert_keyfram…
I've currently implemented this as a free function since it operates on a bAction rather than an Action. But it could just as easily be a method on Action, and we just always wrap before calling.
