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
{{ message }}
This repository has been archived by the owner on Nov 18, 2024. It is now read-only.
Currently, the native rendering processes in this package are executed synchronously on the main thread, which can cause performance issues and potential UI freezes, especially when swiping through multiple pages using the ListView.builder example from the README file. Is it possible to make the rendering processes asynchronous and execute them in a separate thread for at least both Android and iOS? I think it is possible to return the rendering result to the method channel from the new thread, so it should be no big deal to change the source code for this, or am I missing something?
The text was updated successfully, but these errors were encountered:
Currently, the native rendering processes in this package are executed synchronously on the main thread, which can cause performance issues and potential UI freezes, especially when swiping through multiple pages using the ListView.builder example from the README file. Is it possible to make the rendering processes asynchronous and execute them in a separate thread for at least both Android and iOS? I think it is possible to return the rendering result to the method channel from the new thread, so it should be no big deal to change the source code for this, or am I missing something?
The text was updated successfully, but these errors were encountered: