Skip to content
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

Implement UI-Grid Infinite Scroll #949

Closed
jkmarx opened this issue Mar 14, 2016 · 4 comments · Fixed by #987
Closed

Implement UI-Grid Infinite Scroll #949

jkmarx opened this issue Mar 14, 2016 · 4 comments · Fixed by #987

Comments

@jkmarx
Copy link
Member

jkmarx commented Mar 14, 2016

In the angular data-set view, implement ui-grid infinite scroll.
http://ui-grid.info/docs/#/tutorial/212_infinite_scroll

@jkmarx
Copy link
Member Author

jkmarx commented Mar 14, 2016

@jkmarx jkmarx modified the milestones: Quincy, Next, Randolph Mar 18, 2016
@jkmarx
Copy link
Member Author

jkmarx commented Mar 22, 2016

"Avoid jumpy appearance, you can explicitly save the scroll position before you add data to your data array, through calling saveScrollPercentage, and the dataLoaded call will then take that position into account, and attempt to adjust the scroll so that the same rows are showing once the grid has ingested the data you have added."

@jkmarx
Copy link
Member Author

jkmarx commented Mar 22, 2016

"If you are using external sorting or external filtering you may reload your data whenever scroll or filter events occur. In this situation you'll want to call resetScroll to tell the grid not to try to preserve the previous scroll position. "

@jkmarx
Copy link
Member Author

jkmarx commented Mar 30, 2016

The bug was due to the routing and tabs. The ui-grid was being initialized twice, so there were two grids in the scope causing issues. To correct it, the default address for dataset2 is http://192.168.50.50:8000/data_sets2/uuid/#/files/browse. http://192.168.50.50:8000/data_sets2/uuid/# will reroute to the above address. http://192.168.50.50:8000/data_sets/uuid/#/ is fine though for the meanwhile.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant