Age | Commit message (Collapse) | Author |
|
The problem is that string width computing is performed in integers
(pixels), which can generate a rather annoying error (a few pixels)...
Simply work around that for now, by trimming an extra middle char when
needed.
|
|
`to_strlen` just benefits from using pre-computed kerning table for
ascii chars (gives about 30% speed improvements).
`to_rstrlen` was re-written and heavily simplified, basically using same
logic as `to_strlen`, and `BLI_str_find_prev_char_utf8()` to loop
backward in the string, instead of looping forwards the whole string,
storing each gliph's width in temp array, and looping backward on that
temp array to find final string matching expected width. Gives about 70%
speed improvements!
And both functions can now share their core logic.
|
|
|
|
Correct the outline blending for alpha 0 background.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
With new jemalloc versions memory allocated by threads that then become
inactive is not longer automatically freed. Instead we have to enable a
background thread to do it.
Some testing is needed to find out of this is sufficient, because the
background thread only runs periodically.
|
|
This parameter allows to define the percentage of offset of a stroke when uses surface mode.
Before, this was a fixed value, but for some artists' purposes, it's good to have the option to change it.
|
|
Users can select the main unit they want to use now.
Previously the displayed unit always depended on the magnitude of the value.
The old behavior can be restored by switching to the "Adaptive" mode for length, mass and time units.
Meters, kilograms and seconds are the default units for new and old scenes.
The selected unit is also the default unit for user input.
E.g. if cm is selected, whenever the user inputs a unitless number into a field of type length, it will be interpreted as cm.
Reviewer: brecht
Differential: https://developer.blender.org/D3740
|
|
Currently some modes share tool keymaps, we might want to disable
this since it's confusing editing one thing in multiple places.
However this should be resolved in the tool definitions.
|
|
Holding Alt now disables.
|
|
|
|
Transform the gizmo's drawing function into a generic function for use in other parts of the code.
|
|
|
|
|
|
This matches mesh add methods, and doesn't force it to be a keyword arg.
|
|
Was giving errors on each access.
|
|
Accessing from the tool and keyboard had different defaults,
disable by default for both.
|
|
|
|
|
|
This was listed under the armature task yet it is used for meshes too.
Also make sure all the UI names are capitalized (normal > Normal).
|
|
And final one as well.
|
|
|
|
Also added epsilon into the mix.
|
|
Also added epsilon into the mix.
|
|
This includes all the modes that don't need multi-object support:
* SIMEDBONE_CHILDREN
* SIMEDBONE_CHILDREN_IMMEDIATE
* SIMEDBONE_SIBLINGS
* SIMEDBONE_GROUP
* SIMEDBONE_SHAPE
Unlike the mesh select similar operator, in this case we take
only the active bone in consideration, not all the selected ones.
I decided not to change that, and keep this 2.79 behaviour.
We could though if we want to.
|
|
|
|
|
|
It was not taking duplicated objects into consideration, so the operator would
only work if you had an off number of objects with the same armature.
|
|
|
|
Looks like new depsgraph may initialize some IK trees, without ever
executing them (which also frees them with legacy IKSolver code)...
|
|
Reviewers: brecht
Differential Revision: https://developer.blender.org/D3758
|
|
evaluated or original data-block.
Since RNA depagraph API mostly returns evaluated data, it is mandatory
to have access to original datablocks now...
|
|
COW data.
It is crucial that scripts do not write, and even more importantly, do
not store any references to those. Otherwise, that’s a rather straight
path to crash.
|
|
|
|
After rB3da46a8d8df2 the vertex color shader can't draw the raw
weight data produced by DRW_cache_mesh_surface_weights_get.
|
|
This is quite an obscure option only useful in rare cases,
when enabled by accident it's confusing since single objects
can't be transformed.
Also, w/ 2.8x you don't see the option change in the header.
|
|
The problem with previous fix was that only the original pixels were blurred, but the surrounding pixels no.
|
|
The normal and xyz no longer overlap so can be the same size.
|
|
To get the toolbar Key binding, the same operator needs to be
referenced from the tool.
|
|
|
|
The z-depth must not be blurred, but use the original value.
|
|
|
|
|
|
Having this setting here wasn't correct (the operator ignores it).
|
|
This allows gizmo groups to store properties in the tool.
This makes sense for gizmo options which only control gizmo display and
don't control operator execution.
Unlike similar kinds of properties,
this isn't accessible via the gizmo-group-type instance.
For now the it's only stored in the workspace tool as can be done for
operator properties, so each instance doesn't have different settings
which would be confusing from a user perspective and complicate access
from the top-bar.
Later we could add gizmo-group properties if needed.
|