-
-
Notifications
You must be signed in to change notification settings - Fork 498
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
Support Tabulator scrollToRow #2485
Comments
I'm out on vacation this week but will work a little bit on Thursday to release Panel 0.12. If a PR to implement this were to magically appear before then I'd happily merge it and get it into this release :) |
First time I touch Javascript in ~14 years but I'll give that a shot, I guess it should not be too hard :) |
So as a starter I was contemplating scrolling to the currently selected row, like pn.widgets.DataFrame. I tried this:
In the little experiment with jscallback, everything works well, until I add Any idea on what is happening ? |
Scroll automatically to the selected rows when the selection is updated, just like the DataFrame widget. Closes holoviz#2485
Scroll automatically to the selected rows when the selection is updated, just like the DataFrame widget. Closes #2485 Co-authored-by: Douglas RAILLARD <[email protected]>
Is your feature request related to a problem? Please describe.
Being able to scroll inside the table programmatically is very useful when linking plots with custom interactivity with some tabular data.
Describe the solution you'd like
An API allowing to scroll to the given row, and possibly linked to a stream so that a holoviews plot X position can scroll directly in a table displayed under it.
Tabulator seems to already have support for scrolling programmatically:
http://tabulator.info/docs/4.1/navigation#scroll-row
Describe alternatives you've considered
pn.widgets.DataFrame() automatically scrolls when its "selection" attribute is modified. It would be nice to have a similar behavior for Tabulator.
EDIT: add alternative
The text was updated successfully, but these errors were encountered: