Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maintain functionality even after blend file/library is moved #115

Open
gregzaal opened this issue May 17, 2024 · 0 comments
Open

Maintain functionality even after blend file/library is moved #115

gregzaal opened this issue May 17, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@gregzaal
Copy link
Member

gregzaal commented May 17, 2024

Right now we use asset.library_weak_reference to get the path and determine if a datablock is an asset or not. This is not entirely always reliable and can cause strange behavior especially when the blend file or library itself is relocated.

Perhaps there's a better way to keep track of our assets (e.g. custom property) and maintain the ability to do things like resolution switching even after the user has moved their library or when the current file was moved in the OS and relative paths are no longer correct.

@gregzaal gregzaal added the enhancement New feature or request label May 17, 2024
@gregzaal gregzaal changed the title Maintain functionality even after library is moved Maintain functionality even after blend file/library is moved May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant