Blender Git Commits

don't write file history in backgound mode (running ctest would overwrite all my recent-files.txt), and add an error about mingw/quicktime being unsupported.

svn merge -r 37212:37306 https://svn.blender.org/svnroot/bf-blender/trunk/blender

sync addons and tests with trunks

draw sequences with invalid effect frame ranges pink to highlight they are invalid and wont render.

fix for vertex group copy to selected
- was using un-initialized stack memory if the source / target object had no vertex group.
- if the target object had no vertex groups it would fails silently (not a bug but not very good functionality)
- added an error message if any copying fails.

editarmature.c and paint_vertex.c
I added the first version of multi-bone selection for faster, temporary locking/unlocking; right now, if multiple bones are selected, the selection is considered unlocked, despite any vgroup checkbox status.
Every other group is considered locked.

paint_vertex.c
A modified Auto Normalize was inserted to normalize the active group normally instead of locking the values: it was causing the active group to steal weights from locked groups if the active group had a weight of 1.0, and that destroyed the locked groups deformations.

fix for sequencer transform with effects strips where the effects could be moved to invalid times to avoid overlap but would immediately refresh back to overlapping locations after.

disable the readonly state while rna property callbacks run.

Fix: correct spacing for file select items, using font size + dpi.

rna option not to save certain properties for redoing later, currently only used by operator presets.

fix for edge slide snapping values being incorrect (reported by Nether Hound).
Also dont call the value a 'Percent' and clamp the range displayed in the header.
snap range being

update ctest md5sums for import/export to match changes to the scripts, also some minor formatting change for bpy_props.c

getting useful results out of the round compo node was tricky, use the second value to determine how much to round by (can be used like a posterize filter)

error pointed out by Jeroen Bakker with the math nodes round function. was incorrectly using the output rather then the input.

Modify the unifont.ttf to have a better look

fix for glitch in previous commit with 0.00002 displaying as 0.000020, this uses 2 calls to double_round which I'd rather avoid but at least it now works right for users.

smarter precision calculation, so 0.000001 isn't displayed as 0.00.
there is a minor problem with this commit:
0.00001 --> 0.00001 # good
0.000015 --> 0.000015 # good
0.0000199 --> 0.00002 # ok
0.00002 --> 0.000020 # wrong, has trailing 0

Tried to fix this but the case is hard to check for without more calculations which Id like to avoid.

Move UI float precission calculation into its own function.

BGE Animations: Removing some redundant pose copies from BL_Action.

A line of code -can- wreck your day. Should work now, :)