- 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
channel_group_containing_index()
to return the group index
ReportList *
parameter from RNA function
I think this is fine for now, yeah. I'm not sure if I agree that it really belongs in this function, but I also just generally feel that it's pretty unclear right now what's responsible for what anyway, and we'll probably want to do some refactoring at some point to sort that out. So I think this is a fine fix given the current state of the code.
The comment here suggests that this line was here to affect the behavior of insert_vert_fcurve()
, which it's now been moved into. Can you confirm whether this line has any effect anymore? Because at least at a glance, I can't see anywhere that this flag is used after this point. If we can just kill this line altogether that would be great.
So it turns out it would be a bit annoying to completely remove it, since then I'd have to duplicate the calls needed to just to basic removal of an element from an array. But I did simplify it…
Just to be extra clear: yes, please just land as-is.
I'm probably giving mixed messages by continuing to discuss things, but I'm really just continuing the discussion for how we might want to…
Yeah, go ahead and land it as-is. I don't think it makes sense to block PRs on relatively minor and subjective things like this.
but having a separate function allows me to go by function…
channel_group_remove_raw()
and make it private
That's totally fair! Not to block landing this in any way (just for the sake of discussion), I do, however, want to make a case for more liberal use of lambdas in c++ code:
I think one of the…
I think we can keep this open as a known issue.
There's no way to completely solve it in a robust mathematical sense, but I suspect we could do something like find the multiple-of-360 offset…
since quaternions seem to "ease in ease out" even when set to linear.
Yeah, that happens when there are large angles between the keys. If you key every 90 degrees instead, that effect is…