Revision 2cdb3d8 by Jacques Lucke (builtin-simulation-nodes, functions, functions-experimental-refactor, functions-temp, particle-solver-dev, simulation-tree) March 1, 2019, 15:33 (GMT) |
Merge branch 'master' into functions |
Revision 8085925 by Jacques Lucke (builtin-simulation-nodes, functions, functions-experimental-refactor, functions-temp, particle-solver-dev, simulation-tree) March 1, 2019, 15:31 (GMT) |
naming cleanup |
Revision 1f504e3 by Jacques Lucke (builtin-simulation-nodes, functions, functions-experimental-refactor, functions-temp, particle-solver-dev, simulation-tree) March 1, 2019, 15:27 (GMT) |
separate dependencies from tuple call body |
Revision 73ceb30 by Jacques Lucke (builtin-simulation-nodes, functions, functions-experimental-refactor, functions-temp, particle-solver-dev, simulation-tree) March 1, 2019, 15:08 (GMT) |
cleanup |
March 1, 2019, 15:06 (GMT) |
Cleanup: typo and update comment |
Revision b25aa2c by Jacques Lucke (builtin-simulation-nodes, functions, functions-experimental-refactor, functions-temp, particle-solver-dev, simulation-tree) March 1, 2019, 14:51 (GMT) |
only equal types are allowed to be linked |
March 1, 2019, 14:44 (GMT) |
Outliner: Collections Duplicate - remove original duplicate operator Now that we have better options (duplicate collection and duplicate linked) there is no longer need for the original dupli operator. In fact, as it was it was of little use if you ever had nested collections. |
March 1, 2019, 14:44 (GMT) |
Outliner: Collection - Duplicate Hierarchy, and Duplicate Linked Hierarchy As per the suggestion on T57064, this introduces two new options to duplicate collections. We then have: * Duplicate > Collection (New collection with linked content). * Duplicate > Hierachy (Duplicate entire hierarchy and make all contents single user). * Duplicate > Linked Hierarchy (Duplicate entire hierarchy keeping content linked with original). Development TODO: `single_object_users` can/should use the new functions. Reviewers: brecht, mont29 Subscribers: pablovazquez, billreynish, JulienKaspar Differential Revision: https://developer.blender.org/D4394 |
March 1, 2019, 14:44 (GMT) |
Cleanup: Update comment |
March 1, 2019, 14:44 (GMT) |
Cleanup: Set BKE_key_from_object/_p to take const Object * |
Revision 7260d03 by Jacques Lucke (builtin-simulation-nodes, functions, functions-experimental-refactor, functions-temp, particle-solver-dev, simulation-tree) March 1, 2019, 14:44 (GMT) |
fix |
Revision bdf1522 by Jacques Lucke (builtin-simulation-nodes, functions, functions-experimental-refactor, functions-temp, particle-solver-dev, simulation-tree) March 1, 2019, 14:34 (GMT) |
move CPU specific stuff to backend folder |
March 1, 2019, 14:30 (GMT) |
Cleanup: use variable instead of define |
March 1, 2019, 13:53 (GMT) |
Cleanup: move theme reset into it's own operator file |
March 1, 2019, 13:30 (GMT) |
Fix: Better fix for KeyingSet "Export to File" and unescaped characters Use Python's native raw formatting instead, which should take care of any issues we may face. |
March 1, 2019, 13:30 (GMT) |
Cleanup: Adding braces around all cases here to make it easier for the next step |
March 1, 2019, 13:30 (GMT) |
Fix T62057: Particle settings keyframes not showing in Graph Editor channels In short, the settings to expand/collapse the Particles Animation Dopesheet expander were no longer getting exposed, so the F-Curves attached to the particle settings were not showing up in the channels list as that section was collapsed and couldn't be opened from the UI. Early on during the development of 2.8, we originally wanted to completely remove the Particle System. Eventually that decision got walked back, and so particles were reinstated. Well... most of the relevant code was! One of the areas that was the most messed up during this process was the animation editor support for these channels. It seems that there was almost a two-step removal process here - the first pass tried to keep the channel definitions while removing all references to particle stuff, while the second pass tried to remove the definitions completely and/or re-added them in the wrong places, etc. To say the removal/reverting history is here is "colourful" is an understatement... |
Revision aac8754 by Charlie Jolly (greasepencil-experimental, greasepencil-object, greasepencil-refactor, soc-2019-npr, temp-gpencil-eval) March 1, 2019, 13:29 (GMT) |
GPencil: Fill changes + Replace Strokes with Adaptive + Remove dilate option, always on + UI changes |
March 1, 2019, 13:23 (GMT) |
Cleanup: use preferences prefix for Python operators |
March 1, 2019, 13:11 (GMT) |
Collections: mark visibility properties as not animatable. Better to communicate the current state clearly until this is supported, for now only object visibility can be animated. |
|
|
|


Master Commits
MiikaHweb | 2003-2021