February 15, 2015, 15:35 (GMT) |
Cleanup of SpaceFile, from asset-experiments branch mostly. Helps keeping diff with branch relevant and clean... |
February 15, 2015, 14:55 (GMT) |
Fix for previous commit, sorry for the noise. |
February 15, 2015, 14:28 (GMT) |
Cleanup of ugly allocation stuff (cast of void pointer, not-so-safe sizeof()'s, etc.). |
February 15, 2015, 14:10 (GMT) |
Merge branch 'master' into asset-experiments |
February 15, 2015, 14:07 (GMT) |
Cleanup: BLI_listdir (direntry): get rid of usage of raw malloc/free here. No reason at all not to use MEM_xxx as everywhere else, especially confusing when members of direntry **are** MEM_-allocated (relname, etc.)! |
February 15, 2015, 12:21 (GMT) |
Possible todo notes for more polished UI? |
February 15, 2015, 12:21 (GMT) |
Outliner: "Purge All" function for Outliner in "Orphaned Datablocks" mode Many users have been requesting a way to remove unused datablocks from the file/session "without closing and reopening" Blender (or at least that's the impression I'm getting). This commit adds a new operator (exposed as the "Purge All" button in the header of the "Orphaned Datablocks" mode in the Outliner, which seems to be the logical place for this) for doing so. It does so by wrapping up the save and "revert" (i.e. reload the saved file from disk, without needing to quit Blender) operators along with a confirmation prompt for good measure. Caveats: * Ultimately, we still cannot really cleanly delete any datablocks from the current session outright without reloading the file/data at some point. Thus, we do need to reload the file again before it can be used. * This does mean that this operation is irreversible. Notably, Undo history is lost is doing this operation. Hence the warnings... (Then again, undo/redo actually reloads the entire scene DB from memory, so it's not anything uncommon ;) Other Notes: * The addition of this operator brings this mode more into line with being a kind of "Trashcan" place, with this new operator being the manual "Empty Trash" button. If the "Orphaned Datablocks" name is too obscure, maybe we could rename this mode to "Trash" or something similar? |
February 15, 2015, 12:21 (GMT) |
Code Cleanup: Reshuffle libraries and orphaned datablocks views to a more appropriate place in the file |
February 15, 2015, 12:21 (GMT) |
Outliner: Do not show RMB menu for "ID Base" entries |
February 15, 2015, 12:21 (GMT) |
Outliner: Use restriction columns in "Orphaned Datablocks" view to manage usercounts When in "Orphaned Datablocks" mode, the restriction columns are used to display usercount indicators and toggles to manage whether datablocks get saved or not. * The first column shows an icon to indicate whether that datablock is going to get saved. A tick indicates the datablock will be saved, while a cross indicates the opposite. Clicking on this changes whether the datablock will get saved. * The second column shows the usercount. * The third column shows whether the datablock has a fake user. Notes: * The second and third columns are pretty much redundant (functionally speaking). While it is possible to also toggle fake users by clicking in the third column, its role here is more as information for power users (and hopefully to allow others to connect the relationship between the saved/not saved status and fake users) * I'm not sure whether the use of the X here for the "not saved" state stands out enough to draw user's attention to items which are "in the danger zone". |
February 15, 2015, 12:21 (GMT) |
Outliner: Added new mode for displaying "orphaned" datablocks Orphaned datablocks are those which have either: * 0 users * A "fake" user only In the case of the former, they will be quietly discarded from the file on the next save + reload. Hence, it is helpful to have a view where you can confirm which ones fall into this category and might be worth saving. We also include datablocks with a fake user only so that datablocks given a user above can have that easily turned off again (in case the user makes a mistake). Another benefit of showing these is that it become easier to remove fake users from datablocks you no longer want retained without having to hunt for them. |
February 15, 2015, 09:39 (GMT) |
Merge branch 'master' into asset-experiments |
February 15, 2015, 03:29 (GMT) |
Revert/Remove "Auto View" Feature Turned out that I misinterpreted the feature request, plus there are some minor issues with the commit that would need to be corrected. After all, I decided to just remove it again as it seems to not be really useful for the users. |
February 15, 2015, 03:11 (GMT) |
missed this second last commit |
February 15, 2015, 03:02 (GMT) |
mathutils: Implement __hash__() functions - all mathutils types - only works on frozen data (so vectors can be used in sets/dict keys) - uses same method as CPython, (matches hashing a tuple) D1104 by @juicyfruit with own modifications |
February 15, 2015, 03:01 (GMT) |
mathutils: add freeze() method, is_frozen attr This allows you to make any mathutils object immutable. |
February 15, 2015, 02:46 (GMT) |
mathutils: remove redundant read callback |
February 15, 2015, 02:46 (GMT) |
mathutils: avoid extra alloc for Vector.lerp |
February 15, 2015, 02:46 (GMT) |
Fix crash setting Euler.order to a non-string |
February 15, 2015, 01:00 (GMT) |
Fix T42919 & T42218: BGE: Python-driven armature animation got buggy Due to changes in the way animation updates were handled, BL_ArmatureObjects were no longer registering to KX_Scene as animated. Moguri says: It might have been relying on the deformer update which moved rom being called on every object in the render step. Now armature deformers are only updated if they need to be. Fix T42919 & Fix T42218 |
|
|
|


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