Blender Git Loki

Kaikki Blender Git kommitit.

Page: 4311 / 8462

July 2, 2016, 12:16 (GMT)
Modified the guide strand creation operator to allow shorter-than-max strands.

The guide strand format may change, but it should allow varying numbers of control
points.
July 2, 2016, 10:22 (GMT)
Correction for MSVC
July 2, 2016, 10:15 (GMT)
Calculate barycentric interpolation weights using a simple kdTree method.

This method uses the 3 closest points on the scalp for defining interpolation
weights. This method has drawbacks in cases of thin geometry, but it is
simple to implement.
July 2, 2016, 08:32 (GMT)
Vertex attributes for the strand root points.

These attributes carry information for interpolating guide strands
in the geometry shader. Each strand can have up to 4 guide strands
(identified by index) with a normalized weight for each.
July 2, 2016, 08:18 (GMT)
BMesh: utility function to resize bmesh elements

This can be used to re-allocate bmesh data with/without tool flags.
Needed for Symmetrize since it uses bmesh operators from dyntopo.
July 2, 2016, 00:59 (GMT)
merged master, but something in the merge broke my windows build, so I had to change something. Also fixed a bug in mirrored painting.
July 2, 2016, 00:19 (GMT)
Merge branch 'master' into soc-2016-pbvh-painting
July 2, 2016, 00:17 (GMT)
Added mirror painting and radial symmetry.
July 2, 2016, 00:08 (GMT)
Cleanup: comment blocks
July 2, 2016, 00:00 (GMT)
Cleanup: style
July 1, 2016, 21:48 (GMT)
Fix Cycles OpenCL not taking Extend and Clip extension types into account.

(See T48720).
July 1, 2016, 19:24 (GMT)
Merge branch 'master' into soc-2016-cycles_images

Overwrite branch specific changes, make it match vanilla master again. Have to re-think some of that half stuff there.
July 1, 2016, 18:50 (GMT)
Fixed undo bug.
July 1, 2016, 17:20 (GMT)
Cleanup: Alembic and HDF5 CMake modules.

- Remove references to Samplerate
- Copyright year
- hdf5_hl requirement removed in Alembic 1.6.0

Patch by @ejnersan.
July 1, 2016, 16:55 (GMT)
Remove extra statement from some test.
July 1, 2016, 16:52 (GMT)
add robustness to correspondence adding:
- when the correspondence has been added, give an error message and
return
- when a conflict correspondence is added, give an error message
July 1, 2016, 16:50 (GMT)
Merge branch 'master' into alembic_basic_io
July 1, 2016, 16:33 (GMT)
Curves: read/write orders, knots, weights and radiuses.
July 1, 2016, 16:29 (GMT)
"Fix" crash when deleting linked object which has indirect usages.

This is in fact very hairy situation here... Objects are only refcounted by scenes,
any other usage is 'free', which means once all object instanciations are gone Blender
considers it can delete it.

There is a trap here though: indirect usages. Typically, we should never modify linked data
(because it is essencially useless, changes would be ignored and ost on next reload or
even undo/redo). This means indirect usages are not affected by default 'safe' remapping/unlinking.

For unlinking preceeding deletion however, this is not acceptable - we are likely to end with
a zero-user ID (aka deletable one) which is still actually used by other linked data.

Solution choosen here is double:
I) From 'user-space' (i.e. outliner, operators...), we check for cases where deleting datablocks
should not be allowed (indirect data or indirectly used data), and abort (with report) if needed.
II) From 'lower' level (BKE_library_remap and RNA), we also unlink from linked data,
which makes actual deletion possible and safe.

Note that with previous behavior (2.77 one), linked object would be deleted, including from linked data -
but then, once file is saved and reloaded, indirect usage would link back the deleted object,
without any instanciation in scene, which made it somehow virtual and unreachable...

With new behavior, this is no more possible, but on the other hand it means that in situations of dependency cycles
(two linked objects using each other), linked objects become impossible to delete (from user space).

Not sure what's best here, behavior with those corner cases of library linking is very poorly defined... :(
July 1, 2016, 16:29 (GMT)
Outliner: pass operator's reports to all operation callbacks.

Also define single callback func typedef, cleaner this way!

Note: maybe we want to do that for the other callbacks too (data, etc.), but will be enough for now.
Tehnyt: Miika HämäläinenViimeksi päivitetty: 07.11.2014 14:18MiikaH:n Sivut a.k.a. MiikaHweb | 2003-2021