| Age | Commit message (Collapse) | Author |
|---|
|
When the mouse cursor is inside the UV face,
extend the selection threshold.
This means when zoomed in, a face can always be selected when the cursor
is inside it.
In the case of multiple overlapping faces - the face with the closest
center is used.
|
|
This makes it possible to pass multiple hit arguments.
Also rename 'hit_final' to 'hit', since there are no longer a local
'hit' variable defined in these functions.
|
|
The target stroke bounding box was not checked properly and when using layer transform the error was noticeable, but really the error was before the layer transform commit.
|
|
|
|
|
|
|
|
This is intended to be used when settings don't fit in the top bar,
so it makes sense to keep them last.
|
|
Draw the cursor plane smaller then further away from the view.
This makes the plane being drawn onto easier to perceive.
|
|
In practice it's common these settings shouldn't be linked for drawing
the initial (base) plane, compared with the height.
|
|
|
|
|
|
This helps avoid copy-paste errors which have happened a few times,
no functional changes.
|
|
The fallback tool was used as the tool name.
Regression in a8ce9a143abbb51eae28e5d0cae1fb310bd0c24c
|
|
|
|
This implements the node tree update function, which is needed so that the
reroutes get updated to the correct type. It is based on the same code in
the shader and compositor node trees.
Differential Revision: https://developer.blender.org/D10123
|
|
When scale a layer to zero must be hidden.
|
|
ED_gpencil_stroke_material_editable
|
|
The value has changed due a previous commit and the minimum value cannot be 0.
|
|
When using grease pencil for drawing Storyboards, it's very common to require a transform of the layers. This transform can be done using the offset modifier, but in some cases, the scene requires a lot of modifiers and makes the file hard to work.
This new feature adds a transforms Location, Rotation and Scale at Layer level, and allows to transform the layer without using a modifier, keeping the scene more clean.
{F9480695}
This feature was suggested by @pepeland after receiving feedback from several artists.
Also, done some code cleanup and rename some functions to get a better naming.
Maniphest Tasks: T83660
Differential Revision: https://developer.blender.org/D9761
|
|
|
|
The issue was that the mesh shared its vertex weights with the
original mesh (to reduce memory consumption). The solution is
to make a local copy of the vertex weights in this case.
|
|
virtual overrides."
This made Blender considers all materials to be overridden.
This reverts commit 2aa7bc06e7a6adb196e552fca3289ed7b7a18f3f.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This makes it more convent to add many objects with a fixed aspect ratio.
|
|
Move some of the more obscure options into a popover,
so they don't take up so much room in the top-bar.
|
|
This adds a "Snap to" option that allows using all the scenes snap
settings which includes incremental & absolute grid snapping options.
This is optional because always following scene snapping would not
snap to geometry by default (which seems to be the most useful default).
|
|
|
|
The size property was only used for the cube
|
|
Make the name follow the convention of other View3D keymaps.
|
|
Based on feedback from @dbystedt, include this in 2.92
with some updates (coming next).
|
|
|
|
The absolute position desktop mapping has been corrected. The correct
mapping is 0-65535 inclusive. Additionally, division by the virtual
desktop width and height needed to be subtracted by 1 as width and
height are one more than the final pixel index.
|
|
These properties are unused and serve no purpose.
Reviewed By: sergey, #motion_tracking
Differential Revision: https://developer.blender.org/D9803
|
|
|
|
BKE_cryptomatte_extract_layer_name was using std::isdigit
without including <cctype> somehow only MSVC 2017 had a
problem with that.
|
|
|
|
Those (aka root node trees and master collections) share same 'traits'
as the shapekeys: RNA cannot assign them, so we need to handle them as
sub-data of their owner IDs.
Not sure how much this will help in improving support of overrides for
scenes and nodetrees, but this is a mandatory step towards that goal for
sure.
|
|
We should now have the tools to ensure consistency of ID pointers
diffing in `rna_property_override_diff_propptr`.
As a reminder, for most ID pointers we just check the actual pointer value,
but this is not possible for embedded IDs like root node trees or master
collections, and for fake embedded ones like shapekeys, so those should be
handled as mere sub-data of their owner IDs in override context.
|
|
|
|
instance.
Code generating override operations would not deal properly with Pointer
RNA properties, trying by default to use and check pointers' names
properties like it does with items of a collection.
However, using name property in pointer RNA property case makes no
sense, so specialize the `no_prop_name` flag for each case (pointer or
collection).
here, since second override would generate local data-blocks with
different names than the linked data ones, name matching would fail and
breck handling of override diffing in shapekeys.
Note that shape keys are the only one concerned by that problem, since
other embedded IDs (root node trees and master collections) are fully
real ones, so they always get the same names.
|
|
Our beloved shapekeys are 'virtual' overrides, they need special
snowflake treatment here as well.
They do not have any override data, from override perspective they are
considered as mere sub-data from their owning ID (mesh, lattice, etc.).
Therefore, we should not copy override data from them, but instead
properly flag those new IDs as `LIB_EMBEDDED_DATA_LIB_OVERRIDE`.
Found while investigating T84373.
|
|
instance.
Code generating override operations would not deal properly with Pointer
RNA properties, trying by default to use and check pointers' names
properties like it does with items of a collection.
However, using name property in pointer RNA property case makes no
sense, so specialize the `no_prop_name` flag for each case (pointer or
collection).
here, since second override would generate local data-blocks with
different names than the linked data ones, name matching would fail and
breck handling of override diffing in shapekeys.
Note that shape keys are the only one concerned by that problem, since
other embedded IDs (root node trees and master collections) are fully
real ones, so they always get the same names.
|
