Blender Git Commits

Add translation context for volume (Audio), pitch (Rotation) and rename tip->tooltip for custom properties

Tracked in [#31062] [2.6x] Context Ambiguity List & Discussion (keep updating)

make ED_view3d_project_int equivalent to ED_view3d_project_short functions.

refactor ED_view3d_project_short & ED_view3d_project_short_noclip,

This is apart of a code cleanup to make ED_view3d_project_short/ED_view3d_project_int/ED_view3d_project_float interchangeable. Currently they work very differently in a way thats quite confusing (and cause of bugs in blender that remain uncorrected) - fixes coming.

There are also cases where ED_view3d_project_short is used, then the values are converted from shorts into int's after because ED_view3d_project_int() behaves differently, will unify behavior of these functions after this commit.

- rather then clip/noclip versions, pass flags (for bound-box clip, window clip).
- rather then store the invalid clip-value, return success (or error value clip_near, clip_bb, clip_win, overflow).
- remove local copies of project functions from drawobject.c: view3d_project_short_clip, view3d_project_short_noclip, view3d_project_short_clip_persmat.


add functions:
- ED_view3d_project_short_global() global space projection
- ED_view3d_project_short_object() object space projection.
- ED_view3d_project_short_ex() take perspective matrix and local space option as args.
- ED_view3d_project_base() - special function to set the Object 'Base' screen coords (sx, sy), since this is a common enough operation.

Have CPack rpm builder install the colorspace folder too

Kind of cleanup of "menu strings": always have a space between the entry's label and value (these strings are a nightmare to handle in RTL languages like arabic or persian, but a bit less of a nightmare this way ;) ).

Fix for rtl processing of menu strings...

Color Management: fallback to stub ocio implementation in cases when
ocio configuration file failed to load

This solves issues with infinite NULL-checks to prevent crashes in
such situations. Currently only happens if there's no configuration
file at all, but could be tweaked further to fallback if this file
isn't usable by blender.

style cleanup: comment blocks

code cleanup: comment verse outliner views, also correct warning in recent commit.

OSX/cmake: fix warning: go back to initial state, not the right way to get rid of this

OSX/cmake: fix warning: second try

Bugfix [#32754] Clear Motion paths button not available on Motion paths panel

On second thought, perhaps it is more convenient/natural if this was shown in
both places, given that many
people may only find the motion paths options through the UI now.

Added convenience operator to clear animation (i.e. all keyframes = F-Curves)
from selected objects and bones

OSX/cmake: fix warning: -Wuninitialized is not supported without -O, in debug-mode

fix for using hsv uninitialized in ui_draw_but_HSVCIRCLE()

code cleanup: make the behavior of set_current_material_texture() clearer and remove redundant NULL check there. also small changes to ui_draw_but_HSVCIRCLE().

avoid a sqrtf call in ui_hsvcircle_vals_from_pos() for values outside the circle.

use GCC's -Wpadded on DNA files, gives more useful warnings then makesdna.

code cleanup: remove USE_BMESH_FORWARD_COMPAT - this was added to load bmesh in pre-bmesh blender version, remove MODSTACK_DEBUG, was never used.

* Trunk is open again, BCon 1.