Initial attribute list for non-point cloud geometries #87827

New Issue

Dalai Felinto · 2021-04-26T14:19:37+02:00

Dalai Felinto commented

2021-04-26 14:19:37 +02:00

The point cloud object type already has an attribute list, but not the other object types.

List of all the attributes
Sort the list per domain then their own order (use the same order we have in the spreadsheet editor).
Allow to create/remove attributes
Allow to filter attributes that exist in other panels (UVMaps, Colors, Vertex Groups, and Others for the generic ones).
There should always be an "active" attribute.
Use the same domain > attribute data_type we have in the attribute search lookup.

Initial delivery:

List of the custom attributes (don't need to include attributes that are in other panels nor the built-ins such as position)
- The attributes that are created when you apply a geometry-nodes modifier.
Sort the list per domain then their own order (use the same order we have in the spreadsheet editor).
Allow to create/remove attributes
There should always be an "active" attribute.
Use the same domain > attribute data_type we have in the attribute search lookup.

The point cloud object type already has an attribute list, but not the other object types. * List of all the attributes * Sort the list per domain then their own order (use the same order we have in the spreadsheet editor). * Allow to create/remove attributes * Allow to filter attributes that exist in other panels (UVMaps, Colors, Vertex Groups, and Others for the generic ones). * There should always be an "active" attribute. * Use the same `domain > attribute data_type` we have in the attribute search lookup. --- Initial delivery: * List of the custom attributes (don't need to include attributes that are in other panels nor the built-ins such as position) * The attributes that are created when you apply a geometry-nodes modifier. * Sort the list per domain then their own order (use the same order we have in the spreadsheet editor). * Allow to create/remove attributes * There should always be an "active" attribute. * Use the same `domain > attribute data_type` we have in the attribute search lookup.

Dalai Felinto commented

2021-04-26 14:19:37 +02:00

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

Dalai Felinto commented

2021-04-26 14:19:37 +02:00

Added subscriber: @dfelinto

Hans Goudey commented

2021-04-27 00:32:48 +02:00

Added subscriber: @HooglyBoogly

Hans Goudey commented

2021-04-27 00:32:48 +02:00

By other object types, I assume you just mean mesh objects, right? This would become a much bigger task if you meant something different.

Dalai Felinto commented

2021-04-28 09:41:16 +02:00

I mean mesh objects at first. The criteria can be that we only do this for object types that:

Support attribute editing (as we do with vertex paint now).
Support arbitrary attributes in geometry nodes and/or modifiers.

That makes curves and point clouds the next ones to get this, once attribute edit support them.

I mean mesh objects at first. The criteria can be that we only do this for object types that: * Support attribute editing (as we do with vertex paint now). * Support arbitrary attributes in geometry nodes and/or modifiers. That makes curves and point clouds the next ones to get this, once attribute edit support them.

Jacques Lucke self-assigned this 2021-05-07 13:30:35 +02:00

Jacques Lucke commented

2021-05-07 13:41:14 +02:00

I just noticed that we will run an issue with vertex groups again here. Vertex group names are stored on the object (for historical reasons) and not on the mesh.. So we need some object context when displaying mesh attributes and want to include vertex groups.

I just noticed that we will run an issue with vertex groups again here. Vertex group **names** are stored on the object (for historical reasons) and not on the mesh.. So we need some object context when displaying mesh attributes and want to include vertex groups.

Jacques Lucke commented

2021-05-10 12:47:42 +02:00

The most basic functionality for this is in the temp-attributes-panel, currently it only shows custom non-legacy attributes in the panel (so basically only attributes that were created with geometry nodes after the modifier is applied).

The most basic functionality for this is in the `temp-attributes-panel`, currently it only shows custom non-legacy attributes in the panel (so basically only attributes that were created with geometry nodes after the modifier is applied).

Dalai Felinto changed title from ~~Attribute list for non-point cloud geometries~~ to Initial attribute list for non-point cloud geometries

2021-05-10 14:20:02 +02:00

blender-admin commented

2021-06-28 16:52:49 +02:00

This issue was referenced by 6ce4d39e6b

This issue was referenced by 6ce4d39e6bd585257845e29a3de4eb278b941fd3

Dalai Felinto commented

2021-07-05 14:46:38 +02:00

Changed status from 'Confirmed' to: 'Resolved'

Dalai Felinto closed this issue

2021-07-05 14:46:38 +02:00

Dalai Felinto commented