ErikUggeldahl 90c91f60af Support 16kb devices by bumping to NDK r27
As suggested by the docs, this is the best way to support newer devices requiring 16kb page support.

https://developer.android.com/guide/practices/page-sizes#compile-r27

- [x] Looking to see that Goldens pass before merging.

Diffs=
f653f3f73f Support 16kb devices by bumping to NDK r27 (#8558)
572265df3b call syncStyleChanges on update (#8715)
e8d6e5db26 Override layoutcomponent x/y using layoutX/Y (#8714)
d3f6a49778 Nnnn data bind fixes part 3 (#8663)
baf832a6ce Instance data converters when attached to data binding objects (#8664)
0664f994df Snap verycomplexgrad gm stops to pixel boundaries (#8685)
39c62a94ef ScrollBar constraint autosize toggle (#8707)
7c3c8a3a1a Don't use GL_PIXEL_UNPACK_BUFFER (#8708)
5df5be1940 Add "no_rive_jpeg" and "no_rive_png" build options (#8702)
d7794cb556 Improve scroll time precision on web (#8705)
d0c9e98d2e Scroll fixes (#8698)
ca10c9ec63 re add clean to diff (#8697)
f00a5a6c78 do not break when component is found (#8695)
437688c18e Add yoga renames to non-v2 lua build scripts (#8693)
423301a95b Fix integer precision issues with pathID in vertex shaders (#8689)
b1c0e80625 use draw proxy for scroll bar draggables (#8692)
302606642c GL fixes for Imagination PowerVR GPUs (#8684)
e5879a1a5c Fix scrollbar thumb offset (#8691)
7414d20597 Sort by % diff pixels in diff.py when histogram is equal (#8683)
00e9ad43a7 fix sorting hittable components (#8690)
fa8f7c6755 fix crash when dividing by 0 (#8687)
cd310b1b68 Nnnn scrolling override poc part 2 (#8679)
ac7c458bc7 Small Scroll fixes (#8682)
0ff13be381 Make scroll physics core objects (#8672)
9dfd01fb3a made compatable with python 9_9 (#8678)
454bc50aaf diff.py: don't count identicals as differences (#8666)
c642488df3 added some changes to make building easier for unreal (#8667)
1647a7ad92 use actual sizes for calculating position offset (#8671)
599ab0eeb7 Reapply "Merge branch 'master' of https://github.com/rive-app/rive"
406a2ef952 Revert "Merge branch 'master' of https://github.com/rive-app/rive"
3c0cc1f329 skip object on animation reset if it is null (#8670)
1d2c9175d4 remove letter spacing subtraction (#8669)
96ec927371 fix fatal warnings compiler flag to use latest version (#8668)

Co-authored-by: Erik <erik@rive.app>
2024-12-10 03:09:42 +00:00
2024-09-04 09:24:54 +00:00
2023-07-06 08:49:14 +00:00
2024-11-27 19:17:23 +00:00
2022-11-15 23:07:11 +00:00
2024-07-25 22:33:33 +00:00
2022-11-15 23:07:11 +00:00
2022-11-15 23:07:11 +00:00
2022-11-15 23:07:11 +00:00
2024-04-05 21:34:08 +00:00
2020-07-08 16:36:55 -07:00
2024-06-17 09:08:46 +00:00
2024-03-01 22:45:42 +00:00
2022-06-16 15:51:45 -07:00

Pub Version Build Status Discord badge Twitter handle

Rive Flutter

Rive hero image

Rive Flutter is a runtime library for Rive, a real-time interactive design and animation tool.

This library allows you to fully control Rive files with a high-level API for simple interactions and animations, as well as a low-level API for creating custom render loops for multiple artboards, animations, and state machines in a single canvas.

Table of contents

Overview of Rive

Rive is a powerful tool that helps teams create and run interactive animations for apps, games, and websites. Designers and developers can use the collaborative editor to create motion graphics that respond to different states and user inputs, and then use the lightweight open-source runtime libraries, like Rive Flutter, to load their animations into their projects.

For more information, check out the following resources:

🏡 Homepage

📘 General help docs

🛠 Rive Forums

Getting started

To get started with Rive Flutter, check out the following resources:

For more information, see the Runtime sections of the Rive help documentation:

More advanced usage:

Choosing a Renderer

For more information see: https://rive.app/community/doc/overview/docD20dU9Rod

Note on the Impeller renderer

Starting in Flutter v3.10, Impeller has replaced Skia to become the default renderer for apps on the iOS platform and may continue to be the default on future platforms over time. As such, there is a possibility of rendering and performance discrepancies when using the Rive Flutter runtime with platforms that use the Impeller renderer that may not have surfaced before. If you encounter any visual or performance errors at runtime compared to expected behavior in the Rive editor, we recommend trying the following steps to triage:

  1. Try running the Flutter app with the --no-enable-impeller flag to use the Skia renderer. If the visual discrepancy does not show when using Skia, it may be a rendering bug on Impeller. However, before raising a bug with the Flutter team, try the second point below👇
flutter run --no-enable-impeller
  1. Try running the Flutter app on the latest master channel. It is possible that visual bugs may be resolved on the latest Flutter commits, but not yet released in the beta or stable channel.
  2. If you are still seeing visual discrepancies with just the Impeller renderer on the latest master branch, we recommend raising a detailed issue to the Flutter Github repo with a reproducible example, and other relevant details that can help the team debug any possible issues that may be present.

Supported platforms

Be sure to read the platform specific considerations for the Rive Flutter package.

Awesome Rive

For even more examples and resources on using Rive at runtime or in other tools, checkout the awesome-rive repo.

Contributing

We love contributions and all are welcome! 💙

Issues

Have an issue with using the runtime, or want to suggest a feature/API to help make your development life better? Log an issue in our issues tab! You can also browse older issues and discussion threads there to see solutions that may have worked for common problems.

Description
Flutter的Rive解决方案
Readme MIT 16 MiB
Languages
Dart 96.8%
C++ 1.3%
Lua 0.7%
CMake 0.6%
Shell 0.2%
Other 0.2%