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

Performance issue in $scope.destroy() #34

Open
dejavu1987 opened this issue Jan 20, 2015 · 4 comments
Open

Performance issue in $scope.destroy() #34

dejavu1987 opened this issue Jan 20, 2015 · 4 comments

Comments

@dejavu1987
Copy link

Figured out that while angular tries to destroy the isotope directive scopes the relayout method is being triggered for every call of $scope.destroy(). Since every isotope element will be destroyed when you try to change the view eg. when you are navigating away form the route which is using the isotope directives.
This leads to relayout call equal to the number of elements that are currently visibile on the view.
I tried it with some 50 elements and it was already taking few seconds to complete the destroy+relayout process.
Is there a way to avoide this in angular?

there was a way around for non angular implementation. metafizzy/isotope#195
which did not work with the angular because it was $.remove() ing the elements which is not acceptable in angular.

thanx

@hydrotik
Copy link

👍

@carlosatta
Copy link

.

@carlosatta
Copy link

hi guys. any idea how to fix it?

@dejavu1987
Copy link
Author

I am assuming @hydrotik and @carlosatta already dumped angular :D

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

No branches or pull requests

3 participants