Revision 9e3f86e by Julian Eisel (asset-browser) November 13, 2020, 17:21 (GMT) |
Fall back to single threaded preview creation if ID can't do it thread-safe |
Revision 871962f by Julian Eisel (asset-browser) November 13, 2020, 16:54 (GMT) |
Make object preview generation thread-safe When creating the preview, the object is now deep-copied so the preview generation doesn't have to be done on the main thread, or block it. There's a failing assert for objects with particle settings, I think the assert needs to be corrected but I'll leave this aside for later. Disabled it for now. |
November 13, 2020, 00:23 (GMT) |
Automatically refresh "Current File" repository when creating assets It's confusing when this doesn't refresh, it's local data after all. It's not entirely cheap to do, but is quite fast to do still. I don't think it will be an issue if it's just done for creating/deleting assets. |
November 12, 2020, 23:14 (GMT) |
Merge branch 'asset-metadata' into asset-browser |
November 12, 2020, 23:13 (GMT) |
Fix crash loading some files after recent merge Caused by badly resolved merge conflicts. |
November 12, 2020, 22:45 (GMT) |
Merge branch 'asset-metadata' into asset-browser |
November 12, 2020, 22:37 (GMT) |
Merge branch 'master' into asset-metadata |
October 30, 2020, 14:04 (GMT) |
Merge branch 'asset-metadata' into asset-browser |
October 30, 2020, 14:00 (GMT) |
Merge branch 'master' into asset-metadata |
October 29, 2020, 16:43 (GMT) |
Merge branch 'asset-metadata' into asset-browser |
October 29, 2020, 16:43 (GMT) |
Merge branch 'master' into asset-metadata |
October 29, 2020, 15:40 (GMT) |
Operator to create asset catalogs (aka smart-filters) A catalog at this stage is just a named item stored in a file's asset repository meta-data. With these changes one can create a named asset catalog that is written to the file and can be read successfully. |
October 29, 2020, 14:24 (GMT) |
Support storing asset repository data in files Given that a repository can be built up from a single, or multiple .blends, it's not clear where the repository data should live. It should still be possible to easily share a .blend file to share assets, including relevant meta-data that is not solely stored on the asset level. E.g. if you want to share a single pose library, that should be doable by sharing a single .blend. So the .blend needs to have the pose library meta-data, i.e. the name of the library and which poses belong to it. The current design forsees that the Pose Library is implemented as a "cataloge" (aka "smart-filter", to be determined). These should be stored per asset category in the repository. So this commit works towards the following design idea: Each .blend file with assets can additionally store repository meta-data. When reading a repository, we don't only read the asset meta-data but also the repository meta-data in each .blend file. The union over all the .blend files is the total repository meta-data the asset browser can display. That way each .blend file still is an isolated unit that doesn't necessarily depend on the existence of other .blend files (or an index) in the same repository. This commit implements the storage framework of the repository meta-data. I also added a temporary define to help spotting the related changes in future. |
October 26, 2020, 14:01 (GMT) |
Ensure custom asset repository names are unique These names are used as identifiers for the UI, we have to ensure their uniqueness. |
October 22, 2020, 11:18 (GMT) |
Merge branch 'asset-metadata' into asset-browser |
October 22, 2020, 11:12 (GMT) |
Merge branch 'master' into asset-metadata |
October 8, 2020, 13:52 (GMT) |
Fix issues with browsing repository .blend file The file selection in the Preferences wasn't working well at all. Should now work fine. |
October 8, 2020, 12:45 (GMT) |
Fix default asset repository not being added |
October 7, 2020, 17:18 (GMT) |
Merge branch 'asset-metadata' into asset-browser |
October 7, 2020, 17:17 (GMT) |
Fix compile error after last merge |
|