-
Notifications
You must be signed in to change notification settings - Fork 184
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
Row selection for the server-side processing mode #75
Comments
Finally I managed to make row selection work for the server-side processing mode as well. Please update DT from Github, and see Section 2.1: http://rstudio.github.io/DT/shiny.html |
@yihui Thanks for working on that, but the trick to do row selection by rowname doesn't really help with large tables when a user won't spend the time to click-select thousands of rows individually. In #50 I was expecting a fix that would make |
@ReportMort Unfortunately, you are right. That is not possible with I do have the row indices inside the server-side processing function, though: https://github.com/rstudio/DT/blob/master/R/shiny.R#L168 The problem is DataTables does not seem to allow me to pass these indices back to the client: http://datatables.net/manual/server-side |
@yihui I am curious to hear your thoughts about adding names to the filter input elements and then adding ChangeInput functions for when the values of those inputs change. Here is an example app I have working to show the filter inputted values and then parsing them to determine the server side row indices: https://reportmort.shinyapps.io/DT-filter-info/ It seems hacky, but wondering if you would be interested in adding more functionalities for the table inputs like this. Adding Names to Input Elements A Few Lines Where I Add ChangeInput for Each Filter Input |
@ReportMort That probably works, but is certainly inefficient, because you essentially did searching twice. What I would do is to check if it is possible to pass the row indices back from BTW, the search items are available as |
Moving @ReportMort's issue here from #50. Also mentioned by @frajuegies in #20.
The text was updated successfully, but these errors were encountered: