Nodes: Use socket subtype in tooltip #120601
No reviewers
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#120601
Loading…
Reference in New Issue
No description provided.
Delete Branch "mod_moder/blender:subtype_it_tooltip"
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?
Add subtype info into tooltips of node sockets. This reuse already existing code
to generate text from value, so this is trivial change. Now tooltip display the same
value as socket field itself.
Everywhere in examples values are different.
Float type:
Vector type:
Integer type:
Precision issue (#118073) it seems is not there due to now tooltip use the same function to generate the string as UI fields.
But this issue still should be taken into account to be fixed in future if we'll switch UI to
fmt
.I like showing the units in the tooltip, but I think the actual numerical value that Blender uses under the hood should still be displayed, as well. At least if it's different from the subtype value.
E.g. when it says
180 °
for the angle subtype it should still also mention that the actual value being passed around is3.14...
I've seen people being confused by this and even just looking at the screenshot I'm unsure if
56.5 %
means a value of0.565
or56.5
.So this might also help communicate that subtypes do more than just tag on a unit symbol at the end.
I was thinking about
180 °
as reason why we need to display this instead of raw value. But i see issue with56.5 %
. So i think it should be okay if display 2 row with numbers, what do you think?I think that could work.
Maybe dimming the second row could be a good idea. Otherwise I worry it could get too visually busy for long values like the acceleration vector.
Mockup:
I'll added support for such formatting of text in #121083.
Checkout
From your project repository, check out a new branch and test the changes.