Skip to content

Collapsable grouping is awkward when using paging. #21

Open
@GoogleCodeExporter

Description

@GoogleCodeExporter
What steps will reproduce the problem?
1. use datatable plugin with pagination.
2. use rowGrouping plugin on the above datatable.
3. collapse a group that spans many pages.

What is the expected output? What do you see instead?
the group collapses but you still have to page thru all the original pages 
event though they are empty.

What version of the product are you using? On what operating system?
1.1.6

Please provide any additional information below.

I understand that by changing the collapsed entries to display non is the 
reason it behaves this way.

I modified the plugin to not hide the rows but filter them out.  
I attached a filtering function to the datatable plugin.  It filters out the 
rows that have collapsed groups. 
I modifed the click routine to not hide the rows but invoke the table draw 
function.

These were the easy parts.

I had to modify the draw routine to figure out which groups were collapsed and 
add the proper collapsed rows.  That took a bit of doing.

I do not use it in the mode of calling a server side routine for each page.  It 
may break completely in that scenario.

I call a server side routine to bring all my rows at once and then call the 
datatable plugin sending it the json data.

Attached is the modified plugin.


Original issue reported on code.google.com by The.Bob....@gmail.com on 16 Mar 2012 at 7:28

Attachments:

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions