Export UV Layout is an add-on document it as such? #54429
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#54429
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
https://docs.blender.org/manual/en/dev/editors/uv_image/uv/editing/layout.html#export-uv-layout
is actually an addon but we document it like it is an eternal feature.
This might be a larger question but how do we document add-ons enabled by default.
Added subscriber: @Blendify
Added subscriber: @brecht
I think addons that are enabled by default should be documented as builtin features. It's basically an implementation detail if it's an addon or not, why should the user care?
The fact that it's an addon only matters in that it can be disabled, but that's not important I think.
Added subscribers: @VukGardasevic, @ideasman42
I do not have a strong opinion here but I think we should keep this information in the manual. Having it elsewhere can make it harder to find. This, however, would also mean that we should port all the import/export add-ons to the manual. @VukGardasevic @ideasman42 Any thoughts here?
I think that adding a notice box about it being an add-on with the default name / category could be enough. Just in case if for some reason, the user has disabled it.
The inclusion of documenting all the default start-up add-ons could be postponed until the 2.8 finalization.
Changed status from 'Open' to: 'Resolved'
Fixed