-
Notifications
You must be signed in to change notification settings - Fork 8
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
Interactive slicer example #48
Conversation
- uses input fields to both display and change slider position - uses three viewers for volume
also unhide the sliders
Nice! Looking good, and nicely commented so its easy to follow along. Could you also add a docstring at the top to briefly explain the purpose of the example? CI is stuck on formatting. Run |
ok, I added a short comment at the start. The file was already run through black before, I removed some unused imports now.
|
Probably a different version of black. It's annoying :/ |
One thing I just thought of while implementing this in my own app: why do we even need the secondary slider here? can't we just listen directly for the "drag_value" event from the "builtin" slider? That should also break the circularity, no? |
Yeah, either listening to I thought that the extra slider was a deliberate thing to show that it can be done :P |
Ah, good point. Yeah let's say that was the intention :). I think it does serve that purpose (to see the difference between drag and mouse-up). |
Yeah, but perhaps still better to remove it, since users won't be able to run the example otherwise, until a new dcc is released (and the users upgrade). |
I just ran black on the code. Let's merge this as-is. We can always remove the sliders later if needed. This example is really nice! |
small example that shows how to link three slicers to an interactive table-like element that both displays the current slicer positions and allows user input to change them.
verbose labeling