-
Notifications
You must be signed in to change notification settings - Fork 171
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
[Feature Request]: Remove hidden "Advanced Widgets" #2240
Comments
@pythongosssss Can you take a look at this issue? We might want to drop the support for group node if we have subgraph planned on the horizon. In case it's too much effort to fix the group node. |
The issue is solved if the widget isn't hidden. If I knew the widget was there, I would have noticed the incorrect value. It's difficult to debug something you can't see! |
Can you describe the issue that occurred? I don't fully understand. |
This 'feature' is really unneeded If you think it has future applications (currently, it only exists on CLIP loaders), then make a symbol or something with tooltip to indicate there are Advanced widgets hidden. An off-the-cuff suggestion: the top-left minimize button could be a tri-state toggle; fully minimized, show partial, show all. One could right-click a widget and toggle it only shown in "show all". (the nomenclature could be better lol) |
This would be more useful if we could select the widgets we want to hide.
I agree, we could have a tri-state button, when there are hidden widgets. |
I agree with this. |
This feature is unrelated to group nodes and was explicitly asked for by multiple developers in order to hide widgets that users should rarely need to interact with. The initial design was a tri-state indicator for it however it was deemed to be overly complex for the feature. Edit: 2024-03-firefox_TZGCERHJFB.webm |
It looks great ! On a side note, the |
Is there an existing issue for this?
What would your feature do ?
Node Widgets should not be hidden by default.
Proposed workflow
n/a
Additional information
No response
┆Issue is synchronized with this Notion page by Unito
The text was updated successfully, but these errors were encountered: