i wonder how process associated nsoperation mainqueue doesn’t affect uitableview's scrolling.
the main reason of sluggish scroll in code each cell loading slow, because each cell has fetch images server. that’s why used create thread using gcd handle fetching process given each cell. meanwhile, main thread handles exclusively tableview’s scroll, i've understood ensure fast scrolling.
but, in recent days, i’ve noticed sample code using nsoperation. imitated part tableview cell loaded using nsoperation mainqueue. expected tax tableview’s scroll performance, because main thread handles both cell loading , tableview scrolling understand.
but, surprisingly, doesn’t. performance of both cell loading , tableview’s scrolling perfect. still wonder how can be.
i guess i’m either mistaken or miss something. let me know is?
all ios ui animations (including scrolling) performed on separate ui thread. long uitableview has required data (i.e. provide empty cell until image loaded) won't blocked sort of main thread activity.
execution of animations occurs on secondary thread avoid blocking current thread or application’s main thread.
Comments
Post a Comment