Addon Copy-settings #53948
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#53948
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?
System Information
Linux
Blender Version
Broken: 2.79a
Short description of error
When activating copy settings addon, a warning is shown, that it was written for 2.79.1 and it may not work.
Exact steps for others to reproduce the error
Activate the "Render: Copy settings" addon in user prefs.
Added subscriber: @bliblubli
Added subscribers: @mont29, @lichtwerk
pretty sure this warning could be ignored, as from first glance this seems to work correctly (addon was just changed at a time when blenders subversion was actually higher -- some changes that caused a subversion bump have not made it into 2.79a)
@mont29: just to make sure:
267662e07a
is in 2.79a but the changes relating bpy.types arent, but as it seems that everything has been taken care of, should we:Changed status from 'Open' to: 'Resolved'
Eeeeek! I think this commit should not have been backported to 2.79a at all, my bad, will revert it.
Fixed in
1118da4c30