Blender Git Commits

code cleanup: use bool's for snapping functions.

changes to ruler
- click-drag adds a ruler if there are none.
- pressing enter stores the ruler for re-use when activating again (saves as a grease-pencil layer).
- add to toolbar.

add delete key for removing active ruler.

Fix to BLF_pgettext, which was returning "" when passed NULL msgid... Never noticed any problem, but it looks it could produce strange UI issues (like deactivated buttons), and it was not consistent anyway!

Thanks to S. Lockal for spotting the issue and providing a patch.

add ruler snapping vert/edge/face (Holding Ctrl)

avoid floating point exceptions in snapObjects(), was attempting to scale up FLT_MAX.

Feature request:

Blender's anim player (blender -a) now allows drop of image or movie file.
It then restarts itself completely (close window, open new).

Applying similar optimisations as r.55092 for Animation Data

Adding include for NULL define in c++

[#28352]3dsmax preset, patch by Nik Prodanov, this provides both an interaction preset and a keymap preset for those migrating from 3dsmax

code cleanup: 0 --> NULL

fix for typo in skin modifier that resulted in incorrect vertex weights.

style cleanup

Bugfix [#34560] Wrong angle for text in Horizontal mode of Properties space

Rotation angle for text was still in degrees not radians

fix null pointer dereference in BM_edge_is_contiguous() (own code).

[#34541] Sketching bones created bones with 0 radius for envelope

This commit is just a stopgap measure (i.e. it fixes the symptoms but not the
real underlying cause) of this bug. For some reason, iter->size is nearly always
an "effectively zero but not truly zero" value. Hence, the envelope sizes would
get adjusted, but would be scaled to an impossibly small value (taken from
iter->size).

From my investigations so far, iter->size is mostly either set to (or left as)
0, except in a rare case when dealing with volume snapping, when the values
somehow get propagated there from various intermediate data points. But, that
almost never works either.

Improving warnings when keyframing fails for IKEY over a button

Now, instead of silently failing, an error message saying that the property
cannot be animated is displayed

Bugfixes: [#34394] and [#31843] Visual Keying not working for bones

Big thanks to Josef Meier (jomeier) for finding the fix!

It turns out that this was a case of variable shadowing that had been overlooked
and compilers were not warning about.

A big code clean-up patch from Bastien Montagne, many thanks!

OSX/gcc-4.6: workaround a compilerbug, use apple-gcc instead