Rules based row filtering for attribute spreadsheet #86133
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#86133
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?
See #86027 - need final mockup.
{F9914560, size=full}
When a rule row is complete, a new blank one is available.
Each rule is a set of:
Conditions:
Equal
Larger Than
Smaller Than
The rules are AND conditions. So they don't add new rows, but only remove them.
If the column name is not available (e.g., the active object doesn't have attribute Mask), user should be aware of that. (e.g., warning icon, red background, ...). The other rules should still be applied though.
The column name should do string search/lookup with the columns names of the spreadsheet. Ideally this should work for scene data in the future.
Operators:
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @dfelinto
The way phabricator handles rules is simple enough and I think it can be the focus of the initial implementation here:
{F9859851, size=full}
Besides we don't even need the "reset" button at first. It is super fast to click the remove button few times in a row. This is based on the phabricator experience. Once we have the basic in master we can reiterate on it.
{F9915014 size=full}
branch:
temp-spreadsheet-row-filter
The UI is basically implemented, it should be straightforward to move it wherever we want it. I just liked the idea of trying it in a popover first (I like it, though it means we won't be able to drag them : P)
Things I'm thinking about:
Hi @HooglyBoogly I couldn't get this to work. Did you implement only the UI?
I think we can do without the data type. The filters should map to the existing columns in the spreadsheet.
That also means there no "Vector" data type since we are filtering the columns individually.
"How are we going to deal with sorting by material_index but seeing the position values for example?
We basically won't. Sorting (if implemented) is local to the current data-set.
"They are separate data sets, so they don't really interact on the spreadsheet level?"
Correct
re: "Equal To".
In the original-original design all we had was a "Range".
Which we could use for floats. But the equal to ca be used for integers and booleans.
(also, the "property search" is important to be able to pick from the existing columns)
Followup tasks:
This issue was referenced by
f9aea19d98
Changed status from 'Confirmed' to: 'Resolved'