Blender Git Commits

Blender Git "temp_widgets_c++_experiment" branch commits.

Page: 7 / 22

September 16, 2015, 23:41 (GMT)
Fix memory leak in facemap drawing

There's still some memory weirdness going on, but haven't found out what causes it yet.
September 16, 2015, 21:03 (GMT)
Fix memory leak in manipulator code
September 16, 2015, 17:20 (GMT)
Fix facemap drawing crash

Issue was that MPoly wasn't reset after iterating.
September 16, 2015, 14:54 (GMT)
Fix old graph editor crash
September 16, 2015, 14:35 (GMT)
Fix some potential bugs in facemap drawing code
September 16, 2015, 14:25 (GMT)
Merge branch 'master' into wiggly-widgets
September 16, 2015, 13:29 (GMT)
Remove unneeded widgetgroup customdata
September 14, 2015, 23:09 (GMT)
Cleanup: Naming, consistent API call order
September 14, 2015, 22:47 (GMT)
Add asserts to ensure functions are called in correct order

A bit silly having to ensure functions are called in correct order, but necessary for now.
September 14, 2015, 22:10 (GMT)
Cleanup: Avoid special widget flag API functions, use general function instead
September 14, 2015, 21:57 (GMT)
Minor corrections to previous commit
September 14, 2015, 21:52 (GMT)
Doxygen documentation for widget library

And of course some minor cleanup.
September 14, 2015, 15:31 (GMT)
Remove redundant arrow widget flag
September 14, 2015, 14:52 (GMT)
Merge branch 'master' into wiggly-widgets
September 14, 2015, 14:43 (GMT)
Get rid of overkill arrow widget custom line vec drawing

Instead, we now can use widget offset property to define starting point and a new arrow widget length property to define line length.
September 10, 2015, 23:38 (GMT)
Merge branch 'master' into wiggly-widgets

Conflicts:
source/blender/editors/transform/transform_manipulator.c
September 10, 2015, 23:31 (GMT)
Cleanup: Use BLI_INLINE
September 10, 2015, 23:24 (GMT)
Remove redundant fixes

Not needed anymore since rB10678f7572ee0d37
September 10, 2015, 22:52 (GMT)
Fix 3D view widgets not updated correctly

Was barely visible to users (noticed only with view oriented manipulator), since I fixed appearing issues individually. Will remove these fixes next.
September 9, 2015, 23:59 (GMT)
Don't offset arrow widget range by property min value

Previously, the min value of the arrow range was set to be at the origin, but figured out in most cases this is actually not wanted (e.g: force field strength widget min value is -200, meaning at strength=0, the widget would be offset 200 pixels; camera focal length widget min value is 1, meaning widget was constantly offset by -1). Instead, the origin should be where the value of the property is 0.

This might still be wanted for some future cases, so leaving old behavior #ifdef'ed out.
By: Miika HämäläinenLast update: Nov-07-2014 14:18MiikaHweb | 2003-2021