Geometry Node: Multi-input socket tooltip #104468
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#104468
Loading…
Reference in New Issue
No description provided.
Delete Branch "mod_moder/blender:multi_input_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?
Tooltip for multi-input socket. This kind of inspection can help to see what data are passed into node.
Any invalid, muted or dangling link will not be taken into account. This feature reuse already exist tooltip
formatting and just add column indentation in multi-line case.
I not sure but it seems to make sense to add one person from ui for reviewing this.
The idea seems nice to me, the code is a bit outdated though.
@ -486,3 +490,2 @@
if (socket->runtime->total_inputs > 2) {
multi_input_socket_offset = (socket->runtime->total_inputs - 2) *
NODE_MULTI_INPUT_LINK_GAP;
multi_input_socket_offset = socket->runtime->total_inputs - 2;
Unrelated change
@ -1454,3 +1519,3 @@
}
/* Don't draw multi-input sockets here since they are drawn in a different batch. */
if (sock->flag & SOCK_MULTI_INPUT) {
if (sock->is_multi_input()) {
+1, but unrelated cleanups
@ -28,6 +28,7 @@
#include "BLI_compute_context.hh"
#include "BLI_enumerable_thread_specific.hh"
#include "BLI_function_ref.hh"
Necessary to add this include?
@ -289,6 +290,18 @@ class GeoTreeLog {
ValueLog *find_socket_value_log(const bNodeSocket &query_socket);
};
inline Vector<ValueLog *> multi_input_socket_value_logs(GeoTreeLog &tree_log,
I don't think this needs to be inline, it's not really a trivial function.
@ -292,0 +294,4 @@
const bNodeSocket &query_socket)
{
BLI_assert(query_socket.is_multi_input());
Vector<ValueLog *> logs;
Array
would be a better fit based on the logic hereOther than the indentation on the 4th item "Curve" (not sure if related to this PR in particular), LGTM +1
@pablovazquez Fixed.
Thanks!
In that screenshot the bullet points go 1, 2, 3, 6. Are we skipping empty/invalid/disconnected entries?
I think we should not skip those and communicate what's happening instead. Some of the wires are red while others are just a reroute to nowhere, would that yield the same "broken" link or is there a way to say if it's "invalid", "wrong type, "missing", etc.
Correct. This is how internally result would looks like.
How this should looks like? Not sure about just print numbers with nothing (or some text to duplicate this a lot of time) like\
We just ignore link if there is no connected source of value:
It is useful to keep see last one value while user is pulls the connection, rather just show 0.
I am okay with add colored elements into tooltip for invalid/muted/dangling links, but not sure about UI of this (and how to add this..)
Adding this seems fine to me, if that info is easily accessible right now. If not, I think it's worth committing this now and improving it further later.
Checkout
From your project repository, check out a new branch and test the changes.