
Blender Git Statistics -> Developers -> LazyDodo
Ray molenkamp (LazyDodo)
Total Commits : 595
Master Commits : 533
Branch Commits : 62
First Commit : July 18, 2016
Latest Commit : January 26, 2021 (Yesterday)
Commits by Month
Date | Number of Commits | |
---|---|---|
January, 2021 | 5 | |
December, 2020 | 5 | |
November, 2020 | 4 | |
October, 2020 | 4 | |
September, 2020 | 13 | |
August, 2020 | 23 | |
July, 2020 | 7 | |
June, 2020 | 9 | |
May, 2020 | 24 | |
April, 2020 | 19 | |
March, 2020 | 18 | |
February, 2020 | 27 | |
January, 2020 | 13 | |
December, 2019 | 4 | |
November, 2019 | 18 | |
October, 2019 | 10 | |
September, 2019 | 3 | |
August, 2019 | 36 | |
July, 2019 | 7 | |
June, 2019 | 13 | |
May, 2019 | 31 | |
April, 2019 | 10 | |
March, 2019 | 8 | |
February, 2019 | 14 | |
January, 2019 | 1 | |
December, 2018 | 6 | |
November, 2018 | 3 | |
October, 2018 | 10 | |
September, 2018 | 14 | |
August, 2018 | 52 | |
July, 2018 | 8 | |
June, 2018 | 34 | |
May, 2018 | 14 | |
April, 2018 | 2 | |
March, 2018 | 5 | |
February, 2018 | 7 | |
January, 2018 | 3 | |
December, 2017 | 3 | |
November, 2017 | 1 | |
October, 2017 | 5 | |
September, 2017 | 11 | |
August, 2017 | 6 | |
July, 2017 | 0 | |
June, 2017 | 2 | |
May, 2017 | 5 | |
April, 2017 | 9 | |
March, 2017 | 1 | |
February, 2017 | 3 | |
January, 2017 | 6 | |
December, 2016 | 3 | |
November, 2016 | 9 | |
October, 2016 | 19 | |
September, 2016 | 16 | |
August, 2016 | 9 | |
July, 2016 | 3 |
Commit Distribution
Favourite Files
Filename | Total Edits |
---|---|
platform_win32.cmake | 69 |
versions.cmake | 47 |
CMakeLists.txt | 47 |
CMakeLists.txt | 40 |
harvest.cmake | 37 |
make.bat | 34 |
parse_arguments.cmd | 22 |
macros.cmake | 21 |
configure_msbuild.cmd | 18 |
platform_win32_msvc.cmake | 17 |
File Changes
Action | Total | Per Commit |
---|---|---|
Added | 107 | 0.2 |
Modified | 1 386 | 2.3 |
Deleted | 177 | 0.3 |
Code Changes
Action | Total | Per Commit |
---|---|---|
Lines Added | 13 188 | 23.7 |
Lines Removed | 6 589 | 11.8 |
Latest commits 
1 day and 1 hour ago |
Merge remote-tracking branch 'origin/blender-v2.92-release' |
1 day and 1 hour ago |
Windows: Fix wchar_t truncation BLI_strncpy_wchar_from_utf8 made the assumption that wchar_t is UTF-32 bit regardless of environment, while this holds true on both mac and linux, on windows wchar_t is actually actually UTF-16. This resulted in the upper 16 bits being dropped from from some string conversions and prevented blender from starting when installed in a path with unicode code-points over 0xffff. There was also a fair bit of code duplication between BLI_strncpy_wchar_from_utf8 and BLI_str_utf8_as_unicode_and_size this change essentially removes all logic from BLI_strncpy_wchar_from_utf8 and calls the right function for the right environment. Reviewed By: brecht , Robert Guetzkow Differential Revision: https://developer.blender.org/D9822 |
January 25, 2021, 15:50 (GMT) |
Windows: Remove zero terminator from stack trace Important lesson to be learned here, leaving comments is great and in the moment, they usually make sense. Many months later they may not quite make as much sense any more and time will have to be spend to figure out what was meant, all of this would have been averted with a better comment. The zero terminator in this case, I can find no evidence of it being used or relied on at any point. It does however break GTests's `EXPECT_EXIT` macro that stops looking in the output as soon as it sees the zts and doesn't end up looking at the actual assert text being thrown. Which in turn makes the`fcurve_active_keyframe`test fail when run in debug mode on windows. |
January 15, 2021, 19:36 (GMT) |
Merge remote-tracking branch 'origin/blender-v2.92-release' |
January 15, 2021, 19:36 (GMT) |
Fix: Build error with MSVC 2017 BKE_cryptomatte_extract_layer_name was using std::isdigit without including <cctype> somehow only MSVC 2017 had a problem with that. |
December 17, 2020, 04:03 (GMT) |
Clean-up: Fix build warning with MSVC Callback function was using int while update_render_passes_cb_t was using eNodeSocketDatatype leading to a build warning about different argument types with MSVC. |
December 16, 2020, 14:27 (GMT) |
Fix: Python warning in windows debug builds When doing a debug build on windows, blender will start with the following warning: "Unable to find the python binary, the multiprocessing module may not be functional!" The root cause for this issue is: for a debug build the python binary is called python_d.exe rather than just python.exe This change fixes BKE_appdir_program_python_search to look for the _d suffix for debug builds on windows Differential Revision: https://developer.blender.org/D9775 Reviewed by: Campbell Barton |
December 11, 2020, 19:09 (GMT) |
Fix: Fix potential memory leak in BLI_getenv Issue introduced in rB87b19b3aba0c and unlikely to occur but no reason not to have correct code. |
December 11, 2020, 18:59 (GMT) |
Fix: BLI_getenv returns ascii not UTF8 on windows BLI_getenv has always incorrectly returned ascii rather than UTF-8. This change corrects this behaviour. This resolves issues when the `BLENDER_USER_CONFIG` environment variable contains a path with Unicode characters on windows as reported in T74510 (but unlikely the root cause for the issue at hand there) Differential Revision: https://developer.blender.org/D9831 Reviewed by: brecht |
December 3, 2020, 18:00 (GMT) |
MSVC: Enable clang-tidy analyser This enables the use of clang-tidy in the VS IDE. To use it: 1 - Enable WITH_CLANG_TIDY in your cmake configuration 2 - From the Analyse pull down menu select Run Code Analysis on... The analyser is currently not enabled by default on build given it is quite slow and there are quite a few problems it reports that we still need to deal with. |
MiikaHweb - Blender Git Statistics v1.06