-
Notifications
You must be signed in to change notification settings - Fork 146
Strange behavior on drag cards when fetch a list of "cards" asynchronous #47
Comments
I am seeing the same behavior if the cards are loading in a different view and then you select the view with the cards. Not sure what the problem is. @mlynch can you talk a look at this? |
I am having the same issue when I do something like this |
My work arround is based on ng-if. Involves the element |
Can you elaborate as to what that looks like? Post some code? |
Follow the CodePen sample: http://codepen.io/anon/pen/LEjYeY |
Any updates on this issue? Was anyone able to get it working? |
I'm having the same issues. It seems that your work around ends up with the same glitches... Did you found anything else? |
I temporarily work around it by showing only one card at a time, keeping track of other 'card data' in another variable and adding a card to queue every time a card is swiped. And when the other queue reaches a certain threshold, I'll asynchronously retrieve more 'cards' from my server. The only downside is there isn't some sort of a 'shadow' of having multiple cards underneath. But I suppose that could be solve using some graphic/CSS. There is also minimal lag for the next card to show up. |
You mean having two cards in the collection? One to swipe and one underneath? |
I think this issue happens when you swipe two cards fast, not letting the animation to put the new card on the front to finish. If you swipe slow it seems to work always. Anyone can confirm? |
Ok, in my case I didn't have a proper on-destroyed handler, and it's seems that is needed. Now have some glitches but a lot fewer... |
When i start drag the card, he moves to the center.
Code Pen - http://codepen.io/anon/pen/dPRdPj
The only difference between in the example above and the original example, is a "timeout" simulating a call asynchronous to populate the list of cards.
The text was updated successfully, but these errors were encountered: