Blender Git Loki

BMesh: utility function to split off wire edges

cleanup: C99

- for loop scope
- tighter scope on local vars
- more bool
- more const

BGE clean up: use float version of trigonometric functions

BGE Ketsji clean-up: double-promotion warnings

Cycles: Fix wrong assert failure happening after recent de-duplicate

This is actually intended behavior to return NULL when the socket is not
found. It's used in certain BSDF nodes to query whether some inputs exists
or not.

Perhaps we can be more explicit here and have dedicated logic to query
socket existance and keep assert in place.

In any case, even if we lost assert() for the constant fold now it's
still somewhat better than duplicated code. Perhaps.

Cycles: De-duplicate utility functions in ccl::Graph

Temp workaround: Object mode pie glitches since 'Edit Strokes' mode was introduced

To ensure all items of a pie are always at the same position, invisible dummy buttons were added for unavailable items. This caused mainly two issues: Command line printed warning because of the > 8 elements, and some modes weren't visible in some cases ('Object Mode' entry was missing in stroke edit mode).
To solve this nicely, we had to support > 8 items per pie. Will look into that this week, but for now, drawing dummy buttons is disabled.

From a user POV this has two ugly consequences: 1. While this temporary workaround is used, *some* pie items are positioned differently than before, 2. The 'Edit Strokes' mode entry might change its position depending on the amount of available modes.

Temporary solution for Add/Subtract toggles being meaningless for some GPencil brushes

For now, we just change the labels of these toggles so that it makes sense what
results we should expect from each. A better solution may be to create separate
"direction" props for the different brush types here, so that we can also define
more appropriate tooltips too to go with the labels.

Compositor: Expose track velocity via the Track Position node

velocity is measured in pixels per frame. It is basically a coordinate
difference of track coordinate at current frame and previous one (no future
prediction happens).

It's not really most intuitive place for such a things, but historically the
node was called this way..

Track velocity could be used to face effects like motion blur bu piping it
to the vector blur node.

Reviewers: campbellbarton

Reviewed By: campbellbarton

Subscribers: hype, sebastian_k

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

Correct own error in knife edge-net cutting

Need to ensure no duplicate edges in the array.

Cleanup: math lib naming

Distinguish between line / line_segment

Cleanup: math lib naming

Rename not-very-descriptive (p1, d) -> (ray_origin, ray_direction)

Cleanup: consistent naming for closest_to_line api

BMesh: split-py-edge now splices verts into edges

Edge chains spanning faces or ending without a connecting edge
are now supported by splicing verts into the face boundaries.

Fix split-py-edge assuming valid face indices

Also reduce variable scope

OpenGL: remove utility functions that take doubles

Kill these before someone is tempted to use them! Discourage use of fp64
generally.

use float (not double) for font matrix

Following up on recent double --> float commits in the game engine.

Fix T46936: cycles GLSL should not draw outlines for transparent materials.

Fix T46951: invalid OpenGL mipmaps when using high bit depth textures.

Fix 'change path' opening file browser with wrong filter for sound strips

Changing path of a sound strip (select strip->C->'Path/Files') opened a file browser without filter for sound files, so sound files weren't visible.
Also, for movie/image files, now only movie **or** image files are visible in the file browser by default (instead of both).

Reported by @venomgfx, thanks!