Asset Pipeline: Use a weak ref for Asset Collection to improve performance #213
No reviewers
Labels
No Label
Kind
Breaking
Kind
Bug
Kind: Community
Kind
Documentation
Kind
Easy
Kind
Enhancement
Kind
Feature
Kind
Proposal
Kind
Security
Kind
Studio Request
Kind
Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: studio/blender-studio-tools#213
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "TinyNick/blender-studio-pipeline:fix/asset-collection-as-string"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What's Changed
Breaking Changes
@Mets Feel free to squash commit if you want this rolled out asap, but be aware how this can break files
How about adding this load_post handler to version old files?
Without this, the pointers would stick around anyways.
@ -74,3 +82,4 @@
default="",
description="Top Level Collection of the Asset, all other collections of the asset will be children of this collection",
)
@ -167,9 +176,7 @@ classes = (
def register():
bpy.app.handlers.load_post.append(AssetPipeline.set_asset_collection_name_post_file_load)
...
bpy.app.handlers.load_post.remove(AssetPipeline.set_asset_collection_name_post_file_load)
@ -73,0 +71,4 @@
@property
def asset_collection(self):
return bpy.data.collections.get(self.asset_collection_name)
This also needs a tweak to not return None during pull, since we are actually renaming the asset collection before transfer.