UI: Show Labels for BSDF "Distribution" and "Subsurface Method" #111766

Closed
Harley Acheson wants to merge 2 commits from Harley/blender:BSDFNames into main

When changing the target branch, be careful to rebase the branch in your fork to match. See documentation.
Member

Add labels to the BSDF options "Distribution" and "Subsurface Method",
since this type of enum list no longer shows titles since #109798.


All these items should have labels since we longer show the titles in this type of situation. With this PR it looks like this:

image

Add labels to the BSDF options "Distribution" and "Subsurface Method", since this type of enum list no longer shows titles since #109798. --- All these items should have labels since we longer show the titles in this type of situation. With this PR it looks like this: ![image](/attachments/28e10f9d-4c3a-4f57-abe1-2a1dd1981b6e)
Harley Acheson added 1 commit 2023-09-01 01:22:12 +02:00
aa9f503bdf UI: Show Labels for BSDF "Distribution" and "Subsurface Method"
Add labels to the BSDF options "Distribution" and "Subsurface Method",
since this type of enum list no longer shows titles since #109798.
Harley Acheson added this to the User Interface project 2023-09-01 01:22:25 +02:00
Harley Acheson requested review from Hans Goudey 2023-09-01 01:22:37 +02:00
Member

Makes sense in the screenshot. But how does it look in the node editor?

Makes sense in the screenshot. But how does it look in the node editor?
Author
Member

Makes sense in the screenshot. But how does it look in the node editor?

Ewww.... With factory settings and default sizes it looks cut off...

image

Is there some way of fixing that?

> Makes sense in the screenshot. But how does it look in the node editor? Ewww.... With factory settings and default sizes it looks cut off... ![image](/attachments/4ebe4710-63ff-452a-afee-551d1efa7b5f) Is there some way of fixing that?
Member

Hmm, how about checking the context (node editor vs properties) in the drawing callback? A bit weird to do that but not really wrong!

Hmm, how about checking the context (node editor vs properties) in the drawing callback? A bit weird to do that but not really wrong!
Author
Member

@HooglyBoogly - Hmm, how about checking the context (node editor vs properties) in the drawing callback? A bit weird to do that but not really wrong!

I didn't think of that. That does work, but then only solves the problem in one place. But maybe that is okay?

With #109798 we are assuming that we need the enum list title if we are clicking on an icon, but that we don't need it if we are showing text since we normally show those with labels. If I do this differently depending on context I get the following:

image

It shows that clicking on Subsurface Method on the Node itself does not show the title for that list. Nor will it in the Sidebar. However, it isn't needed in Properties since there is the label to the left.

Does this matter? If yes, then the next step is probably just adding a flag somewhere to force titles on?

> @HooglyBoogly - Hmm, how about checking the context (node editor vs properties) in the drawing callback? A bit weird to do that but not really wrong! I didn't think of that. That does work, but then only solves the problem in one place. But maybe that is okay? With #109798 we are assuming that we need the enum list **title** if we are clicking on an icon, but that we don't need it if we are showing text since we normally show those with labels. If I do this differently depending on context I get the following: ![image](/attachments/737640d5-dc49-46b4-92b5-0d9329070773) It shows that clicking on Subsurface Method on the Node itself does not show the title for that list. Nor will it in the Sidebar. However, it isn't needed in Properties since there is the label to the left. Does this matter? If yes, then the next step is probably just adding a flag somewhere to force titles on?
109 KiB
Harley Acheson added 1 commit 2023-09-01 17:31:45 +02:00
First-time contributor

The value fields and their labels are consolidated in nodes -taking up all available width- but split in the material editor. Perhaps the dropdowns could behave the same? ->one wide dropdown, label left-aligned, item/value right-aligned. This would benefit a number of node dropdowns (principled hair, refraction, etc). Right now it looks like they take up a proportion of the total node width, not accounting for contents.

The situation could be made better for colors as well, their labels also get clipped (subsurface color most notably), but that's a different issue since we can't really overprint text on an arbitrary color. I guess these would have to be a fixed size, or something.

The value fields and their labels are consolidated in nodes -taking up all available width- but _split_ in the material editor. Perhaps the dropdowns could behave the same? ->one wide dropdown, label left-aligned, item/value right-aligned. This would benefit a number of node dropdowns (principled hair, refraction, etc). Right now it looks like they take up a proportion of the total node width, not accounting for contents. The situation could be made better for colors as well, their labels also get clipped (_subsurface color_ most notably), but that's a different issue since we can't really overprint text on an arbitrary color. I guess these would have to be a fixed size, or something.
Author
Member

I don't need to do this.

I can decide whether to show enum list titles based on the previous item in the layout. So show titles if there isn't a prior label. So far seems to work fine.

I don't need to do this. I can decide whether to show enum list titles based on the previous item in the layout. So show titles if there isn't a prior label. So far seems to work fine.
Harley Acheson closed this pull request 2023-09-02 01:57:51 +02:00

Pull request closed

Sign in to join this conversation.
No reviewers
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
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#111766
No description provided.