Fix: Use __package__ to get addon prefs for Blender 4.x compatibility#5
Open
starzynhobr wants to merge 1 commit intoRedHaloStudio:masterfrom
Open
Fix: Use __package__ to get addon prefs for Blender 4.x compatibility#5starzynhobr wants to merge 1 commit intoRedHaloStudio:masterfrom
starzynhobr wants to merge 1 commit intoRedHaloStudio:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello! This PR fixes a
KeyErrorcrash that occurs when trying to import a file in Blender 4.2+ due to changes in the new Extensions system.The Problem:
The addon was trying to access its own preferences using methods that are no longer reliable in the context where the operator runs, leading to a
KeyError: 'key not found'crash.The Solution:
This change replaces the preference access method with
context.preferences.addons[__package__].preferences. The__package__variable reliably provides the addon's own ID without needing to look it up, resolving the issue.This makes the addon usable again.