May 1, 2020, 16:14 (GMT) |
Merge branch 'panel-list-patch-2' into panel-list-patch-3 |
May 1, 2020, 16:09 (GMT) |
Finish last changes |
May 1, 2020, 16:04 (GMT) |
Simplify subpanel registration arguments |
May 1, 2020, 15:37 (GMT) |
Cleanup: Animation, refactored FCurve interpolation Early returns are used to heavily reduce code indentation and clean up some code flow. No functional changes. |
May 1, 2020, 15:37 (GMT) |
Cleanup: Animation, split FCurve interpolation into separate function |
May 1, 2020, 15:22 (GMT) |
Merge branch 'panel-list-patch' into panel-list-patch-2 |
May 1, 2020, 15:22 (GMT) |
Merge branch 'master' into panel-list-patch |
May 1, 2020, 15:19 (GMT) |
Avoid redundant label |
May 1, 2020, 14:13 (GMT) |
Tracking: Cleanup, localize variable Also avoid possible accumulation of floating point error. |
May 1, 2020, 14:13 (GMT) |
Tracking: Cleanup, localize iterator variables |
May 1, 2020, 14:06 (GMT) |
Fix: Fix build error on windows Headers and implementation had slightly different signatures |
May 1, 2020, 13:38 (GMT) |
Cleanup: Animation, unify FCurve extrapolation Previously there were two functions for FCurve extrapolation, one for before the first keyframe, and the other for after the last. After the previous cleanup made the variable names consistent, it was clear that the code was almost identical. The biggest difference was in the sign of many of the calculations, which was cancelled out by swapping `B-A` to `A-B`. This showed that the computations are actually the same, and the only remaining difference was which neighbouring handle to use in case of B�zier curves. No functional changes. # Conflicts: # source/blender/blenkernel/intern/fcurve.c |
May 1, 2020, 13:38 (GMT) |
Cleanup: Animation, refactored FCurve extrapolation Variables have been renamed so that they refer to the endpoint and its neighbor (rather than `bezt`, `prevbezt`, or `lastbezt`), and unnecessary variables have been removed. By returning early the code flow is also easier to understand. No functional changes. |
May 1, 2020, 13:38 (GMT) |
Cleanup: Animation, split FCurve extrapolation into separate functions The `fcurve_eval_keyframes` consists of three parts: - Before the first keyframe - After the last keyframe - Between the keyframes This commit splits the first two parts into separate functions. This is the first of a series of refactors, which will be committed into smaller parts so that each is easier to follow & validate. No functional changes. |
May 1, 2020, 13:37 (GMT) |
Windows: Support backtraces on release builds. This diff add supports for crash logs on windows for release builds. This can be toggled on/off with the `WITH_WINDOWS_PDB` cmake option. by default it is on. Things to take into consideration: Release builds are hightly optimized and the resulting backtraces can be wrong/misleading, take the backtrace as a general area where the problem resides rather than an exact location. By default we ship a minimized symbol file that can only resolve the function names. This was chosen to strike a balance between growth in size of the download vs functionality gained. If more detailed information is required such as source file + line number information a full pdb can be shipped by setting `WITH_WINDOWS_STRIPPED_PDB` to off. Differential Revision: https://developer.blender.org/D7520 Reviewed by: brecht |
May 1, 2020, 13:21 (GMT) |
UI: Use property split layout and decorators for material properties Use the automatic property split layout (hence, change to the new 40/60% split ratio) and add decorator buttons for animatable properties. This actually applies to all node input buttons in the properties, e.g. world shading, light shading, texture nodes. Doing this makes the layout more consistent with other layouts in the properties. But the decorators are also a useful hint for users that these options can be animated. Previously using decorators and the automatic split layout wasn't possible, I've done a number of changes now to have it supported. Before I moved the socket icons to the left side, the decorators also looked weird (two circle icons next to each other). {F8497704} With nested items: {F8497708} Reviewed By: William Reynish, Pablo Vazquez Differential Revision: https://developer.blender.org/D7544 |
May 1, 2020, 13:00 (GMT) |
May 1, 2020, 12:35 (GMT) |
Revert "Improve proportional edit drawing" Accident! This reverts commit ae049a6c6ac545b2c9eadf759f40ad864f436ff1. |
May 1, 2020, 12:32 (GMT) |
May 1, 2020, 12:32 (GMT) |
Improve proportional edit drawing (This is a simplified version of D4786) The advantage of highlighting the points would be to indicate more clearly what is affected by the proportional edit. The default circle is not so informative and sometimes it is even off screen so the user loses the quick identification of the influence. (See T75482) The disadvantage of this design is that the points could end up hiding the mesh. The original patch added the option `draw_proportional_gradient`, but I prefer to avoid adding more options and more information to the interface. I'm not sure if the advantages outweigh the disadvantages. {F8504097} Reviewers: #user_interface, #modeling Subscribers: |
|
|
|


Master Commits
MiikaH:n Sivut a.k.a. MiikaHweb | 2003-2021