May 23, 2019, 08:33 (GMT) |
Fix T64528: error in RenderEngine API docs example |
May 23, 2019, 08:29 (GMT) |
Depsgraph examples: don't assign to names of built-in Python objects `object` is the superclass of all objects. Old-style code could still be using `class SomeClass(object)` and assigning something else to `object` could have unexpected results. This is now also documented in the [Python style guide](https://wiki.blender.org/wiki/Style_Guide/Python) on the wiki. Differential Revision: https://developer.blender.org/D4922 Reviewed by: sergey |
May 23, 2019, 08:23 (GMT) |
Merge branch 'blender2.7' Conflicts: source/blender/blenkernel/intern/library_remap.c |
May 23, 2019, 08:19 (GMT) |
Fix (unreported) missing remapping of proxy_from pointer. That would break proxy behavior after a library reload. The usual super-annoying loop-back pointers... At least that one is easily detectable and can be fixed in-place. Found while investigating T64764. |
May 23, 2019, 08:02 (GMT) |
Fix T65023: Tracking marker color is not updated when using Copy Color Missing dependency graph update. Ideally need to introduce more clear ID_RECALC flag, and maybe go over all of the operators (some of them might not use dependency graph still). |
May 23, 2019, 07:47 (GMT) |
Masks: Properly port to Copy-on-Write concept Masks were not really covered by Copy-on-Write due to mistake in the dependency graph. After correcting that mistake a lot of tools became broken, so majority of the patch is related on making it so access to evaluated/tessellated masks is done. When accessing evaluated mask state make sure access to an evaluated dependency graph is done. This solves possible access to NULL data on redo. Fixes T64899: Re-doing new point addition causes crash Reviewers: brecht Reviewed By: brecht Maniphest Tasks: T64899 Differential Revision: https://developer.blender.org/D4918 |
May 23, 2019, 07:21 (GMT) |
Correct last commit (gizmo order was reversed) |
May 23, 2019, 06:33 (GMT) |
Cleanup: replace the visible gizmo linked list with an array Avoids an allocation per gizmo & simplifies limiting the lookup past the first intersecting 2D gizmo found. |
May 23, 2019, 06:32 (GMT) |
Cleanup: allow BLI_Buffer to be used without it's header Without this any functions declared that take BLI_Buffer also needed to include the header. |
May 23, 2019, 04:27 (GMT) |
Gizmo: highlighted gizmo now handles all events first Only mouse events were handled by the highlighted gizmo, this allows more flexibility with event handling. |
May 23, 2019, 04:08 (GMT) |
Cleanup: split keymap handling into functions Move keymap handler logic for keymap and gizmo handlers into their own functions. This makes it possible to refactor keymap handling without large changes or duplicating code. |
May 23, 2019, 02:29 (GMT) |
Cleanup: de-duplicate popover_group arguments |
May 22, 2019, 21:50 (GMT) |
Cleanup: modernize code of new `BLE_main_id_refcount_recompute()`. No functional change expected! |
May 22, 2019, 21:36 (GMT) |
Merge branch 'blender2.7' Conflicts: source/blender/blenkernel/intern/library.c source/blender/blenloader/intern/readfile.c source/blender/editors/screen/screen_edit.c |
May 22, 2019, 21:33 (GMT) |
Fix (unreported) broken collections after undo/redo, or remapping (leading to crashes). Those are two cases where keeping infamous backward `parents` pointers of collections in sync is kind of impossible to do... So rebuilding those relationships from scratch instead. Fixes e.g. a crash when undoing, then reloading a library, and likely many more weird ones like that. Uncovered while investigating T64764. |
May 22, 2019, 21:33 (GMT) |
BKE Collection: Add new function to rebuild parent relationships. It's not always possible to keep 'by hand' parent relationships valid in collections hierarchy. Add functions to remake those (re-using/factorizing code from `readfile.c` `lib_link_collection_data()` function). Can't stress again how painful it is to have those kind of backward relationships in our data structures, those *always* end up being serious issues to keep in sync... Should only be generated on the fly when needed, period. :( |
May 22, 2019, 21:33 (GMT) |
Fix T64764: 'Reload' on linked libraries disconnects proxy armature datablocks. Note that this only fixes the core issue reported (caused by own dummy mistake in rBd0df7fb3b94ea), investigating that report uncovered at leat two more issues, including a crasher (when reloading after an undo)... |
May 22, 2019, 20:35 (GMT) |
Merge branch 'master' into collada |
May 22, 2019, 19:34 (GMT) |
fix T64873 collada export crashes Blender on Mac |
May 22, 2019, 19:10 (GMT) |
Fix (unreported) usercount of linked IDs becoming garbage after undo/redo. Not re-reading linked data-blocks in undo/redo case also means that we do not touch to their usercounts. Even worse, lib_link process in readfile will increase those (for cases where local data uses linked one). Whole data management code is now heavily relying on valid consistent refcount of all IDs, so we cannot allow that anymore. Simple solution here could have been to then not increase that one for linked IDs in `newlibadr_us()`, but unfortunately that would not be totally bullet-proof, as some local users of linked data may be added or removed by an undo step... So I cannot think of any other solution than the ugly brute force one, i.e. going over the whole Main database and recompute linked IDs users count... Should not be a big issue performance wise though, this is fairly cheap process. |
|
|
|


Master Commits
MiikaHweb | 2003-2021