| Age | Commit message (Collapse) | Author |
|---|
|
Don't force square pixel, since on a more real pipeline
expected delivery is same anamorphic as an input footage.
|
|
The default compositor node update function sets the need_exec flag on the node
which the Auto Render feature checks, but the custom update function that was
added as part of rB4cf7fc3b3a4d didn't do so.
Therefore, the two custom update functions that were added now also call the
default update function.
|
|
|
|
Was not freeing undo nodes themselves.
|
|
|
|
|
|
|
|
Using near far and optionally clipping planes is
involved and not needed in many cases.
Rename so a simpler version of this function can be added.
|
|
|
|
|
|
Most other software expects to read indexed vertex colors, so write indices
along with the colors as we already do for UVs.
Differential Revision: https://developer.blender.org/D3704
|
|
Differential Revision: https://developer.blender.org/D3700
|
|
Same issue as rB39f7c8256d58.
|
|
Sorry for the noise...
|
|
|
|
Caused by commit rB28c34ae7e2d6
Unlike `strncpy`, `BLI_strncpy` ensures the last character is '\0'.
|
|
Terms get/set don't make much sense when casting values.
Name macros so the conversion is obvious,
use common prefix for easier completion.
- GET_INT_FROM_POINTER -> POINTER_AS_INT
- SET_INT_IN_POINTER -> POINTER_FROM_INT
- GET_UINT_FROM_POINTER -> POINTER_AS_UINT
- SET_UINT_IN_POINTER -> POINTER_FROM_UINT
|
|
Trivial fix, just using same code as in Image editor...
|
|
This partially solves ASAN report about unfreed memory. There is still
something in the report, need to have a closer look with debug version
of OpenEXE library.
|
|
|
|
Since that button is then totally useless and unusable...
|
|
This causes a feedback loop in 2.8x,
where gizmo redo caused fake mousemove that executed gizmo again.
Move the mousemove into the undo/redo operator.
|
|
|
|
That bug probably did not affect 2.7x, only 2.8 with COW copying IDs in
threads... But root of the issue is that underlying boost i18n lib does
not support well multi-threaded access. So simply forbid any translation
from non-main thread. This *may* be an annoying limit at some point, but
doubt it will be any issue currently.
|
|
Getting the instance leaks memory and was only meant to be used for
generating docs.
|
|
|
|
Replace direct access using PyThreadState_GET
|
|
|
|
That pointer can be NULL, RNA default string handling does not support
that. (that whole uv_layer prop is quite nasty actually, since it does
not own that string, always borrows it from some other data :((( ).
|
|
Matches threading API.
|
|
Just pass as an argument.
|
|
* WITH_SYSTEM_OPENJPEG is removed and is now always on, this was already
the case for macOS and Windows.
* This should not break existing Linx builds. If there is no new enough
OpenJPEG installed, CMake will no find libopenjp2 and WITH_IMAGE_OPENJPEG
will be disabled.
* install_deps.sh was updated with new package names, since distributions
put this version in a new package.
Differential Revision: https://developer.blender.org/D3663
|
|
|
|
Was using UI_BLOCK_LOOP to control draw style,
this meant we couldn't use popup theme colors for cases
where it the interface has the same purpose as a popup but happens
not to use this flag.
|
|
One need to check that there is something to free, before trying to free it...
|
|
|
|
When using the 'normal' orientation, the normal would be ignored
if the plane couldn't be calculated.
Now use only the normal if the plane is zero length,
this was already done, just not in all cases.
|
|
|
|
In a real world it is very weird to disable AA on a mask,
it will give ugly looking result. For some fast preview
passes (like in the node preview) the system can decide
to disable AA without asking user to do anything.
One thing we can consider doing is to remove Feather
option as well. If real compo becomes measurably slower
in cases when mask has no real feather, we can disable
feather internally, without user input. Disabling
feather in the interface is like making things faster
but giving a wrong result, which doesn't sound that
helpful either.
Reviewers: brecht
Reviewed By: brecht
Subscribers: hype, sebastian_k
Differential Revision: https://developer.blender.org/D3677
|
|
|
|
The issue there was that number of layers did not include normals,
while element size counts bytes used by normals. This sounds very
fragile and dangerous to work further. Also, one value can easily
be delivered from another, so it is redundancy going on here.
Possible difference now is that multires subdivision will copy
normals to a higher levels. Shouldn't be big of a problem, since
leaving old normals and updating coordinates is not correct either.
|
|
The rest of Blender uses backslashes.
|
|
|
|
|
|
Was ignoring the option, using the mouse in all cases.
D3671 by @ISS w/ edits.
|
|
|
|
Wasn't properly clamping on the window minimum.
|
|
objects to test against.
Followup to rBc6bbe6c5aac29, much more elegant solution to the problem. ;)
|
|
Differential Revision: https://developer.blender.org/D3668
|
|
Not freeing its BVHTree in case there were no collision objects,
could quickly lead to hundreds of MB of memleak!
|
