Skip to content

[Feature Request]: Allow overriding step and/or min/max values for numbers #594

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

Open
1 task done
asagi4 opened this issue Aug 22, 2024 · 1 comment
Open
1 task done
Labels
enhancement New feature or request

Comments

@asagi4
Copy link

asagi4 commented Aug 22, 2024

Is there an existing issue for this?

  • I have searched the existing issues and checked the recent builds/commits

What would your feature do ?

Number value ranges and step should be overrideable per node from the UI; the backend does not enforce them anyway.

Sometimes it's useful to override the step value configured for a node. For example, often a step of 0.001 is too small, which makes the value difficult to control and using a coarser step would make the user experience better.

Sometimes nodes also specify min and max values that are either too restrictive or too broad in range, leading to the same problem as with too small step sizes; users should be allowed to override them.

Proposed workflow

I do not really have a preference for how this should be implemented. Perhaps the existing "properties" facility can be used somehow.

Additional information

This feature would become even more useful once there's some alternative to noodle soup and you can actually build nicer UIs for workflows.

@asagi4 asagi4 added the enhancement New feature or request label Aug 22, 2024
@doctorpangloss
Copy link

some interfaces like unity, maya let you specify the stepping size for spinners.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants