1.0-rc stable #173
Replies: 7 comments 6 replies
-
It works great ! But can you also add step size ? This really improves the slider usability.
|
Beta Was this translation helpful? Give feedback.
-
|
mockup:
|
Beta Was this translation helpful? Give feedback.
-
|
Happy to tweak the layout if there is general agreement. |
Beta Was this translation helpful? Give feedback.
-
|
Using just I just start scrolling over an image, a text box, or a header, and it does not interfere with the sliders. But, you could add an user setting to use |
Beta Was this translation helpful? Give feedback.
-
|
Not trivial to control how the column scroll responds, so...
|
Beta Was this translation helpful? Give feedback.
-
When I suggested using scroll for sliders, I was thinking about using it to move by 1 single step. Can you add an extra option to this list: This, together with step size editing, would be a great combination !
|
Beta Was this translation helpful? Give feedback.
-
|
Gone away. Just uses step size. |
Beta Was this translation helpful? Give feedback.
-
|
Also about slider editing, with the old mechanism gone, we've lost the ability to apply settings to multiple sliders. For instance, I want the same ranges in all my Is your original idea still possible, in future versions ?
|
Beta Was this translation helpful? Give feedback.
-
|
I intend to add an option “apply to all [nodetype]”, probably as a checkbox
in the edit panel.
…On Mon, 21 Oct 2024 at 9:24 PM, JorgeR81 ***@***.***> wrote:
Also about slider editing, with the old mechanism gone, we've lost the
ability to apply settings to multiple sliders
Can you apply changes we make, in this new editing GUI, per "node type",
instead ?
For instance, I want the same ranges in all my 'Apply ControlNet` nodes.
I want the max. strength value to be 1 ( or maybe 2 ) but not 10.
This is the most sensible option.
I think it's the behavior that people is expecting.
If you have this, we don't need other options in this editing GUI.
—
Reply to this email directly, view it on GitHub
<#173 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABBLMAYIFYOYPM7DBBFWYEDZ4TI6FAVCNFSM6AAAAABQJEVNQGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMBQGM4DANA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Yeah, that would also work, and it's simpler. |
Beta Was this translation helpful? Give feedback.
-
|
Checkbox only appears if there are other nodes of the same type. |
Beta Was this translation helpful? Give feedback.
-
|
Plan for RC2: Make scroll wheel single step Add step size to slider edit Add "apply to all [type] nodes to edit" Visual tweaks in 174-178 Add images to documentation |
Beta Was this translation helpful? Give feedback.
-
|
rc2 now stable. Discussion should move to #183 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
See https://github.com/chrisgoringe/cg-controller/milestone/10 for issues and features.
The big one... min/max editing is now live. shift-click a slider to bring up the dialog.
And as a little bonus, you can now also adjust slider values with the scrollwheel when hovering. There are four sensitivity levels in the settings.
If you copy-paste a node, or clone it, or duplicate it in any other way, the new node should have all the settings of the old one (heights, minimised, min/maxes).
Note that (as previously mentioned) there is a backward compatibility break: previously saved workflows will have lost their widget heights, and the old min/max setting mechanism is gone.
I'll leave the code untouched for the next 24-48 hours (unless there are critical fixes), while I do some documentation (so that should be steadily updated over the next couple of days).
Beta Was this translation helpful? Give feedback.
All reactions