I think the check exists to restrict the user from applying values that would be grossly impractical, like 1e-20. That said, if we want to keep the check, we could ask if the applied sum is zero;
float angvelsum = angvel.length2()
if (m_object && ( angvelsum == 0 || angvelsum > (SIMD_EPSILON*SIMD_EPSILON)))
I've got no idea how to submit patches, though.
Abandoning this since I don't like the approach used here. Maybe I'll find the time to look into this again soon.
Forgot some pieces of code in previous update
Made needed modifications to curve intersection code
Now OpenGL rectangle updates are done per symmetry brush
Sorry this took so long to review - must have slipped through the net :(
@sergey, it seems, that you were right. If I create a plane track on the 64 bit system, save it, open it on the 32 bit system and click on the plane track, blender crashes immediately. The same is vise versa. With the build dated 24.04.2015 the problem seems to be solved.
@venomgfx, since this is already pretty old, would you mind going over the list of added info to check which info you'd still consider as useful? I can then make things ready for master (and commit if changes remain trivial)
Revisions after code review
Closed as wished by Jim.
No answer for almost one week -> closed! Sorry, but we have to be very strict in order to keep our bug tracker organized. We can consider reopening after we've got the requested information.