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, i met a problem, need to get your help, which is like title said.
The scene is, i have more than 400 cell nodes in my ASTableNode, and each cell node refers to one network request, when the network request finished, the cell node would be reload or delete from this ASTableNode, of course, i just update those cell nodes in visible area. And now, anyway, i need to update cell nodes multiple times in short time, and the main thread is blocked.
Screenshot is like blow:
From the screenshot, dispatch_group_wait(_editingTransactionGroup, DISPATCH_TIME_FOREVER); matters.
That is, if last update (reloadRow、deleteRow or reloadData) did not end, the current update would sleep to wait until the main thread has spare time to handle.
Anyone had same problem? I am really confused. Thanks for any coming support.
The text was updated successfully, but these errors were encountered:
Hi, i met a problem, need to get your help, which is like title said.

The scene is, i have more than 400 cell nodes in my
ASTableNode
, and eachcell node
refers to one network request, when the network request finished, thecell node
would bereload
ordelete
from thisASTableNode
, of course, i just update those cell nodes in visible area. And now, anyway, i need to update cell nodes multiple times in short time, and the main thread is blocked.Screenshot is like blow:
From the screenshot,
dispatch_group_wait(_editingTransactionGroup, DISPATCH_TIME_FOREVER);
matters.That is, if last update (
reloadRow
、deleteRow
orreloadData
) did not end, the current update would sleep to wait until the main thread has spare time to handle.Anyone had same problem? I am really confused. Thanks for any coming support.
The text was updated successfully, but these errors were encountered: