- User Since
- Oct 26 2005, 7:41 AM (643 w, 1 d)
Closing. The previous commits should implement the desired functionality now. (But somehow, I ended up quoting the wrong task number when making the commits)
Ack! This should have linked to T53905 instead!
Ack! This should have been T53905
@Julian Eisel (Severin) Right. That sounds reasonable.
In general, I don't have any major objections to the stuff proposed here.
Thu, Feb 15
Tue, Feb 13
Hmm.. that sound strange. Assigning to self to investigate
Fri, Feb 9
Thu, Feb 8
I've taken a look at what the code is currently doing. Basically, it makes several assumptions (based on the grabbing/translating keyframes case):
- You're only moving a few keyframes at once (and mostly not a whole set of consecutive points that may end up overlapping after the transform)
- You're more interested in the ones that you're currently moving (i.e. the selected ones) than the ones not moving, so it only keeps the selected ones if they come in conflict with anything
WIP update of the changes from the branch (as of ~5 minutes ago).
I just discovered that this commit breaks the datablocks viewer (specifically, the block of code I've left a comment on).
Wed, Feb 7
Tue, Feb 6
The problem is that when a bone used as a custom handle reference "goes missing" while in Edit Mode (e.g. by merging it directly, deleting it, or making it zero-sized and having it automatically removed), Blender will crash as it cannot resolve the missing custom-handle pointers after the change.
Fri, Feb 2
Great to see you picking this up again :) Let's try and wrap this thing up!
Thu, Feb 1
Wed, Jan 31
Tue, Jan 30
Mon, Jan 29
Ok, so carefully re-reading the bug description, it sounds like there are two parts to this: 1) Animation Data, 2) Constraints