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
Currently when options like item sizes are changed I have to somehow force the component to redraw. It seems that emitting the options itself is not enough to trigger any sort of redraw.
If I only emit options they seem to only take effect as I scroll through the items and the rows are updated.
For now I'm emitting an empty array and then right after that the data array, this seems to make it redraw but it feels messy.
Hi @ktersius, yeah, this is an issue I am aware of and I will look into it. The reason I did not implement it in the first place is that I was unsure, whether it could harm the performance or not.
But as there seems to be a use case, I will evaluate the practicability.
Thanks!
data$=newSubject<number[]>();change(){// use this to force redrawthis.data$.next([]);this.data$.next(newArray(100).fill(0).map(x=>Math.floor(Math.random()*1000)));}
Yeah thanks. But it's still something, which needs to be addressed in future. I hope I will find some time for another maintenance/feature request round.
Currently when options like item sizes are changed I have to somehow force the component to redraw. It seems that emitting the options itself is not enough to trigger any sort of redraw.
If I only emit options they seem to only take effect as I scroll through the items and the rows are updated.
For now I'm emitting an empty array and then right after that the data array, this seems to make it redraw but it feels messy.
The text was updated successfully, but these errors were encountered: