Add-ons Blender 2.79 - more generic Panel rename code #50726
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#50726
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
This is a task is part of #50357, but marking it as separate to not clutter the main one.
It introduces, like the title said, a more generic function for add-ons that don't have the feature and modify the existing scripts if needed, as some more robustness in case of a failure.
What needs to be changed for individual add-ons:
The error message already gives the script name.
Example for Bool Tool:
Example of the error message on double register:
As a part of this task, add-ons can have their locations for panels altered conforming with the current policy of not creating new tabs when not needed.
Changed status to: 'Open'
Added subscriber: @VukGardasevic
Added subscriber: @BrendonMurphy
hi, it could be too much to implement this now, might be a better 2.8 target? we still have not updated the contrib addons to the first panel location as option changes, if we want to do this, it needs to be all or none.
I do agree with the change. i think also we could look at adding the base code into addons_utils.py so it's accessible by all addons & not on a per addon base.
As for the implementation it shouldn't be a problem apart from a series of commits, as it doesn't change the functionality, however I'm open to a decision in regards to it.
As for 2.8 depending on how the add-ons are handled (like being registered per workspace or similar) probably there will be some API or utils code that handles the location of the Panels in the UI or specific tab locations.
If during 2.79 development we make some more generic code in addon_utils I'm fine with that too. :)
@VukGardasevic I think it's fine to go ahead with this soon, It's a good change & fits code design well.
One question, why the use of:
you could use:
or is it needed at all? thanks.
Raising to confirmed as this is a developer task
move to high task as this task belongs to dev tasks
Changed status from 'Open' to: 'Resolved'
Since we are in the RC1 I think this task can be closed.
Probably there could some more add-ons added having this feature (like Tissue or ANT and some exporters in the contrib that have panels in the
TOOL_PROPS
section) but that is something that is not a priority as the first two have rational locations / layouts, and the contrib ones are not part of the release.