GPencil: Rename intermal layer info
variable/prop to name
#96341
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
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#96341
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?
Actually, the layer name is defined as
info
at C code level, but also as python api level and this breaks all naming conventions.The objective of this task is to do a full rename of this variable and discuss what is the best approach for python API because if we rename this prop, we are going to break a lot of add-ons.
My initial idea for the python API was to create a duplicated
name
prop and use this new prop in all Blender python code. For the oldinfo
prop, the ideal would be marked as deprecated and allow the users to run add-ons with old prop, but with a warning. In future versions we could remove this deprecated option.As an alternative plan, we could wait for a planned release number and break the API, but IMHO this would be the last option.
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @antoniov
GPencil: Rename intermal layer `info`variable to `name`to GPencil: Rename intermal layer `info` variable/prop to `name`Added subscribers: @mont29, @ideasman42
@ideasman42 @mont29 What is your advice here?
Added subscriber: @JasonvanGumster
Am not sure how critical this renaming is... In general we try to avoid those as much as possible...
But if this absolutely has to be done, then think the proper process is:
Add new RNA prop Keep existing old one, add deprecation warning.
** Keep name in the DNA struct as it is, with clear comment it will be changed.
Remove the old RNA property Do rename in DNA struct (since afaik DNA rename ensures backward compatibility, but not forward one).
Added subscriber: @dfelinto
@mont29 Thanks for the detailed steps for doing the rename. Really, this is something that is not critical, but IMHO it would be better to harmonize this prop name asap. Maybe we would need the opinion about this by @dfelinto before doing it.