Move vertex group names from object to geometry #88951

Closed
opened 2021-06-08 12:24:47 +02:00 by Jacques Lucke · 11 comments
Member

For (unknown) historical reasons vertex group names are stored on the object instead of on the geometry.
This is causing technical problems when we want to access attributes of a mesh in a generic way and don't have the object. Also see #88460 (Technical design for attribute ui list).

The solution is to move the names of vertex groups to the geometry (mesh, lattice, grease pencil).
This can cause data loss when the geometry and object are in different .blend files, but this case is expected to be quite rare.

For (unknown) historical reasons vertex group names are stored on the object instead of on the geometry. This is causing technical problems when we want to access attributes of a mesh in a generic way and don't have the object. Also see #88460 (Technical design for attribute ui list). The solution is to move the names of vertex groups to the geometry (mesh, lattice, grease pencil). This can cause data loss when the geometry and object are in different .blend files, but this case is expected to be quite rare.
Author
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Author
Member

Added subscriber: @JacquesLucke

Added subscriber: @JacquesLucke
Member

Added subscriber: @HooglyBoogly

Added subscriber: @HooglyBoogly
Hans Goudey self-assigned this 2021-06-23 18:03:18 +02:00
Member

Should the Python API for vertex groups be moved to object data as well? Other than consistency and clarity, another reason to do it is so the "Vertex Group" panel can display when you have a mesh pinned in the property editor, but no object.

Also, maybe moving the active vertex group index would be a good opportunity to get rid of the "index starts at one" thing for actdef

Should the Python API for vertex groups be moved to object data as well? Other than consistency and clarity, another reason to do it is so the "Vertex Group" panel can display when you have a mesh pinned in the property editor, but no object. Also, maybe moving the active vertex group index would be a good opportunity to get rid of the "index starts at one" thing for `actdef`

Added subscriber: @hadrien

Added subscriber: @hadrien

In #88951#1181740, @HooglyBoogly wrote:
Should the Python API for vertex groups be moved to object data as well? Other than consistency and clarity, another reason to do it is so the "Vertex Group" panel can display when you have a mesh pinned in the property editor, but no object.

Also, maybe moving the active vertex group index would be a good opportunity to get rid of the "index starts at one" thing for actdef

Always found it odd that pinning a mesh in properties would hide its vertex groups, which I thought were object data. So, the reason is lost to history ? in any case, changing this would be an improvement from my point of view.

> In #88951#1181740, @HooglyBoogly wrote: > Should the Python API for vertex groups be moved to object data as well? Other than consistency and clarity, another reason to do it is so the "Vertex Group" panel can display when you have a mesh pinned in the property editor, but no object. > > Also, maybe moving the active vertex group index would be a good opportunity to get rid of the "index starts at one" thing for `actdef` Always found it odd that pinning a mesh in properties would hide its vertex groups, which I thought were object data. So, the reason is lost to history ? in any case, changing this would be an improvement from my point of view.
Hans Goudey changed title from Move vertex group names from object to geometry. to Move vertex group names from object to geometry 2021-06-29 05:48:04 +02:00

This issue was referenced by 3b6ee8cee7

This issue was referenced by 3b6ee8cee7080af200e25e944fe30d310240e138

Added subscriber: @dfelinto

Added subscriber: @dfelinto

This introduced a big issue. This should have bumped the minimum blender version:

diff --git a/source/blender/blenkernel/BKE_blender_version.h b/source/blender/blenkernel/BKE_blender_version.h
index dffd70c077f..926938b7419 100644
--- a/source/blender/blenkernel/BKE_blender_version.h
+++ b/source/blender/blenkernel/BKE_blender_version.h
@@ -44,8 +44,8 @@ extern "C" {
 /* Minimum Blender version that supports reading file written with the current
  * version. Older Blender versions will test this and show a warning if the file
  * was written with too new a version. */
-#define BLENDER_FILE_MIN_VERSION 290
-#define BLENDER_FILE_MIN_SUBVERSION 0
+#define BLENDER_FILE_MIN_VERSION 300
+#define BLENDER_FILE_MIN_SUBVERSION 11
 
 /** User readable version string. */
 const char *BKE_blender_version_string(void);

I'm going to report it as a UnbreakNow! bug soon.

This introduced a big issue. This should have bumped the minimum blender version: ``` diff --git a/source/blender/blenkernel/BKE_blender_version.h b/source/blender/blenkernel/BKE_blender_version.h index dffd70c077f..926938b7419 100644 --- a/source/blender/blenkernel/BKE_blender_version.h +++ b/source/blender/blenkernel/BKE_blender_version.h @@ -44,8 +44,8 @@ extern "C" { /* Minimum Blender version that supports reading file written with the current * version. Older Blender versions will test this and show a warning if the file * was written with too new a version. */ -#define BLENDER_FILE_MIN_VERSION 290 -#define BLENDER_FILE_MIN_SUBVERSION 0 +#define BLENDER_FILE_MIN_VERSION 300 +#define BLENDER_FILE_MIN_SUBVERSION 11 /** User readable version string. */ const char *BKE_blender_version_string(void); ``` I'm going to report it as a UnbreakNow! bug soon.

Report: #89870

Report: #89870

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Sign in to join this conversation.
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
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#88951
No description provided.