Blender Git Loki

add armature_foreachScreenBone(), use for lasso and circle select.
also add boundbox checking for lasso select.

code cleanup: de-duplicate enum.

code cleanup: use functions to initialize selection user data structs, use radius-squared for circle select comparisons.
edge_fully_inside_rect() & edge_inside_rect() args were shorts when all callers were passing ints.

Code cleanup
* Added/fixed some comments
* Swapped order that invoke/exec calls are defined in the operator definitions
to reflect flow better

Fix generated texture coordinate issue after "from dupli" option was added.

Follow Path Constraint - "Animate Path" Operator

Added a convenience operator to the Follow Path constraint which adds a F-Curve
for the path (or the operator's "fixed position" value if no path is assigned),
with options for setting the start frame and length of motion. This makes it
easier for common users to just set up a quick follow-path animation where the
camera (e.g. flying around a set over certain number of frames).

A key advantage of this is that it takes care of the underlying math required
for setting up the generator curve accordingly (I've got some plans for making
this a bit friendlier to use later). Now, animating the paths is a one-click
operation, with the start and length properties able to be controlled using the
operator properties.

Whitespace edits

Warning indicators for animators when Auto Keying is enabled during transform

Recently on the bf-funboard list, there have been some requests for clearer
indications for animators that autokeying has been enabled when transforming so
that corrective action can be taken sooner if this wasn't expected. This is
especially important in distributed+collaborative environments where multiple
artists may work on a single shot file: someone working on a shot from
another animator may not be aware that autokeying was enabled, thus accidentally
setting a whole bunch of extra keyframes.

In this current incarnation, we display using red (not hardcoded, but using an
existing theme color) a solid 1px border around the 3D view while transforming
with autokeying enabled. In addition to the border, a blinking indicator (record
icon + "Auto Keying On" text) appear in the top right corner, as inspired by the
traditional recording indicator icons on camcorders.

Fix #32770: iTaSC IK solver not working correct with bones that have stretch with
have all rotation axes disabled.

Typo fix: Tooltip for "Offset Factor" for FollowPath constraint referred to
"bone" instead of "curve"

Clean up in "add object" code:
* Get rid of ED_object_add_generic_invoke() and all invoke callbacks using it, it was doing nothing exec() callbacks would not do. In fact, its only action (setting part of common add ops properties, like loc, layers, etc.) was needed too by direct exec call, so it was done twice in case of using invoke()!
* Replace custom invoke code for metaballs by WM_menu_invoke helper (as already used by lamps).
* Add a new OBJECT_OT_empty_add op, to allow direct addition of empties of a given drawtype.
* And some general code cleanup (like trailing spaces, empty lines, ...).

Did quite a bunch of tests/verifications, but obviously could not tackle all possible scenarios... Anyway, if any, bugs should arize quite quickly (but I donâ??t expect any! :p ).

Fix #32734: Object.to_mesh() gave wrong user count for curves/surface/text objects.

Fix related to #32734: crash saving blend file from render_pre callback. Not
sure I want to recommend anyone doing this, but the fix is simple.

Fix #32735: GLSL shadows not working together with X-ray drawing.

more improvements to logic for selection/projection: replace ED_view3d_project_short_global() with ED_view3d_project_int_object() in some places.

Fixed compilation error on widows

Was caused by mixing up own C-API typedefs with OCIO's

Booleans: epsilon for planar checks seems a bit too small for single precision math

This could solve issue #32748: Boolean Modifiers Making unneeded edges?

Fix #32707: texture preview not loaded

Some effect-less code cleanup...

Bugfix [#32760] Crash on entering pose mode if motion paths have no baked points

Dunno how a file with this situation arose, but we now perform some more sanity checking to abort in this sticky situation.