December 13, 2020, 15:27 (GMT) |
Cleanup: Reduce variable scope in view_2d_ops.c |
Revision a00a03e by Alexander Gavrilov December 13, 2020, 14:37 (GMT) |
tweak: add options to drive B-Bone scale from handle local scale channels. |
December 13, 2020, 04:52 (GMT) |
Merge branch 'master' into xr-actions-D9124 |
December 12, 2020, 18:07 (GMT) |
UI: Add more property editor operators to IC keymap As a followup for rB2b3d85d7d6771, this commit adds the remove and copy operators for grease pencil modifiers, effects, and constraints where they apply. |
December 12, 2020, 18:02 (GMT) |
GPencil: Fix merge error |
December 12, 2020, 17:55 (GMT) |
Merge branch 'master' into greasepencil-object Conflicts: source/blender/blenkernel/BKE_gpencil_geom.h source/blender/blenkernel/intern/gpencil_geom.c |
December 12, 2020, 17:49 (GMT) |
Fix T83705: GPencil - Duplicate strokes of destination layer when merge layer If the destination layer hadn't keyframe, a new keyframe was added and later the merge layer strokes were added, but this could change the animation because the new frame replaced the old drawings of the target layer. Now, before merge the layer, all keyframes are added in the target layer in order to keep the drawings. |
December 12, 2020, 15:49 (GMT) |
GPencil: Add uniform subdivide BKE to improve interpolation This patch introduces a new BKE function that performs a uniform subdivide. The goal of this function is to subdivide the stroke to reach a target number of points while maintaining its shape, color, and weights. This is done by repeatedly subdividing the longest edge in the stroke. Every subdivision adds a new point at the exact middle point of an edge. The function is intended to be used in the interpolation operators to give better results when interpolating between different sized strokes. Reviewed By: antoniov Differential Revision: https://developer.blender.org/D9835 |
December 12, 2020, 15:17 (GMT) |
Cleanup |
December 12, 2020, 11:54 (GMT) |
GPencil: Revert wrongly changed variable type for flag This was changed by error in previous commit |
December 12, 2020, 11:52 (GMT) |
GPencil: Replace uint32 with int32 According to style, negative must be checked with asserts. |
December 12, 2020, 11:24 (GMT) |
Cleanup: clang tidy |
December 12, 2020, 11:04 (GMT) |
Merge branch 'master' into cycles_procedural_api |
December 12, 2020, 10:28 (GMT) |
Merge branch 'master' into cycles_procedural_api |
December 11, 2020, 22:08 (GMT) |
UI: Allow UI to pass focused data-block to operators via context This is similar to c4a2067130130d, but applies to the general UI and is only about single data-blocks. Here there was a similar problem: How can buttons pass the data they represent to operators? We currently resort to ugly ad-hoc solutions like `UI_context_active_but_get_tab_ID()`. So the operator would need to know that it is executed on a tab button that represents a data-block. A single button can now hand operators a data-block to operate on. The operator can request it via the "id" context member (`CTX_data_pointer_get_type(C, "id", &RNA_ID)` in C, `bpy.context.id` in .py). In this commit, it is already set in the following places: * Generic RNA button code sets it to the pointed to data-block, if the button represents a data-block RNA pointer property. (I.e for general data-block search buttons.) * Data-block selectors (`templateID`) set it to the currently active data-block. * The material slot UI-List sets it for each slot to the material it represents. The button context menu code is modified so its operators use the context set for the layout of its parent button (i.e. `layout.context_pointer_set()`). No user visible changes. This new design isn't actually used yet. It will be soon for asset operators. Reviewed as part of https://developer.blender.org/D9717. Reviewed by: Brecht Van Lommel |
December 11, 2020, 22:08 (GMT) |
UI: Allow Outliners to pass selected data-blocks to operators via context The way the Outliner integrates operations on selected tree elements is known to be quite problematic amongst developers. The context menu is generated in an unusual way and doesn't use the normal operator system. Instead, changes are applied via a recursive callback system. Things are quite ad-hoc, and the callbacks often implement logic that should not be in the Outliner, but in entirely different modules. Often these modules already contain the logic, but as proper operators. This commit is a step into a hopefully better direction that should allow us to put actual operators into Outliner context menus. It starts solving the problem of: How can the Outliner pass selected data to operators. It implements it for data-blocks only, but other data could do it in the same way. Idea is to keep doing what operators were initially designed to do: Operate on context. Operators can now query a "selected_ids" context member (`CTX_data_selected_ids()` in C, `bpy.context.selected_ids` in .py). If an Outliner is active, it will generate a list of selected data-blocks as a response, via its `SpaceType.context` callback. Any other editor could do the same. No user visible changes. This new design isn't actually used yet. It will be soon for asset operators. Reviewed as part of https://developer.blender.org/D9717. Reviewed by: Brecht Van Lommel |
December 11, 2020, 22:07 (GMT) |
Cleanup and fix/mini-refactor the tiling function |
December 11, 2020, 21:05 (GMT) |
Merge branch 'master' into soc-2020-io-performance |
December 11, 2020, 21:05 (GMT) |
Exporter: Cleanup: clang-format, comment |
December 11, 2020, 21:05 (GMT) |
Exporter: create new API for writer. Isolate formatting options. Add exceptions instead of three layers of booleans. Separate header writing from constructor. |
|
|
|


Master Commits
MiikaH:n Sivut a.k.a. MiikaHweb | 2003-2021