Skip to content
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

Closed
andydandy74 opened this issue Oct 18, 2015 · 8 comments
Closed

Wish: Visually identify optional inputs #5550

andydandy74 opened this issue Oct 18, 2015 · 8 comments
Assignees
Labels

Comments

@andydandy74
Copy link
Contributor

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.

@redinkinc
Copy link

+1

@Racel Racel added the UX Love label Oct 20, 2016
@Racel Racel self-assigned this Oct 20, 2016
@Racel
Copy link
Contributor

Racel commented Oct 20, 2016

@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.

@radumg
Copy link
Collaborator

radumg commented Feb 23, 2017

@Racel, perhaps instead of input port colors, text emphasis could be used :

  • black/bold = required (prominent)
  • grey = optional (subtle)

@smangarole
Copy link
Contributor

@Racel Can we get an update on this feature request?

@Racel
Copy link
Contributor

Racel commented Oct 2, 2017

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.

@johnpierson
Copy link
Member

Tracked internally as QNTM-5923

@johnpierson johnpierson added tracked and removed priority Related to a release. labels Nov 26, 2018
@Amoursol
Copy link
Contributor

@andydandy74 - This work is once again in-play.

@mmisol
Copy link
Collaborator

mmisol commented Feb 20, 2020

Fixed by #10361

@mmisol mmisol closed this as completed Feb 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

9 participants