-
Notifications
You must be signed in to change notification settings - Fork 208
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
Revise appearance of enable/disable for node parameters #65
Comments
Top option is the pick.
|
bentoogood
pushed a commit
that referenced
this issue
Sep 24, 2013
* for use with compound plugs that have an enable/disable toggle * contributes to #65 * new icons labeled "toggleOn", "toggleOnHover" "toggleOff" "toggleOffHover" * no disabled modes - can be added if required
icons are in, over to John to add new widget type. |
Thanks Ben - my plan is to rename GafferUI.CheckBox to GafferUI.BoolWidget and then add methods to control the appearance (switch/checkbox). I'll keep CheckBox around as an alias to BoolWidget to provide backwards compatibility for a bit though. Sound OK? |
sounds fine to me. |
lucienfostier
referenced
this issue
in lucienfostier/gaffer
Apr 4, 2017
lucienfostier
referenced
this issue
in lucienfostier/gaffer
Apr 7, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The enable/disable mechanism could be a little confusing to users, especially for bool params where the enable/disable toggle has the same appearance as the value toggle.
Also - as some params have enable/disable and some don't, how best can we communicate its use?
The text was updated successfully, but these errors were encountered: