-
Notifications
You must be signed in to change notification settings - Fork 68
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
Scope Watch #3
Comments
My bad. That's not the actual problem. By using that event, it limits the items on first DOMReady event. Which means, if the items are to be modified after, it won't trigger relayout. I ended up setting-up timeout of 10ms to trigger relayout instead of relying on elem.ready event. Any suggestions? |
Yes, elem.ready is an option that can be removed once it generates no problem with back compatibilities, can you run some tests? |
@klederson how it the best way to achieve this from a Controller ? (not in angular-masonry-directive.js directly) Many thanks for your time and help. |
@klederson in the meantime I added to you directive and it works
|
Hi @gablabelle i think using events ( and firing it from masonry directive ) could be a nice way to do that, this scope.$watch will drain your performance. I'll try to find out more time to help on this but suggestions are welcome ) |
Is there any solutions for this? I need to keep loading my items until they are out of the viewport. |
Allow multiple masonry containers on one page
Hi there,
First of all, great work! I've been stuck with lots of other masonry alternative and trying to tying them to Angular. Yours worked just fine.
One thing I would add though. It doesn't have any scope monitoring that it couldn't update the layout once the data are updated.
The text was updated successfully, but these errors were encountered: