Blender Git Commits

Code cleanup: float/double promotion

Code Cleanup: PBVH, avoid sqrt and use bool for raycast functions

Code cleanup: style

Fix for invalid abs() use (from daccaa7)

Change to sampling: Take biggest triangle side as detail size on
intersection, since detail determines the maximum allowed triangle edge
size

Fix T39356: unsatisfied with uv pin unpin button, small bug

Fix typo in API documentation.

Cycles Standalone: XML Updates for Branched Path Multi Light.

Code cleanup: Move AA Samples variable, this is not exclusive to Branched Path.

Fix T39351: Blender crashes when enabling Mesh Analysis.

This code was using a //const// char array for fallback colors and then
writing to it (hidden to the compiler by explicit casting). Bad!

Fix T39353: Make Single User menu entries do not work correctly.

Fix T39347: Pressing backspace during empty number input for translation results in 0.5828 increments

Interesting one, took me hours to understand the issue - a stupid typo checking the wrong value against the wrong flag (present since 2008!).

Further tweaking to numinput - enhance 'Reset' behavior.

Ways how it was resetting its values (backspace) was far from satisfaying. Now, e.g. when scaling, it will reset at 1 (or whatever mouse-value it was before entering numinput), instead of some ugly 0.0 value.

Implementation details:
* Values passed to applyNumInput() are stored as default ones (val_org), if it is not EDITED.
* applyNumInput() returns a boolean saying whether it actually set values or not.
* When backspace hits its ultimate step (where it clears all EDITED flags and reset all default values),
it sets a temp FAKE_EDITED flag that will be used to apply one last time values of numinput
(so that default values actually get applied!).

There are important things to note here for code using numinput:
* Values passed to applyNumInput() should be valid and are stored as default ones (val_org), if it is not EDITED.
* bool returned by applyNumInput should be used to decide whether to apply numinput-specific post-process to data.
* *Once applyNumInput has been called*, hasNumInput returns a valid value to decide whether to use numinput as drawstr source or not.

Those two steps have to be separated (so do not use a common call to hasNumInput() to do both in the same time!).

Use eyeliner cursor for sampling. Thanks to Thomas Beck for the
suggestion :)

Slight cosmetic improvement on UI. Add eyedropper icon to detail sample
operator and move it next to the detail slider

Detail sampling operator

Located on topology panel.

To use just click on button and click on mesh.
Operator will just use the dimensions of the triangles below to set the
constant detail setting.

Also changed pair of scale/detail size with nice separate float
percentage value.

Cycles: SSE optimization for line segments/ribbons hair

Gives ~11% speedup for hair.blend, ~10% for koro_final.blend

Also extract few common subexpressions in hair calculation.

Reviewed By: brecht

Differential Revision: https://developer.blender.org/D318

Flood fill for dyntopo constant detail mode.

Nothing spectacular here, fill tools are easy. Just take the dyntopo
code and repeat until nothing more to do.

The tool can be located in the dyntopo panel when the dyntopo constant
detail is on.

Also added scale factor for constant detail. This may change when detail
sampling gets in, I am not very happy with having two numbers here,
still it will give some more control for now.

Warning cleanup:

* Comparison in utf detection code always failed
* Cast to integer to silence grumpy 64bit gcc

Cleanup: Restrict the debug -gline-tables-only to cxx_debug in cycles and spelling