User interface improvements for attribute search #85881
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#85881
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?
Design task: #85280
This depends on #85658.
{F9750374, size=full}
The idea is to go beyond the basic search list and indeed show:
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @dfelinto
#85280 was marked as duplicate of this issue
Added subscriber: @user1
Could a dropdown inside of the new string node be a good place to store existing attributes in a list?
Added subscriber: @HooglyBoogly
@user1 That's exactly what this design is for.
Note that in D10623 I strayed from the design above in a few ways:
One thing to keep in mind is that we can also use custom tooltips and even a right click menu for the search if it's helpful.
Can you give some examples?
This is a separate issue. We can add pattern/hashes/... for the sockets as a whole to make them more accessible.
It does indeed. However this is the same for categories. The question may then be, are users thinking in terms of (let me find the attribute X that is in the points; or let me find the attribute Y that I created as a node/builtin/...)
We can have a generic "User/Original Data/..." however we want to call them in the spreadsheet in those cases. Though I can't see why Vertex Group wouldn't be a good category.
In the design we have "Nodes", "Built-in", and the Custom, the work "Custom" is never exposed to the user though, and it is actually UV Map, Vertex Group. In the documentation we can use what we plan to use for spreadsheet (User/Original Data)?
Added subscribers: @Sparazza, @MiroHorvath, @OscarBaechler
Final user interface improvements for attribute searchto User interface improvements for attribute searchThis issue was referenced by
71eaf872c2
@HooglyBoogly remember in the future to add an image here of the final result.
I was testing it and have two remarks:
Test file: attribute-order.blend
{F9934333, size=full}
Note if we want to move this task to done I would then ask for us to have new tasks for the issues above. Also, although polishing usually can be left for the community remember that we decided on prioritize this to have this one part of the pipeline super polished. So I think it is worth to address those remaining issues.
Looks like I had an unfinished comment from a while ago here:
Right now there is 2D vectors for example, I don't doubt there may be more in the future though.
Anyway, I see node sockets themselves as different from attribute data types themselves anyway. After all we access attributes by name, not by plugging in sockets.
Thanks for the screenshot
I'll approach this as a bug fix, since it's the same in other menus. I agree it should change. I made a task: #87526
This is just whatever way the search orders them, we don't really have the flexibility to change the order manually at the moment. Though this could be improved I suppose, I'm not sure exactly how at the moment.
Removed subscriber: @Sparazza
Changed status from 'Confirmed' to: 'Resolved'