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

Make configurations in remote and parameter nodes update values in linked controls #693

Open
rubberduck9999 opened this issue May 19, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@rubberduck9999
Copy link

Feature/enhancement description:
In this simple example I made a material with presets to choose from, let's say you have a preset "blue" to set the color to blue, which it does in the node itself, that is also driven by a linked control, so the "Material Color" setting should change to blue too.

This way I can define presets, but also use the other input fields to modify the values without the need to check, which values changed to what.

It could be even as a separate option (next to the 3 existing, linked control, configurations and named parameter) and could show a "*" when some values are changed next to the preset option
MM_presets

@rubberduck9999 rubberduck9999 added the enhancement New feature or request label May 19, 2024
@RodZill4
Copy link
Owner

I don't understand the difference between what you suggest and configuration parameters.

@rubberduck9999
Copy link
Author

yeah, the difference isn't really that much, the main thing is, that if I set it to a different preset / configuration, the values in the input field get updated too.
I made previously my own custom scratch generator (where I even extended the splatter node to have random x and y scale values). I have both parameters to set, but also setup some presets.

And the Idea I had there, is to show an "*" like in this image, if you changed some default values from linked parameters, though I think this is optional
grafik
In the case I change the preset, the values in the input fields are still the same, which is confusing when editing them, as it changes to something else, not representing the value of the preset which I may want to modify more or less
grafik

Though I think such presets could be even a separate feature, so that a user can quickly create own presets

scratches_v2.zip

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