Blender Git Commit Log

All Blender Git commits.

Page: 4626 / 8462

November 9, 2015, 20:00 (GMT)
Fake user: add BKE_library helpers to set/clear that flag.

Since it also involves usercount manipulation, safer and cleaner to do it in BKE_library...
November 9, 2015, 20:00 (GMT)
Rework a bit id_us_min, and make it assert on usercount error.
November 9, 2015, 20:00 (GMT)
Cleanup: avoid incrementing/decrementing id->us outside of BKE_library.

We have callbacks for that, they also do some checks and help ensure things are done
correctly. Only place where this is assumed not true is blenloader (since here we
may affect refcount of library IDs as well...).
November 9, 2015, 20:00 (GMT)
Cleanup: readfile: get rid of USER_ONE, replaced by USER_REAL everywhere.

USER_ONE was only ensuring id->us was non-zero, while USER_REAL ensures
it is non-zero **and** >1 in case fake_user flag is set (which at least
ensures us unsetting fake_user won't leave id->us in invalid zero state).
November 9, 2015, 19:31 (GMT)
CMake: remove setting of policy CMP0043 to OLD.

CMake 3.0 ignores the suffixed COMPILE_DEFINITIONS_<CONFIG> variants if policy
CMP0043 is NEW, preferring instead to consume the unsuffixed COMPILE_DEFINITONS
property and evaluate generator expressions in it.

Setting the policy to OLD causes CMake 3.0 to not ignore those properties.

Use the suffixed properties for compatibility only for CMake versions older
than 3.0 using an explicit version check. Use the non-suffixed property with
generator expressions otherwise.

These definitions should mostly not be needed at all - CMake already sets
NDEBUG in suffixed CMAKE_CXX_FLAGS_<CONFIG> variables. The _DEBUG macro is
non-standard, but is used in several places in blender (usually in an OR
combination with the DEBUG macro). Additionally, blender overwrites (instead
of appending to) the CMAKE_CXX_FLAGS_<CONFIG> variables on WIN32.

Rather than try to fundamentally change how debug-macros are handled in
blender, change the buildsystem to keep the same behavior without requiring the
CMP0043 policy set to OLD.
November 9, 2015, 18:31 (GMT)
UI: avoid duplicating the string to set the cursor

Internal change only.
November 9, 2015, 15:53 (GMT)
Revert "Increase CMake minimum version to 3.0"

This reverts commit ff3cf93405e63fa367f64412bcfe96b382b24b38.

Turns out distros only a year old still use CMake 2.8x
November 9, 2015, 15:16 (GMT)
Refactor: renamed 'Expression' to 'Function'.
November 9, 2015, 13:53 (GMT)
Fix broken groupobject usercount handling.

As we can see in (original) read code, ob pointer in groupobject is actually a 'USER_ONE' case.
This was not done in 'add object to group' code, probably because we can assume objects always
have at least one user in that case? Made it explicit now. Also fixed foreach_ID_link looper.

In general we have waaayyyyyy too much 'own handling' of ID->us count in code currently,
will clean up that...
November 9, 2015, 12:37 (GMT)
Increase CMake minimum version to 3.0

This allows us to use newer features of CMake, and less hassles having to test & support older versions.
November 9, 2015, 12:22 (GMT)
Removed unused deprecated code parts.
November 9, 2015, 09:59 (GMT)
fix for dynamic fracture rotation glitch (was wrong calculation)
November 8, 2015, 23:12 (GMT)
Correction to recent commit, bone face map wasn't written to .blend
November 8, 2015, 22:58 (GMT)
Initial steps for a connected bone and face map selection

Now, when a face map is selected, all bones it is assigned to are selected as well. If this will stay in final design is not sure yet, but the logic added will be needed anyway (likely).
November 8, 2015, 21:25 (GMT)
Support reading Face Map assignments from .blend, corrections to previous commit
November 8, 2015, 17:04 (GMT)
Rework workflow for connecting Face Maps and bones

Previously, a Face Map was 'connected to a bone' by giving it the same name as the Face Map, and assigning the armature which includes the bone to the object's Face Map using an Armature modifier. This was pretty unintuitive and tiresome to set up and it also brought some technical issues (there was no nice way to find a Face Map assigned to a bone from the bone - this means we couldn't use Face Maps together with bones in pose mode as current design approach would require).

So finally I came up with a new approach:
The bone context in the Properties Editor got a new panel "Face Maps". In this panel there is a search button to choose an object. After an object is chosen, a Face Map from this object can be chosen using a second search button. That means a user can assign a Face Map to a bone directly, without having to worry about the armature.

This approach currently has the limitation that only one Face Map can be assigned to a bone (a Face Map can be used by multiple bones though). This means we can later use one Face Map to manipulate multiple bones, but we can't use multiple Face Maps to manipulate one bone.
Anyway, this could be changed easily later, but I'd rather avoid this since it complicates the UI/workflow again.

----

Old code is kept.
Also includes minor cleanup.
November 8, 2015, 16:59 (GMT)
Merge branch 'master' into id-remap
November 8, 2015, 14:17 (GMT)
Code cleanup: remove some unused mesh laplacian code.
November 8, 2015, 11:20 (GMT)
Disabled some unused function args.
November 8, 2015, 08:35 (GMT)
Merge branch 'master' into object_nodes
By: Miika HämäläinenLast update: Nov-07-2014 14:18MiikaHweb | 2003-2021