You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My application allows the user to "push" the list the isotope layout uses either to the right or the left, wrapping the last or first element back to being the first or last respectively.
Here is what it looks like :
Unfortunately, if the user "pushes" the array too fast, the layout breaks and the visible array of elements are duplicated, even though the list managed by Vue.Isotope itself is still 20 items :
For now, the application works around this by debouncing the action of the user. It seems changing the possible timing of the changes done to the list allows the problem to be minified.
Still, when clicking to a certain rhythm, the same issue still occurs. I could nullify it entirely by setting an higher debounce limit, but this would hinder the user experience.
For reference, here's the push code :
The vue :
pushBack: function(){if(this.setupInit){letnewArray=utils.pushBack(this.tab);this.arrangeArray(newArray);}},arrangeArray: function(newArray){// It seems I must do that to trigger a change.// Else it will apply the new array without doing anything visuallythis.tab.splice(0,20);setTimeout(()=>{this.tab=newArray;// [...]},0);}
Hello !
My application allows the user to "push" the list the isotope layout uses either to the right or the left, wrapping the last or first element back to being the first or last respectively.
Here is what it looks like :
Unfortunately, if the user "pushes" the array too fast, the layout breaks and the visible array of elements are duplicated, even though the list managed by Vue.Isotope itself is still 20 items :
For now, the application works around this by debouncing the action of the user. It seems changing the possible timing of the changes done to the list allows the problem to be minified.
Still, when clicking to a certain rhythm, the same issue still occurs. I could nullify it entirely by setting an higher debounce limit, but this would hinder the user experience.
For reference, here's the push code :
The vue :
The utils :
Any help would be appreciated !
The text was updated successfully, but these errors were encountered: