We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Native application could leverage threading feature.
Currently, thorvg.flutter initializes with 0 config, which means this won't thread.
0
We might need to check to use thread.
explicit TvgLottieAnimation() { errorMsg = NoError; // No threading if (Initializer::init(CanvasEngine::Sw, 0) != Result::Success) { errorMsg = "init() fail"; return; } canvas = SwCanvas::gen(); if (!canvas) errorMsg = "Invalid canvas"; animation = Animation::gen(); if (!animation) errorMsg = "Invalid animation"; }
We can drive Widget parameters for user so they can decided how many thread they want to enable. Something like this:
Lottie.network( 'https://lottie.host/6d7dd6e2-ab92-4e98-826a-2f8430768886/NGnHQ6brWA.json', renderConfig: RenderConfig( threads: 4 ) ),
The text was updated successfully, but these errors were encountered:
@tinyjin Suggest the default thread as 4.
Sorry, something went wrong.
No branches or pull requests
Native application could leverage threading feature.
Currently, thorvg.flutter initializes with
0
config, which means this won't thread.We might need to check to use thread.
We can drive Widget parameters for user so they can decided how many thread they want to enable.
Something like this:
The text was updated successfully, but these errors were encountered: