April 25, 2020, 02:22 (GMT) |
Cleanup: Select sync from outliner Move the condition to check if selection syncing is enabled to inside the syncing function rather than before each time it is called. |
April 25, 2020, 02:18 (GMT) |
Fix: Selection syncing for outliner operators A few outliner operators that modify selection were not tagging for a selection sync which led to selection inconsistencies. This adds syncing for the following operators: * Duplicating and deleting collections * Selecting/deselecting collection contents * Drag and drop * Object select, deselect, delete, and delete hierarchy |
April 24, 2020, 21:52 (GMT) |
BLI: add LinearAllocator This allocator is useful when it is necessary to allocate many small elements. |
April 24, 2020, 21:35 (GMT) |
BLI: improve StringRef.copy |
April 24, 2020, 21:14 (GMT) |
BLI: add DefaultHash specializations for StringRef and StringRefNull |
April 24, 2020, 20:33 (GMT) |
BLI: Implement StringMap.add and StringMap.add_or_modify |
April 24, 2020, 18:05 (GMT) |
UI: Move Scene Statistics to the 3D Viewport Removes statistics from footer and to an (optional) overlay in 3DView. Differential Revision: https://developer.blender.org/D7410 Reviewed by Campbell Barton |
April 24, 2020, 15:23 (GMT) |
Fix T69753 Instanced Metaballs not rendering but showing up in Viewport This hides the original metaballs when they are used in duplifaces/-verts instancing, and still shows the instanced metaballs. The visibility of the original metaballs is now determined by the visibility of the instancer. I'm not too thrilled about this, but at least it gives users the ability to show/hide the metaballs for viewport/render. Differential Revision: https://developer.blender.org/D7478 |
April 24, 2020, 15:10 (GMT) |
Tests: use explicit Python to run unit tests CentOS on the buildbot still runs Python 3.6, which is also used for the unit tests. This means that the tests can't use language features that are available to Blender itself. And testing with a different version of Python than will be used by the actual code seems like a bad idea to me. This commit adds `TEST_PYTHON_EXECUTABLE` as advanced CMake option. This will allow us to set a specific Python executable when we need it. When not set, a platform-specific default will be used: - On Windows, the `python?.exe` from the installation directory. This is just like before this patch, except that this patch adds the overridability. - On macOS/Linux, the `${PYTHON_EXECUTABLE}` as found by CMake. Every platform should now have a value (configured by the user or detected by CMake) for `TEST_PYTHON_EXE`, so there is no need to allow running without. This also removes the need to have some Python files marked as executable. If `TEST_PYTHON_EXE` is not user-configured, and thus the above default is used, a status message is logged by CMake. I've seen this a lot in other projects, and I like that it shows which values are auto-detected. However, it's not common in Blender, so if we want we can either remove it now, or remove it after the buildbot has been set up correctly. Differential Revision: https://developer.blender.org/D7395 Reviewed by: campbellbarton, mont29, sergey |
April 24, 2020, 14:17 (GMT) |
Defaults: Change default axes for Track To constraint The main use-case for the Track To constraint is camera tracking, so this sets up a better default for this. That is, track to -Z with Y up. Agreed on internally with Pablo Vazquez and William Reynish. Should there be a reason to revert this, that would be fine compatibility-wise. |
April 24, 2020, 14:17 (GMT) |
Defaults: Reduce near-clipping in factory settings For newly opened 3D Views, the default would actually be 0.01m. But the code to update the default for all existing 3D Views in the startup.blend was missing. So the defaults were out-of-sync. 0.01m is the more reasonable default as agreed on by the UI team. |
April 24, 2020, 13:27 (GMT) |
Merge branch 'master' into greasepencil-object |
April 24, 2020, 11:08 (GMT) |
Alembic: added camera writer |
April 24, 2020, 11:08 (GMT) |
Alembic: support writing metaballs This commit also introduces a change in how Alembic C++ objects are created. This no longer happens in the constructor, but is done in a different function that's only called when `writer->is_supported(context)` returns `true`. |
April 24, 2020, 09:34 (GMT) |
Depsgraph: Use BLI::Map instead of GHash for operations_map Reviewers: sergey Differential Revision: https://developer.blender.org/D7509 |
April 24, 2020, 09:23 (GMT) |
Alembic: fixed subsurf modifiers not being re-enabled after export |
April 24, 2020, 09:18 (GMT) |
Alembic: much cleaner way to get the parent Alembic object Rather than juggling pointers around, the iterator's writer map is used. This makes it possible to construct the Alembic object in the writer's constructor, and makes the writers much simpler to understand. |
April 24, 2020, 09:15 (GMT) |
Alembic: CMake cleanup No functional changes. |
April 24, 2020, 08:48 (GMT) |
Depsgraph: Use BLI::Set instead of std::unordered_set Reviewers: sergey Differential Revision: https://developer.blender.org/D7506 |
April 24, 2020, 08:40 (GMT) |
Merge branch 'blender-v2.83-release' |
|
|
|


Master Commits
MiikaHweb | 2003-2021