Hello Dynamo Community! :raised_hands: The Dynamo team wants to find out which information is important to display on Dynamo Nodes. Please fill out this brief poll and survey to help us optimize our design efforts. Also, apologies for the rather verbose polling below, but the forum polling options are limited :roll_eyes: If the following elements were displayed on Dynamo nodes, please rank the information options below from most important to least important to you - There are 6 items and 6 individual polls where you get to vote once per poll: Most Important poll Second Most Important poll Third Most Important poll Fourth Most Important poll Fifth Most Important poll Least Important poll Please also feel free to answer the following questions in a reply to this thread: Are there any options listed above that you would not want to see at all? Why or why not? Are there any options you would want to see that are not listed above? Why or why not? We’re super excited to see what you, our awesome community think as we look to better explore how Nodes can look and feel! The Dynamo Team

I’m OK with somehow indicating that a Node has been renamed, but the current implementation is FAR too intrusive. The large RENAMED text takes up too much space, and is too “in your face”. Something more subtle like changing the background color, or italicizing the name, or a small icon would provide the same information but more subtly.

General Note: Text can always be reduced by introduction of graphic language. (think Magritte) -More compact @Level indication–perhaps more graphic to eliminate buttons. -More compact Lacing indication (graphic between inputs? (Currently gets its own row!-- and is rarely used) -Node icons as alternate to node names (for us visual folk). Many icons are already made! -Differentiation between Inputs with Default Values and inputs that require a value. -find a way to abbreviate input/output text for standard data types, either through letters or icons. See attached PDF. Dynamo_Nodes-Noted.pdf (566.1 KB)

We have done an investigation into this (What we call Spikes). The short answer is we can enable it to work inside of multi-threaded environments such as Dynamo Sandbox, FormIt or Alias, but cannot currently do so inside of single-threaded applications such as Revit or Civil 3d. So, we are looking into how to properly de-couple Dynamo from this constraint :slight_smile:

Hello Tony, Out of curiosity, have you used the Documentation Broswer yet as it surfaces warnings in a human readable way? So far we’ve added in the 30 most common error messages. An example of Null value cannot be cast to type is below: [image] Good shout! We’re looking to bring the Dynamo Dictionary into product also, you can read more about it here: https://github.com/DynamoDS/Dynamo/wiki/Dynamo-Public-Roadmap#when-knowledge-is-not-necessarily-power We also have plans for this with both the Dynamo Dictionary work as above, and a new Node Autocomplete feature we are starting work on a proof of concept in the next few weeks. This would require major structural changes to Dynamo, but is still on our radar. Simply won’t be fast I’m afraid.

Great suggestions @Nick_Curtis! We have already introduced Differentiation between Inputs with Default Values and inputs that require a value - default ports are now italicized, as below: [image]

Interesting idea Marcel… What if right clicking (say) on the node output gave a list of possible nodes… You click one… It then appears with its wire connected at a reasonable distance? Then you could just right click your way across the screen…

Hello solamour, thanks for the reply. Where does documentation browser live in Dynamo, a setting to activate? I am mostly using RVT2019 Dynamo 2.04 so i am guessing it is maybe in RVT2020 Dynamo? Unfortunately we are driven by what RVT an Architect is using and they are generally 2 years behind. I have seen the above mentioned before as i am keenly interested in the advancements that it can achieve however it is always difficult when the build of Dynamo RVT is not backwards compatible. The other future developments look awesome as well. While i dont believe making something so dumb down that anyone can use it is the way forward, the users approach to finding solutions should be considered.

@Mark.Ackerley What i was thinking, is that it would flatten the learning curve a bit and unlock creativity. Now you need to know the nodes first (hundreds) and have a goal for the graph. In the reorganized left pane option as mentioned above, you could go ahead and play a bit more.

I had a very simple suggestion a while back - add a bool flag that gets checked before the start of each individual node’s execution. That means that if a node is in execution (or stuck in an infinite loop) we can’t stop it and have to wait for it to finish processing (or kill revit/civil). However since we have clicked the the cancel button, prior to processing the next node we check the flag and if it’s true, stop the overall graph execution.

[Request for Feedback] Dynamo Node information

Request for Feedback

Marcel_Rijsmus August 13, 2020, 6:59pm 14

An option to reorganize all nodes in the left pane by input /output
(eg. give me all the nodes that take points as input)

[Request for Feedback] Language Preferences

Topic		Replies	Views
[Poll] Ask for what you need on right side panel Uncategorized	26	2803	November 20, 2019
[Request for Feedback] Gen-AI Assistant from Dynamo Team Request for Feedback dynamo , ai	29	3239	April 30, 2024
📢 Question for Dynamo 2.13+ Users! Request for Feedback	31	1561	July 12, 2023
[Request for Feedback] New Dynamo Library UI Request for Feedback	23	1686	March 17, 2015
UI refresh causing UX issues Uncategorized	23	873	February 8, 2024

[Request for Feedback] Dynamo Node information

Related topics