Age | Commit message (Collapse) | Author |
|
Don't attempt to build docs when generation fails.
|
|
|
|
|
|
Now using same UI as in object/armature properties, also save one line in 3DView panesl. ;)
Nothing crucial there, but nice & safe to backport to 2.77 imho.
|
|
|
|
|
|
|
|
To be backported to 2.77.
|
|
usable, if still slightly offset
|
|
|
|
by Pokedstudio
|
|
Splash and RC1 AHOY are incoming.
|
|
|
|
ked->iterflags actually already had an enum defined, but at the time of the previous
fix, I'd forgotten that it was defined. As a result, "f1 needs NLA remap" got given
the same flag as "include handles when doing keyframe selection checks".
|
|
|
|
In response to user feedback, this commit brings back the ability to
limit motionpath clearing to only happening for those on selected
objects/bones.
By default, the "Clear" operator will clear from all objects/bones,
unless the Shift key is held.
|
|
Previously CMake would show many messages about missing libs before checking for a missing LIBDIR.
Now show the error immediately and exit.
Also allow for custom LIBDIR on OSX.
|
|
This feature wasn't exposed anywhere in the interface.
|
|
With continuous grab disabled, non-linear mapping for int buttons
wasn't working usefully with small mouse movements.
Now 2x pixels motion adjusts by at least 1 w/ int buttons.
|
|
1811 by @mangostaniko
Fixes regression since moving to floats.
|
|
Cache reading was not using the right simulation flags (outdated), which
made it lookup non-existent grids, and crash on de-referencing null
pointers.
|
|
|
|
|
|
Also name more clearly
|
|
|
|
|
|
Copied from original function.
|
|
|
|
Needed since older versions are unsupported (giving cryptic errors).
|
|
Operator no longer exists.
|
|
Was confusing since zoom icons were used for add/remove elsewhere (color-ramp & presets).
|
|
OpenVDB is compiled with Blosc support, meaning we should pass Blosc to
a linker now.
Unfortunately, the Blosc has compiled-in crt and pthread library, which
still screws up linking.
|
|
|
|
It was wrongly considering 1 is a power of 2. While it is a correct thing
(1 == 2^0) it's not what the math in some later formulas expects.
|
|
|
|
Internally custom-id-properties used soft-limits, but there was no way to edit these.
|
|
option is disabled.
Took me some time to figure out what was going on here... Was again that delayed button
callback stuff (`ui_apply_but_funcs_after()`), first calling button op, and then
its callback func.
Issue was that 'open file' op (through call to `WM_file_read()`) would clear
the splash screen (as more or less the entire 'dynamic' UI), but callback func of that splash
(`wm_block_splash_refreshmenu()`) would still try to access that freed menu's region.
So, root of the issue seems to be that setting context's wm/win/etc. would not clear
context's menu pointer (while clearing all other 'sub' pointers). I could not find
nor imagine any case where this behavior could be desired, so simply added nullification
of that pointer when setting context's wm/win/etc.
Note that crash was due to read-after-free, infuriating debug builds with asan,
but seems like release builds never actually crashed on it.
|
|
|
|
|
|
|
|
Thanks Bastien for finding this out!
|
|
It was basically doing nothing, for ages.
|
|
|
|
It should be all fine to sample same point density from multiple threads,
this is something what Blender Internal is doing actually.
|
|
The issue was happening when having unconnected point density which
will cache data but will not free it because there's no actual call
to the actual sampling.
Now the idea is to make sure cache is zeroed on file load and undo
and then caching via RNA will free the data if any exists. This could
leave us with a single copy of cache in the node if it's not used,
but it's quite small amount of memory and it's not leaking.
|
|
This wasn't working and used extra undo steps.
|
|
This will respect the official build configuration where we should
have BLOSC enabled.
We can't really detect if OpenVDB was compiled with BLOSC or not,
so seems we can't really avoid this extra flag.
|
|
Mainly it's related on a bad practice in SDL to force-define __SSE__
and __SSE2__ flags which generates quite some warnings and causes too
much noise.
There are some other warnings fixed. Should be no functional changes.
NeXyon, please check the changes in audaspace :)
|
|
- division often visibly clipped channels.
- division by zero caused NAN pixel values.
|
|
|