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
Hi,
Is it normal for this package that all grid items gets rebuilt when dragging a single item? (even when just hovering in place without actually reordering anything).
My app takes a major performance hit because of this.
I would expect that the items won't get rebuilt but only their transform would be changed.
Is there any way to optimize this?
Thanks
The text was updated successfully, but these errors were encountered:
Hey,
do you have some more data about what unexpected rebuilds are happening? when dragging an item, all items will have to recalculate their position and constraints.
Hey @casvanluijtelaar,
Should it really rebuild All items? I think an optimization could really improve this package - so it would know which items needs rebuilding lazily.
For example I have a grid of 2 items in a row, when ordering an item in the first row to the second position in the same row, not all items needs rebuilding, but just the two items in the first row..
maybe probably, but right now these items need to recalculate their position to know if they should move or not. if you have suggestions, I'd love to hear them!
Does the item need to rebuild even if it's position is not changed?
Every finger movement causes a rebuild for all items. I think maybe a check if the position is changed then the item needs to be rebuilt. Don't know if it's possible though.
Hi,
Is it normal for this package that all grid items gets rebuilt when dragging a single item? (even when just hovering in place without actually reordering anything).
My app takes a major performance hit because of this.
I would expect that the items won't get rebuilt but only their transform would be changed.
Is there any way to optimize this?
Thanks
The text was updated successfully, but these errors were encountered: