picker isn't working on cryptomatte matte id picker #99445
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#99445
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?
System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96
Blender Version
Broken: version: 3.3.0 Alpha, branch: master, commit date: 2022-06-27 22:46, hash:
7a44f62bdb
Worked: (newest version of Blender that worked as expected)
add a cryptomatte node (new or legacy), hover over matt id and press E . No picker will appear meaning user must click the + icon.
Added subscriber: @3di
Added subscriber: @PratikPB2123
Changed status from 'Needs Triage' to: 'Confirmed'
Thanks for the report. Shortcut only works when hovering over +/- icons
Different problem, but may be related to #101058
Does not seem to be related. This report is about eyedropper not starting at all and the #101058 is about eyedropper not properly picking up matte id.
As for this report, the way how the cryptomatte eyedropper is implementes is quite horrible and can not support text fields. We need to move it out of the generic eyedropper, which will remove some internal tricketry with invisible properties, as well as will allow using eyedropper from the field itself.
I'd consider this a known limitation, using the eyedropper from the main text button isn't supported.
Problem is that the cryptomatte eyedropper reuses the color eyedropper operator, this is kind of a hack. It doesn't seem difficult to add a separate eyedropper operator. We also have data-block, driver and depth eyedropper operators for example. The button could then even display the eyedropper icon we show in other places (at least when there's no value set yet):
Design wise there is the question how this should work though: Does it always add? Or does it replace? Or can you for example hold Alt while clicking to toggle from add to remove? Sounds like straight forward design decisions though.
@JulianEisel I think we should try to implement the feautre properly. It is kinda a bug from expectation point of view -- it doesn't work the same as, for example, bones selection where you can click "E" on the entire field.
I'd give it a try, and only move to known limitation if some big design limitation is encountered.
As for the behavior: doesn't seem like a complicated decision to be made either :)