Revision ccc2a79 by Jacques Lucke July 20, 2020, 14:03 (GMT) |
BLI: add typedefs for containers that use raw allocators Those are useful when you have to create containers with static storage duration. If those would use Blender's guarded allocator, it would report memory leaks, that are not actually leaks. |
Revision ed18405 by Bastien Montagne July 20, 2020, 13:36 (GMT) |
Fix T78958: Library Override crash: undo make local. |
Revision 4f4af0c by Jacques Lucke July 20, 2020, 13:31 (GMT) |
Particles: support removing particles during the simulation This still cannot be controlled by the user. Currently, all particles are killed after two seconds |
Revision 9016a29 by Antonio Vazquez July 20, 2020, 13:23 (GMT) |
Fix T79107: Crash changing brush size in GPencil sculpt Reviewed By: fclem Maniphest Tasks: T79107 Differential Revision: https://developer.blender.org/D8353 |
Revision 230f7d7 by Jacques Lucke July 20, 2020, 12:04 (GMT) |
Fix signed/unsigned comparison |
Revision cbf2278 by Campbell Barton July 20, 2020, 11:55 (GMT) |
Fix T79075: Tool popup fails with experimental vertex colors enabled Register key-maps from tools in functions. |
Revision ac5f011 by Germano Cavalcante July 20, 2020, 11:52 (GMT) |
Fix T70455: Knife Tool failing to cut edges Analyzing the cuts, the points shown in the viewport (indicating the previous and current cuts) do not correspond to the final cuts. Sometimes a point, even snapped to a vert, is a point that cuts an edge and sometimes a point, even snapped to an edge, is a point that cuts only the face. This is because the detection of snapping vertices from mouse is different from the "snap" that detects vertices that are cut. So small projection inaccuracies can result in detection failures. The solution for this is simply to confirm the cuts whose vertices indicate the `prev` ou and `cur` point. The tolerance distance does not need to be calculated in these cases. |
Revision 33ad95b by Sybren A. Stüvel July 20, 2020, 11:14 (GMT) |
Animation: Fix MSVC warning about C incompatibility of `AnimationEvalContext` Thanks @JacquesLucke for pointing this out. No functional changes. |
Revision 579b180 by Jacques Lucke July 20, 2020, 11:02 (GMT) |
BLI: add Vector/Array.fill methods |
Revision 8cbbded by Jacques Lucke July 20, 2020, 10:16 (GMT) |
Refactor: Update integer type usage This updates the usage of integer types in code I wrote according to our new style guides. Major changes: * Use signed instead of unsigned integers in many places. * C++ containers in blenlib use `int64_t` for size and indices now (instead of `uint`). * Hash values for C++ containers are 64 bit wide now (instead of 32 bit). I do hope that I broke no builds, but it is quite likely that some compiler reports slightly different errors. Please let me know when there are any errors. If the fix is small, feel free to commit it yourself. I compiled successfully on linux with gcc and on windows. |
Revision 686ab4c by Sybren A. Stüvel July 20, 2020, 09:51 (GMT) |
T77086 Animation: Passing Dependency Graph to Drivers Custom driver functions need access to the dependency graph that is triggering the evaluation of the driver. This patch passes the dependency graph pointer through all the animation-related calls. Instead of passing the evaluation time to functions, the code now passes an `AnimationEvalContext` pointer: ``` typedef struct AnimationEvalContext { struct Depsgraph *const depsgraph; const float eval_time; } AnimationEvalContext; ``` These structs are read-only, meaning that the code cannot change the evaluation time. Note that the `depsgraph` pointer itself is const, but it points to a non-const depsgraph. FCurves and Drivers can be evaluated at a different time than the current scene time, for example when evaluating NLA strips. This means that, even though the current time is stored in the dependency graph, we need an explicit evaluation time. There are two functions that allow creation of `AnimationEvalContext` objects: - `BKE_animsys_eval_context_construct(Depsgraph *depsgraph, float eval_time)`, which creates a new context object from scratch, and - `BKE_animsys_eval_context_construct_at(AnimationEvalContext *anim_eval_context, float eval_time)`, which can be used to create a `AnimationEvalContext` with the same depsgraph, but at a different time. This makes it possible to later add fields without changing any of the code that just want to change the eval time. This also provides a fix for T75553, although it does require a change to the custom driver function. The driver should call `custom_function(depsgraph)`, and the function should use that depsgraph instead of information from `bpy.context`. Reviewed By: brecht, sergey Differential Revision: https://developer.blender.org/D8047 |
Revision 6fbfa52 by Antonio Vazquez July 20, 2020, 09:10 (GMT) |
GPencil: Fix unreported wrong SNAP menu in Point Context menu It was using the mesh menu instead of GPencil one. |
Revision e4daac8 by Antonio Vazquez July 20, 2020, 09:07 (GMT) |
Fix T79094: GPencil Snap menu with Shift+S not pie menu In order to keep UI consistency, now it's a pie menu. |
Revision eb5cd62 by Campbell Barton July 20, 2020, 07:52 (GMT) |
Revision b219ae4 by Campbell Barton July 20, 2020, 01:32 (GMT) |
Fix T79077: Off-screen rendering ignores shading argument Thumbnails used the 3D view shading mode when a camera wasn't used. |
Revision 615af4e by Campbell Barton July 19, 2020, 23:25 (GMT) |
DRW: draw hook relationship lines This wasn't added back from 2.7x, making "Recenter Hook" applier to do nothing. |
Revision 9db4e44 by Campbell Barton July 19, 2020, 23:19 (GMT) |
DRW: overlay engine support for drawing isolated points This matches similar functionality for drawing lines. |
July 19, 2020, 21:23 (GMT) |
UI: use "Recalculate" instead of "Recalc" |
Revision 6247ec7 by Clément Foucault July 19, 2020, 20:23 (GMT) |
Fix T78977 GPU: blf fonts are not gamma corrected |
Revision 3884d78 by Jacques Lucke July 19, 2020, 20:06 (GMT) |
Particles: Make it easier to add attributes internally |
|
|
|


Master Commits
MiikaHweb | 2003-2021