Skip to content
This repository has been archived by the owner on Feb 21, 2025. It is now read-only.

Way to specify input metadata #22

Open
SirVeggie opened this issue Jul 24, 2024 · 1 comment
Open

Way to specify input metadata #22

SirVeggie opened this issue Jul 24, 2024 · 1 comment

Comments

@SirVeggie
Copy link

Currently there's no way to specify input options (except default). Mainly I'm after being able to set {forceInput: True} on an input, but other options would be a nice to have as well. Currently I can kind of force and input to appear as a slot by using the default node, but then that input slot is optional.

@SirVeggie
Copy link
Author

To add on to this, I'm currently having a problem where I'm connecting an input to two different nodes, but I can't choose which one it'll use as a basis for the widget. I want the node that has a 0-1 float values to act as the widget, but no matter in which order I connect them in, it always chooses the other node where the widget has a 0.5 step, making the widget very difficult to use.

I had to make a custom node with the correct widget settings that just reroutes the float...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant