-
Notifications
You must be signed in to change notification settings - Fork 636
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wish: Visually identify optional inputs #5550
Comments
+1 |
@andydandy74 - Assigning different color to input nodes might be difficult as we are already starting to use input port colors to signify different things. Maybe we can do some other affordance, like an asterisk or italicized text. In any case, adding to UX Love backlog. |
@Racel, perhaps instead of input port colors, text emphasis could be used :
|
@Racel Can we get an update on this feature request? |
I also think that this will be a nice feature to have. Since this is a minor UI change, I believe we should consider for 2.0. This has been filed in our UX Love board and will be discussed as to whether or not it makes it in to the release. |
Tracked internally as QNTM-5923 |
@andydandy74 - This work is once again in-play. |
Fixed by #10361 |
It would be helpful if node input ports that have a default value assigned to them had a different color/grayscale. That way one could immediately see that it is not necessary to connect anything to them.
The text was updated successfully, but these errors were encountered: