-
Notifications
You must be signed in to change notification settings - Fork 481
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
New Widget: Slider #5208
base: develop
Are you sure you want to change the base?
New Widget: Slider #5208
Conversation
This is just like Range_Slider except that it has only one slider bar.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
don't forget a changelog entry (in the Lua section)!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is cleaner, but not quite clean enough. The RangeSlider attributes are still visible in Slider, but are useless, which leads to a confusing API.
I think both RangeSlider and Slider should inherit from a base class that holds the common logic, keeping the externally visible ATTRS clean for both classes.
|
||
This widget implements a mouse-interactable slider. The player can move the handle to | ||
set the value of the slider. The parent widget owns the slider value, and can control | ||
it independently (e.g., with ``CycleHotkeyLabels``). If the value changes, the ``Slider`` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it independently (e.g., with ``CycleHotkeyLabels``). If the value changes, the ``Slider`` | |
it independently (e.g., with a ``CycleHotkeyLabel``). If the value changes, the ``Slider`` |
This is just like Range_Slider except that it has only one slider bar.