Nodes: Add info about implicit input of value to tooltip #120498

Open
Iliya Katushenock wants to merge 8 commits from mod_moder/blender:implicit_input_field_tooltip into main

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

Add note about the fact that socket have implicit input of value to tooltip.
There is no general way to add name or description of implicit field, but
usually this is enough clear from the name of the socket.

image image
Add note about the fact that socket have implicit input of value to tooltip. There is no general way to add name or description of implicit field, but usually this is enough clear from the name of the socket. | | | | -- | -- | | ![image](/attachments/0f5d180e-4165-4a91-a64d-2018cf61df69) | ![image](/attachments/22e7a388-d74d-4cc8-9b85-1f445787732e) |
Iliya Katushenock added 6 commits 2024-04-11 01:10:30 +02:00
Iliya Katushenock added this to the Nodes & Physics project 2024-04-11 01:10:35 +02:00
Iliya Katushenock added 1 commit 2024-04-11 19:18:23 +02:00
Iliya Katushenock requested review from Hans Goudey 2024-04-11 19:18:59 +02:00
Iliya Katushenock added 1 commit 2024-04-11 19:19:54 +02:00
Iliya Katushenock requested review from Jacques Lucke 2024-04-30 16:01:37 +02:00
Member

I wonder if "implicit field input" is a useful tooltip to someone who doesn't already know what it is.

I wonder if "implicit field input" is a useful tooltip to someone who doesn't already know what it is.
First-time contributor

I wonder if "implicit field input" is a useful tooltip to someone who doesn't already know what it is.

Luckily I am here to answer this question. No, I have no idea what this means. Under normal circumstances I'd look for more info in the documentation after reading that.

> I wonder if "implicit field input" is a useful tooltip to someone who doesn't already know what it is. Luckily I am here to answer this question. No, I have no idea what this means. Under normal circumstances I'd look for more info in the documentation after reading that.
Author
Member

There is could be 2 option i think:

  1. Send user to manual by this word.
  2. Call this as Auto Field input in UI and have no relatations with manual.
There is could be 2 option i think: 1. Send user to manual by this word. 2. Call this as `Auto Field input` in UI and have no relatations with manual.
First-time contributor

There is could be 2 option i think:

  1. Send user to manual by this word.
  2. Call this as Auto Field input in UI and have no relatations with manual.

I just looked up implicit fields online and I believe the 1st option is better. The sites that came up seemed unusual and initially confused me more until I read a little on a couple of them. Finding this information in the relevant area of the documentation would be an immediate click in my head about what implicit fields are.

> There is could be 2 option i think: > 1. Send user to manual by this word. > 2. Call this as `Auto Field input` in UI and have no relatations with manual. I just looked up implicit fields online and I believe the 1st option is better. The sites that came up seemed unusual and initially confused me more until I read a little on a couple of them. Finding this information in the relevant area of the documentation would be an immediate click in my head about what implicit fields are.
First-time contributor

image
just to mention I think the information marked here is more descriptive and helpful without introducing new terms.
if this can be done. whichever name will be fine. Whether it's "Default", "Automatic", "Implicit", "Prefilled", etc.

![image](/attachments/631aec5e-dbe1-4489-9902-62e6fcfa5551) just to mention I think the information marked here is more descriptive and helpful without introducing new terms. if this can be done. whichever name will be fine. Whether it's "Default", "Automatic", "Implicit", "Prefilled", etc.
Author
Member

just to mention I think the information marked here is more descriptive and helpful without introducing new terms.

This is not the best idea to mention default value in description and this is violate current guideline of UI: https://developer.blender.org/docs/features/interface/human_interface_guidelines/tooltips/#the-item-description

I just looked up implicit fields online and I believe the 1st option is better. The sites that came up seemed unusual and initially confused me more until I read a little on a couple of them. Finding this information in the relevant area of the documentation would be an immediate click in my head about what implicit fields are.

I wonder if "implicit field input" is a useful tooltip to someone who doesn't already know what it is.

I don't think that we can do a lot in case if user don't read manual and no one have said this in tutorial that user have seen.
Becuse of this, i think the best that we can do, is:

  1. Send user to manual by this word.
  2. Call this as Auto Field input in UI and have no relatations with manual.

As example of first one, there is: https://docs.blender.org/manual/en/latest/search.html?q=implicit&check_keywords=yes&area=default
As second one case, tooltip can be paraphrased to:

  1. Default value is Implicit Field
  2. Auto field input
  3. Field by default

I'd like to avoid Field word to reuse this for shaders, but this might be okay\

> just to mention I think the information marked here is more descriptive and helpful without introducing new terms. This is not the best idea to mention default value in description and this is violate current guideline of UI: https://developer.blender.org/docs/features/interface/human_interface_guidelines/tooltips/#the-item-description > I just looked up implicit fields online and I believe the 1st option is better. The sites that came up seemed unusual and initially confused me more until I read a little on a couple of them. Finding this information in the relevant area of the documentation would be an immediate click in my head about what implicit fields are. > I wonder if "implicit field input" is a useful tooltip to someone who doesn't already know what it is. I don't think that we can do a lot in case if user don't read manual and no one have said this in tutorial that user have seen. Becuse of this, i think the best that we can do, is: 1. Send user to manual by this word. 2. Call this as `Auto Field input` in UI and have no relatations with manual. As example of first one, there is: https://docs.blender.org/manual/en/latest/search.html?q=implicit&check_keywords=yes&area=default As second one case, tooltip can be paraphrased to: 1. `Default value is Implicit Field` 2. `Auto field input` 3. `Field by default` I'd like to avoid `Field` word to reuse this for shaders, but this might be okay\
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u implicit_input_field_tooltip:mod_moder-implicit_input_field_tooltip
git checkout mod_moder-implicit_input_field_tooltip
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 Assignees
4 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#120498
No description provided.